@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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421249 Title: bluetooth can not be enabled sometimes (when booting with flight mode on being one case) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421249/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
