touch-packages team mailing list archive

[Simon Fels <simon.busch@xxxxxxxxxxxxx>]

The case where we reboot with flight mode being enable is still valid. I
did some further analysis on this as I stumbled upon this again during
my current BlueZ 5 work and the underlaying problems goes down to the
kernel.

The bluetooth driver we have on krillin isn't implemented as a module
but is initialized by a subsystem it uses. It now turns out that this is
bound to the WiFi driver being initialized too. If WiFi doesn't get
enabled at boot time the Bluetooth driver can proceed providing a HCI
device and we end up without any Bluetooth functionality.

Needs further investigation on the kernel side what we can do to work
around this.

** Tags added: krillin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1421249

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421249/+subscriptions