Related
Hello all!
I wonder if its possible to have an alarm on the phone when turned of. Ive searched everywhere for some answers.
I want to shut down the phone at nights and I want the phone to start up and wake me up hehe
I just tried it 2 times , and it doesn't seem to work with klaxon.
Sorry mate i think you should keep it on if you don't want to be late tomorow
Its hilarious that a phone this new doesnt support that kind of alarm. All of my other phones works that way....
It's not a phone, it's a smartphone, pretty much a small PC...
So if you poweroff your desktop, usually not much it can do
That's the same, workaround is to use PlaneMode (along WirelessTime freeware in example)
This way, it wont be off at all..
Like for PDA, you usually never power off this kind of system. You put it in standby mode instead (either automatically or manually)
And the alarm works well with the HD is in stanby mode. It will wake up and ring.
Note that the usual phone are in some kind of standby mode, not fully powered off otherwise the alarm wouldn't work either !
you can switch off the phone part in standby mode and it will give you busy signal though reminders and alarms will work.
The whole point of setting the alarm is that you can just leave it and know that it will go off at the assigned day and time. Unfortunately, it is just not reliable at the moment. I have already been late for work once, and have gone back to using my WinMo phone for the alarm, as at least that works every time.
It does seem to be an Android issue, I have seen it mentioned on other forums for other handsets, but I want to track down exactly what might be causing it on the Hero, and if there is a work around until HTC/Android releases fix it.
First off, the screen is switched off, but the phone is stil powered on, just like any other phone when you have the alarm set.
When I got the phone on Thursday, I set the alarm for Monday through to Friday, 10.30am.
Friday morning, the phone wakes and the alarm goes off at 10.30. Fine.
Monday morning, nothing happens. Go into the settings, check alarm set for the correct time and day, all is fine, it just didnt go off.
Tuesday morning, it works fine, phone wakes and alarm goes off at 10.30.
Wednesday morning, nothing. WinMo phone alarm wakes me at 10.34. I switch on the Hero's screen, and immediately the alarm goes off, 4 minutes late!
Last night I didnt charge it, thinking it may be an issue when being charged. But this morning it didnt work, so it is not an charging issue.
The Alarm icon was showing the top corner, so the alarm was obviously set, and the Clock App was still running (I checked in Advanced Task Killer). I will try to set it again tonight from scratch, and see if that works.
Having to set it every night would be a pain, but at least it would actually work like it is supposed to.
I've got the same issue and was about to get late for work this very morning just because of it. Luckily me I've got some sleeping disorders so I woke up before the clock should have went of either way...
HTC Needs to fix the clock in their TouchFLO..
Got somewhat the same problem...
Could a hard reset help?
A hard reset didn't do the trick for me. I really need the alarm clock to work so I think I'll buy an alarm clock app on the market, but I shouldn't have to ...
If you are using taskiller or advanced task manager, make sure you exclude the clock app from killed processes. I had this problem, when the clock came back after being killed the alarm wouldn't work even though the icon was there. Excluding it fixed it.
Cheers Ewans, i was killing the clock process and it was this that stopped my alarm this morning. Made me late! Still, i forwarded my boss this link so he could read himself. (Not that he was mad. He's a great boss!)
We should maybe think about making a list of processes, what they do and what you can/can't kill.
For instance, i don't use the Twitter widget as i find the notification bar and having Peep on my home screen just as quick and less resourceful hungry. But if you kill Peep sitting in the background, it will stop any notifications, so this needs to be left alone.
Even if I don't kill it (noticed that too), it still fails to go off sometimes.
Yes, it is not totally obvious what is going on yet.
The fix (based on one days trial!) seems to just before I sleep to go into the clock app, disable the alarm, then immediately enable it again.
This results in the "Your alarm will sound in 7 hours 10 minutes" type message.
That worked this morning, the question is if I leave it alone now, and dont kill the clock app, will it still work tomorrow? And if I restart the phone, will the Clock app and then the alarm still be running or do I have have to go into the Clock App manually?
If my clock is showing on the home page, and the alarm icon is in the top bar, I expect the alarm to go off.
It should not be possible to kill the alarm process, it shouldnt be part of the clock app at all, but a separate background process with settings controlled by the clock app, but not reliant on the clock app running.
This is what I've found out.
When you program your alarm for multiple days, it only sounds the first day.
If you uncheck and check your alarm, it will go of the next day.
This is without using TasKiller or something similar and without resetting. (just did nothing)
It looks like the multiple day option is a fake and you will have to set it every day. Allthough I haven't tried out multiple alarms, thinking about seven alarms, but you'll have to reset at least once a week.
Good luck waking up
Alarm works fine for me now, I use one for weekdays that goes off everyday, and another just on Sundays at a different time. I'm using a standard G2.
Check out the alarm volume settings.
The alarm has its own volume setting which can be change when you are inside the clock app and select the ringtone for an alarm (by pressing the standard volume up/down keys).
By accident mine was set to lowest value so it didn't go off but just vibrated.
Ok, after a week of testing, it seems that if you dont bugger around with killing the clock app via Task Killer or something else, it is fine.
I havent yet seen whether it will still be set if I completely switch off and switch on again. I will try that tonight. Even though alarm icon is shown, will the alarm be set without me going into the Clock app explicitly?
Works for for me, 2 alarms set for 6:15 & 6:30am mon - fri, never had an issue.
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
I use Timely as my timer for my breaks at work. Also I use it as my alarm to wake up. At first I couldn't get the countdown timer to show in the notifications or update as it counted down.
After going into power managagement and turning off all power saving policies, I could see the timer countdown but only until the phone locks. Once locked it won't show the timer at all. The alarm I set is the same way it didn't go off or wake up phone, but as soon as I hit the power button to turn on the lock screen then alarm went off.
I've tried turning off smart power-save all together as well with no luck. I use smart lock so my phone shouldn't even lock when I'm at home but still didn't work.
Any other ideas or features to that I could try ? I've been using Timely for the past couple years on multiple android devices and never had this issue before. Any help would be appreciated.
I use Timely without any issue and it wakes me up every morning . What device are you using? What ROM? root? Xposed? Any battery saving app?
Yep.
Yes, I've been using Timely on every Android for the past 3 or 4 years. It miserably failed on the Axon 7. Every measure I took came to no avail. Uninstalled. Anyway, they stopped updating it on February 2015. Using "Alarm Clock Xtreme Free" currently.
Yurik46 said:
I use Timely as my timer for my breaks at work. Also I use it as my alarm to wake up. At first I couldn't get the countdown timer to show in the notifications or update as it counted down.
After going into power managagement and turning off all power saving policies, I could see the timer countdown but only until the phone locks. Once locked it won't show the timer at all. The alarm I set is the same way it didn't go off or wake up phone, but as soon as I hit the power button to turn on the lock screen then alarm went off.
I've tried turning off smart power-save all together as well with no luck. I use smart lock so my phone shouldn't even lock when I'm at home but still didn't work.
Any other ideas or features to that I could try ? I've been using Timely for the past couple years on multiple android devices and never had this issue before. Any help would be appreciated.
Click to expand...
Click to collapse
ohc1492 said:
Yes, I've been using Timely on every Android for the past 3 or 4 years. It miserably failed on the Axon 7. Every measure I took came to no avail. Uninstalled. Anyway, they stopped updating it on February 2015. Using "Alarm Clock Xtreme Free" currently.
Click to expand...
Click to collapse
I have the Axon 7, stock with b29 software, not rooted. I'm going to give Alarm Clock Xtreme a try tonight and see what happens.
I use Timely and it's randomly off by as much as 8 minutes. Usually it's 4 minutes late when the alarm goes off. And no I'm not sleeping through 4+ minutes of an alarm, my alarm is a song and I wake up right from the start of it. This is annoying since it forces me to set my alarm to earlier to make sure I'm not late, but then sometimes it does work on time so I've woken up a little early for nothing.
It's always been like this for me, before bootloader unlocking, before root, before Xposed or anything. Now I'm BL unlocked, rooted, with Xposed, etc, installed and I'm still having the exact same issue. B29 of course, prior versions had the same issue.
Alarm clock Xtreme did work for me last night with no issues. Woke the phone right up even with Smart power save enabled, and allow deep sleep in the power management features turned on. (That's how it was configured at install, and I didn't change anything)
I will miss some of the features of Timely, but I guess it's time to move on if they're no longer supporting it.