I have seen many notes concerning the hit and miss performance of loading phonebooks and call lists when connecting a mobile phone to a Garmin GPS.
Nobody seems to be able to bypass the 'get rid of you' answer, ' We will tell the development team'.
However I have found that there is a way to increase the reliability of the bluetooth connection with respect to phonebook loading.
Incidently I have asked the question as to why Garmin cannot load the phonebook of any phone and burn it into flash memory and therefore
there would be no need to repeatedly load this data from the phone. But as usual the Support comment is 'We will tell the development team',
and as usual nothing happens. How many phones do Garmin think a user needs to use with the GPS ? Even if it was 2 or 3 you could share
the pre-loaded phonebook or select another phonebook and also have an edit facility in the GPS, (another lacking feature).
In these days of fines for phoning while driving the phonebook in the GPS is quite important.
Anyway here's what works for me :-
GPS = Garmin 1490T, Phone = HTC Desire C.
1. Make sure the GPS and phone are paired.
2. Disable the Bluetooth on the phone.
3. Switch on and let the GPS boot up.
4. When the GPS has settled enable the phone Bluetooth.
5. Go to Settings on the phone and select Bluetooth.
6. You should see a list of paired devices - select the Nuvi GPS.
7. The phone will then make the connection to the GPS and say 'connected' when finished.
8. The phone icon should appear on the Nuvi.
9. Wait for a while for the phone to send the phonebook and call data to the Nuvi, (approx 2-3 minutes).
10. Press the phone icon on the Nuvi screen and check that the phonebook has loaded.
ALSO !
When disconnecting from the GPS reverse the above process by turning off the phone Bluetooth
at which point the phone icon on the Nuvi should disappear.
It appears that the Nuvi code section that asks the phone for data is not always entered when connecting the phone or the Nuvi.
Putting the phone in charge of making the connection appears to force the Garmin to enter this code section.
Anyway Good Luck !:cool: