Clock getting slower - Nexus 5 Q&A, Help & Troubleshooting

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.

Related

[Q] CM7 Notifications go silent

Hi everyone, I was just wondering if anyone else has had a problem with notifications going silent on CM7?
I searched and found a couple of threads about the issue, but no fix or workaround was mentioned.
I had the problem before on my EVO as well, so I wonder if it's an app I'm installing. The only constant between the 2 phones was CM7. I have tried updating to the nightlies and it still occurs.
Basically, I boot up my phone. Get a message or email notification and all is working well. I then go about my day and notice I have a few more messages but no sound was made. Now notifications will remain silent until I reboot once more, and the cycle starts all over again. Sometimes they work longer, sometimes I get 1 notification and all others are silent again.
What I've tried:
I tried messing with a profile to see if that was causing issues. No go...
I have tried switching to Oxygen which worked great but I had to switch back to CM7 because MMS did not work for me at all on that rom. MIUI also worked well but I have some contacts I like sending directly to VM and their DND did not allow that, just silent ring and answer/hangup, so back I go to CM...
Can anyone help me out?
Thanks so much!
I did notice the same thing on my Nexus S 4G! I was running CM7, as well. And a reboot seemed to fix it.
Never solved what caused it, but it didn't happen often enough to where it was a big concern of mine.
Yea a reboot fixes it for me too, but then it will happen again. I wonder why that is. Maybe it's something I'm doing?
Did you guys ever find a solution for this aside from rebooting? This has happened to my samsung infuse (running on infused 1.5) a few times already and it is pretty frustrating. I believe it's happened a few times on the stock rom as well. I've tried uninstalling programs one by one to see if I can find the culprit, but no dice. It just doesn't happen consistently enough for me to pinpoint the app or problem. Thanks in advance!

[Q] System Time Goes Backward ~20 Days Randomly

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.

Cant dismiss Alarm?

Hello and pretty much as the title says for some reason I cannot dismiss my alarm. If I dismiss it it turns itself back on a few seconds and sometimes minutes later. I first noticed this on Blisspop but I have since clean wiped (including locally stored files) and put CM12 back on but oddly the problem is still occurring.
Has anybody else had this problem?
PS I did have a good google around but cannot seem to find something that related to my problem :\
loonitic said:
Hello and pretty much as the title says for some reason I cannot dismiss my alarm. If I dismiss it it turns itself back on a few seconds and sometimes minutes later. I first noticed this on Blisspop but I have since clean wiped (including locally stored files) and put CM12 back on but oddly the problem is still occurring.
Has anybody else had this problem?
PS I did have a good google around but cannot seem to find something that related to my problem :\
Click to expand...
Click to collapse
I'm on Blisspop unofficial that include CAF kernel... And i don't facing that kind of problem...
Are you sure that you are dismiss it, instead of just snooze it?
Hello, definitely dismissing it. I decided to wipe every bit of info\data etc on the phone so that nothing is left, installed CM12 again, without GAPPS so that it cant pull any settings that might be stored on my google account and guess what? Even on a pretty much blank rom I am still getting the same issue :\. Now starting to think it could be hardware but it seems very unlikely.
I have been facing same problem. It comes back after I dismiss an upcoming alarm after turn off the screen and turn it back on, it comes back. Any suggestions?
Same issue on CM12.1 ROM I'm using. I dismiss the upcoming alarm, but most of the time it activates back.

Calendar notifications sometimes stop working

Hi everyone,
I'm running 6.0.1 and recently performed a hard reset and cleared caches to try and resolve the problem.
Did not resolve. Also disabled power managment for apps. Problem persists.
Whenever a calendar event is skipped (by the device) all future events stop working and I have to reboot to get the alerts back.
Mostly the problem comes when there is one emty day, but it also happened when I got a notification in the morning and in the evening nothing anymore.
Thus I thought it could be powersaving related, but powersaving is disabled.
It's really driving me crazy, my calendar is verry important to me as I tend to forget things.
Anyone knows how to resolve the problem ?
How to debug ?
Your input is verry much appreciated.
Thanks.

Notification in Notification after Pie update

Hi,
after updating my HTC U11 to the official HTC Android Pie Europe release, so far the only real problem i found is, that for some reason the commute notification of google maps are now shown as a notification within a notification. Before the updated they worked fine. If you don´t know what that is supposed to mean, see here:
imgur.com/SQ27lSW
So far that only happens to the commute notifications. Pressing on either of the settings buttons only leads to the commute settings where i can disable the notification completly, which is not what i want.
Before the update it was only one notification with the map in a size where you could actually see something straight from the notification.
I already tried deactivating the function and activating it a few days later withouth any difference. I also tried clearing the cache and data, as it is set as a system app so that is the closest i could get to an uninstall.
As far as i know, i can´t really make a useful bug report through the app itself, as it is a notification i can hardyl make a screenshot of with the integrated bug report tool.
I also tried looking at the notification logs, but could´t see anything out of the ordinary with my simple knowledge of it: imgur.com/Fk9U0dk
After living with this "problem" for the last few months, I wanted to see if someone had the same problem and maybe found a solution in the mean time, which lead me here in the hope of finding such an answer
Thanks in advance for your help
Hi.
Last week I decided to reflash my U11, it's a Europe Pie version too, aka HTC__034. I had several bugs, with apps crashing like Google Assistant, the Dialer (unable to type a number or letter) and others. Flashing the RUU went fine and I got rid of those bugs, and even got better SOT than before (from 4 to 5 hours).
Reading your message, I just realized that I also got rid of another bug I had with the Google Phone dialer app. It also had such nested notifications when I received a call. Now it works fine.
So maybe flashing the RUU could solve your problem.
Hi kurtschmeichel,
thanks for the quick answer.
From what i read, flashing the RUU also clears all your data and settings, or did I get that wrong? As this is currently the only "problem" I have, I think I will not take this route as this entails a lot of reconfiguring.
Yes your phone will be "like new". You have to backup ALL your data before flashing a RUU.

Categories

Resources