Guest Epohax Posted January 20, 2010 Report Posted January 20, 2010 Quick question. My Pulse is running MCR 1.7 (T-Mobile style), with some Market apps, nothing more. My alarm was set to 6:45 this morning. It however did not go off. Luckily I am a little paranoid, so I set a back up alarm on different device so I woke up (my Pulse suddenly died from 44% to zero in under 6 hours, from standby mode, probably due to excess of apps in the background?). So, I had a backup device, woke up, checked my Pulse and noticed it didn't go off. Puzzled, I went to Alarm options, changed the alarm time to 7:05 and when the time came, it went off properly. Why could this be? I just editted the time it should go off, and it went off properly. This is not very reliable... Anyone else?
Guest edwardblum Posted January 20, 2010 Report Posted January 20, 2010 Quick question. My Pulse is running MCR 1.7 (T-Mobile style), with some Market apps, nothing more. My alarm was set to 6:45 this morning. It however did not go off. Luckily I am a little paranoid, so I set a back up alarm on different device so I woke up (my Pulse suddenly died from 44% to zero in under 6 hours, from standby mode, probably due to excess of apps in the background?). So, I had a backup device, woke up, checked my Pulse and noticed it didn't go off. Puzzled, I went to Alarm options, changed the alarm time to 7:05 and when the time came, it went off properly. Why could this be? I just editted the time it should go off, and it went off properly. This is not very reliable... Anyone else? The operating systems switches off when the phone battery goes to zero so the alarm doesn't come one, same when you power off the device. Why they don't have this feature I don't know because I don't always like leaving the phone on.
Guest robot1000 Posted January 20, 2010 Report Posted January 20, 2010 The operating systems switches off when the phone battery goes to zero so the alarm doesn't come one, same when you power off the device. Why they don't have this feature I don't know because I don't always like leaving the phone on. What you can do is get the software LOCATE and set it that during the night it turns on 'flight mode' this uses less battery and the alarm will still sound. Also a good piece of software is Task-killer to get rid of the unwanted software in the background. I tend to find that my battery is very low come the evening so I usually charge it while keeping the phone on.
Guest murph_ne Posted January 20, 2010 Report Posted January 20, 2010 I had this problem despite my phone on charge overnight. The phone alarm was very unreliable and would often not go off at all. Installed alarmed light and have had no problems since
Guest zerosignull Posted January 20, 2010 Report Posted January 20, 2010 (edited) Quick question. My Pulse is running MCR 1.7 (T-Mobile style), with some Market apps, nothing more. My alarm was set to 6:45 this morning. It however did not go off. Luckily I am a little paranoid, so I set a back up alarm on different device so I woke up (my Pulse suddenly died from 44% to zero in under 6 hours, from standby mode, probably due to excess of apps in the background?). So, I had a backup device, woke up, checked my Pulse and noticed it didn't go off. Puzzled, I went to Alarm options, changed the alarm time to 7:05 and when the time came, it went off properly. Why could this be? I just editted the time it should go off, and it went off properly. This is not very reliable... Anyone else? Oddly enough my Alarm isnt working right too since I put on MCR 1.7. Yesterday it didnt go off and today it kinda went of for 5-10 seconds but their was no Alarm screen with the usual "snooze" and "Disable" buttons on. Then after about 5 minutes the phone went a bit mental, alarm sound was going off but was playing fast, and I had to switch the phone of to kill the alarm. Epohax: do you have setcpu running? what apps have u installed on your rom? EDIT: IM running MCR Vanilla Sytle Edited January 20, 2010 by zerosignull
Guest Epohax Posted January 20, 2010 Report Posted January 20, 2010 Oddly enough my Alarm isnt working right too since I put on MCR 1.7. Yesterday it didnt do off and today it kinda went of for 5-10 seconds but their was no Alarm screen with the usual "snooze" and "Disable" buttons on. Then after about 5 minutes the phone went a bit mental, alarm sound was going off but was playing fast, and I had to switch the phone of to kill the alarm. Epohax: do you have setcpu running? what apps have u installed on your rom? EDIT: IM running MCR Vanilla Sytle Zero: strange! That seems even more extreme than my issue. I have to clarify myself though, I wrote as if my phone died this morning, but that is an earlier case. It was just to describe the phone is unreliable, and I set a backup device since it has failed for me before. This morning, the phone was fully charged, alarm set, but it did not go off. I woke up, set a new time, fell asleep and the alarm went of properly. As far as I know, I don't have setcpu running (used to control cpu throtthling I assume? battery saving? down and overclocking?) I only have standard Android Market apps. I will post a full list, but mainly... Zedge, Layar, Advanced App Killer, Ringdroid, Google Sky, Seesmic, ... Nothing exotic.
Guest Epohax Posted January 20, 2010 Report Posted January 20, 2010 (edited) The operating systems switches off when the phone battery goes to zero so the alarm doesn't come one, same when you power off the device. Why they don't have this feature I don't know because I don't always like leaving the phone on. Sorry for confusion. It's indeed normal for the phone's alarm not to go off when the phone is OFF. Misunderstanding, this is due my bad writing in English, I wrote it as if my phone died and I was dissapointed that the alarm didn't go off. This was not the case! It's just that in an unrelated matter some days ago, I noticed my phone's battery at 44% when I fell asleep. When I woke up, the battery was dead already and the alarm didn't go off of course. The purpose of this thread was to complain that even though my battery was fully charged, volume up, normal profile, the alarm set, it did not go off. When I woke up when my backup device went off, I set a new time, fell asleep and it went of properly. Anyone any ideas what could be causing this? I am by no means an expert, but to dissect this problem: - It shouldn't be an Android issue, since most Android phones are fine. - Normally speaking, this should not be caused by Paul's MCR modifications. If it is, only Paul can comment on this, especially regarding changes between 1.6 and 1.7 - since someone reports the problem to have arrised since 1.7. I cannot help on that matter: I jumped into Android only when 1.7 was available, no experience with earlier versions. - Interference with some kind of application. But what? And why would that even be involved in any kind? Edited January 20, 2010 by Epohax
Guest niko1986 Posted January 20, 2010 Report Posted January 20, 2010 Sorry for confusion. It's indeed normal for the phone's alarm not to go off when the phone is OFF. Misunderstanding, this is due my bad writing in English, I wrote it as if my phone died and I was dissapointed that the alarm didn't go off. This was not the case! It's just that in an unrelated matter some days ago, I noticed my phone's battery at 44% when I fell asleep. When I woke up, the battery was dead already and the alarm didn't go off of course. The purpose of this thread was to complain that even though my battery was fully charged, volume up, normal profile, the alarm set, it did not go off. When I woke up when my backup device went off, I set a new time, fell asleep and it went of properly. Anyone any ideas what could be causing this? I am by no means an expert, but to dissect this problem: - It shouldn't be an Android issue, since most Android phones are fine. - Normally speaking, this should not be caused by Paul's MCR modifications. If it is, only Paul can comment on this, especially regarding changes between 1.6 and 1.7 - since someone reports the problem to have arrised since 1.7. I cannot help on that matter: I jumped into Android only when 1.7 was available, no experience with earlier versions. - Interference with some kind of application. But what? And why would that even be involved in any kind? Had the same problem, i have to make sure before i go to sleep to open alarm and uncheck then recheck the alarm box. Then it works, problem again came when i moved to 1.7 modaco.
Guest Epohax Posted January 20, 2010 Report Posted January 20, 2010 Niko: It's possible that I not only set a new time for the alarm, but I unchecked and checked the box first as well. Having a hard time remembering, but it certainly seems the case. So fixing it was uncheck then recheck, not setting the time to a different hour... Are you saying that in the previous versions of MCR, this issue was non-existant? In that case we should notify Paul.
Guest zerosignull Posted January 20, 2010 Report Posted January 20, 2010 Using TaskPanel 6.3.1 im noticing a app running called: alarm Version huawei.openos.baseapp.generall.b211 Wondering if its crashing when its been on for a long period of time? I'm half certain last time the alarm did not go off it wasnt in the running app list.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now