In my own case it don't work.

It's impossible to pair the MX4 (OTA-10.1) to "Nissan Connect"
bluetooth. Also, it's now impossible to forget the "Nissan Connect"
paired before. The "forget" button isn't cliccable (see pictures
attached).

You can find my bluetooth log file (with OTA-9) attached at the message
number 22 (
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/22
).

If needed, I can prepare a new log file.

** Attachment added: "MX4_bluetooth_car_pair_problem.zip"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4635443/+files/MX4_bluetooth_car_pair_problem.zip

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "0000" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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

Reply via email to