Related
Dear All,
I wanna have some quick facts: Who have WM5 alarm not wake up issue?
The issue is- when you have scheduled an alarm (e.g. a morning wakeup call) and then suspend your unit, it fails to launch the alarm. When you turn on the unit, usually the unit realize the missing alarm and then re-sound the alarm for you. (Which is too late :evil: )
For people who encountered such issue, please enclose the following details:
1. Hardware (e.g. Qtek 9100, Dopod 838, i-Mate K-Jam, O2 XDA Mini S, etc.)
2. Firmware distribution and version:
a. IPL
b. SPL
c. GSM (hehe not quite related I think though)
d. OS
For me:
Hardware: Dopod 838
IPL: Qtek 1.01
SPL: Qtek 1.01
GSM: MDA 1.12.10
OS: O2 Mini 1.5.4.2
i have this issue only using spb time.
The internal alarm works without problems.
ROM 1.6.7.1 WWE
CPU OMAP850
WIZA200
OK, not all fact, but what i thought (until today) from reading many many posts.
1) Bad app design, no fix, wait for new ROM (possible, probable infact but maybe not)
2) When you change the alarm and standby the device before the alarm settings were saved properly (thus, when the device wakes it finishes the save and realises its past the alarm time) this is my fav answer!
I've had the problem in the past using my O2 mini-s UK with ROM 1.5.4.2 WWE. I started leaving the device for 2 min from setting an alarm to entering standby - no more problems.
Til today..
Yesterday i set the alarms like normal, used the phone for over 2 mins then entered standby with the mains charger plugged in.
At 4 am my 5 am alarm woke me, i turned it off, realised the time, almost threw my wizard out the window & went back to sleep for an hour. For info - the alarm WAS set for 5 am, the clock WAS right. Even when the alarm was going off it told me it was a 5am alarm & the clock was saying 4. The alarm then worked properly at 5.
Until there is a real fix for this i cant trust my phone to wake me, my old nokia's could manage the time & alarm, but the Wizard seems to find it too challanging
my 9100 does this all the time now. bugs the hell out of me.
i haven't heard of any other wm5 devices having this problem which might mean it's a wizard issue rather than a wm5 issue ?
:-(
It is a very common problem:
http://forum.xda-developers.com/viewtopic.php?t=31895
Please read through that thread first - and if at all possible, reply there.. unless your reply would be specific to the information requested by the poster here.
For what it's worth, I stand by my recommendation in that thread: just don't let your PPC go to standby, and use any of the freeware apps out there to turn the display (not just the backlight) entirely off. Your battery will drain only a *slight* bit more, but you will not run into the issue discussed here.
not sure where to reply. Probably here, it is less crowded and it is more of a WM5 topic here than a hardware topic there.
Anyway, just to let you know I have a MDA Compact 2 (aka HTC Charmer) which runs WM5. The alarm seems to worked fine so far. I have it set to 7am all day, using a the standard WAV sound. Works well.
I'm not sure if this matters, but the alarm works when it is in standby mode (aka one button will switch it on instantly) BUT it doesn't work if I had the device switched off (aka needs to bootup upon switch on).
And, the only problems that I had with the alarm is when I have a VERY big WAV file in it. The last time I had a 3.0MB WAV file as my alarm sound, the 'Reminder' failed to pop up and the alarm keep sounding. And if you had another alarm on it will still sound it together. Bit like a mixed up WAV in the system. Other than this, the alarm works well in Charmer.
I recently have a Dopod838 (I think) ROM (WM5) flashed into it and the alarm still works alright. Hopes this info helps.
Heya,
Yeah, if the device is entirely off (i.e. needs boot-up), then no alarm/etc. will run at all. In that mode, there is only enough power for the device to react to the button press to turn it on. This is similar to switching a regular mobile phone completely off. You'll miss any calls as well
I get the same problem, I just leave my phone on all the time.
ZeBoxx said:
just don't let your PPC go to standby, and use any of the freeware apps out there to turn the display (not just the backlight) entirely off.
Click to expand...
Click to collapse
If this helps, I use Pocket Candy as a screen saver and change the default s/saver to 'blank screen'. (Unsure if this completly turns the display off) but my phone fully charged with regular use (camera & vids as well) will last around 36 hours...
Pocket Candy can be found HERE:
I don't know how much people have been thru the same problem in wm2003;the reason why I have started this thread is to find out if there is an OEM secretly fixed the bug already. The time when I am using wm2003, OEM never really admitted the bug is fixed, but in fact the bug is gone after certain version of rom.
so hope everyone could post if you have the problem or not, as well as the detail rom version, so we could know if we could avoid this problem.
after I tried Menmaid and most all the solution on the internet out there, my alarm still not wake up from standby mode...
But yesterday, I found if i enable "voice commend" (which I disabled previously), the alarm will wake up from standby mode.
Hope that helps, my is MW 6.1
I have started this thread so that we can begin development of a program or a solution which will make the alarm system on our Wizards totally reliable.
As we know, a number of us have a problem whereby our devices fail to wake up when an alarm is due to go off, causing us to sleep in, and be late for work. This is an unacceptable situation. It is my intent to develop a program which will replace or augment the alarm system in WM5 so that we never again have to worry that our PPCs won't wake us up in the morning.
So far, we know there are a number of problems which might be contributing to the failed alarms:
1. Duplicate alarm/calendar notifications being entered into the notification database (same alarm shows repeatedly in the database)
- This can be resolved with CheckNotifications (http://www.scarybearsoftware.com/ppc_cn_overview.html) which will remove duplicate entries. It does not prevent the duplicates from being entered in the first place.
2. Alarm settings not saved to registry. It seems there may be a problem whereby registry changes are not being copied from RAM to Flash immediately, so if you Standby the device shortly after setting/changing the alarm, the alarm is not saved.
- This can be resolved by leaving the PPC for a minute or so before putting it in Standby after changing an alarm.
3. The big one. An alarm notification not turning the device on from standby. Why this affects some people and not others, we don't know. Some users report than when an alarm is due to go off, the device doesn't wake up. When the device is turned on manually, the alarm then sounds. This seems to happen randomly (with some alarms working OK, and others not) but doesn't affect everyone.
As yet, there is no known solution to this problem. This thread is intended to develop that solution.
My idea so far is to develop an application to replace the standard alarm on WM5. Our main objective is to create an event which will, reliably, and without fail, wake the device from standby. Once we have developed this program, a new alarm system can be tacked on to it, or the source code can be made available for developers of current alarm systems to integrate into their programs.
My PPC programming knowledge is limited, so the intention is for this project to be a joint effort, and I would urge anyone who has any useful input to contribute it on this thread.
I have noticed a few people mention that a program called Pocket WakeUp is a reliable alarm system, and doesn't suffer from the known bugs in the WM5 one.
http://www.pocketpcfreewares.com/en/index.php?soft=1299 (French version - see below for translated English version)
Unfortunately, there doesn't seem to have been an update of the program for quite a while, and also, the program is in French, so there aren't many people using it to see exactly how reliable it is.
I have done a quick-n-dirty translation of the program into English (I hope the author doesn't mind - no other changes were made), and attached it to this post. The interface isn't great, and it can be quite convoluted to use, but perhaps with an English version, more people can give it a try and see if it actually is reliable.
From what I can gather, Pocket WakeUp adds a notification when an alarm is due, which loads with WakeUpStart.exe program, which then loads the main program and sounds the alarm.
If this program is actually reliable, then I expect the author has found a way to make the device wake up from standby without fail, and the WakeUpStart.exe is the important part.
Please let me know if you use Pocket WakeUp and it works reliably, or randomly fails. Also, if the author of this program reads this board (or someone knows how to get in contact with him in English) I'd be interested to hear your views.
Good effort, I'll try the cab and report back over the next week.
Excellent endeavor! I have been using PPC devices for sevearl years and this has always been my biggest problem. Its hard to believe that MS has issued 3 new versions of their WM platform, all with this issue. This should be one on the first things you need to get right in these devices.
On the WM2002 and WM2003 platform I have good success with both PhoneAlam with AlarmToday for Pocketmax and also SuperAlert. But since moving on to the KJAM, the current versions of these programs just don't work.
I am not a developer, but will certainly help with testing etc. I'll try the FR prog now and will also post results.
Regards
Chris
The alarm not waking up on standby bug was fixed in the leaked 9100 test rom.. so whats the point in fixing a problem thats already been fixed
MilanoRex said:
The alarm not waking up on standby bug was fixed in the leaked 9100 test rom.. so whats the point in fixing a problem thats already been fixed
Click to expand...
Click to collapse
Says who? I'm using the latest i-mate ROM and the problem still persists.
I've been using Pocket WakeUp to check - *zap* - and so far it seems to work fine. Problem is, that's what I thought of the standard alarms until they failed a couple of times on me. Unfortunately, it also seems that my battery is draining faster now - but I would have to confirm that absolutely with a full copy of pocketbatteryanalyzer. I'm using my old phone in the mean time to make sure I do wake up.
For me, just not switching the device to standby is still the best bet. This also negates any issues related to point 2. Point 1 remains, and is actually a cause for old alarms going off when they shouldn't - and the cleanup thing is something I still do.
One thing that I think I should point out, though, is that the problem isn't just with a wake-up alarm. Pocket WakeUp may very well be a perfectly fine solution to that (no way to be 100% certain, I guess). The problem is that on at least one occasion, the device failed to wake up for a meeting event. Thankfully I was keeping an eye on the clock and I was leaving only 5 minutes late - and with a little speeding got there in time just fine. Point is, a wake-up alarm won't fix -those- :\
ZeBoxx, as far as I can see, Pocket WakeUp does use the notification system. Set an alarm with it, and check the notification queue. Delete the item from the notification queue and the alarm never sounds.
If we can work out how Pocket WakeUp reliably brings the device out of standby, then there's the possibility of writing a program to tack a wake up event in front of every calendar entry.
gah.. WakeUpStart? totally missed that.. I'll stfu now
ZeBoxx said:
gah.. WakeUpStart? totally missed that.. I'll stfu now
Click to expand...
Click to collapse
Yep! Thing is, if WakeUpStart can wake up the device without fail, then it will be simple enough to tack a similar wake up event a few secs before each alarm or appointment. Just need more people to test Pocket WakeUp to see if it's reliable - and hopefully we can get a hold of the author so he can tell us how he did it!
I upgrade to the new KJAM rom and now my alarm works.
texasez said:
I upgrade to the new KJAM rom and now my alarm works.
Click to expand...
Click to collapse
Yep, the whole problem with this bug is that it affects people randomly. Some people have the bug, some don't. Some people just get it one day for no apparent reason. There is no one solution to everyone's problems. Upgrading worked for you - good for you - doesn't mean it will work for everyone, and there's always the possibility that you never had the bug, and then you upgrade to the latest ROM and you start getting the bug!
thanks alot elyl !!
the translation of this program is the best news in months! I have been using this prog for 3 months without any problems. It seems very reliable to me. I dont understand French thoug, so it has been a little bit hard to use.
Before I started using the program, I had alot of problems with the alarm...
I tried Pocket wake up yesterday with mixed results. My KJaM seemed to be waking up for each event, but I was expecting it to continue to repeat the alarm beyond the few repeats that you get with the built in reminder. That did not happen though... I have set Pocket alarm wake up call take is set go in a few minutes, so will see if that works (guess that I am already awake though, so it won't be a big deal if it doesn't go off )
cbrow51 said:
I tried Pocket wake up yesterday with mixed results. My KJaM seemed to be waking up for each event, but I was expecting it to continue to repeat the alarm beyond the few repeats that you get with the built in reminder. That did not happen though... I have set Pocket alarm wake up call take is set go in a few minutes, so will see if that works (guess that I am already awake though, so it won't be a big deal if it doesn't go off )
Click to expand...
Click to collapse
Did you try setting a snooze time for about 5 mins? It will repeat then if you don't cancel it. Also, if you are using a short audio file for the alarm, make sure you increase the Minimum time of alarm to be X number of seconds - then it will repeat your alarm sound for however many seconds.
Hi Elyl
Yes, stumbled into that in the end. My French is very poor, so I had to guess at the options. Still, that seemed to work. I did notice that if you change the settings and then let the device go into standby, the alarm did not repeat...:-( I had to reset a new time, then it worked. I will now set a reoccuring alarm and not touch the settings and see how that goes... Will post back at end of day today..
Regards
chris
to be thorough...
In an effort to be thorough, I'll add my experience so that maybe a developer can read a solution. I use my kjam as a daily alarm. It has almost always worked when I leave the device plugged in and though the backlight is off but the actual system never goes into standby (everyday except one in six months). I have also experimented with using the alarm from a battery power source, but again, making sure that the device never goes into standby (this is a real battery drain).
I have used SPB time, Ptravel Alarm, and the built in alarm. SPB time is completely unreliable and has never worked (not even when set immediately after a more reliable alarm). Ptravel alarm has worked over the past week when I have tried it in both power/active and non-powerd/active, but I haven't tried it when the system was in standby. The Ptravel Alarm developer (Burroak Software) is a very very active developer and seems to really care about making his products work. The only flaw I have is the interface (i.e. stop button) is somewhat small to press first thing in the morning.
The built-in alarm is the one I have used most and seems to work well from a power source. Again, it does not work from standby reliably.
I know this is re-hashing the obvious for all of you, but thought it might give some more background. There simply must be something that is develop-able, which wakes up the device from standby (a turned off state) in time for the system to register and activate an alarm program or a few seconds before.
Could there be a way to extrapolate the program which activates the device or part of it to remotely activesync on a time schedule?
I will use the WakeUp program and report back.
wakealarm
just to stress the point, i will also use wakealarm and report at the first failures. If 100 users would do the same, we can improve our evaluation time by 100X. If even to a single user it will not work, i cannot fully trust the program for professional reasons or travelling.
Today, I have the test rom, SPB pocketplus, and yes ONCE the standard wm5 alarm didn't work on this configuration (over about 20 alarms and 200 calendar reminders that worked successfully). i use once in a while checknotifications and sktools to keep the notify queue clean - should i do it or not? sometimes, i am afraid that the alarm i loose are those that these two programs remove by believing they are unnecessary duplications....
i noticed that - in the infamous occasion of a missed alarm in the morning - i forgot the wifi connection on while the system was recharging beside my bed, and in the morning i had a pop-up message it complaining about the absence of network (instead of waking me up...).
Did i understand it correctly that - at midnight - the wizard does some internal procedures and wakes up? do i guess that - after waking up - it had to deal with the wifi network search instead of some alarm critical procedure? if it would be so, i would be happy - for example - to do the alarm critical procedures every few hours, so to be sure not to miss any.
Few hours later, finally at work, i saw the wizard rebooting by itself (second time ever, the first one was with the 1.6 ROM!) and, at reboot, started sending a list of alarms that i could not easily dismiss (since the system was in an early phase of reboot, no today screen available yet). i had to softreset a couple of times, after dismissal of the pending alarms it started to work correctly again.
I am reporting this in order to increase empirical understanding of the reasons why the standard alarm fails.
cbrow51 said:
Hi Elyl
Yes, stumbled into that in the end. My French is very poor
Click to expand...
Click to collapse
That's why I translated it! See the attachment.
Maybe its just me but I cannot see any link to a translation?
I can see the link to the cab file and I can see the link to the web site but no document?
Robin
Brand new HTC HD2, No software or any tweakings, nothing.
Alarm set to wake me up this morning.
Woke up an hour later, phone was on, alarm screen was on display with the machine freezed, had to soft reset. What the hell is that? This is a brand new nothing installed device. A simple thing as an alarm clock freezes the device?
Anyone experiences same problem?
I had the same problem, but with galarm.I never thought this can happen with the original software.It should be bugs free...
I get a similar problem sometimes with GAlarm. Luckily for me, it sets the alarm off then freezes up. That gets you out of bed believe me
The screen is on, with the time displayed and what looks like one of the balls from the maze/snooze function in the very top right hand corner. You can't do anything to get rid of the screen. I had to press the Home hard key then end task GAlarm to get it to stop. So it's not totally frozen up but GAlarm is fubard
chimpsinties said:
I get a similar problem sometimes with GAlarm. Luckily for me, it sets the alarm off then freezes up. That gets you out of bed believe me
Click to expand...
Click to collapse
Maybe a new function from g-alarm .
I don't have the problems you (all) are having, even with g-alarm. It's working like a charm on my HD2 orignal WWE 1.66 rom.
You guys/girls got all patches etc installed?
What kind of patches?
Doesn't 1.66 come with them already in?
I'm using BsBTweaks 1.6.
I think mine might be a setting within GAlarm. I quite often get an error while setting up alarms, usually either when adding tracks or when I get right to the end and save it. But it is there and set up when I next go in. I'm using GAlarm 2.3.
Never had this problem with my HD2. However it happened often with my HTC Touch Diamond. Maybe it has something to do with a specific device, dunno. Anyway just in case I have one alarm set on my iPod Touch so there's always at least one device that will wake me up. Maybe you should hard reset your phone or smth... Did you tweak your soft in some way? Edited the registry?
just this morning, fir the first time, the alarm clock didn't trigger. Had it set for 8:40, all days of the week active, obviously alarm was active, vibration was off.
I had a gut feeling that it MAY not work, so I setup the other phone at 9am just in case... as expected, the other phone woke me up, the hd2 didn't... but no freezes nor anything, simply no alarm sounded...
same for me. hd2. it has to do with
1. the windows lock screen
2. galarm
3. backlight/device timeout settings while locked
BOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.
nothing like a frozen device MID alarm forcing you to pull the battery, and restart, etc
I have the same problem. But i will try something i found. Since the problem occurs occasionally I cannot reproduce the error and post a result. Maybe you can try and share the results too.
There's an option in G-Alarm settings that says "Turn backlight off during an alarm after x seconds". I will disable this feature.
I'm also using S2U2. This feature may interfere with S2U2.
Cheers
Well I am not using G alarm or any other app. Its just plain WM 6.5 alarm. I have tried it on 4 different ROM(stock) and other and I get same result.
If I don't reset my phone before going to bed at night, I will get this issue in the morning that my phone will be frozen during the alarm.
Any advice?
Try these, it should help freezing problems with htc hd2 and galarm
allthese settings are in galarm settings option
1)Disable "turn backlight off during snooze"
2) Disable "turn backlight off during an alarm after x secomds"
3)Disable "show flightmode function"
4) Disable "unlock the device"
I also have the same problem, sometimes the WM alarm fails to sound the alarm, the phone says that it has gone off, but no alarm sounds.
Have done some research, and it sounds like a fault with WM, the phone "wakes" its self at ~03:00 for 30seconds to schedule all its tasks for the day, BUT if it takes too long scheduling other tasks, it cant do the alarm call due to running out of time.
Hi,
the clock component has got a nasty bug:
1. Set alarm to now + a few minutes
2. Wait for screen to turn off
3. Press home button to look at the current time
4. Let screen go off again
5. THE ALARM DOES NOT SOUND!!
This could cause major chaos - luckily for me I just woke up half an hour later than was planned - I didn´t have to catch a plane or anything thankfully.
Phone is not rooted etc. original out of the box with a few extra apps and widgets installed.
Info. (from Android System Info. App):
1. Build: 2.1-update 1
2. Release codename: REL
3. Running Launcher Pro
Anybody else noticed this?
Cheers,
Mark
I´ve been scanning some forums and it has been suggested that using a taskkiller is a no-go. If that is right then something is badly amiss with the architecture - a non-rooted taskkiller should have no permission to kill, what I would expect to be root tasks such as the alarm.
MoWa22 said:
Yikes - that was a bit harsh. Just got an e-mail from the WSPA demanding me to apologize. I'm sorry, I'm very sorry, that I suggested that Korean mountain monkeys should be responsible for the coding at Samsung.
Click to expand...
Click to collapse
The monkies got really pissed off by your post. They don't give a **** about your phone, and you shouldn't imply that they do.
Sent from my personal Dis-organizer GT-I9000
Using it everyday and I tried several FW no issue
If you have a auto-task killer or you kill a lot clock it's sure that it won't work properly
get this one it's awesome
Alarm Clock PlusV2
http://forum.xda-developers.com/showthread.php?t=765081
it will turn on your speakers, no matter what
it can even TALK to you
it's fantastic!!!
markwil said:
Hi,
the clock component has got a nasty bug:
1. Set alarm to now + a few minutes
2. Wait for screen to turn off
3. Press home button to look at the current time
4. Let screen go off again
5. THE ALARM DOES NOT SOUND!!
This could cause major chaos - luckily for me I just woke up half an hour later than was planned - I didn´t have to catch a plane or anything thankfully.
Phone is not rooted etc. original out of the box with a few extra apps and widgets installed.
Info. (from Android System Info. App):
1. Build: 2.1-update 1
2. Release codename: REL
3. Running Launcher Pro
Anybody else noticed this?
Cheers,
Mark
Click to expand...
Click to collapse
Are you sure that the alarm is the problem?
Lately I experienced problems with the alarm, but the real problem is that the clock doesn't update! It freezes and then suddenly jumps forward to the right time.
My alarm was set to 0700, but when I woke up I immediately understood that I overslept. I looked at my phone and the clock showed 06:48 and I was confused. A few seconds later the clock changed to 1003 which was the right time.
This problems has encountered many times, which makes the phone useless as an alarm clock.
Been using the alarm every morning for the past 2 months now, without any problems.
I also use launcher pro, and have advanced task killer set to aggressive, though with alarm in ignore list. I can press home button to check time after alarm is set, and the alarm will go off as planned.
The only minor thing I'm encountering is that I sometimes find myself turning off the alarm completely by pressing the stop button when the smooth alarm goes off, while still half asleep, when in fact I want to snooze until the real alarm goes off. I somehow need to train myself to press the home button when waking up at the first alarm...
Sent from my GT-I9000 using XDA App
iammichel said:
The only minor thing I'm encountering is that I sometimes find myself turning off the alarm completely by pressing the stop button when the smooth alarm goes off, while still half asleep, when in fact I want to snooze until the real alarm goes off. I somehow need to train myself to press the home button when waking up at the first alarm...
Click to expand...
Click to collapse
I used to do this myself, so I now have three alarms set to go off within five minutes of each other. So far I haven't managed to stop all three.
The bug that i have experienced is that If i wake before the alarm rings and i off it manually by going into "clock" the alarm still rings on the time ive set. Happened to me twice so far and i'm very sure that i have offed the alarm as the alarm sign in the taskbar was not there. The bug only occurs when i set the alarm overnight, If i set it for 2 mins from now and off it halfway, it deosn't ring which is correct.. but leaving it overnight, then waking up myself and offing it, it still rings when the time ive set the night before has reached...
I have this nasty bug with alarm. If I didnt dismiss the alarm, after awhile the alarm screen disappear. After that the screen wont turn off even if I press the power button. Have to klill the clock.
Itsme87 said:
Are you sure that the alarm is the problem?
Lately I experienced problems with the alarm, but the real problem is that the clock doesn't update! It freezes and then suddenly jumps forward to the right time.
My alarm was set to 0700, but when I woke up I immediately understood that I overslept. I looked at my phone and the clock showed 06:48 and I was confused. A few seconds later the clock changed to 1003 which was the right time.
This problems has encountered many times, which makes the phone useless as an alarm clock.
Click to expand...
Click to collapse
Had the same issue, but after disabling "Automatic (Use network provided values)" it's worked fine.
The only reasons that I found that could freeze your phone is too low cpu with setcpu or auto task killer ...
Alarm
Hi,
I disabled all task killers etc. yesterday and set the alarm (with my old mobile as backup!). It worked - I pressed snooze but the alarm did not sound again....
A colleague experienced my original problem this morning and arrived late for work...
My main issue with the sgs is that a "root"-system task like the alarm should not be killable by any other app. not posessing root rights.
Sure I could add the alarm app. to the ignore list of my task killer but it feels wrong and should be unnecessary.
I´ll try the other alarm apps. recommended (and add them to the ignore list of my task killer as they are not native sgs "system" apps.).
Cheers,
Mark
i use the alarm every single day and i dont think i have your issue, and by that i mean i dont ever do the steps that you listed.
the only time i had the alarm not come back on after hitting snooze is when i used the smart alarm. since i dont use check the smart alarm box i have no issues, and i hit snooze 3-5 times every morning!
i did have an issue with the alarm not going off at all and i figured out that if i set an alarm, then pressed the back key while in the alarm app it would close the app and the alarm wouldnt work. just before i go to bed i open the alarm app then press the home button (while the screen is still on) and i have not had an issue in over two weeks.
i do not use task killers any more. i do use the built-in task killer to kill the music player or any streaming apps or i just press the back key while in any other app that i dont want running in the background and my device runs great
No problems here.. Been using my SGS for 3 Months, I've set 3 alarms in the morning M-F.
using Stock FW XJF4 and TaskPanel (task killer)
Hi,
I am also experiencing the same alarm bug.
When i set it and leave the phone unused for a couple of hours it doesn't go off in the scheduled time (and not even after I turn on the screen).
Also the clock doesn't update....for 1-2 seconds after turning on the screen it shows a past time!
I 've searched elsewhere and the problem might be that the phone goes into a deep sleep/suspend state and the alarm app cannot wake it, only by manually turning on the screen.
One solution is to leave it connected to the charger all night, so it doesn't go to deep sleep.
The thing is that i cannot recall having this problem before rooting the phone with OCLF 2.0.
I am wondering if RyanZA's minfree has to do something, and if it is possible to exclude the alarm/clock app from ever being killed.
I am using the latest standard firmware JF5 and Android 2.1 update 1
I've not had that issue, but I'll tell you one thing I've had happen once or twice... if I set the countdown timer, the lock screen sometimes appears over the top of it when it goes off and then when you unlock it, you are just greeted by the home screen and not the clock, despite the thing going off, so you can't turn off, and you can't even switch to the task because trying to do so opens another clock - so you end up having to kill it with the task manager.
I'd actually forgotten about that little bug when I was ranting in another thread.
I've said it before though - I would NOT rely on this phone for anything mission critical.
the stock alarm is crap, don't use it at all
use the app i suggested above, it beats all any other alarm apps hands down
http://forum.xda-developers.com/showpost.php?p=8124064&postcount=44
AllGamer said:
the stock alarm is crap, don't use it at all
use the app i suggested above, it beats all any other alarm apps hands down
Click to expand...
Click to collapse
No good...
Clock still doesn't update during deep sleep/suspend mode and AlarmClock rings only when you switch-on the screen.
Any other help/suggestions?
PDA: JG1
PHONE: JF5
CSC: JF9
OCLF: 2.0
minfree: moderate
i also have the alarm clock problem since day 1 ..
now it's better with fw jm8 anyway...
i don't use taskkillers etc..btw..
but still i had 2 alarm occations that it missed..
i'm thinking it maybe could be amount of available ram that is the cause?
the 2 times alarm have missed is when i have i have forgotten to clear ram using the samsung task manager..
u who have problems....how much available free ram u have?
and have you changed the snooze settings?..(i'm thinking this also could be the problem.... hmmm )
cheers!/H
Right, my alarm seems to be playing up on the HD2. I have the alarm set in the week only Monday - Friday.
As I don't work weekends, I turn the alarm off, and DID double check this last night. But this morning @ 3,40am the Alarm went off?
How is this possible, when I physically turn the alarm off? Getting really on my nerves now if im honest.
happens to me too, seems to come and go.....
hard reset wont resolve it either....
edit;
hard reset probably did resolve it but it occured again after reinstalling all the stuff that I deem "essential"
so its probably caused by something in there....
I really cant think of any link between what I have installed and the alarm function......
That's why I use the old free version of gAlarm still. Windows alarm is unreliable. gAlarm wakes me up every time I want it to, and never when I don't.
Since the old version that I have is freeware, but the app has since become payware, I'm not sure if I can post the cab.
If I can get confirmation from a mod, I'd be happy to attach it for you
I've no answer to this other than to use SPB Time,G-alarm or Klaxon
All 3 work just fine...
I solved the problem with a £3.99 clock radio
I have NO issues at all with the alarm, BUT I set it up using the control panel not via the Manila home page, It's not failed me in months, the snooze (every 5 minutes) works, and if I leave it on it repeats every 45 seconds until I get fed up with it (normaly between 3 and 7 times)
All three alarms work, and I can set a different alarm for each of the 3
I also suffer this problem, the alarm is unreliable.
I heard you can fix it by turning off sense and setting it in windows because these values would become out of sync, but have not tried.
Klaxon resulted in crashes for me, resulting in the alarm (an mp3 file) not going off.
Just be warned in advance.
reijkelhof said:
I also suffer this problem, the alarm is unreliable.
I heard you can fix it by turning off sense and setting it in windows because these values would become out of sync, but have not tried.
Klaxon resulted in crashes for me, resulting in the alarm (an mp3 file) not going off.
Just be warned in advance.
Click to expand...
Click to collapse
There's another alarm bug thread here where it has been tested and confirmed that it's not a sense related issue. It's Windows.
It has been said that changing volume settings after setting your alarms has a big effect on whether the alarms will behave as expected, or go off at all.
Seems changing your volume after setting the alarms messes things up, and so does having pending appointments, as Windows will play your reminder right before the alarm goes off, messing things up too.
I'm gonna go ahead and post gAlarm v1.51 in a while,after my kids go to bed. If any mods/admin have a problem with it, I'll take it down. I think it should be ok, since that version is freeware
EDIT: Here ya go guys. Hope I'm not breaking any rules here.
You might need .netFW3.5 to install/run it.