Comment 174 for bug 1435040
Revision history for this message
| Mons ter Wade (monsterwade) wrote | #174 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Update/Correction #171 & #172
In the meantime I drove 1300 km. I think I now fully understand what is and was going on.
After connecting like in #171 & 172 described, I had 4 phone calls on a 600 km trip. 2 times bluez crashed (had to reboot phone) and I wasn't able to update the phonebook in the car system.
So I enabled ‘autoconnect’ in the bluetooth settings on the phone and tried to connect again from the car system. Tatataaa ... on my way back no crashes during phone calls and updating the phonebook now always worked.
What happened? It turned out that I myself messed up the bluetooth connecting process with my impatience. As soon as the car system showed the bluetooth sign and my mobile service provider, I started playing around on both ends (car system & phone). But at this point the connecting process was not completely finished and I fooling around at the same time finally caused crashes on both systems.
I just have to wait like another 10-20 s and everything works perfectly. In my case the connection process is finished when the media player sign shows up in the cars display.
Everything works now as intended, if ‘autoconnect’ is enabled and the car starts the connecting process. Turn on phones bluetooth, get in the car, wait until the car establishes the connection COMPLETELY and enjoy! Nothing else has to be done.