Calendar alarms rings forever if Low Battery dialog visible
Bug #1442166 reported by
Bill Filler
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Fix Released
|
High
|
Canonical Phone Foundations | ||
| indicator-datetime (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
| usensord (Ubuntu) |
Fix Released
|
High
|
Ricardo Mendoza | ||
Bug Description
I'm on rtm build 258 on krillin
Steps to reproduce:
- let battery run down on phone (was sitting unplugged for 1 or 2 days)
- in the morning, a calendar alarm starting ringing/vibrating and would not stop
- when I looked at the phone, the screen was on and I see the Low Battery dialog
- after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop
Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever
Related branches
lp://staging/~ricmm/usensord/vibrate-no-sleep
- Ricardo Salveti (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
- Charles Kerr (community): Approve
-
Diff: 73 lines (+37/-0)1 file modifiedhaptic/haptic.go (+37/-0)
| Changed in indicator-datetime (Ubuntu): | |
| assignee: | nobody → Charles Kerr (charlesk) |
| importance: | Undecided → High |
| Changed in canonical-devices-system-image: | |
| importance: | Undecided → High |
| milestone: | none → ww15-2015 |
Revision history for this message
| Oliver Grawert (ogra) wrote | #1 |
| Changed in usensord (Ubuntu): | |
| importance: | Undecided → High |
| assignee: | nobody → Ricardo Mendoza (ricmm) |
| Changed in canonical-devices-system-image: | |
| status: | New → Confirmed |
| assignee: | nobody → Canonical Phone Foundations (canonical-phonedations-team) |
Revision history for this message
| Jussi Lind (jussi-lind) wrote | #2 |
Revision history for this message
| Ricardo Mendoza (ricmm) wrote | #3 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in indicator-datetime (Ubuntu): | |
| status: | New → Confirmed |
| Changed in usensord (Ubuntu): | |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| milestone: | ww15-2015 → ww17-2015 |
| Changed in indicator-datetime (Ubuntu): | |
| assignee: | Charles Kerr (charlesk) → nobody |
| status: | Confirmed → Invalid |
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → In Progress |
| Changed in canonical-devices-system-image: | |
| status: | In Progress → Fix Released |
| Changed in usensord (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
it seems to actually be usensord's fault and is easy to reproduce, i think the low battery dialog is just a coincidence here ...
to repro:
echo 10000 >/sys/devices/
usensord needs to hold a wakelock while theres an active vibration timer ...