Android 6.0.1 fixes the system clock on your Android device that broke with Android 6.0

Android 6.0.1 fixes the system clock on your Android device that broke with Android 6.0
If you are rocking a device that has recently been updated to Android 6.0, you might have noticed something different about the system clock on your phone. A large number of complaints have been posted to the Google Code site about the clock running slow following the Android 6.0 update. This can play havoc with your alarms and event reminders set from your calendar.

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



4. magnanimus

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

5. WeezyF

Posts: 155; Member since: Jul 09, 2015

M? where ya at bruh?

22. magnanimus

Posts: 565; Member since: Mar 29, 2013

I meant N sorry

6. vincelongman

Posts: 5745; 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

7. uchihakurtz

Posts: 428; 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??

10. Awalker

Posts: 1986; 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.

13. vincelongman

Posts: 5745; Member since: Feb 10, 2013

I only noticed this after enabling Greenify's Aggressive Doze feature I wouldn't be surprised if this is mainly only affecting power users messing with Doze Mode

14. uchihakurtz

Posts: 428; Member since: Nov 12, 2012

Oh, I thought it affected many device. Sorry, I'm still recovering from Lollipop's failure.

15. joey_sfb

Posts: 6794; Member since: Mar 29, 2012

Never encounter the bug with my Nexus 6 either.

8. ThePython

Posts: 902; Member since: May 08, 2013

When the clock drags heavy... And there's no time for tea...

16. javy108

Posts: 1004; Member since: Jul 27, 2014

I always stop to read your comments, and its because the grumpy-cat pict.

9. joevsyou

Posts: 1093; Member since: Feb 28, 2015

that's a serious bug to let through

12. Mxyzptlk unregistered

I guess it was time for Google to fix this issue.

17. Professor

Posts: 223; Member since: Aug 02, 2013

I have the Nexus 5 with 6.0 since it was released and I dont have this (or any other) bug!!!

18. baldilocks

Posts: 1542; Member since: Dec 14, 2008

No 'bug' on my Nexus 5...

19. mike2959

Posts: 697; Member since: Oct 08, 2011

Most Android phones will never see it.

20. mrslark01

Posts: 1; Member since: Dec 13, 2015

looks great phone but with the clock problem its big issue.

23. ikenvape

Posts: 309; Member since: May 28, 2014

I swear, it's like Google is pressure selling the nexus line.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.