[AidyChap]

I've had my memo pad since Christmas, and its been working great. It has become slower over time, but I've put that down to me filling it with apps and leaving it on all the time (I use it as an alarm clock).
However this last week or so, it's been losing time. I've gone back to factory settings and even manual time entry, but it's still losing time.
Has anyone else experienced this, or can possibly tell me why this is happening?

[B. Diddy]

Welcome to Android Central! Does it have an Automatic Network Time/Date setting?

[AidyChap]

Yes, it was on automatic when it started to lose time. Have you heard of this happening before?

[B. Diddy]

Only on old desktop computers, which would rely on an onboard battery to power the computer's clock--it could periodically sync, but if the battery was running down, the clock would slow down as well. I can't imagine that this would be the case with a tablet, though--the time should be syncing pretty frequently with network time.

EDIT: There's a relatively long-running thread over here about it, but no solution posted: https://code.google.com/p/android/is...51#makechanges

[Epic Leather]

Ever since I updated to Lollipop 5.0 mine has done the same in addition to random reboots, crashes, and lags. I'm hoping 5.1 will fix it...

[AidyChap]

Ever since I updated to Lollipop 5.0 mine has done the same in addition to random reboots, crashes, and lags. I'm hoping 5.1 will fix it...

Thanks Epic Leather. As long as I'm not the only one experiencing this, I'll keep my eyes peeled for the next update.

[Wocli]

I have the same problem. Factory reset has made no difference. I have done a test with the stopwatch on the tablet and compared it to the one on my watch. When my watch has reached 1 minute, the Asus tablet has only reached 45 seconds! I am curious if you have the same experience.

[Wocli]

Now the time is correct again, and the stopwatch als runs in sync with my watches stopwatch. I don't know what changed. I restarted a couple of more times, entered the bootmenu. Also tried recovery, but that gave an error. Very mysterious this. Keep you posted.