Database Users

Damn phone keeps turning itself on

Upgraded to the new 1.60 ROM hoping to cure this annoying problem but if anything its worse.
I turn the phone off and within 5 minutes its turned itself back on for no apparent reason. No notifications or anything. Cant be doing my battery life any good if it keeps switching on
Any ideas?

That may be something to do with the way that ActiveSync is set up.
I've had this kind of problem in the past and found that by killing activesync by using a task manager of some variety and changing my 'network' settings that the problem goes away

Please excuse me, im quite a newbie at this xda malarky. My xda also turns its self on randomly since installing 2003. you said change your network settings. How and what do you change them to? I made sure that activsync is turned off, but it doesnt make much difference either way.
cheers

I have experienced the same...
And, I've been on multiple ROM's with no avail.
I'm not sure anyone has ever found a solution.

My activesync is turned off, but the damned thing keeps turning on. Its sitting in the cradle at present and it turns on every 3-4 minutes!!!

It is Active Sync
I had this problem with my charger in the car. It is not sufficient to kill the Activesync. You would have to go to the options in the Activesyn menu, go to the new options button in the PC tab (the first one) and there disable the box with the name "Enable PC sync using this connection". This you will have to enable each time you want to sync via the cradle. I don't have the problem in the original cradle, it is only with the thirdparty car charger. I sync via IR or bluetooth and that is always available via the menu in Active Sync.
Good luck!
Johan

ActiveSync i can understand when its in the cradle but currently its sitting on my desk and still turning on at random intervals sometimes 30 secs after i switch it off!!!

Signal strength maybe?
I have same problem, happens mostly in car but not exclusively.
I get the feeling that it's related to the cellular signal strength and the device loosing or regaining the GSM connection.
San Francisco has several zero or almost zero coverage areas so it's not unusual for a phone to loose and then regain a connection while driving or walking.
I would love this device if it worked as expected but at this moment it is the source of endless frustration.

im also having these problems they are head doing never used to turn itself on as soon as i hard reset it just started to do this now and its annoying me so much

Im also having these problems . I find a solution using registry cleaner of pocket mechanic.
Bye

Guys, Check the setting of the ActivSync, most probably you will find a schedule for synchronization is set every certain time. So, you have to switch it to Manual Sync.
I think this should soulve your problem.

Sprite Backup
I too had this problem. For some reason the enabling Sprite Backup battery monitoring and Scheduled Backups caused this. try turning these features off if you have it installed.

I have same problem, its really anoying, have not found a way to stop auto connection even after changing some setting on my computer Activesync & XDAii activesync. I'm guessing theres no way to stop it.
Is there an active sync update available? I'm using 3.7 (build 3083)

For those whose unit turns on by itself, please check:
From your PPC:
Start > ActiveSync > Tools> Options > Mobile Schedule
Make sure all 3 options are set to "Manually".
From your Desktop PC ActiveSync:
Tools > Options > Schedule
Make sure every active options are set to "Manually" as well.

You can manually sync but Activesync still keeps "looking for changes"

I need for help plsssss
if some body plsssss attch the last eddition of xda2nbftools because I am living in Saudi Arabia, and the web site to can download this file is BLOCKED here in Saudi Arabia, they are blocking web sites here then u can't open it at all and no way to can download it unless if it attached here in this forum

Here is it:

Same for me too,
Mine can turn itself on almost as soon as i turn it off, its a running battle to get it to turn off and i very rarely win, I have accepted the fact that mine will stay on most of the time now and have a second battery to help me through the day,
I checked all my settings and all mobile schedule settings were on manual and all the active options are set to manual too, so it wasnt those settings causing the problem,
I cant believe the lack of support that O2 are providing, if this was an HP handheld there would have been a fix for each problem as it cropped up within a week as they have done with each of their handhelds

do the people experiancing turn ons have a card in the Sd slot? i do but i notice when the device is off...... put a sd card in and the device turns itself on i only started to notice it turning on when i got my SD card i might take it out tonight and try then?

Yup, i have a card in the slot all the time, took it out for a few hours this morning and it was no different, still kept turning itself on,
I looked a bit deeper into it this morning too,
It seems that i use it, turn it off and it turns back on 13 seconds later, i turn it off again and it turns itself back on again 13 seconds later, so i try to turn it off and the power button has no effect, i have to press it twice to turn it off, then it seems to stay off for at least 30 minutes before going through the exact same sequence again,
I will list all my installed programs a bit later when i have more time, hopefully everone else can do the same (whether you have the problem or not) then we can see if there's a common program that is on all the XDA2's that might be making them turn on and see if its absent from the XDA2's that are fine

My Jamin just slept to Death...

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...

WM5 automated nightly reboot?

I have a question. I've only had a WM5 device for about 9 months now. I now have Cingular 8525 and for the past 5 days I have left it on overnight only to find it frozen, won't wake up in the morning and the battery drained.
I did the Activesync hack, scanned the notifications queue and did not see any notifications for midnight on the dates the device would not wake up.
Its frustrating.
I was wondering if WM5 did some form of house cleaning nightly. It seems that this house cleaning wakes up the device and somewhere it freezes on and finally the battery gives out. I don't have any backup software going on.. Nothing. I just find the device won't wake up, won't even soft reset. Plug it in for a minute, then it soft resets with a dead battery.
I am going to look at the notifications queue tonight and delete any notifications I see that are for 0:00 and tomorrow and see what happens.
I am hard resetting it Monday and re-installing if I can't figure it out. It has been really annoying these last 5 mornings.
Sometime when I reboot I see a NO GSM message. Then get no radio, then about 10 minutes later I get service. But the password and the userid on the wap data connection has been erased and my bonded blue tooth headset password is forgotten, the device is there but it prompts me to bond with a passkey when I go to intiate the headset...
Thanks for your thoughts

This has, I believe, alot to do with your microSD card - see the link below.
http://forum.xda-developers.com/showthread.php?t=284636

Thanks I'll check it out. I do have a sd card in the device. It may be the cause.
Thanks.

I use SPB Backup, to initiate automated reboots. What it does is back up to ur microsd and then initiate a reboot. i do this every second night. which is cool, keeps the fone fast.

Nightly lockups were a pain in the neck for me - I have had 2 Orange M3100 and both suffered the same nightly lockup issues.
I found that 4 things have fixed the issues and i found that all 4 have to be done
1. Fake server trick
http://www.aximsite.com/boards/showthread.php?t=112638
But i found that not deleting the new server works fine
2. Untick Enable Advanced Network Functionality
Under Settings\Connections\USB to PC
3. Stopping Activesync running when not needed
In the notification queue there are 3 entries to start replog.exe (activesync)
you can safely delete the instruction to start after time change - This will stop Activesync from running.
NB the other 2 need to be there, do not delete any other notification of replog.exe
4. Never leave activesync running so always do a soft reset after syncing or at least before you charge the phone.
Not saying that these will work for everyone but they have worked for me on both phones.

try XBar. It incorporates cron, so you can schedule whatever program to run whenever you want it. Grap a copy of quickreset and run it. It will reset the Tytn at whatever time you set it for. I have mine resetting at 5 in the morning.

You may disable the standby mode when the unit on the external power supply. I have done, and I think it's not a big deal and it does not worth to struggle with locks on wakeups with external power!

I having a sort of similar 'morning trouble' with my TyTN, but limited to GSM connectivity. When I wake up, I am most of the cases disconnected from network with 'No service' message in the baloon. Searching for network is unsuccessful, nothing works until I soft reset the device.

Just a thought: You do have the "poweroff after x minutes" setting checked right?
I had what I thought was the same issue this morning, but it was caused by me unchecking the above setting (I do this during meetings when I'm using my BT keyboard) the previous day. This morning, while it was still dark out, I pressed the power button and nothing (the backlight was off and this actually put it into powersave mode). I pressed it again and still nothing (device came out of powersave mode with backlight still off). Because it was dark when I did this, I initially thought that I had the "won't return from powersave" problem.

machmandp said:
Nightly lockups were a pain in the neck for me - I have had 2 Orange M3100 and both suffered the same nightly lockup issues.
I found that 4 things have fixed the issues and i found that all 4 have to be done
1. Fake server trick
http://www.aximsite.com/boards/showthread.php?t=112638
But i found that not deleting the new server works fine
2. Untick Enable Advanced Network Functionality
Under Settings\Connections\USB to PC
3. Stopping Activesync running when not needed
In the notification queue there are 3 entries to start replog.exe (activesync)
you can safely delete the instruction to start after time change - This will stop Activesync from running.
NB the other 2 need to be there, do not delete any other notification of replog.exe
4. Never leave activesync running so always do a soft reset after syncing or at least before you charge the phone.
Not saying that these will work for everyone but they have worked for me on both phones.
Click to expand...
Click to collapse
I have a similar problem. Every monring when the device is still plugged on the wall charger, it hangs before I wake up. I would therefore miss a lot of calls or other notifications. I have done the defragmentation of the card, but it still doing the same thing every morning.
I have also tried all your steps above, ecept step 3, which I need your assistance as to how to delete the particular file you were referring to.
Many thanks in advance.

marsb007 said:
try XBar. It incorporates cron, so you can schedule whatever program to run whenever you want it. Grap a copy of quickreset and run it. It will reset the Tytn at whatever time you set it for. I have mine resetting at 5 in the morning.
Click to expand...
Click to collapse
holy crap, i thought i was the only one that used xbar.. i have been using this program for 2 or 3 years, this is my one and only must have program!! FYI 3.2 beta was released
anyway.. on to this problem, i used to have this on my wizard, what i found was that plugging it and leaving it on would cause the lock up. Now when i plug it in i hit the power button and havent experienced it since on my wizard or on my 8525 yet. and i still get all of my push mails etc.. however i will say that if i get a call or text while im sleeping the device does wake up and the screen stays on..

another program you might want to try is SKSchema... they have several scripts that you can run, including a soft reset at a certain time. I also use the script which allows me to toggle between 3G/UMTS to save battery when I don't need 3G.

"Fake Server" did not work for me
Tried what is outlined - fake server, soft-re-boot, stopping activesync. Not sure how to delete the specific files in the notification queue.
Worked for one night! Next night back to the sleeping Tytn.
I am going to try spbTime to trigger an alarm at 12:01am and see if that helps.

TyTn does not "die" anymore!
The fake server is definitely part of the answer. As is stopping ActiveSynch. This needs to be combined with one other suggestion made on the forum of leaving the unit on when plugged in. This however has the potential drawback of "burning" the screen with the same image as when left powered on.
In addition to Activesynch, the problem is with the Notification queue (again as someone suggested on this forum). In the Suspend/Sleep mode under power, the unit cannot notify and goes into a perpetual loop.
Here is what I did that has now worked for 11 days. I installed spb PocketPlus and placed the "Screen Toggle" icon on the main screen. (According to spb, "Toggle" simply blanks the screen but does not put it to sleep/Suspend). So when I plug the unit in to charge it, I simply "toggle" the screen. The screen is blank (just like "Sleep"/"Suspend") but the unit is powered up. This has the added benefit of allowing you to listen to music with the screen blank.
I have now gotten to "toggling" even under battery power. Miraculously, my intermittent BT and Wi Fi issues have also disappeared. There may be cheaper solutions than buying Pocket Plus, but spb's Pocket Plus is convenient and has some other nice features.

Mortsaver might be a cheaper option?

Active Sync
I don't know if any of you have tried Active Sync "beta" 4.5". Its seems to have fixed many of my problems with connection and some of the issues described here.
flane

coolshot said:
This however has the potential drawback of "burning" the screen with the same image as when left powered on.
Click to expand...
Click to collapse
This problem affects CRT and plasma displays (phosphor based), but not TFT.

[SOLVED] Can't shut off the phone, it always turn on again

well, i was following a thread about it, but i guess it was deleted cause it was in wrong area...
if a fix was found please tell me! =oP
it seems to be a commom issue: when i try to turn off the phone, it just turn on again...
what i've done until now: i was running cm7 and i believed it was a rom related issue, but i'm back to uk stock (1.32.405.6) and keep it with no root (just ship s-off that remains after flash ruu), and the problem remains, just take a little longer to turn on again... BUT, when i plug it into pc by usb cable it stays off, when i unplug it turns on again...
i'm tending to believe that's a hardware issue, maybe a short in phone plug, but in this case, it is the most commom issue that i've saw...
any idea is welcome
thanks...
Edit:
Okay Folks, looks like the "fix" was found. I made a little summary for the next generation! =oP
this weird issue happened due summer time changes (don't ask why), but after March 27 the phone simply didn't stay off, if you tried, it just turned on again.
The "fix" is:
- disable automatic hour update (just in case)
- remove battery and let it out for around 10 hours, then put it back and turn on!
- Hour and date may reset (or not)
- now you can reactivate automatic hour update if you want.
- the device just stays off properly again
credits for
XL3N7 that found the problem,
Rodomar705 that found how to fix in this thread: http://forum.xda-developers.com/showthread.php?t=1014520
And everyone else that probally lost every data (like me) so many times trying find out how to solve it. =oP

I really dont understand why the admins deleted and not removed the thread from the development section.
What really happens: I have my dhd with cm7 around two months now and i always flashed the nightlies.I know the issue, when the phone is powered off and plug a charger reboots in cwm recovery. I never had problem just to "power off" my phone and actually did that every night before going to bed (so i know that the "power off" used to work ok) .Two days ago i flashed RC3 , power off worked ok, then nightly 32 and next morning i had the issue.When i select to "power off", without any charger or usb connected , phone just reboots.Just to remind you that if the phone is powered off and you connect it to charger then the phone goes to cwm recovery!So i tried various combinations :
1. Back to stock 1.32 (both with img file and exe file). After that flashed 3.0.0.5 and the newer version of cwm
Phone powered off correcty and the vol down+power goes to hboot.After flashing cm7 problem appears again.
2. Also had a backup and load it (nightly from 16/02/11) but still the same problem.
Please devs tell me what kind of files you need in order to help me solving the issue.
Also i see posts from guys using other custom roms and having the same problem, so i dont really understand why the admins deleted last night the thread started in development section.
You guys using customs rom just check if your power off works and if you have problem write it here and hope not to be deleted.
@thiagodark I think you have to change a little bit thread's title

same problem!!....i think is a bug of CWM...or there is a conflict between recovery and "idontknow"!!....
this situation is funny ... we are afraid to brick and our DHD doesn't want to turn off...

well, i think my problem is a little different, cause i get this problem even after flash official ruu, i'm all stock right now and the phone keeps reboot when i try to power off. when i select "power off" with micro usb cable connected, it works okay, but when i disconnect, it power on again.
Also, sometimes when i try to power off with or without the micro usb connected, it just dies and the only way i can power on it again is by removing the battery.
suggest me a tittle and i change, as you can see, my engrish is not something i can proud myself! =oP

cesco89 said:
same problem!!....i think is a bug of CWM...or there is a conflict between recovery and "idontknow"!!....
this situation is funny ... we are afraid to brick and our DHD doesn't want to turn off...
Click to expand...
Click to collapse
Yes，it must a bug of CWM 3.0.2.4r1,I hope they can fix it in a few days

Ok, I think I have found the problem.
Go to settings --> Date & Time, untick the option to use network values and set the date somewhere before the 27th of March when the daylight changes took place. Reboot and power off. The phone should stay off (at least it did for me). Now power on, go to date & time settings and tick the option to use network times. Power off and it will probably come back on.

XL3N7 said:
Ok, I think I have found the problem.
Go to settings --> Date & Time, untick the option to use network values and set the date somewhere before the 27th of March when the daylight changes took place. Reboot and power off. The phone should stay off (at least it did for me). Now power on, go to date & time settings and tick the option to use network times. Power off and it will probably come back on.
Click to expand...
Click to collapse
Confirmed.

XL3N7 said:
Ok, I think I have found the problem.
Go to settings --> Date & Time, untick the option to use network values and set the date somewhere before the 27th of March when the daylight changes took place. Reboot and power off. The phone should stay off (at least it did for me). Now power on, go to date & time settings and tick the option to use network times. Power off and it will probably come back on.
Click to expand...
Click to collapse
WTF?!?! Worked here!
it doesn't make ANY sense for me!
and by the way: i don't even know what you mean by "daylight changes took place" =o)

XL3N7 said:
Ok, I think I have found the problem.
Go to settings --> Date & Time, untick the option to use network values and set the date somewhere before the 27th of March when the daylight changes took place. Reboot and power off. The phone should stay off (at least it did for me). Now power on, go to date & time settings and tick the option to use network times. Power off and it will probably come back on.
Click to expand...
Click to collapse
But why？I think it is not the best way to fix this bug.

thiagodark said:
WTF?!?! Worked here!
it doesn't make ANY sense for me!
and by the way: i don't even know what you mean by "daylight changes took place" =o)
Click to expand...
Click to collapse
Daylight saving time

wjwj929658 said:
But why？I think it is not the best way to fix this bug.
Click to expand...
Click to collapse
I know but at least we know know what is causing it. Probably an issue HTC will have to look at, since it doesn't seem to be a cm issue.

wjwj929658 said:
But why？I think it is not the best way to fix this bug.
Click to expand...
Click to collapse
we, first of all, must to know why the problem occurs, now we can try to fix.
isolate to destroy! =oP

wjwj929658 said:
Yes，it must a bug of CWM 3.0.2.4r1,I hope they can fix it in a few days
Click to expand...
Click to collapse
No its not a bug of 3.0.2.4 r1(i had 3.0.0.5 when problem appears). As i wrote everything worked perfect (cm7+cwm 3.0.0.5) till one morning (was on cm7 nightly 32+cwm 3.0.05) want to boot in bootloader, so i select to power off.After that never powered off.What makes me nervous is that i didnt install any appl or changed the cwm recovery version.Nothing like that.I always powered off my phone so i know that there is not cm7 nightly related.
So the big question is what changed in a few minutes?
What the f******k?????? Daylight? )))))))))))
Confirmed working.Changed the date back to 03/26/2011
A guy mentioned that last night (about the daylight change) on the initial thread which admins decided to delete

afilopou said:
No its not a bug of 3.0.2.4 r1(i had 3.0.0.5 when problem appears). As i wrote everything worked perfect (cm7+cwm 3.0.0.5) till one morning (was on cm7 nightly 32+cwm 3.0.05) want to boot in bootloader, so i select to power off.After that never powered off.What makes me nervous is that i didnt install any appl or changed the cwm recovery version.Nothing like that.I always powered off my phone so i know that there is not cm7 nightly related.
So the big question is what changed in a few minutes?
Click to expand...
Click to collapse
The time has changed http://forum.xda-developers.com/showpost.php?p=12517111&postcount=6

XL3N7 said:
Daylight saving time
Click to expand...
Click to collapse
ok, but i don't get how it could affect me, since i live in a place where March 27th was a normal day... here summer time OVER almost a month ago! =o)

I have no idea m8. I've just put 2 & 2 together. The issue first appeared shortly after the time change. Maybe a bug in htc's code? Surely not a cm thing. I have tried fastboot erase system -w and the problem was still there. I have also tried different radios, cwm versions and the issue is still there. Probably HTC. Hopefully one of the greater minds of this forum can pin point the issue.

Perfectly good work around
Hi, If you want to, you can untick the setting in Date & Time and install Clocksync from the Market. Using this app you can sync your phone's time at whatever schedule you like to the atomic clock (it is much more accurate than HTC's provider).
This will enable you to shut down correctly and have accurate time displayed on your device.
You need root though.

nobnut said:
Hi, If you want to, you can untick the setting in Date & Time and install Clocksync from the Market. Using this app you can sync your phone's time at whatever schedule you like to the atomic clock (it is much more accurate than HTC's provider).
This will enable you to shut down correctly and have accurate time displayed on your device.
You need root though.
Click to expand...
Click to collapse
can't make it works here, what steps did you follow?
okay, i realised... i need root! =oP
rooted, but not getting make it works, could you guide me?!

thiagodark said:
can't make it works here, what steps did you follow?
okay, i realised... i need root! =oP
rooted, but not getting make it works, could you guide me?!
Click to expand...
Click to collapse
Open Clocksync
Press menu button on phone
Press Settings
Enable > Tick
Interval > I chose 1 hour
detect Time Zone > Tick
Sync On boot > Tick
Restore permissions > Untick
(Everything else untick)
Press the back button top go to app
Press menu button
Press Synchonize
Grant Superuser permissions when prompted

So，it is a bug of HTC ？in other words,Even if we do nothing,It still will happen sooner or later?

Nexus 10 not keeping accurate time

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.