who has problems with the alarm not ringing on time
I have tried reset and clean flash and no solution to the problem that happen sometimes and other times the clock ring on time
arfaoui said:
who has problems with the alarm not ringing on time
I have tried reset and clean flash and no solution to the problem that happen sometimes and other times the clock ring on time
Click to expand...
Click to collapse
Its always possible for the clock app to have a problem and need an update or for the OS to have a problem and need an update. At least make sure in the Samsung store that the clock app is fully updated.
The part of Android and the clock programming for time specific stuff is delicate and so problems are more likely. Because of the high rate of change with OS's, things break repeatedly. Its an effort of futility
Related
Hello,
My phone has been doing this weird thing where my system time would go back about 20 days. This would occur randomly and for some reason would only occur in the morning around 7-9am(pacific time). Eventually it would revert back to normal. It is extremely annoying when it happens because:
- My morning alarms create about 20 instances of themselves.
- Games dependent on system time(Happy Street, Farmville, etc.) think I'm cheating and I can't play them anymore.
- My android tasker resets and causes my phone turn off silent mode while I'm at work.
My phone specs are:
Verizon Galaxy S3(SCH-I535)
Synergy Rom v1.7(Android 4.0.4)
There are some things that may need to be considered such as:
- I upgraded from Synergy 1.6 to 1.7 w/o doing a full wipe. Just your typical cache wipes.
- I have android tasker v1.3.1m
- I tried doing the GPS fix on the android development forum. Since then, I have had trouble with syncing to my google account. Random disconnects, etc.
I'm trying to figure out if any one of these may be the cause, but I vaguely remember the exact date I updated to 1.7 or when I tried doing the GPS fix. Any ideas out there?
Thanks in advance.
So I turned off android tasker to see if this incident would happen again and it did occur again. I can mark off android tasker as the cause of this.
lawpnoy1 said:
So I turned off android tasker to see if this incident would happen again and it did occur again. I can mark off android tasker as the cause of this.
Click to expand...
Click to collapse
I would revert back (you did make a backup , right?) if you have a nandroid backup restore it if no backup factory reset and flash the old 1.6.
Then if you still have the problem you've ruled out just about everything you've said you did and you may have some bad HW.
Did you try to fix permissions? It is a long shot, but, you never know.....
Sent from my SCH-I535 using xda premium
Thanks for the suggestions, though I would like to try and not have to revert to my backup.
However, I did find that after uninstalling the alarm app I use(alarm droid), my system time did not malfunction so far. I will keep the post up to date on this for the next week or so to see if that may have been the cause.
I'm thinking that when I upgraded to 1.7, my alarm profiles in the alarm droid app may have malfunctioned and thought there was an alarm on a date prior to upgrading. When the alarm would activate, it would change my system time, but after a few seconds would revert to the correct time since it's getting pulled automatically from the network. We shall see.
lawpnoy1 said:
Thanks for the suggestions, though I would like to try and not have to revert to my backup.
However, I did find that after uninstalling the alarm app I use(alarm droid), my system time did not malfunction so far. I will keep the post up to date on this for the next week or so to see if that may have been the cause.
I'm thinking that when I upgraded to 1.7, my alarm profiles in the alarm droid app may have malfunctioned and thought there was an alarm on a date prior to upgrading. When the alarm would activate, it would change my system time, but after a few seconds would revert to the correct time since it's getting pulled automatically from the network. We shall see.
Click to expand...
Click to collapse
Don't know why an alarm clock would ever need to change your time but good luck.
If not you can make a backup and then revert. If that doesn't fix you can revert back to the broken one. But going back is the fastest way to figure out if it was your changes or even the ROM that caused the problem.
Piiman you're right, the alarm clock has nothing to do with it. It went back in time this morning again to September 3rd. I will go ahead and try backing up and restoring an older instance of the ROM when I have some extra time on my hands. Thanks for the support and I'll keep everyone up to date on this issue.
lawpnoy1 said:
Piiman you're right, the alarm clock has nothing to do with it. It went back in time this morning again to September 3rd. I will go ahead and try backing up and restoring an older instance of the ROM when I have some extra time on my hands. Thanks for the support and I'll keep everyone up to date on this issue.
Click to expand...
Click to collapse
That's to bad but good luck with the next step.
It may well be something is broken though HW rise. Normally you would have several reports of the problem if its was a ROM. I can't remember what else you said you changed but if that's un- doable you may want to start there. However like I said previously I'd just revert back. You may even consider going all the way back to Stock, if it happens then you can just call VZW for your replacement.
Ever since I got away from Sense and started using the Jellybean clock app, I am having particular difficulties with the countdown timer feature of the clock app. I have found that no matter what I do, I can't get it to make a sound when the timer reaches 0. The screen will turn on, so if I can see my phone I notice it, but otherwise it's pretty useless.
Also, I have noticed that occasionally when I start a timer, it will stop counting part way through by itself.
Anyone know what might be going wrong?
I've never had this problem but you can try deleting the clock, reflash the 4.2 clock, wipe dalvik, and see if it fixes anything.
Here's the zip for the 4.2 clock
http://db.tt/KK9Qp83a
Hello, i have my nexus 5 for 2 weeks now and I noticed a problem my friend with a N5 doesn't have.(or anyone else) At night, right before I sleep i put my phone on silent so i dont get awakened by calls or anything else . But if i set it on silent the alarm volume gets on silent as well.
Seriously, i didn't have this problem on any other device and everyone sets his phone on silent for obvious reason. I had android 4.2.2 on my older device and even there you could tick "Alarm on silent".
What's causing this bug?
Stock Android 4.4.2
Edit: this is a basic feature every phone has, please dont suggest me getting 3rd party alarms from the google play store, thanks.
Try checking the alarm volume in settings and see if it changes when you put the phone in silent/vibrate.
It shouldn't.
Yes, when i put it on vibrate/silent i cant even scroll the alarm's volume in settings , it goes straight to no volume.
There's a post with users complaining about the exact opposite. They want to know why the phone isn't 100% silent when in silent mode. This would contradict what's happening to you.
Sent from my Nexus 5 using Tapatalk
bblzd said:
There's a post with users complaining about the exact opposite. They want to know why the phone isn't 100% silent when in silent mode. This would contradict what's happening to you.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok, what can i do to repair this bug?
I just tested this on my Nexus 5, and I can confirm that this is NOT happening on mine. Setting the phone to vibrate or even silent has no effect on my alarm setting whatsoever. (See the attached image. Note the vibrate icon in the notification bar.)
Do you possibly have a third-party alarm or other sound-controlling app installed? You say your phone is stock, but do you have anything such as Xposed, that can affect system settings?
I know it's probably the last thing you want to do, but you might try doing a hard-reset, and seeing if the conditions persist BEFORE installing any 3rd party apps. If it's working normally at that point, then keep checking it as you reinstall your apps to see if you can narrow down the culprit. If it DOES persist with a freshly wiped device, then you may want to call Google support, as that would be considered a defect.
Oh! Also, make sure you're on the latest build (KOT49H). If you're on an earlier build for some reason, it could be why your device is acting differently than everyone else's.
jt3 said:
I just tested this on my Nexus 5, and I can confirm that this is NOT happening on mine. Setting the phone to vibrate or even silent has no effect on my alarm setting whatsoever. (See the attached image. Note the vibrate icon in the notification bar.)
Do you possibly have a third-party alarm or other sound-controlling app installed? You say your phone is stock, but do you have anything such as Xposed, that can affect system settings?
I know it's probably the last thing you want to do, but you might try doing a hard-reset, and seeing if the conditions persist BEFORE installing any 3rd party apps. If it's working normally at that point, then keep checking it as you reinstall your apps to see if you can narrow down the culprit. If it DOES persist with a freshly wiped device, then you may want to call Google support, as that would be considered a defect.
Oh! Also, make sure you're on the latest build (KOT49H). If you're on an earlier build for some reason, it could be why your device is acting differently than everyone else's.
Click to expand...
Click to collapse
Hard restted once with the apps being restored and it was the same, then i hard resetted the last time without signing in my google account and everything works fine now, thanks!
did you ever find out which app caused this? i have the same problem
it might be a late answer, but it may help anyone who happens to find this post with this issue (as i did)...
I was having the exact same problem with my alarm, but I noticed that it happened after installing "Alarmy (Sleep if you can)" app from play store. It somehow overrides system volumes, and locks it after uninstall.
I reinstalled it and set the alarm volume from inside that app, and now it works as expected to do (silient ringer with alarm on).
This might happen with other Alarm apps, remember if you did install any.
Hopefully it helps someone, as this happened even on 4.4.4
I was having the exact same problem
joaquin.mik said:
it might be a late answer, but it may help anyone who happens to find this post with this issue (as i did)...
I was having the exact same problem with my alarm, but I noticed that it happened after installing "Alarmy (Sleep if you can)" app from play store. It somehow overrides system volumes, and locks it after uninstall.
I reinstalled it and set the alarm volume from inside that app, and now it works as expected to do (silient ringer with alarm on).
This might happen with other Alarm apps, remember if you did install any.
Hopefully it helps someone, as this happened even on 4.4.4
Click to expand...
Click to collapse
I have figured out that problem happened after installing "Xtreme alarm clock."
And I solved this problem with "Alarmy(Sleep If U Can)."
Thanks for your information.
I'm facing a strange issue on my N5. After the update to Marshmallow, the clock is getting slow. I have tried to malually fix the time, set it on automatic and even automatic time zone; but no prevail.
Any advise?
I was facing this issue as well when I was on DP3. It got solved once I flashed to Marshmallow 6.0. You can try flashing again and see if it helps.
Got the same problem.
Only a reboot fixes it temporarily, but the clock gets slow shortly after again.
Doesn't matter if it's set to automatic or manual.
Also tried to format cache, reinstalling the clock app as well as excluding it from doze.
Maybe it's a bad app or widget messing with the system time, but that's probably quite unlikely.
Hope a fix is being found soon!
The clock going slow can cause a number of problems with apps such as Google Authenticator or Authy. Please do update this thread if you find a solution as it'll be useful to know just in case this happens.
Sent from my Nexus 5 using Tapatalk
I don't know about other user but for me the phone is getting unusable because of this issue. The clock gets really show when the phone is sleeping and this has caused me to miss alarms and appointments.
Wow I can't believe I have spent so much time on this simple issue which even old phones were able to do flawlessly.
Brand new Nokia 2.1 running oreo go 8.1. Alarms would suddenly disappear from the lock screen or the top notification bar and then won't go off on the time specified.
Apparently a lot of people are facing this issue as it turns out by google search and I have tried the latest version of the google clock and another 3rd party alarm clock and it happens to both. Contacted support and they ask to clear cache and do things like a soft reset neither of which work at all.
I'm lost for solution as I can't get my alarms to keep running in the background until I open my clock app every now and then again and reset the alarm.
It happens to any other app that can run in the background 'auto silence scheduler' app the notification disappears and the app fails to start the scheduled silent time.
Seems like oreo is force closing apps that are running in the background when the phone is put to sleep for a while. Then those apps wont start until they are manually started.
Alarms is the worst because if it will happen during the night and I won't wake up at the time in the morning.
Exact same issue with my Nokia 2.1, Alarm's are a hit or miss scenario these days.