Closed Bug 986516 Opened 11 years ago Closed 11 years ago

No timer screen visible when ringing

Categories

(Firefox OS Graveyard :: Gaia::Clock, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rik, Unassigned)

Details

(Keywords: regression)

When the timer is ringing, we have no way to stop it. The timer screen never appears, whether you are looking at the clock or in another app or the screen is locked. I didn't verify it was a regression but I can't believe we shipped a timer without this screen. This is fixed on master but not on 1.3 Alcatel One Touch Fire build identifier: 20140319164001 - 4982b268 Git commit info : 2014-03-19 17:56:00
Summary: No timer screen when → No timer screen visible when ringing
QA, Please review and investigate if reproducible on 1.3.
Keywords: qawanted
QA Contact: bzumwalt
Unable to reproduce issue as described. Set Timer in Clock app for one minute and stayed on Timer screen. Phone vibrated twice when timer ran out then returned to screen to set new timer, no additional screen was displayed no additional alerts were given. Same results with Timer running out while on main clock screen. If user sets timer then returns to (and stays on) home screen the timer does not vibrate or make a noise when countdown has finished. This appears to be a separate issue if it is a bug at all. Also set timer for one minute and moved to different screens (e.g. main clock screen, Home screen, etc.) then returned to timer screen. Was able to pause, resume, or stop timer at will. In case this issue is talking about the alarm: alarm screen shows no matter what screen user is on as well as when the screen is locked. Environmental Variables: Device: Buri v1.3 Mozilla RIL BuildID: 20140319164001 Gaia: 4982b2680645e1506d72159ae73b04b14718ee6b Gecko: 155d55074aaa Version: 28.0 Firmware Version: v1.2-device.cfg
Keywords: qawanted
Please renominate with clear STR on 1.3. We can't reproduce this.
blocking-b2g: 1.3? → backlog
Whiteboard: [closeme 3/28/2014]
try this : set timer in clock for 1 minute, in "sound" change "no sound" (as set by default !) and select "ringing strings". then "start". wait 1 minute and ... it rings but you can't stop the sound.
QA Wanted to try the steps in comment 4
Keywords: qawanted
Whiteboard: [closeme 3/28/2014]
Issue described in comment 4 DOES occur in latest 1.3. The entire sample plays out (~10 - 20 seconds) with no apparent way to cease sound. Sound does cease if user closes Clock app through task manager. Environmental Variables: Device: Buri v1.3 Mozilla RIL BuildID: 20140324004001 Gaia: f7742fb4929cc57c9f72955ce5cebb8279745ac0 Gecko: e42b778a010f Version: 28.0 Firmware Version: v1.2-device.cfg
Keywords: qawanted
Okay I can confirm this as well. If this is a regression, then we probably should nominate this cause this really poor UX. If it isn't, then we're probably stuck with this, given that we're string frozen.
Marcus - When this feature was implemented, did we have a modal dialog appear allowing the user to stop the playback of sound? Specifically, is the UI seen on 1.4 right now supposed to be present on 1.3?
Flags: needinfo?(m)
No, there is no visual display, nor a way to stop the sound except letting it play through[1]. Bug 898354 was the feature for adding the notification screen, but it was rejected for 1.3 due to being too far fast feature-complete. The feature is present in 1.4, which matches the report here. I am assuming this report indicates that the sound ceases after one play-through; if that's the case, I'm closing this bug as we won't be able to uplift the 1.4 feature to 1.3. Please re-open otherwise, or if you feel something needs to be done other than uplift. [1]: https://github.com/mozilla-b2g/gaia/blob/v1.3/apps/clock/js/timer.js#L145
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(m)
Resolution: --- → WONTFIX
thanks a lot. Can it be fixed for tarako & dolphin ? I'm expecting that (as we're targeting feature phone owners) Firefox OS phones should be on par with...feature phones.
blocking-b2g: backlog → 1.3T?
blocking-b2g: 1.3T? → ---
You need to log in before you can comment on or make changes to this bug.