Closed
Bug 1190416
Opened 10 years ago
Closed 10 years ago
Device powered off, no alarm on restart
Categories
(Firefox OS Graveyard :: Gaia::Feedback, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1160923
People
(Reporter: sfoster, Unassigned)
Details
(Keywords: foxfood)
Attachments
(1 file)
231.45 KB,
text/x-log
|
Details |
>> Feature Request Summary:
Device powered off, no alarm on restart
>> Description of feature, or problem to be solved
Last night i left the device plugged in and on. this morning it must have crashed at some point as it indicated 100% charged but was powered off. When I powered on, I had to open the clock app before I realised it was supposed to have triggered an alarm an hour ago. I got a logcat, will attach it
Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]:Broken Functionality
blocking-b2g: --- → 2.5?
QA Whiteboard: [foxfood-triage]
Comment 3•10 years ago
|
||
UX team, Can you confirm if old alarms should buzz after turning on?
blocking-b2g: 2.5? → 2.5+
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 4•10 years ago
|
||
The old alarms should not go off, but it would be handy to show an notification indicating that you have missed an alarm.
Some considerations would be to collapse multiple alarm missing
What sort of information to show in the notification
And to show notifications when alarm is missed either b/c your phone was off or b/c you just didn't act on it
NI to Eric for notification stuff and Harly to see if there's a UX person available to do the small bit of design work.
Flags: needinfo?(hhsu)
Flags: needinfo?(firefoxos-ux-bugzilla)
Flags: needinfo?(epang)
Comment 6•10 years ago
|
||
(In reply to Harly Hsu[:harly] from comment #5)
> Ni Juwei for the clock part
let's see what Juwei says, if needed we'll add a notification.
Comment 7•10 years ago
|
||
Agree with Tiff, the expired alarm should not go off. Currently we don't have a notification to tell users the expired alarm, yet we do have similar thought about the notification back to 2.x on bug 942837.
It's a different use case, but it also reveals the needs that users want to know what happen to their alarm.
As for "a notification for expired alarm", I think it depends on the purpose of the alarm:
1. If the purpose is for calling attention to users at a specific time (such as wake them up), then an expired alarm notification wouldn't help that much since users might overslept already due to unpredictable reason.
2. If user consider the alarm as a reminder (such as go to the doctor), it would be helpful to have a notification to tell users what they missed and they can make up for it later.
I can see people kind of using the alarm in multiple purposes nowadays so in some cases it'd better to have a notification of expired alarm. Yet I would suggest that keeping the alarm as simple as description 1.
Let me know your thought,
Thank you:)
Flags: needinfo?(jhuang)
Comment 8•10 years ago
|
||
This looks like the same race condition as bug 1160923. Please reopen if you think that's not the case.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 2.5+ → ---
Updated•8 years ago
|
Flags: needinfo?(epang)
You need to log in
before you can comment on or make changes to this bug.
Description
•