Hellow Konrad: I enable the developer mode, connect the phone to the computer and write adb shell in a terminal. It shows this:
c@C:~$ adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device not found c@C:~$ I don't know how to continue. Cheers, Cesar ---------------------------------------- > Date: Thu, 28 Jul 2016 08:54:41 +0000 > From: konrad.zapalow...@canonical.com > To: c...@outlook.es > Subject: [Bug 1539158] Re: Unable to pair with in-car hands-free system after > OTA-9 update > > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > > -- > You received this bug notification because you are subscribed to the bug > report. > 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: > Confirmed > 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 -- 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: Confirmed 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