Comment 76 for bug 1539158

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 <email address hidden>
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
>
>
>
>