river-runner
New member
I could not get the contacts to load into my brand new $950 USD Nav 6. Just got off the phone with Garmin, seemed like the Garmin rep knew the product well - good guy.
Garmin says the reason my contacts would not load on to my NAV 6 was that my contact list in my Samsung S-4 is too large at 900 contacts. Rep says the maximum you can load is around 200 contacts. Rep also says it could take up to 20-minutes to load 200 contacts via bluetooth and that once the bluetooth connection is stopped, the NAV 6 loses all the contacts and needs to reload contacts again from the start with your next ride....after the 20-minute load delay.
This seems to be a little different reason for the contacts not loading than I have seen here to date. At least the Garmin Guy provided a plausible reason versus it just won't work.
1) 200 contact limit,
2) long load time due to bluetooth, up to 20-minutes,
3) (This one blows me away) contacts lost to Nav 6 when bluetooth connection is terminated, then must load again from scratch the next time you want to use contact list.
I don't see a workaround to this problem for me. Darn........
Garmin says the reason my contacts would not load on to my NAV 6 was that my contact list in my Samsung S-4 is too large at 900 contacts. Rep says the maximum you can load is around 200 contacts. Rep also says it could take up to 20-minutes to load 200 contacts via bluetooth and that once the bluetooth connection is stopped, the NAV 6 loses all the contacts and needs to reload contacts again from the start with your next ride....after the 20-minute load delay.
This seems to be a little different reason for the contacts not loading than I have seen here to date. At least the Garmin Guy provided a plausible reason versus it just won't work.
1) 200 contact limit,
2) long load time due to bluetooth, up to 20-minutes,
3) (This one blows me away) contacts lost to Nav 6 when bluetooth connection is terminated, then must load again from scratch the next time you want to use contact list.
I don't see a workaround to this problem for me. Darn........