Calendar alarms rings forever if Low Battery dialog visible
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
High
|
Canonical Phone Foundations | ||
| | indicator-datetime (Ubuntu) |
High
|
Unassigned | ||
| | usensord (Ubuntu) |
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
- Ricardo Salveti: Approve on 2015-04-23
- PS Jenkins bot: Approve (continuous-integration) on 2015-04-23
- Charles Kerr (community): Approve on 2015-04-22
-
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 |
| 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) |
| Jussi Lind (jussi-lind) wrote : | #2 |
This same thing happened to me but with alarm clock:
https:/
(See comment #6)
| Ricardo Mendoza (ricmm) wrote : | #3 |
From the description this seems like a different case of the vibration. Does it keep *ringing* literally, or just vibrating? Is it with the screen off? or on.
| Launchpad Janitor (janitor) wrote : | #4 |
Status changed to 'Confirmed' because the bug affects multiple users.
| 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 |


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/ virtual/ timed_output/ vibrator/ enable (as root in the terminal app) then suspend and the buzzing wont stop
usensord needs to hold a wakelock while theres an active vibration timer ...