@Simon: yes, I was pleasantly surprised too. I had always heard that it was a hardware issue so when I read that rc-proposed had the new bluetooth kernel stack I thought maybe they worked around the issue in some manner in the kernel. Initially after booting into r109 I used the indicator and it all appeared to work properly (like on arale). Satisfied, I went and looked at bug #1318360 again (unrelated to this but...) then I updated the radio firmware as described in https://lists.launchpad.net/ubuntu-phone/msg08514.html. Then I saw your 'really' comment and decided to try this bug for real in my car. I enabled bluetooth via the indicator, it paired with the car. I played a song with the music-app via bluetooth. I disabled bluetooth via the indicator. It unpaired with the car. I enabled bluetooth via the indicator and it paired and I played a song with the music-app via bluetooth. All without rebooting.
I mention the updated radio firmware only because while I don't think it had anything to do with fixing this bug, because I didn't test pairing with the car prior to updating it, I'm not 100% sure it isn't needed. -- 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
