Clock Keeps Resetting #552

Closed
BobsUncle opened this Issue Dec 30, 2016 · 27 comments

Comments

Projects
None yet
7 participants
@BobsUncle

Successfully flashed Nexus5x

Purchased 6P.

Flashed. After every reboot the clock resets back to year 1971.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 30, 2016

Contributor

On which device?

Contributor

thestinger commented Dec 30, 2016

On which device?

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 30, 2016

brand new Nexus 6P

brand new Nexus 6P

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 30, 2016

Contributor

Can you try with stock Android?

Contributor

thestinger commented Dec 30, 2016

Can you try with stock Android?

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 30, 2016

Contributor

Also, best to try without it having a SIM card / network access to make sure it's not simply updating the time itself. As in set proper time, reboot, without it having a way to get it if it gets reset.

Contributor

thestinger commented Dec 30, 2016

Also, best to try without it having a SIM card / network access to make sure it's not simply updating the time itself. As in set proper time, reboot, without it having a way to get it if it gets reset.

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 30, 2016

Reflashed to stock. Clock works fine all normal.

No sim card has been used in this phone period so that can't be the cause.

I will now try to reflash the 6P to copperhead see what happens.

Reflashed to stock. Clock works fine all normal.

No sim card has been used in this phone period so that can't be the cause.

I will now try to reflash the 6P to copperhead see what happens.

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 31, 2016

The problem still persists. Just to do a recap:

Fresh Nexus 6P unlocked. Clocks reset to 1971 after every reboot. Followed instructions exact same process as Nexus 5X which I worked successfully. Problem persists so I refreshed stock android. The clock was working fine under stock android. So I re flashed back to copper head re downloaded all files and did it fresh. Problem persists.

The problem still persists. Just to do a recap:

Fresh Nexus 6P unlocked. Clocks reset to 1971 after every reboot. Followed instructions exact same process as Nexus 5X which I worked successfully. Problem persists so I refreshed stock android. The clock was working fine under stock android. So I re flashed back to copper head re downloaded all files and did it fresh. Problem persists.

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 31, 2016

Please someone suggest something I might be able to do to fix this

Please someone suggest something I might be able to do to fix this

@zongo

This comment has been minimized.

Show comment Hide comment
@zongo

zongo Dec 31, 2016

Make sure all update are done on stock. Then flash.have a brand new 6P and have been using copperheadOS as my daily driver for the past month with no issue at all. Clock resetting sounds more hardware related though

zongo commented Dec 31, 2016

Make sure all update are done on stock. Then flash.have a brand new 6P and have been using copperheadOS as my daily driver for the past month with no issue at all. Clock resetting sounds more hardware related though

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 31, 2016

but it only happens on copperhead works fine in stock android

but it only happens on copperhead works fine in stock android

@canary5

This comment has been minimized.

Show comment Hide comment
@canary5

canary5 Dec 31, 2016

I can confirm this issue. But if you flashed factory earlier, and update recent otas, you have no problems. I have another 6p, updating it from september i think, the time doesnt reset

canary5 commented Dec 31, 2016

I can confirm this issue. But if you flashed factory earlier, and update recent otas, you have no problems. I have another 6p, updating it from september i think, the time doesnt reset

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 31, 2016

Contributor

@zongo You don't need to do stock updates before flashing CopperheadOS. Nothing remains from the stock images after flashing CopperheadOS. It flashes / updates the low-level firmware too.

Contributor

thestinger commented Dec 31, 2016

@zongo You don't need to do stock updates before flashing CopperheadOS. Nothing remains from the stock images after flashing CopperheadOS. It flashes / updates the low-level firmware too.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 31, 2016

Contributor

Can't reproduce this so someone with the problem will need to debug it. At the very least, logs will be required, but that's probably not going to provide the information required to fix the problem.

Contributor

thestinger commented Dec 31, 2016

Can't reproduce this so someone with the problem will need to debug it. At the very least, logs will be required, but that's probably not going to provide the information required to fix the problem.

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 31, 2016

Solved!

The nexus I purchased for this project was brand new. After I put a non-activated SIM card in the problem resolved itself and now the clock works even after reboot.

So perhaps, put a note somewhere for anyone else like myself who goes and buys a new Nexus 6P phone to setup copperhead that they should insert a SIM card to make sure the hardware clock gets proper sync. The SIM card does not need to be activated.

Thank you community for support.

BobsUncle commented Dec 31, 2016

Solved!

The nexus I purchased for this project was brand new. After I put a non-activated SIM card in the problem resolved itself and now the clock works even after reboot.

So perhaps, put a note somewhere for anyone else like myself who goes and buys a new Nexus 6P phone to setup copperhead that they should insert a SIM card to make sure the hardware clock gets proper sync. The SIM card does not need to be activated.

Thank you community for support.

@BobsUncle

This comment has been minimized.

Show comment Hide comment
@BobsUncle

BobsUncle Dec 31, 2016

OK, I just noticed if I reboot the Nexus 6P in airplane mode the internal clock resets back to 1971.

OK, I just noticed if I reboot the Nexus 6P in airplane mode the internal clock resets back to 1971.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jan 15, 2017

Contributor

So perhaps, put a note somewhere for anyone else like myself who goes and buys a new Nexus 6P phone to setup copperhead that they should insert a SIM card to make sure the hardware clock gets proper sync. The SIM card does not need to be activated.

I thought I made it clear, but this isn't a normal issue. It isn't something that everyone is experiencing, only a few people, and none of them bought phones from us where we know the OS is flashed properly and unmodified.

Contributor

thestinger commented Jan 15, 2017

So perhaps, put a note somewhere for anyone else like myself who goes and buys a new Nexus 6P phone to setup copperhead that they should insert a SIM card to make sure the hardware clock gets proper sync. The SIM card does not need to be activated.

I thought I made it clear, but this isn't a normal issue. It isn't something that everyone is experiencing, only a few people, and none of them bought phones from us where we know the OS is flashed properly and unmodified.

@thestinger thestinger closed this Jan 15, 2017

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jan 15, 2017

Contributor

This doesn't appear to be a CopperheadOS issue since there are many reports about this upstream and it can't be reproduced here. The reason you're getting inconsistent results is likely inconsistent testing.

Contributor

thestinger commented Jan 15, 2017

This doesn't appear to be a CopperheadOS issue since there are many reports about this upstream and it can't be reproduced here. The reason you're getting inconsistent results is likely inconsistent testing.

@canary5

This comment has been minimized.

Show comment Hide comment
@canary5

canary5 Jan 18, 2017

I did clean install. Edited time settings settings. Rebooted. And it was reset. Heres the log.
pastebin.com/QmNG6rQe

canary5 commented Jan 18, 2017

I did clean install. Edited time settings settings. Rebooted. And it was reset. Heres the log.
pastebin.com/QmNG6rQe

@thestinger thestinger reopened this Jan 18, 2017

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jan 30, 2017

Contributor

Are you using airplane mode?

Contributor

thestinger commented Jan 30, 2017

Are you using airplane mode?

@canary5

This comment has been minimized.

Show comment Hide comment
@canary5

canary5 Jan 30, 2017

Yes

canary5 commented Jan 30, 2017

Yes

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jan 30, 2017

Contributor

Check what happens with WiFi disabled, no SIM card inserted but airplane mode not enabled.

Contributor

thestinger commented Jan 30, 2017

Check what happens with WiFi disabled, no SIM card inserted but airplane mode not enabled.

@canary5

This comment has been minimized.

Show comment Hide comment
@canary5

canary5 Jan 30, 2017

Still same, the clock was resetted

canary5 commented Jan 30, 2017

Still same, the clock was resetted

@e-lektryk

This comment has been minimized.

Show comment Hide comment
@e-lektryk

e-lektryk Feb 5, 2017

I think I have just seen simillar issue on my Nexus 6p. Today 05.02.2017 aproximatelly at 9 have installed February update. Just after phone restart, it showed date 04.02.2017, time aproximatelly at 22. Correct time was displayed after I entered pin for SIM card (and synchronise with network). I have a feeling that "last known time" is stored somewhere in the system and restored on phone restart, however it is updated only in some specific condition.

I think I have just seen simillar issue on my Nexus 6p. Today 05.02.2017 aproximatelly at 9 have installed February update. Just after phone restart, it showed date 04.02.2017, time aproximatelly at 22. Correct time was displayed after I entered pin for SIM card (and synchronise with network). I have a feeling that "last known time" is stored somewhere in the system and restored on phone restart, however it is updated only in some specific condition.

@ubestemt

This comment has been minimized.

Show comment Hide comment
@ubestemt

ubestemt Feb 17, 2017

My Nexus 6P also has this bug. I have used it with a SIM card, but in airplane mode. Whenever I restart the phone, the clock gets reset (to 1971). I ran some simple tests:

  1. flight mode enabled, "automatic time & date" enabled: Clock gets reset.
  2. flight mode enabled, "automatic time & date" disabled: Clock gets reset.
  3. flight mode disabled, "automatic time & date" enabled: Clock gets set correctly.
  4. flight mode disabled, "automatic time & date" disabled: Clock gets reset.

Then I removed the SIM card and repeated test 1 and 3...and got the same results. (I didn't keep track of when wifi was enabled, but it has always been enabled before when the clock has been reset before.)

Whenever I disabled flight mode and enabled automatic time & date, the clock would be set correctly.

So it seems that the clock gets reset on every boot and the network-provided time is needed to set the clock again.

My Nexus 6P also has this bug. I have used it with a SIM card, but in airplane mode. Whenever I restart the phone, the clock gets reset (to 1971). I ran some simple tests:

  1. flight mode enabled, "automatic time & date" enabled: Clock gets reset.
  2. flight mode enabled, "automatic time & date" disabled: Clock gets reset.
  3. flight mode disabled, "automatic time & date" enabled: Clock gets set correctly.
  4. flight mode disabled, "automatic time & date" disabled: Clock gets reset.

Then I removed the SIM card and repeated test 1 and 3...and got the same results. (I didn't keep track of when wifi was enabled, but it has always been enabled before when the clock has been reset before.)

Whenever I disabled flight mode and enabled automatic time & date, the clock would be set correctly.

So it seems that the clock gets reset on every boot and the network-provided time is needed to set the clock again.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 17, 2017

Contributor

The symptoms are understood at this point, not the cause. All that's needed is for someone able to reproduce this to debug the cause so it can be fixed.

Contributor

thestinger commented Feb 17, 2017

The symptoms are understood at this point, not the cause. All that's needed is for someone able to reproduce this to debug the cause so it can be fixed.

@kittenpirate

This comment has been minimized.

Show comment Hide comment
@kittenpirate

kittenpirate Mar 8, 2017

I have the same problem with my Nexus 6P whenever I use it in airplane mode with CopperheadOS.

I have the same problem with my Nexus 6P whenever I use it in airplane mode with CopperheadOS.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 9, 2017

Contributor

As I said the symptoms are well understood, this only requires someone to work on it.

Contributor

thestinger commented Mar 9, 2017

As I said the symptoms are well understood, this only requires someone to work on it.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Apr 8, 2017

Contributor

Closing in favour of #616 which can actually be reproduced.

Contributor

thestinger commented Apr 8, 2017

Closing in favour of #616 which can actually be reproduced.

@thestinger thestinger closed this Apr 8, 2017

@thestinger thestinger locked and limited conversation to collaborators Apr 8, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.