Hi Konrad, the problem was that my bluetooth is turned off :D :D Now I'm able to remove the NISSAN CONNECT device
[bluetooth]# remove 60:38:0E:59:32:39 [DEL] Device 60:38:0E:59:32:39 NISSAN CONNECT Device has been removed Now I will try to pair it again. Thank you, Marco Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto: > Marco, > > this is super strange, I will think of possible solutions however in > the meantime what is the output from > > info 60:38:0E:59:32:39 > > Thanks, > K > > On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti > <graziottima...@gmail.com <mailto:graziottima...@gmail.com>> wrote: > > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this > error: "*Failed to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39** > **Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: >> 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 a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp