Soo.... I'm guessing there's no good solution, but posting anyway..
Suddenly, whenever I do a battery pull (frozen device or just swapping batteries) .... when I boot the phone back up, the date/time has reset to sometime in 2006 at 6:00pm...
I have the checkbox to automatically update date/time checked in Settings... this happened with CM7 and is also happening with MIUI now..
I downloaded an app to auto-sync date and time, but it doesn't kick in until several minutes after bootup if at all... so whenever the clock is fixed, all sorts of apps are affected - anything that tracks by date thinks 7 years just passed! Alarms go off, app alerts go off, etc..
I suspect this may be a capacitor/small battery used for keeping the time, inside the phone going bad ... anyone else had this happen to their g2x? Am I wrong in suspecting there's no fix?
lotherius said:
Soo.... I'm guessing there's no good solution, but posting anyway..
Suddenly, whenever I do a battery pull (frozen device or just swapping batteries) .... when I boot the phone back up, the date/time has reset to sometime in 2006 at 6:00pm...
I have the checkbox to automatically update date/time checked in Settings... this happened with CM7 and is also happening with MIUI now..
I downloaded an app to auto-sync date and time, but it doesn't kick in until several minutes after bootup if at all... so whenever the clock is fixed, all sorts of apps are affected - anything that tracks by date thinks 7 years just passed! Alarms go off, app alerts go off, etc..
I suspect this may be a capacitor/small battery used for keeping the time, inside the phone going bad ... anyone else had this happen to their g2x? Am I wrong in suspecting there's no fix?
Click to expand...
Click to collapse
Actually this happens to me everytime I swap my batteries, but date and time always correct themselves once the sync with a network, for me usually under a minute. I don't have any app issues though because of the incorrect time at start up. Very odd.
Sent via Sosei "III" BakedBean Iconia A100/4.1.2 AOKP/AOSP Hybrid
Related
Hi,
It's been the fourth time my LG Optimus 7 (NoDo) changes the time and date by itself, without any reason.
This is weird, coz' "automatic time setting" is disabled in the settings.
This is a very annoying bug, especially for appointments and alarm clock.
Anyone else has this bug?
Thanks
This has happened to me just the once - it is really annoying.
Is the phone just changing to some arbitrary date/time, or is it trying to correct to the local time while you are visiting a different time zone?
I'm curious, because I have never seen this problem on my Focus, but I have automatic updates turned on. My phone does (correctly) update whenever I change time zones, and for DST, but that's it.
RoboDad said:
Is the phone just changing to some arbitrary date/time, or is it trying to correct to the local time while you are visiting a different time zone?
I'm curious, because I have never seen this problem on my Focus, but I have automatic updates turned on. My phone does (correctly) update whenever I change time zones, and for DST, but that's it.
Click to expand...
Click to collapse
For instance, today, my phone was on my desk. 11:30AM in Paris - France.
Suddenly, the time changed to 2:20AM and date to 05/22/2011 (instead od 05/20/2011).
I did not touch the phone. Network is good. Automatic time adjustement is disabled.
It's the 4th time it happens. I noticed it is not arbitrary: I mean the date and time are not dramatically different from the real one (date did not change to December 2012 for instance, only 2 days difference).
But it is not a time adjustement, as the difference can be 2 days for instance.
Hmmm... You don't by any chance live in a TARDIS, do you?
Seriously though, I haven't ever even heard of this problem before you mentioned it. Could it be an LG-specific thing? Either way, I would say it is justifiable reason to get a warranty repair/replacement.
One other question, though. Is there a reason you have automatic time adjustment turned off? Maybe turning it on would help.
I've had the same problem. It's totally random. I called LG (mine is an Optimus 7) and my provider and after some time on the phone with both, neither could tell me what the cause of the problem was. Oddly enough it hasn't happened in some time now.
RoboDad said:
One other question, though. Is there a reason you have automatic time adjustment turned off? Maybe turning it on would help.
Click to expand...
Click to collapse
Thanks for ur answer.
I disabled the automatic time adjustment on purpose, after the first time the time changed by itself. I hoped it would help.
But it changed nothing. Time is still changing...
I guess you should open a support ticket with Microsoft as it seems software related issue.
I have the same issue with my Omnia 7 after doing a combo update (7390+7392).
This didn't happen before that.
Quite frustrating as I'm using my phone as an alarm clock. I'd hate being late at work because of that.
Hi all,
I've also encountered the same issue as OP. Same phone as well. Did exactly the same thing with time settings and even did a hard reset but still returns.
I've noticed it happens when I'm listening to music, it would have either a small pause (which means I know the time has changed) or stops music altogether (need to reboot phone). And with every time those events occur, the time jumps into the future.
I've had this phone sent for repairs because it stopped turning on, which they may have replaced the board.
People still having these issues?
Also by chance, did you guys did the chevronwp7 no brand hack to get nodo? I did and also rolled back to original carrier rom.
Sounds like you all are using an LG phone, so maybe this is some specific driver or hardware feature that LG has included onto their devices.
Has never happened to me on my HD7. I would never buy an LG phone so I don't know what they do to their devices.
HTC... never issues with times and/or dates.
so my phone has recently started to reboot when i power off. ive switched roms the problem still persist. is any one having this problem? and did anyone come up with a soloution?.
seems all of a sudden a few people have been having this issue, i was running many roms for a few months with no problems at all then all of a sudden phone just started rebooting after being powered off. people keep saying its something with CWM but i cant fix the issue.
Just copied this from another thread.
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
I did as he said and it did nothing, but just now i tried it again and set the date to 1/1/2011 and now my phone turns off and stays off
Since I was quoted I thought I would jump in and let you know that changing the date for a whole day like I described did work for me. I have since changed back to automatic date and time and so far the phone has been all right for the last few days. (From what I have researched I think this is some kind of daylight savings time change issue or something like that occurring with CWM that some people are having.)
ok so i changed the date and it worked!!!! thank you!!!!!
so mine works correctly as long as i leave it on the wrong date, as soon as i put it on automatic or change it to the correct date it goes back to rebooting
My Infuse refuses to show the correct time when running any Froyo ROM (including stock). My timezone is GMT-5 Eastern, but my phone says I'm GMT-4 Eastern (huh?) and the time is exactly 4 hours ahead. This is system-wide and affects widgets, text and call logs, email times, etc. This issue has persisted for more than 24 hours now.
This is not fixed by turning GPS/wifi location on or off, disabling and re-enabling automatic date/time, restarting the phone, pulling the battery for 5 minutes etc. it's just constantly 4 hours off. Manually setting the time and later re-enabling automatic time will put me 4 hours off again. None of the other AT&T Android smartphones in my house are showing the incorrect time. I didn't have this issue when running Gingerbread or when I first got the phone, but even flashing back to stock now doesn't seem to resolve the issue.
Well...wtf?
Mine has been fine until I RELOADED Serendipity VII ROM (Gingerbread). It was fine with S7 until I reinstalled it last night.
YES, I CAN set the clock manually but it has never needed to be set manually. It has always been on "use network provided values" with this phone and every other phone I have ever owned.
There have been a few others with the same problem.
MisterEdF said:
Mine has been fine until I RELOADED Serendipity VII ROM (Gingerbread). It was fine with S7 until I reinstalled it last night.
YES, I CAN set the clock manually but it has never needed to be set manually. It has always been on "use network provided values" with this phone and every other phone I have ever owned.
There have been a few others with the same problem.
Click to expand...
Click to collapse
Hmm. It seemed to have corrected itself for a couple of hours this morning, then it was back to being 4 hours off. Just a few minutes ago, the time is back to normal again. I have no idea.
strychninetwitch said:
Another brilliant question. It shows GMT -4 because of DST. I don't have an image to explain the level of obviousness here, sorry.
Click to expand...
Click to collapse
Thank you for not understanding my post at all. Why don't you share your answer with the ongoing general thread on this issue? I'm sure they'll be satisfied with your explanation of DST.
strychninetwitch said:
I would simply leave this blank, but you as you are probably aware, there's a minimum character limit.
Click to expand...
Click to collapse
My post is about the incorrect time bug being talked about now in the general forum. I'm sorry that you're so stupid that I had to spell it out for you again. Begone, troll.
I had a similar problem with timezone issues and was told to put it in manual mode and then back for it to correct itself. This never worked on a back and forth flip but putting it in manual mode overnight and then back did for some reason. Not the best answer but worth a try. My issue has never returned since.
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.
Has anyone experienced your U11+ freezing up.
It has happened to me about 3 times.
It generally happens over night while it's charging. I get up one of those mornings and the green light is on, remove the charging cable and I can't wake up the phone. I can't even turn off the phone by pressing and holding the power button to kill the device. The only way is to put it into download mode by simultaneously holding down the vol down key and power key, and then when the menu comes up to select the reboot option to get the phone back to normal.
Has anyone else experienced this or know what could be causing this to happen?
The problem is that I use my phone as my alarm clock, and when it freezes up, my alarm doesn't work.
Any suggestions anyone?
No problem like that until now.
However, noticed sometimes that the my alarm, which is setup for vibration only, only vibrates once and then continues silently alarming until I turn it off.
Happens randomly but still strange. I've to try with another clock app.
That's really odd.
I'm going to turn off the always - on feature and see if I get anymore freezes. I had another one this afternoon.
I'll report back after some time and let you know if there has been no more freezes.
I'm just updating to the latest update 1.23.709.3 and see also how it performs.
I'm a bit concerned about this random freezing that I have experienced since I got this device.
If it persists I may ask for a new one.
globalgpj said:
I'm just updating to the latest update 1.23.709.3 and see also how it performs.
I'm a bit concerned about this random freezing that I have experienced since I got this device.
If it persists I may ask for a new one.
Click to expand...
Click to collapse
I'm still on the October security patch so I'm expecting one for the December period soon I hope.
In regards to your freezes I've not encountered anything like that so far been working flawlessly so far if there is anything I can test let me know
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
globalgpj said:
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
Click to expand...
Click to collapse
I have been using the AOD since I got the phone yesterday. Not a single freeze
Galactus said:
I have been using the AOD since I got the phone yesterday. Not a single freeze
Click to expand...
Click to collapse
Thanks for letting me know.
I guess I can rule that feature out as a probable cause.
It must be some other app that's causing this issue. But it's a pain to go through the process of finding out which one.
globalgpj said:
Thanks for letting me know.
I guess I can rule that feature out as a probable cause.
It must be some other app that's causing this issue. But it's a pain to go through the process of finding out which one.
Click to expand...
Click to collapse
Yeah trial and error isn't fun. I'd probably factory reset though and see if it happens with barely any third party apps installed.
globalgpj said:
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
Click to expand...
Click to collapse
I have the HK model I think and I had the AOD when I first got it, set to motion and nothing has happened to my phone in regards to freezing fingers crossed. I have disabled it for the moment as I noticed a greater battery usage overall, I believe between 9-10% overnight and only 2% when I had it disabled.
Hopefully you find the problem otherwise see if you can get it replaced...
Since not using the always-on feature, I don't have any more freezes. Must be some conflict with the alarms and always-on. Can't see what else could be causing those freeze ups.
My phone surprisingly just froze up yesterday. But at least it's been a long while since not having the always-on feature enabled. With always-on enabled, it seems to have happened every day.
The issue I have most about this, is missing that important call when I haven't realised that the phone is frozen, because sometimes I don't pick up the phone for hours.
I had to do a complete fresh install from scratch and I have no more issues. I believe all my issues came from using HTC's transfer tool when going from u11 to u11+. Importing all the settings features using the Transfer Tool has caused issues. I'll never use this tool again.
All good now.