I'm on a Nexus 7 (LTE) r.23 from ubuntu-touc/ ubuntu-rtm/proposed from
system-image.tasemnice.eu/
Bluetooth does not even become discoverable - it just times out - even
when I have my bluetooth keyboard scanning
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John McAleely (john.mcaleely)
--
You received this bug
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
"All without rebooting."
You need to reboot to reproduce the issue. Disable bluetooth, then
reboot. Then enable bluetooth and see if it works. The issue only occurs
(for me atleast) when booting the phone with bluetooth already disabled.
--
You received this bug notification because you are a
@Jamie: really?
Will double check that on monday.
** Tags added: bluetooth bluez5
** Tags removed: bluez5
** Tags added: after-bluez5
--
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:
@Sam, that wasn't how I remembered it, but I tried as you said. Disabled
bluetooth, reboot. Enable bluetooth. It worked. I then disabled and
enabled again and it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@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
This appears to be fixed with the new bluetooth stack:
$ system-image-cli -i
current build number: 109
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note, this doesn't even need flight mode, I can reproduce it 100% just
by switching off Bluetooth:
Disable bluetooth.
Reboot phone.
Enable bluetooth.
This fails to enable bluetooth. If bluetooth is disabled when the phone
booted, the only was to enable it is to click enable and reboot the
I noticed this does not seem to affect arale (at least I couldn't
reproduce it), but it is easily reproducible on mako.
--
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
it's easy to trigger on vivid
- enable flight mode
- restart the device
- disable flight mode
- bluetooth is still disabled and can't be enabled
** Summary changed:
- bluetooth can not be enabled sometimes
+ bluetooth can not be enabled sometimes (when booting with flight mode on
being one
I'm pretty sure this has to do with the ordering of the bluetooth-touch,
bluetooth (bluez) and urfkill jobs. IIRC bluetooth-touch jobs do some
firmware tweaks that can't work if the device isn't available or rfkill
blocked, but we also need to be very sure that the radios are off all
the while
12 matches
Mail list logo
