Android 6.0.1 fixes the system clock on your Android device that broke with Android 6.0
posted by Alan F. / Dec 12, 2015, 3:05 PM
You see, we'e not talking about a 30 second difference, or even two minutes. According to Nexus users posting on the Issue Tracker (Issue # 189789), the time discrepancy can be as large as 30 minutes. Some have been able to resolve the issue by turning on Airplane mode and then turning it off again. But this solution doesn't work for everyone.
Rebooting the phone is another fix that some swear by, while others say that switching to a 3G network setting from 4G will get the clock on your phone back on track, and syncing with the network time.
The good news is that once your handset is updated to Android 6.0.1, the issue will be gone. No longer will you show up late for work, miss appointments, or wonder why your date hasn't arrived (when in fact, they gave you 15 minutes to show and left when you didn't appear). So here's your game plan. Keep using one of the workarounds until you install Android 6.0.1. And if you're late for something, blame Google.
Many of those who posted complaints on the Android Issue Tracker thread about the system clock, are using the Nexus 5. Manufactured by LG, you can check out some images of the phone by clicking on the slideshow below. It might take you on a nostalgic trip through time. And time is what this story is all about.
source: GoogleCode via Reddit, AndroidAuthority
Posts: 565; Member since: Mar 29, 2013
I'm very disappointed with the latest Android release tbh. Google didn't seem to impress me as they did in other years. It was Microsoft of all companies that actually managed to wow me. I hope Android M actually packs a lot more new stuff
posted on Dec 12, 2015, 3:36 PM 2
Posts: 5585; Member since: Feb 10, 2013
Its still happening for me on my Nexus 5 But I have Greenify with Aggressive Doze enable, so that's probably why I'm sticking with Aggressive Doze on since it gives me another 1 hr of SOT, I still have my good old normal watch for time
posted on Dec 12, 2015, 3:54 PM 0
Posts: 427; Member since: Nov 12, 2012
Wow, seriously little bug like this came undetected by the biggest IT Company in the World?? WTF Google, can't you test drive an update for a month of use before releasing it to public?? Lolliflop was one hell of mess because of this and yet you didn't learn any lesson from it??
posted on Dec 12, 2015, 4:21 PM 1
Posts: 1957; Member since: Aug 15, 2013
Any bug can go undetected if it only happens on a small portion of devices. I have 4 devices running Marshmallow and none of them have this bug. This article is the first time I'm hearing about it.
posted on Dec 12, 2015, 4:44 PM 5
Posts: 902; Member since: May 08, 2013
When the clock drags heavy... And there's no time for tea...
posted on Dec 12, 2015, 4:25 PM 0
Send a warning to post author
Send a warning to Selected user.
The user has 0 warnings currently.
Next warning will result in ban!
Ban user and delete all posts
Message to PhoneArena moderator (optional):