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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1435040

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to