Ubuntu Touch is no longer a supported.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: canonical-devices-system-image
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Ubuntu Touch is no longer supported.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson EM229 headset caused phone to reboot
Status in
Reduced priority for Ubuntu Touch bugs.
** Changed in: bluez (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson EM229 headset caused phone to reboot
Status in Canonical
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => backlog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson EM229
Yes, this still happens with today's phone image. It took about a dozen
power cycles to trigger.
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@Selene
Sorry for updating the status without a comment. I think my intention
was to get this re-tested on a current image and see if it was still
reproducible.
Looks like Simon has commented about kernel changes that may address the
original issue, so re-assigned to him.
** Changed in: bluez
I'm not sure why this is marked as incomplete now. Has the new upstream
kernel made it into our devices? Is a fix included and ready to test?
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: bluez (Ubuntu)
Assignee: Selene Scriven (toykeeper) => Tony
** Changed in: bluez (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: canonical-devices-system-image
Status: Confirmed => Incomplete
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Selene Scriven (toykeeper)
--
You received this bug notification because you
** Tags removed: bluetooth-ota9
** Tags added: bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson EM229 headset caused phone to
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue for you?
Thanks in advance.
--
You received this bug notification because you
>From the last kernel log this looks like a bug which was recently fixed
upstream in the linux kernel.
See
-
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/net/bluetooth?id=75e34f5cf69bd731d3b7375a786d4a15494fb8c6
-
** Changed in: canonical-devices-system-image
Status: New => Incomplete
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John McAleely (john.mcaleely)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I've raised #1403477 so that the driver team can look at this.
** Changed in: bluez (Ubuntu)
Assignee: John McAleely (john.mcaleely) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) = John McAleely (john.mcaleely)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling
I finally managed to trigger this bug again. The last_kmsg file is
attached, and confirms it is indeed a kernel panic. The traceback looks
promising too.
** Attachment added: last_kmsg
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1387949/+attachment/4279079/+files/last_kmsg
**
Oh, um, this was on krillin rtm 176.
Linux ubuntu-phablet 3.4.67 #1 SMP PREEMPT Tue Dec 9 16:37:17 UTC 2014 armv7l
armv7l armv7l GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Nice, thanks for the trace, it should hopefully be enough to indicate
the problem (which is clearly in the krillin bluetooth driver).
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Importance: Medium = High
--
You
** Changed in: bluez (Ubuntu)
Status: New = Incomplete
** Changed in: bluez (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
If I can manage to reproduce this again, I will. It seems quite a bit
more stable in the more recent images though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Please get the content available at /proc/last_kmsg after a device
reboots, that's the only way to get the kernel crash trace.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Krilin, r140, BT headset: Rocketfish RF-MAB2
On the first attempt, I was not able to connect to BT headset, which always
connected and worked reliably with previous releases. I was able to connect
after I rebooted the phone and power cycled BT headset. I tried about 5 more
times power-cycling
24 matches
Mail list logo
