Database Develop

Anyone else having problems with alarms on 2.2??

So I have been using my phones as an alarm clock for many many years now. I do it the same way every night. I go into the alarms and change the time and press save. BUT with my 2.2 update, instead of saving for the next day, it saves the alarm as that time but a week away. Its like the day counter doesn't move. I almost missed class this morning because I forgot to move the day I needed the alarm for so I woke up to no alarm 10 minutes before class and seeing my alarm set for next Tuesday.
Anyway...am I missing something?? Or is this a but that others have noticed. It is hard to remember to set the day when I have never had to do this before.
Sent from my SAMSUNG-SGH-I897 using XDA App

Same with me, seems the clock got messed up with 2.2. The day doesn't change when I choose the alarm. Also, it's happened before where I have the right day (it says alarm will go off in 8hrs etc.) but when I wake up the alarm is still set, but now for 7 days from now... It is very annoying, and I can't rely on it now.

So when you created the alarm, did you set the alarm repeat to be daily? Just a thought otherwise the default is a one-time event and when you resave it will bump a week.

i dont want it as a daily alarm...if i go in and set the alarm time, and press save, it should update the day also. It has been that way for years of setting alarms on many different phones, and now that i updated to 2.2 it doesn't update the day. Why would i want to set an alarm for a week away? haha

You don't make it active on the days you don't want it. A one-time event sees that the time is past and makes it a week later. Don't ask me, complain to the coder. lol

Justinph5 said:
Same with me, seems the clock got messed up with 2.2. The day doesn't change when I choose the alarm. Also, it's happened before where I have the right day (it says alarm will go off in 8hrs etc.) but when I wake up the alarm is still set, but now for 7 days from now... It is very annoying, and I can't rely on it now.
Click to expand...
Click to collapse
and yes...these are the exact problems i have, except mine has gone off the days i set the day corerctly, it has yet to NOT go off if i set the day correctly.

cappysw10 said:
You don't make it active on the days you don't want it. A one-time event sees that the time is past and makes it a week later. Don't ask me, complain to the coder. lol
Click to expand...
Click to collapse
a one time alarm on 2.1 worked perfect and exactly as expected. I shouldn't have to make a new one-time alarm OR change the day OR set it as a daily. I wake up at different times almost everyday. No offense, but i don't need instructions on how to set up my alarm!
i know how it works and how it should work, i'm asking if anyone else is having the problem.

I dont have this problem.
I do have a related problem. Its called a job. And I use my phone as my alarm to wake up every weekday morning at the same time. my alarm works great. Since I do not use it for a one-time alarm, it must have something to do with that.

Pirateghost said:
I dont have this problem.
I do have a related problem. Its called a job. And I use my phone as my alarm to wake up every weekday morning at the same time. my alarm works great. Since I do not use it for a one-time alarm, it must have something to do with that.
Click to expand...
Click to collapse
cool man

Here's a description of the change:
On 2.1, clicking on a past "one time alarm" would change the day automatically to the following day, so the alarm worked for the morning you activated it on.
On 2.2, clicking on a past "one time alarm" won't change the day automatically to the following day, so the alarms' day must be set manually for the next morning.
Anyways, does someone have the 2.1 clock apk that they can upload here that we could try, and see if that's the problem?

This does not seem to be an across the board issue. Im one that does not have the issue.

Justinph5 said:
Here's a description of the change:
On 2.1, clicking on a past "one time alarm" would change the day automatically to the following day, so the alarm worked for the morning you activated it on.
On 2.2, clicking on a past "one time alarm" won't change the day automatically to the following day, so the alarms' day must be set manually for the next morning.
Anyways, does someone have the 2.1 clock apk that they can upload here that we could try, and see if that's the problem?
Click to expand...
Click to collapse
I flashed back to JH7 today. Posted for your amusement!

Ehh, the 2.1 Clock doesn't work with 2.2 from just replacing it, oh well... Maybe they'll fix it with the final build.

Justinph5 said:
Ehh, the 2.1 Clock doesn't work with 2.2 from just replacing it, oh well... Maybe they'll fix it with the final build.
Click to expand...
Click to collapse
Figured as much, system apps have to be different. Worth a try!

[Q] Alarm not working

I have SGS - official f/w 2.1 via KIES.
In UK on an unlocked phone, with Vodafone SIM.
Set alarm (standard clock) ... and it does not work if phone switched off ! .... i.e works OK if phone is switched on ... but not if phone is off, which is normally how I would leave phone overnight.
I amazed, my 14 yr old Nokia does this no problem ! ..... I googled around and on some other Samsung phones you can fix it under profiles ... but can't find a solution for SGS .
This seems a significant bug, or at least an oversight - can't belive anyone would design it to work like this on purpose.
Any work around ?

Even with my SGS turned on, 4 times out of 5 the alarms do not go off. I think the alarms have a bug.

Probably you have a task killer ending the alarm.

the phone must be on for the alarm to function .
the alarm cant switch on the galaxy s , says it in the manual

Alarm Bug
mayhem2408 said:
Even with my SGS turned on, 4 times out of 5 the alarms do not go off. I think the alarms have a bug.
Click to expand...
Click to collapse
Happened to me this morning as well alarm comes on but no sound,i called my phone and volume works....

I don't have that issue but i recommend you try another alarm app such as "Alarm clock plus" is a good choice.

[Q] Alarm Clock doesnt work in the morning

Anyone else having problems with the alarm clock?
I set 2 alarms to wake me in the morning and they dont activate until i touch the phone in the morning
I have to use a old wildfire for an alarm clock.
I also tried the AlarmDroid app from marked but it didnt work either. I tried to test the alarm in the evening one night and it worked fine. I usually charge the phone each night but that cant have affected the alarm can it ?

I have they exact same problem. Phone didn't gold off this morning until I touched they phone. Anyone got a fix for this ?
Sent from my LG Optimus 2X using Tapatalk

Could it be juicedefender that does something ? Gonna try killing it tonight...
Sent from my LG Optimus 2X using Tapatalk

Juicedefender or a taskkiller probably killed the clockapp
Exclude clock app or stop using taskkillers
Sent from my LG-P990 using XDA App

soulgrip said:
Could it be juicedefender that does something ? Gonna try killing it tonight...
Sent from my LG Optimus 2X using Tapatalk
Click to expand...
Click to collapse
it is juicedefender. had the same problem on my sgs i9000.

I had the same problem, but i don't use any taskkiller ...

I have experienced it too. But only once. No taskkiller, root, custom rom or anything weird.
This phone is far from finished for release!

I tried this once and did not figure out the problem. It has not done it for about 2 weeks now.
Thinks the problem was my lockscreen app maybe.

CenaDK said:
I tried this once and did not figure out the problem. It has not done it for about 2 weeks now.
Thinks the problem was my lockscreen app maybe.
Click to expand...
Click to collapse
Mine did it this morning without lockscreen. Uninstalled juicedefender now. Checking if that makes I difference...
Sent from my LG Optimus 2X using Tapatalk

soulgrip said:
Mine did it this morning without lockscreen. Uninstalled juicedefender now. Checking if that makes I difference...
Sent from my LG Optimus 2X using Tapatalk
Click to expand...
Click to collapse
Alarm worked today. Guess it was juicedefender.
Sent from my LG Optimus 2X using Tapatalk

Mine worked this morning (Running on Pauls FR8)

Another user on a danish forum experienced the same thing as I did:
One day the alarm just did not work.
No juicedefender, taskkiller, custom lock screen, root, custom rom. Just plain stock LG.
Neither of us was able to reproduce the problem. So it is not very likely that your lockscreen, juicedefender or whatever is responsible. Otherwise it is very easy to check. Reinstall juicedefender etc. and verify that it indeed prevents the alarm from working.

had a similar problem.
have to make some more test but maybe the problem is "flight mode".
When the phone was set into flight mode the alarm clock doesn't work.
If i let the network connected it worked.
will test it for some days to see if i can reproduce it.
net

Mine fortunately went off this morning. It was on charge at the time too and had been all night... Amazed it hadn't crashed or something! haha! Bloody thing scared me ****less though. These O2Xs are much louder than my little Hero.

my 2x alarm works great in flight mode..

netrunner7 said:
had a similar problem.
have to make some more test but maybe the problem is "flight mode".
When the phone was set into flight mode the alarm clock doesn't work.
If i let the network connected it worked.
will test it for some days to see if i can reproduce it.
net
Click to expand...
Click to collapse
it is not the flight mode. the alarm clocked work till today without problems, but this morning it stopped working. I did not changed anyting.
very strange. some solutions or some informations from LG ?
thx net

Same issue for me.
With v10a and with v10b, in a totally random way
It's a real pain, because I ever need something different to wakeup.. especially when I'm out of my home.
If you have an alarm that can't wakeup you when it's needed (and you can't know when it don't ring!) is totally and really useless!
Anyone found the trick?
I've tested it many times.. but no way. I can't find the magic combination.
It's not a taskkiller issue, it's not a app issue, it's not am hard reset issue..
The only state I need to try is:
- Phone with a partially discharged battery.
- Connected to the socket for a night charge session
- Airplane mode
- Manually locked

Could the system have killed the process to gain resources? (Do you have a ****load of running apps?)

No memory issue, I think.
I put my phone in airplane mode when sleeping, with a task killer (system process and some apps in exclusion - included the alarm process) that run every 30mins.
I suppose that we have an issue linked to some system process that wait for an user input or that simply lock the system for a strange reason.
I'm aiming to the message box that appear when the phone is under charge and it reach the 100%: "battery charged, disconnect it to save energy [ OK ]".
Something like.. screen locked, the phone stop charging, message pop up.. and than the message box take the full control of the system, waiting user input.. without system messages processing ; so not an app related issue but a system bug, related to this specific message. It's possible?
Everytime the alarm not fired, I noticed the clock was not updated and that it updated itself immediately after unlocking (and the alarm fired if the alarm time is not so far).
what do you think?

Had the same problem, stock rom V10A with Launcherpro.
No other system/utilities apps running.
But interestingly, it only happened once (1st day of using O2x). The alarm went off fine the next few days.

[Q] Alarm Clock going off late

This is my first post/question.... ever here, so go easy on me. I've been searching the interwebs and can't seem to find anything similar to my problem.
As background (may not mean anything), a few days's ago I downloaded the new Bitspin Timely alarm clock after news of Google's purchase. At some point I made it the default clock when Google Now asked for the program to use when setting an alarm. I swear the alarm worked once or twice before all of this, but can't remember now.
Whatever happened, my morning alarm doesn't go off on time. Its always about 25 min late (sometime after I've woken the phone from daydream). I even tried switching back to the regular alarm clock, and it wont go off in the morning on time. Uninstalled Timely, still no dice.
The kicker is that when I test it during the day, everything works perfect. It's like the phone goes in to such a deep sleep (that's a thing, right?) overnight that it just doesn't catch the time in the morning. Thankfully I have a decent internal clock and have had the privilege of just watching the time pass the alarm time and nothing happen. My other thought was that maybe its related to Moto Assist. I set the do not disturb, but its set to end well before my alarm goes off. I've cleared its data and disabled that for tonight to see what happens.
I REALLY don't want to factory reset. And I can't root to use some of the detailed monitoring apps because my company makes us use that stupid Good for Enterprise.
Anyhow, if anyone has any thoughts, I'd appreciate it.

Haven't tried out my alarm clock yet but will set it up for tonight and see what happens. Hope that it works or I'll have to buy an alarm clock for my dorm room.
Sent from my SCH-I925 using Tapatalk

I'm just throwing this out there. Under Settings > Date and Time> is Automatic time chosen? Is the correct time zone chosen? Is it off by 25 minutes to your time vs you set it at 0600 and it goes off 0625?.

When in doubt try clearing the App Data and try again. I'd suggest testing the alarm before going to bed of course I use Timley too and have no real issues with it yef
sent from my Moto X

I thought I had this fixed... worked perfect the night after I cleared cashe/data from the clock, timely, and moto assist. I even disabled the quiet time on the moto assist app. Worked great through Tuesday, but then yesterday it was 4 min late, then 35 min today. Its also a bit strange that when I look at the Timely widget, it was a little under a min behind the system time. I'm sort of at a loss at this point. Would this be software, or possibly hardware?

Pkolb79 said:
I thought I had this fixed... worked perfect the night after I cleared cashe/data from the clock, timely, and moto assist. I even disabled the quiet time on the moto assist app. Worked great through Tuesday, but then yesterday it was 4 min late, then 35 min today. Its also a bit strange that when I look at the Timely widget, it was a little under a min behind the system time. I'm sort of at a loss at this point. Would this be software, or possibly hardware?
Click to expand...
Click to collapse
just curious what's wrong with the built-in alarm clock? i've been using it since it's been bundled with android and it works great.

I love the stock alarm clock as well. I should have been more clear with the issue. I tested both the stock and Timely alarms and both seem to suffer the same issue. So I don't think my problem is with the app itself, but rather however the alarms work.
Sent from my XT1053 using XDA Premium HD app

Pkolb79 said:
I love the stock alarm clock as well. I should have been more clear with the issue. I tested both the stock and Timely alarms and both seem to suffer the same issue. So I don't think my problem is with the app itself, but rather however the alarms work.
Sent from my XT1053 using XDA Premium HD app
Click to expand...
Click to collapse
I've been using Alarm Clock Plus (paid) and haven't had any problems with it setting off alarms at the set time.

I've been using Timely and the stock alarm with no issues on a nightly basis. It seems odd that yours isn't going off on time. Timely and the stock clock are always in sync on my Moto X. It sounds to me that you have no other choice but to try a factory reset. There is a glitch in the system somewhere.

Resurrected
I hate to resurrect an old, dead thread, but consider this one resurrected. I just had this exact same problem occur with my Samsung Note 2. The alarm went off late, (both stock alarm clock and Timely), and it's incrementally getting worse. I'm running an unofficial version of Lollipop, but the alarms worked perfectly up until this weekend.
Anyone have a solution, yet?

PlaidRadish said:
I hate to resurrect an old, dead thread, but consider this one resurrected. I just had this exact same problem occur with my Samsung Note 2. The alarm went off late, (both stock alarm clock and Timely), and it's incrementally getting worse. I'm running an unofficial version of Lollipop, but the alarms worked perfectly up until this weekend.
Anyone have a solution, yet?
Click to expand...
Click to collapse
I was having this problem. Thought it was Amplify or Greenify. Tried everything. Then..... I discovered that somehow DayDreams was turned on. I turned it off and it immediately solved the issue for me.

Unfortunate
That is truly unfortunate to hear, as I use Timely and my clock with the Daydream function of Android every day. I dock my phone, and Daydream immediately kicks in the Timely clock as my sleeping screen saver. I will test this out to see if it's the problem.

So my Phone crashed at night, no alarm in the morning

Received the P4XL yesterday and set it up. Put up an alarm in the morning but the phone crashed in the night and no alarm ring in the morning.
the phone Was half alive, App drawer worked but wasnt able to start any apps (only Black or blank screen). After reboot all the missed alarms showed up.
Anyone else noticed something like this?

I've had this happen with my Pixel 3 and other phones.
It doesn't even have to be a crash, it can be as simple as a reboot. It seems that Android's alarm scheduling doesn't kick in until the phone is first unlocked after a restart, so if anything causes your phone to restart overnight, no alarm. I've been late for work more than once because of this.
Samsung phones in particular let you schedule a weekly automatic restart for maintenance purposes; on all my Samsungs I have to make sure to schedule it for a night where I never need to have an alarm go off the next morning.
I have also had bugs with Do Not Disturb blocking alarms even though I set it not to. It's rare, but it happens.
I have been using phones as my alarm clock for years, but it's always a bit of a gamble. So many things can go wrong.