Bluetooth cannot be enabled on Ubuntu Touch rc-proposed Nexus 4

Bug #1531515 reported by Willem Ligtenberg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After switching from OTA8.5 to rc-proposed (to test if my BT keyboard would work with that) BT cannot be turned on any more.
I can flip the switch, but after 30s it is switched off again (probably never turned on).
I am unable to discover any BT devices.

Running bluetoothctl on the devices from the terminal and then entering "show" results in:
"No default controller available"

I switched to rc-proposed for the Nexus 4 like this:
ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu

Tags: bluez5
Revision history for this message
Willem Ligtenberg (wligtenberg) wrote :
Revision history for this message
Willem Ligtenberg (wligtenberg) wrote :

After a reboot it seems to work.
awe_ mentioned there might be a race condition which he will test.

Now bluetoothctl gives uuids for audio sink etc.

OS build details:
build number: r331
image part: 20160105
build decription: Ubuntu 15.04 - armhf (20160105-020304)

Tony Espy (awe)
Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Tony Espy (awe) wrote :

I just flashed my mako to the same image as Willem ( rc-proposed/331 ) and couldn't reproduce the problem. After a fresh flash, I rebooted the device multiple times with BT enabled, after each reboot, BT was still enabled. I rebooted ten times, and wasn't able to reproduce...

I also verified that toggling BT off and back on again works as expected.

A quick look at the syslog shows that the bluez5 version of bluetoothd was only started at 14:41:46 which appears to be after the final reboot mentioned in comment #2. The previous version of bluetoothd running on the phone was 4.101, which was started at 12:05:44.

@Willem, what time did you flash the device?

My guess is this may have been some kind of system update hiccup.

Revision history for this message
Willem Ligtenberg (wligtenberg) wrote :

Luckily, I still had my terminal with the flash process open.
I flashed it and it rebooted at 14:38:13.
So 14:41:46 is indeed after rebooting, the first time, after the switch to rc-proposed.
A later manual shutdown and start of the device resolved the issue. It might have been one of those things that happen only in very specific circumstances. I didn't update anything after switching to rc-proposed, I did check if there were any updates, but there were none. (which makes sense)

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.