1187527 - Alarm firing whenever it feels like

Status: RESOLVED WONTFIX

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

Description

[(not reading bugmail) Nick Desaulniers [:\n]]

The alarm on my fxos3.0 Aries went off 20-40 minutes early today.  I don't remember exactly, because I fell back asleep after resetting the alarm.  It was a weekday alarm for 8am.

Comment 1

[Kamla Junior]

hi nick! does it work fine some times before this or  was it the very first time you tried to make use of it? ... thanks in advance.

Comment 2

[(not reading bugmail) Nick Desaulniers [:\n]]

That was the first time.  It just happened again today, though it fired at 7:00am.  After stopping the alarm, I looked at my alarms list, and I do not have an alarm for 7am anywhere.

Comment 3

[Kamla Junior]

WORKSFORME.
It seems like an interference with another program(recently installed) as i was unable to reproduce it.

Comment 4

[Marcus Cavanaugh [:mcav]]

If you're able to grab a logcat when this happens, Clock spits out a bunch of debugging information related to the system time and clock alarm database, which would help in finding the source of this problem.

Comment 5

[(not reading bugmail) Nick Desaulniers [:\n]]

Yesterday, it fired at 7:30 PM!

Comment 6

[(not reading bugmail) Nick Desaulniers [:\n]]

Attachment: dev-log-main.log

Comment 7

[(not reading bugmail) Nick Desaulniers [:\n]]

omg, the alarm for 8am was just firing non stop at 11am.  It went off three times! Eventually, I just restarted the phone. Almost destroyed the phone.

Comment 8

[(not reading bugmail) Nick Desaulniers [:\n]]

Are the logs backed up on the device anywhere? I got a pretty good screenshot of the alarm saying it's 8am and the clock in the top right saying it's like 4pm.

Comment 9

[(not reading bugmail) Nick Desaulniers [:\n]]

My alarm did not go off this morning.  I have a weekday 8am alaram.  I woke up around 10am, opened the app, and as soon as I did, the 8am alarm went off.  I think this may have been the first time opening the clock app after installing an OTA update this weekend.  I wonder if the update process resets registered alarms, perhaps?

Comment 10

[Andrew Sutherland [:asuth] (he/him)]

mozAlarms are only purged on "webapps-clear-data" observer events which I believe would also nuke all storage for the clock app.

If the steps you took this morning were:
1) Turn on device screen, alarm does not fire
2) Maybe unlock or something, alarm does not fire
3) Tap clock app, alarm does fire

Then this sounds like the system message failed to open the clock app on initial generation of the mozAlarms notification rather than a wake-lock failure.  The only thing I'm aware of related to that is bug 1220032 but I don't think that should be able to happen.  Is it possible your phone had some other extremely memory hungry app on it open that caused the process manager to reap the alarm app?

Of course, logs would shed a lot of light if you happen to have logs from either 8am or 10am.  Frequently a catch-22 with these type of problems, of course :(

Comment 11

[(not reading bugmail) Nick Desaulniers [:\n]]

(In reply to Andrew Sutherland [:asuth] from comment #10)
> Of course, logs would shed a lot of light if you happen to have logs from
> either 8am or 10am.  Frequently a catch-22 with these type of problems, of
> course :(


yep, will have be to more diligent about gabbing logs...

The steps 1-3 you described are accurate.

Comment 12

[BMO Automation]

Firefox OS is not being worked on