Bug 15201 – SB Radio Back-up alarm doesn't trigger on lost Internet Connection

Bug 15201 - SB Radio Back-up alarm doesn't trigger on lost Internet Connection

Summary:

SB Radio Back-up alarm doesn't trigger on lost Internet Connection

Status:	RESOLVED DUPLICATE of bug 14870

Product:	SB Radio
Classification:	Unclassified
Component:	OS/Bootloader
Version:	Include FW version in comment
Platform:	Other Other

Importance:	-- normal with 7 votes (vote)
Target Milestone:	8.0.0
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-11-27 20:05 UTC by Tony
Modified:	2010-01-12 18:53 UTC (History)
CC List:	7 users (show)

See Also:
Category:	Bug

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tony 2009-11-27 20:05:22 UTC

If my Internet Connection is down when the alarm goes off, a screen flashes with the "no network" screen, then the Alarm Snooze / Off Screen is displayed , BUT, back-up alarm does not sound.

Comment 1 Tony 2009-12-06 10:35:42 UTC

This is a SB Radio Bug, not sure why it was moved to SB Server.

Comment 2 James Richardson 2009-12-07 08:30:49 UTC

Thanks for catching that Tony, I moved it back to SB Radio.

Comment 3 michael 2009-12-18 03:23:43 UTC

This should be PRIORITIZED to #1.  Making the alarm work in all situations is critical to making this product functional at the most basic level.

Comment 4 xelan54 2009-12-20 07:17:36 UTC

I agree that making alarms work reliably is crucial. This device is designed as a clock radio. I hope this can be fixed before 8.0.0

Comment 5 Stefan Hansel 2010-01-12 16:13:23 UTC

Ben - this looks like a duplicate to bug 14870.
Might be solved with your latest changes.

Comment 6 michael 2010-01-12 18:29:21 UTC

(In reply to comment #5)
> Ben - this looks like a duplicate to bug 14870.
> Might be solved with your latest changes.

Can you confirm this?

Comment 7 Ben Klaas 2010-01-12 18:53:09 UTC

Yes, it's definitely a dup of 14870. The issue is not fully solved yet, but we're honing in on it.

*** This bug has been marked as a duplicate of bug 14870 ***