kernel-packages team mailing list archive

[Tony Espy <1531515@xxxxxxxxxxxxxxxxxx>]

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.

-- 
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/1531515

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

Status in bluez package in Ubuntu:
  Incomplete

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531515/+subscriptions