motorola droid owners: help me get a bug noticed/fixed.

[sao123]

If you own a droid phone, id like you to test this big on your phone and see if you can reproduce it. If you can, then I'd like you to go to the bug submission page and report you experienced this bug so it can get fixed...
If you dont experience the bug, id like to know that too...

http://code.google.com/p/android/is...=ID Type Status Owner Summary Stars&start=300

- Steps to reproduce the problem.
Using media station default alarm clock:
Set snooze duration to 5 minutes for ease of testing.
Set 3 alarms with unique sounds so each is identifiable.
Set alarm 1 to a time a few minutes from now.
Set alarm 2 to a time 2 minutes later than alarm 1.
Set alarm 3 to a time 5 minutes later than alarm 2.

- What happened.
Allow alarm 1 to sound. Snooze it. Wait for the time alarm 2 is supposed
to sound. It will not. Alarm 1 will sounds again, this time dismiss it.
Wait for the time alarm 3 should sound. It will.

- What you think the correct behavior should be.
Alarm 2 should sound on time, regardless of the snoozed state of alarm 1.
Each Alarm should be notified, sounded, and snoozed independently of all
other alarms set in the system.

 

[rudeguy]

pretty sure its and Android thing. My myTouch does the same thing. Try running a 3rd party alarm and see if that helps.

 

[sao123]

pretty sure its and Android thing. My myTouch does the same thing. Try running a 3rd party alarm and see if that helps.

tried 4 different downloaded android alarm clocks all with the same result.
I also noted there are similar bugs posed for the android calander.

It seems the sleep notification in the OS is the problem.