Related
Had it at about 70% battery (around) last night, after 12 hours or so today, it refused to turn on.
I got it to turn on finally with a soft reset, and the battery showed 28%!!
I have no idea how it could have run down so fast, though it could have been something I left on (maybe wifi?).
I'm still surprised it would refuse to turn on at 28% though...
My Dopod 818 Pro is having this problem ever since I bought it. If I turn off the screen using the power switch or let it go to standby automatically, most of this time I can't turn it on again and have to do a soft reset.
I do not see a lot of Dopod users complaining about this problem so I am wondering if I have a faulty set. Other than this problem, everything else works fine.
i'm having the same problem. Do you think there will be a rom fix?
I just found an interesting observation regarding this sleep-to-death (STD) issue. If I left my Dopod overnight and got the STD problem the next day, the battery had drained considerably. It was fully charged the night before, but after 8 hours, the battery is only at 40 percent.
But since more than one person is having this issue, is it still a hardware problem?
This is not a hardware issue, its more like an unoptimised ROM issue. I suppose it will be fixed with an update in the future.
Leaving WiFi on does not matter because your device automatically goes into standby mode after a pre-defined time (3 minutes by default). In that case, even if you leave 10 apps running in the background, it won't make a difference for the aforementioned reason.
With the HTC Universal, what happened was that people would leave apps running in the background and once they are done using the device, they would just close the device thinking that it would shut off, but it wouldn't because the standy-mode was disabled by most people to get a snappier device. In such a situation, battery would drain rapidly overnight as the device hasn't gone into standby mode.
This situation will occur on the JAMin too IF there is no default standy-by mode set.
I have an HTC Universal (O2 XDA EXEC) and had the same thing happen to me two nights in a row. The battery was at 100% when i went to bed and i woke up and realized i was late as the alarm i had set didnt wake me up.
I had to soft reset the phone and the battery was down to 24% and then the alarm starting going off, a bit late though. I have had this phone for three days, and im not happy about this failing twice on me.
The only thing i have changed is running a coporate install (0506) so that o2 active wasnt on the phone.
Is there any fix for this??
Rom version: 1.13.82 WWE
Radio version: 1.04.02
Protocol version: 42.37.P8
ExtROM version 1.13.188 WWE
Go to Settings>System>Power and check the "switch off device after x minutes" option. By default it is 3 minutes, but i have set it to one minute as that serves my purpose. You will notice the drastic difference immediately .
It kind of sounds like an issue I've seen on my m600. It's a wm5 bug where activesync will try to connect all the time, randomly, even if your device is off. It can cause STD (sleep to death) and will. It's a simple fix. Just install the autosyncschedule.cpf and run it. It's a simple little .cab that will change some settings. Hope it helps
http://us.f1.yahoofs.com/bc/59d707c...amin/DisableSyncSchedule.cpf?bftVi9DBC7gsZI7r
If that link to my yahoo briefcase doesn't work, you can get this file at eten-users.net in the download section under /utilities/wm5. It solved all STD's with the eten and so far with my jamin. 8)
You can also fix the Active Sync bug manually.
To do so open ActiveSync on your WM5 device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right.
Slept to death- I've sussed out why my device was doing this
I had an SD card from my i-mate Jam inserted, and after taking this out, the situation stopped happening. So if you've got an SD card in try running the device without for a while to see if that helps...
As I write this, my Nexus 7, Samsung Galaxy Note 2, Apple IPod Touch and other WiFi connected devices in my house are all showing 1145
My nexus 10 is showing 1140.
All these devices have "automatic date time" in Settings and are connected to the same WiFi network.
I have also set the time manually but it will still lose time over a few hours.
This isn't a big issue, just an annoyance really. Has anyone else noticed this? Any ideas for a solution?
Mike
Sent from my Nexus 10 using xda premium
I can confirm that I'm having the same issue, it was off by over 10 minutes using the time servers after the first night and right now is slow by around 8 after setting it manually yesterday morning. No idea as to a solution yet.
My Nexus 10 32gb is keeping perfect time.
I have the 32gb Nexus 10. I installed the OTA, I'm currently on JOP40C.
Sent from my Nexus 10 using xda premium
I have the same problem. It is now 16:52 in Germany, but my Nexus shows 16:47. I wonder what could cause this strange behaviour
10 minutes behind. 32gb USB in usa
I dont have this problem. maybe in date & Time settings, tick "automatic data&time" will solve it?
Same problem here, ticking "automatic data&time" on and off does not solve it. In fact setting the correct time manually and ticking automatic back on "corrects" the time to the wrong time instantly.
A reboot helps most of the time, but sooner or later it jumps back to a wrong time (usually 3-10 minutes off).
My Nexus 7 on 4.2 does not show this bug.
Could be a wonky timeserver (unlikely?) or a bug that only manifests on the N10. Set the time manually for now.
Valynor said:
Same problem here, ticking "automatic data&time" on and off does not solve it. In fact setting the correct time manually and ticking automatic back on "corrects" the time to the wrong time instantly.
A reboot helps most of the time, but sooner or later it jumps back to a wrong time (usually 3-10 minutes off).
My Nexus 7 on 4.2 does not show this bug.
Could be a wonky timeserver (unlikely?) or a bug that only manifests on the N10. Set the time manually for now.
Click to expand...
Click to collapse
This is strange. I got my nexus on friday and never had to set up the time manually. The time is correct al the time. Will keep watching this.
Submitted a bug report, please star and comment so Google will fix this quickly:
http://code.google.com/p/android/issues/detail?id=39951&colspec=ID Type Status Owner Summary Stars
I threw my info up there. I called Google and they're sending me a replacement.
Added: It seems that when you reboot it forces a time sync. That sync is OK, but the hardware is keeping time slower than it should I found most of the time it was 5 minutes per hour off, but sometimes it's fine.
Every time I rebooted with a Wi-Fi connection it was OK, but slowly drifted.
The Google rep I spoke with confirmed that I had done a factory reset and then did a replacement.
I am having the same problem with all of my Android devices, but not that badly. However, time starts to drift around 10-30 seconds over time.
I tend to blame Android for this behaviour, because it synchronizes time not often enough, and depending on the accuracy og the integrated clock, it starts to drift. Does anyone know how often Android actually sets the correct time? And why does it not always use the GPS clock as a reference, if GPS is available?
The worst thing about it is that you cannot use NTP servers to automatically set the time without rooting a device. I have an app installed called clock sync, which measures time and gives a hint if it differes by a user defined threshold from the current time, but if yu want to make that app sync your clock, you have to root your device
Time does not drift on my device. I have set it to manual ~12 hours ago and it's accurate within 1 second.
The automatic time&date update via network makes it jump to the incorrect time, so this is not a matter of precision but clearly a different kind of (software) bug.
I just checked mine again...still locked in on the correct time...Automatic settings.
My Nexus is updated, unlocked bootloader, flashed recovery (CWM) and rooted. I got the tablet Friday night, played with it for a while after setting it up but never checked the time to see if it was off.
I unlocked/flashed/rooted it Saturday and then saw this post on time drift/errors. Since Saturday the tablet has been on and time has been correct.
Maybe the system is trying to compensate the lack of december, as it would reach january too early
http://www.androidcentral.com/santa-s-going-be-mad-google-forgot-about-december
As Valynor said, automatic time&date update via network making it jump to the incorrect time makes it seem like a software problem.
There is a free app in the market called ClockSync, works great. Personally I'm having no time issues with mine though.
clocksync requires root to actually sync so it works for some but not everyone. I'd personally rather not be forced to use the app for something the tablet should be doing anyway.
The time bug is even weirder:
-went to bed with time set to manual, Nexus 10 was running for about 12 hours, time was accurate within the second
-9 hours later: switched N10 on (from standby), time was 2 minutes off
-rebooted (with automatic time&date still set to OFF!): time is correct again (1 second off) after the reboot
Conclusion: something is messing with the display of the system time, alas the internal clock seems to keep the correct time nevertheless.
Great news! Your replacement order on Google Play has shipped. Track the status of your package UPS #********************9. Note that it may take 24 hours for your tracking number to return any information.
potatoboyjs said:
Great news! Your replacement order on Google Play has shipped. Track the status of your package UPS #********************9. Note that it may take 24 hours for your tracking number to return any information.
Click to expand...
Click to collapse
Good for you, but I don't think it's likely that the whole time bug thing is a hardware issue.
I've been using my N10 for over a month and I love it. But two things really bug me:
(1) wifi periodically (and unpredicably) drops out
(2) display auto timeout keeps resetting itself back to 15 seconds (when I reboot, but not every time)
Issue #1 seems to be somewhat common, but I have not heard much discussion about #2. Any suggestion? Is this a hardward or software problem? I've rooted, unlocked and stocked, and I have restored the firmware multiple times. I was able to contact google for a possible replacement but I'd like to get some advice first (I really don't want to be without my N10!!).
Hello
I have my G2 for 3 days now, and I keep having the same weird problem every morning when I turn it on: the clock "looses" one day, and either advances or loses a few minutes.
Yesterday I checked as the hour went past 00h and the date changed to day 19, thursday ('I'm on GMT 00). The phone and computer had the same time.
I left my phone off during the night, and today when I turned it on I found it at 10.00 o'clock (8 minutes in advance of my computer). It also switched back to the 18th, wednesday. The weather/time app still detects it was last updated on the 19th.
I have automatic date-time-timezone switched off. If I turn it on, it will sync with the Internet and correct the hour, but that does not fix the problem.
Any ideas on what's happening? Any suggestions?
I'm on Android 4.2.2
Kernel 3.4.0
Software D80210b-EUR-XX
Yesterday (after midnight) I switched the phone off for more than 10 minutes, switched back on: all ok
Restarted the phone: was ok - up till 3 am the date/time was correct.
Turn it off, woke up this morning, turned it on: 5 minutes delayed, date went back to the 19th.
It seems what is happening is not really a lost of time. Today as I turned the phone on, it was showing 10:24, 20th (yesterday). This was over half an hour ahead of correct time. This happened after I had the phone off for 3 hours, so it's not a delay that increases as proportional to the time the phone is off. It must have something to do with some date/time on the settings, that override actual date/time.
I think this is like a "return to last settings", in this case, I believe this was the date/time set when I turned the phone on yesterday morning.
I already went by all apps I think could be related, but I can find no relevant option to prevent this.
That is indeed strange, maybe someone else around here can help you with that.
I don't think many people turn their phones off during the night.
Hi i think this is the same for all g2, my phone does the same thing once you turn it off the device is literally off. I am sure if you check the battery time it will show only from the time you rebooted it and not from last full charge. At the beginning i reported this issue but didn't get any reply but with further investigation i reached to the conclusion it wasn't an issue with device.
Any way regarding date time issue, you can simply make sure its automatically synchronized with network that way no matter whether its on or off it will be correct.
Sent from my LG-D802 using xda app-developers app
its probably cmos battery if phone has one, try warrantee
Thank you for your input
I've done a few more tests. I've flashed a different firmware, but it still does the same. This originally came with 10B-SEA, and I flashed it to 10B-EUR (UK open). Now it's back to SEA.
I've contacted LG about this, and they told me it's under analysis.
The phone will not loose date and time if it's powered off for one hour. After two hours it will happen and it will go back to the last time the phone was powered on and the clock was set.
I've been keeping it synced with the network time, and that way it works fine, but that's not a permanent fix. Yesterday I unchecked the automatic time, left it powered off for two hours, and it went back to monday.
I've read this post http://forum.xda-developers.com/showthread.php?t=2580974, and it seems to be related.
Same problem with date and time
I do have the same problem. My phone model is D802 (international variant). But as far as I remember, this issue did not start from the day one. I purchased the phone some 2 months back. It was fine on the JB. It remained fine even after the KitKat update. But one day, my phone did show some weird problems. Serious lag coupled with overheating and battery drain. I did a factory reset because the phone was hardly usable at that point. After the reset, lag + overheat and battery issue was gone, but I remember that after that incident, it started this weird date/time sync issue. There is something which I wish to highlight by the attached screenshot. There is always a broken curve of battery usage whenever the date/time reverts which happens whenever you keep the phone switched off for a few hours. I am not a technical person, but this might be related to the battery.
Anyone have any luck with this? The main problem that this is causing is that when emails, texts, messages come in whilst the clock is incorrect (before it updates), these items get put out of sync with when they did actually arrive.
I contacted LG and they said...
If you have both options ticked, I would advise you to try and perform a hard factory reset. Before doing the reset, please ensure that you back up all of your files as all data will be lost during the reset. The details of the reset are as follows:
Turn the phone off
Press and hold the power key and the volume down key together
Release the power key only when the LG logo appears and immediately press and hold it again
Release both keys when the hard factory screen shows up
Select yes (use the power key to select yes)
Select yes again
This will then take you through the set up of the phone, and the issue should be resolved. I hope this helps you.
I haven't yet tried this, as from what I've read elsewhere, this wont fix it, plus it is a bit of a hassle to copy everything off and then reset, then et everything back on the way it was and all apps, etc.
Hi,
I've the same problem.
Can you tell me if Hard factory reset or LG support had resolved this issue?
I'm currently using ClockSync app that sync time every 3h and at boot.
The clock seems not to be very accurate : 1.139s of local offset in 2h...
I've tested the Clock_offset_fix. I'll update this post when I'll be sure that this solution is ok for me or not...
pbenoit said:
Hi,
I've the same problem.
Can you tell me if Hard factory reset or LG support had resolved this issue?
I'm currently using ClockSync app that sync time every 3h and at boot.
The clock seems not to be very accurate : 1.139s of local offset in 2h...
I've tested the Clock_offset_fix. I'll update this post when I'll be sure that this solution is ok for me or not...
Click to expand...
Click to collapse
This is not an issue per say. It's just that the device is built this way..... So as far as I know there is no fix to this. Except you can have accurate date and time if you have a sim card in the device and auto date&tme option is ticked in settings. You see the device doesn't have a pc like cmos rom to store basic info like date and time. So when u turn off the device that info isn't maintained and becomes corrupted after some time but it is corrected when synchronized with the cell network provider at boot.
Hi, I have the same problem. is there any way to solve this problem? I have stock lolipop.
გიორგი said:
Hi, I have the same problem. is there any way to solve this problem? I have stock lolipop.
Click to expand...
Click to collapse
Same problem for me, date and time are wrong for some seconds after boot.
Than it switch correctly to the current date and time.
Make sure you have setting > date and time > automatic sync for all options...
On my phone it start wrong than it correct itself if internet is enabled.
The problem ia when mobile data is OFF. :'(
4Freedom said:
Same problem for me, date and time are wrong for some seconds after boot.
Than it switch correctly to the current date and time.
Make sure you have setting > date and time > automatic sync for all options...
On my phone it start wrong than it correct itself if internet is enabled.
The problem ia when mobile data is OFF. :'(
Click to expand...
Click to collapse
Yes, I have automatic sync on, but the problem is when I can't access internet. What if I install Cyanogenmod?
გიორგი said:
Yes, I have automatic sync on, but the problem is when I can't access internet. What if I install Cyanogenmod?
Click to expand...
Click to collapse
I am on Temasek now, same problem.
I'll try Cyanogen CM13 M1 this night or tomorrow.
Hoping
Hi, I have the small 8 inch screen Amazon fire tablet (2 years old, now out of warranty)
A few months ago i noticed that the tablet was resetting the time back to the original factory setting of January the 1st, 2010 sometimes, This affects synching with the wi-fi internet, so webpages do not display. as its says clock time is not correct.
When this happens I have to go to device options, then date and time setting and reset my time zone, and then shutdown tablet and switch it back on to synch with wi-fi. The tablet then works fine with the internet for a few days then it loses the correct time and date.
neither puting settings on select time zone or automatic time zone sorts the problem, as after a few days its back to 2010 (original factory setting).
This problem happens, no matter if tablet battery is needing recharging or has plenty of power, or if wi-fi is on or off, it just seems it lasts a few days at the correct date and time, then it reverts to 2010.
Any solution to this. I know I can keep adjusting date and time by above method, and then reboot the tablet back up, but wondering if there is a reason why the tablet is reseting date and time, and is there a solution?
colin2x2 said:
Hi, I have the small 8 inch screen Amazon fire tablet (2 years old, now out of warranty)
A few months ago i noticed that the tablet was resetting the time back to the original factory setting of January the 1st, 2010 sometimes, This affects synching with the wi-fi internet, so webpages do not display. as its says clock time is not correct.
When this happens I have to go to device options, then date and time setting and reset my time zone, and then shutdown tablet and switch it back on to synch with wi-fi. The tablet then works fine with the internet for a few days then it loses the correct time and date.
neither puting settings on select time zone or automatic time zone sorts the problem, as after a few days its back to 2010 (original factory setting).
This problem happens, no matter if tablet battery is needing recharging or has plenty of power, or if wi-fi is on or off, it just seems it lasts a few days at the correct date and time, then it reverts to 2010.
Any solution to this. I know I can keep adjusting date and time by above method, and then reboot the tablet back up, but wondering if there is a reason why the tablet is reseting date and time, and is there a solution?
Click to expand...
Click to collapse
Almost certainly a hardware or battery fault. Given age of device I suspect the latter is experiencing a spontaneous voltage drop which resets the clock. Not much you can do about that short of replacing the battery.
Thanks, how long should the rechargable battery last in it, as two years seems very short.
colin2x2 said:
Thanks, how long should the rechargable battery last in it, as two years seems very short.
Click to expand...
Click to collapse
Lots of variables; 2 years is not out of the question depending on how it was used and stored. Battery quality/consistency isn't the best on these value oriented Fire devices.
OK thanks, I will just suffer the problem for a few more months by keep resetting time and date when needed, and I will buy the bigger screen Amazon Fire tablet latter this year.