Bluetooth cannot be activated on several devices

seems to be solved in the most recent update. I would love to add a log but i have no idea where i can find that. so heres just a screenshot of the devices showing up now

Bluetooth on = not discoverable

Bluetooth off = discoverable

Bluetooth off = discoverable

The images show that in neither case is the Bluetooth indicator shown in the top panel

Cannot reproduce on any other devices, could be specific to the N7 or the current state of the specific device.

I am (I think) able to observe the slider behaviour referenced in the
bug on my N7, running r329. My device initially discoverable, even when
the slider reverts to "off" by itself. Shortly after (maybe a few
minutes later), the N7 is no longer discoverable and turning the slider
back to "on" has no effect. And, if I wait a few more minutes, I can
once again make the device discoverable with the slider.

Checkbox output attached.

I can confirm this affects rc proposed r332.

Problem persists with r334

I can confirm that the Nexus 4 isn't affected. Seems isolated to the Nexus 7.

some more information: Bluetooth only appears being off in the indicator and the settings. It is, in fact on and working just fine.

This screenshot was taken while a Bluetooth keyboard was connected and functional: http://i.imgur.com/EIUnG9n.png

Note the hciconfig output in the terminal. It shows that it is up and running, and even doing the inquiry as instructed by the systemsettings app. It's just that the app and indicator think its off.

I've experienced this before and was fixed I think when bluez5 landed.
However I experience it again sometimes in the recent rc-proposed images.
A couple of reboots fix the issue though.

Other users who experience the problem suggest that reboots fix the issue.
That doesn't seem to work for me.

It has been confirmed that bluetooth does work just the ui is broken so I
will try to connect a device using terminal.

Thanks,

Dan

On Tuesday, 12 January 2016 15:08:44 UTC, Kugi Eusebio wrote:
> I've experienced this before and was fixed I think when bluez5 landed.
> However I experience it again sometimes in the recent rc-proposed images.
> A couple of reboots fix the issue though.
>

--
Sent using Dekko from my Ubuntu device

Status changed to 'Confirmed' because the bug affects multiple users.

Adding my experience to comment #12, reboots will sometimes fix the issue, but anecdotally I'd estimate the frequency at 10%. (i.e. one in ten reboots clears it.)

fwiw, my current workflow to workaround this is to log onto the device shell and "restart indicator-bluetooth"
the list of available devices always instantly appears.

I'm seeing similar buggy behavior with the indicator on a Xenial desktop with bluez 5.36 and indicator-bluetooth 0.0.6+15.10.20150929-0ubuntu1 installed.

Pat, this problem also affects the nexus 4 I believe.

I confirm that this bug also happens in mako.

current build number: 355
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu

Definitely happens on mako using the -pd image (r127) which renders it completely useless as a -pd image.

This also occurs on frieza, OEM bug: #1534318

Additional OEM bug that's probably a dupe: bug #1544084

I think there is an indicator-datetime issue herer wrt the on/off toggle in the indicator, but there is also a separate issue with the Discoverable / Not Discoverable status being shown in system-settings. indicator-bluetooth doesn't advertise that state; system-settings is getting that from talking to bluez.

My bq 4.5 does not seem to have this problem in normal usage, so here's how I managed to reproduce it:

1) disable autostart of the bluetooth daemon:
$ echo "manual" | sudo tee /etc/init/bluetooth.override

2) reboot your phone

3) wait until everything is loaded, then run:
$ sudo start bluetooth

After that, the on/off switch in indicator and system settings don't seem to match each other, just like described above in the bug.
Also, the bluetooth connection seems to be independent of changes to the switches, since it keeps being discoverable for other devices even any or both of those switches are off.

BlueZ will react either on the "Powered" property of its org.bluez.Adapter1 interface being switch (false/true) or the bluetooth rfkill being changed. If none of both happen the Bluetooth power status will not change and the device will be kept discoverable if the "Discoverable" property was set to true from settings.

Is the linked branch believed to be a fix, or simply part of the puzzle?

This in silo 79

(which worked for me on my frieza device -and seems to fix this bug)

Maybe some of the issues here are a duplicate of bug #1546137 ?

Hi all;

This issue is still reproducible in r6 firmware version, I attached a new record with the actual result.

Please, check it.

Thank you.

Hello all,

 Using ths DUT at least 20 minutes, then trying to turn on the BT. DUT cannot turning on by itself, user need to reboot the DUT to be able to connect any BT device.

Fw: Ubuntu 15.04 (r10)

I think it will be helpful to have a short new bug for this discussion, so I've opened: bug #1587366. Please continue the discussion there.

Reopening for workitem found by dobey to see if https://code.launchpad.net/~morphis/indicator-bluetooth/fix-lp1530807/+merge/290022 should still be landed