X
Tap here to go to the mobile version of the site.

Support Forum

alarm clock buggy?

Posted

Hi i programmed the alarm to wake me at 8 am but it rang at 0:30

i reinstalled the OS Manuelly set time now it rings an 1 hour before the alarm is set. The strange thing is it rings again when the right time is reached. What can I do.

Hi i programmed the alarm to wake me at 8 am but it rang at 0:30 i reinstalled the OS Manuelly set time now it rings an 1 hour before the alarm is set. The strange thing is it rings again when the right time is reached. What can I do.

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Mobile; OPENC; rv:28.0) Gecko/28.0 Firefox/28.0

More Information

Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Helpful Reply

Hi Buffy441,

I understand that you are having problems with your Clock and Alarm application. You mention that you "reinstalled the OS manually", can you share how you installed, and where you downloaded the build for your device?

It's possible that the build you used to flash your device has some bugs in it, since it's not a commercial build.

In order to better understand and investigate on the issue that you are encountering, please reply to this message with the following information:

  • What is the model of your phone? (ZTE Open, LG Fireweb or Alcatel OneTouch Fire)
  • What is the OS version found in the Device Information page? Please visit this link if you need help finding the Build ID of your phone.
  • Please provide the exact steps to reproduce the issue you are encountering.
  • How often do you encounter this issue?

Please be sure to include as much detail as possible, including any websites that may exhibit this issue, and any error messages that you may be receiving, exactly as they appear. This will ensure that we will have all the information needed to investigate into this.

Thanks for your help,

- Ralph

Hi Buffy441, I understand that you are having problems with your Clock and Alarm application. You mention that you "reinstalled the OS manually", can you share how you installed, and where you downloaded the build for your device? It's possible that the build you used to flash your device has some bugs in it, since it's not a commercial build. In order to better understand and investigate on the issue that you are encountering, please reply to this message with the following information: * What is the model of your phone? (ZTE Open, LG Fireweb or Alcatel OneTouch Fire) * What is the OS version found in the Device Information page? Please visit [http://mzl.la/Gzz6Kp this link] if you need help finding the Build ID of your phone. * Please provide the exact steps to reproduce the issue you are encountering. * How often do you encounter this issue? Please be sure to include as much detail as possible, including any websites that may exhibit this issue, and any error messages that you may be receiving, exactly as they appear. This will ensure that we will have all the information needed to investigate into this. Thanks for your help, - Ralph

Question owner

I have a ZTE Open C, Build-ID 20140519040012, FirefoxOS 1.3.

After I bought it on Monday I tried out everything and then I set my alarm for the next day 8 am and it rang at 00:30 I stopped it reactivated it and it rang at 8 am.

Like it listens to two different clocks. I thought I try android but the version I found was without gapps so it was useless why I switched back to firefoxos. Then after setting the clock to manuell it only rang an hour to early ( set 2 pm it rang at 1 pm and again at 2 pm)

Today it actually worked for the first time it rang a 8 am. I will watch it now (I have a second phone with an alarm set to just to be sure :-))

I have a ZTE Open C, Build-ID 20140519040012, FirefoxOS 1.3. After I bought it on Monday I tried out everything and then I set my alarm for the next day 8 am and it rang at 00:30 I stopped it reactivated it and it rang at 8 am. Like it listens to two different clocks. I thought I try android but the version I found was without gapps so it was useless why I switched back to firefoxos. Then after setting the clock to manuell it only rang an hour to early ( set 2 pm it rang at 1 pm and again at 2 pm) Today it actually worked for the first time it rang a 8 am. I will watch it now (I have a second phone with an alarm set to just to be sure :-))
pan_kisiel 2 solutions 5 answers

i have strange alarm behaviour, too. i set the alarm clock for 07:55 from mon-fri. today (sunday) it rang during the night - at about half past three in the morning - and again in the evening. see the screenshot. (language is polish)

i have the flame device with b2g 2.0.0.0 compilation: 20140809160202

i have strange alarm behaviour, too. i set the alarm clock for 07:55 from mon-fri. today (sunday) it rang during the night - at about half past three in the morning - and again in the evening. see the screenshot. (language is polish) i have the flame device with b2g 2.0.0.0 compilation: 20140809160202
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Hi Buffy441 and Pan_Kisiel,

Thanks for your reports and additional information. I've filed a bug to track this issue:

Thanks,

- Ralph

Hi Buffy441 and Pan_Kisiel, Thanks for your reports and additional information. I've filed a bug to track this issue: * [https://bugzilla.mozilla.org/show_bug.cgi?id=1052245] Thanks, - Ralph
Chris78 0 solutions 5 answers

I can confirm this bug as well. For me it happened on a ZTE Open (Movistar) with FFOS 1.1 as well as on a GeeksPhone Revolution with FFOS1.3.

In both cases the alarm clock rang one hour before the set alarm (5:45 instead of 6:45) and then at 6:45 again. Maybe it's worth mentioning, that both times it was a friday (Friday October 3 and Friday October 24). In both devices the alarm was set for "every day" (monday to sunday), vibration turned off.

Last time it happend, the device (Geeksphone) was connected to a PC via USB for charging. The PC (win7) was running when the phone was connected, but it was shutdown in the evening, so it was off when the alarm(s) rang.

My time zone is CEST.

Regards, Chris

I can confirm this bug as well. For me it happened on a ZTE Open (Movistar) with FFOS 1.1 as well as on a GeeksPhone Revolution with FFOS1.3. In both cases the alarm clock rang one hour before the set alarm (5:45 instead of 6:45) and then at 6:45 again. Maybe it's worth mentioning, that both times it was a friday (Friday October 3 and Friday October 24). In both devices the alarm was set for "every day" (monday to sunday), vibration turned off. Last time it happend, the device (Geeksphone) was connected to a PC via USB for charging. The PC (win7) was running when the phone was connected, but it was shutdown in the evening, so it was off when the alarm(s) rang. My time zone is CEST. Regards, Chris

Modified by Chris78

Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Hi Chris,

Thanks for your additional information regarding this issue. I will update the bug accordingly, so that our engineers can investigate.

Do you know if the phones had recently been restarted (possibly because of a system update) prior to the alarm ringing?

- Ralph

Hi Chris, Thanks for your additional information regarding this issue. I will update the bug accordingly, so that our engineers can investigate. Do you know if the phones had recently been restarted (possibly because of a system update) prior to the alarm ringing? - Ralph
Chris78 0 solutions 5 answers

Hi Ralph,

for the second occurrence (this morning on the GeeksPhone/FFOS1.3) I can approve that I rebooted the device yesterday evening (because the phone had lost its GSM connection and couldn't receive any calls nor SMS anymore, but that's another topic...).

Hi Ralph, for the second occurrence (this morning on the GeeksPhone/FFOS1.3) I can approve that I rebooted the device yesterday evening (because the phone had lost its GSM connection and couldn't receive any calls nor SMS anymore, but that's another topic...).
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Hi Chris,

Did the alarm ring shortly after the reboot, or some minutes/hours after the reboot?

The reason I ask, is because our engineers and developers have reason to believe that these alarm-misfires may be due to a bug with the system clock. The general issue, is that the alarm clock changes either into future, causing alarms to ring, or onto the past and then back to the correct time, which also causes alarms to ring. This particular "system time" bugs have generally been caused by reboots:

If you experience this issue again, it would be very helpful to take a screenshot of the device while the alarm is ringing.

Thank you again for providing this additional information and assisting us investigating this issue, thus helping the Open Web and the development of Firefox OS!

- Ralph

Hi Chris, Did the alarm ring shortly after the reboot, or some minutes/hours after the reboot? The reason I ask, is because our engineers and developers have reason to believe that these alarm-misfires may be due to a bug with the system clock. The general issue, is that the alarm clock changes either into future, causing alarms to ring, or onto the past and then back to the correct time, which also causes alarms to ring. This particular "system time" bugs have generally been caused by reboots: * [https://bugzilla.mozilla.org/show_bug.cgi?id=1069863] * [https://bugzilla.mozilla.org/show_bug.cgi?id=1061797] If you experience this issue again, it would be very helpful to take a screenshot of the device while the alarm is ringing. Thank you again for providing this additional information and assisting us investigating this issue, thus helping the Open Web and the development of Firefox OS! - Ralph
Chris78 0 solutions 5 answers

Hi Ralph,

the last reboot was yesterday evening at about ~6pm. The first (false) alarm was this morning at 5:45am, so about 12 hours later. Then at 6:45am the correct alarm rang too.

I think I also remember that a few weeks ago an alarm was completely dismissed.

I will try to reproduce the problem this evening by rebooting the device, then see what will happen tomorrow and try to make a screenshot.

Regards, Chris

Hi Ralph, the last reboot was yesterday evening at about ~6pm. The first (false) alarm was this morning at 5:45am, so about 12 hours later. Then at 6:45am the correct alarm rang too. I think I also remember that a few weeks ago an alarm was completely dismissed. I will try to reproduce the problem this evening by rebooting the device, then see what will happen tomorrow and try to make a screenshot. Regards, Chris

Modified by Chris78

Chris78 0 solutions 5 answers

Hi,

I rebooted my Geeksphone yesterday evening (~17:55), but there was no false alarm last night. The alarm clock rang at 6:45, just as I programmed it.

This evening I will connect it to the PC via USB and reboot it again, to see if this can reproduce the problem next night.

Chris

Hi, I rebooted my Geeksphone yesterday evening (~17:55), but there was no false alarm last night. The alarm clock rang at 6:45, just as I programmed it. This evening I will connect it to the PC via USB and reboot it again, to see if this can reproduce the problem next night. Chris
Chris78 0 solutions 5 answers

Hi Ralph,

this morning the bug reproduced. The alarm was set to 6:15 but the alarm rang at 7:15 (see photo). I rebooted the phone yesterday afternoon.

The change from summertime to wintertime on sunday, Oct.26, 3am seemed to work fine and the alarm was fine on sunday morning.

(Is a photo sufficient or do "real" screenshots container further debug info?)

Chris

Hi Ralph, this morning the bug reproduced. The alarm was set to 6:15 but the alarm rang at 7:15 (see photo). I rebooted the phone yesterday afternoon. The change from summertime to wintertime on sunday, Oct.26, 3am seemed to work fine and the alarm was fine on sunday morning. (Is a photo sufficient or do "real" screenshots container further debug info?) Chris

Modified by Chris78