Mural Watchface Brings 500px to Android Wear

On a traditional watch, you can’t really do too much to change its appearance once … more

Android 5.0 Favorite Features, Release November 3rd? – XDA TV

Google Confirms Android 5.0 Lollipop for November 3rd! That and much more … more

Prepare Your Build Machines: Ubuntu 14.10 Utopic Unicorn Now Official

Today is an important day for any and all Linux enthusiasts. One of the … more

Track the Time You Waste on Social Media with Socials Addict

When you use your phone, you often don’t even realize how much time you … more
Post Reply

[Q] AOSP build from source. Time and date goes back to 1970.

OP bariz143

23rd April 2014, 02:34 AM   |  #1  
bariz143's Avatar
OP Senior Member
▂ ▃ ▅ ▆ █
Thanks Meter: 317
 
1,653 posts
Join Date:Joined: Dec 2009
More
Hi guys.

Just started to buld my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.

I flash the buld and everything works great to. Time and date is correct. Google sync works. Google now works.

But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error. Time error and whats up says time error to. Goggle sync is stuck on sync. google now dont work and so on.

I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.

I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?

I have been trying to fix this for days without any luck.


Last edited by bariz143; 23rd April 2014 at 02:39 AM.
justinisloco
23rd April 2014, 04:11 AM   |  #2  
Guest
Thanks Meter: 0
 
n/a posts
Quote:
Originally Posted by bariz143

Hi guys.

Just started to buld my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.

I flash the buld and everything works great to. Time and date is correct. Google sync works. Google now works.

But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error. Time error and whats up says time error to. Goggle sync is stuck on sync. google now dont work and so on.

I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.

I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?

I have been trying to fix this for days without any luck.


Im not the sharpest crayon in the classroom, so take this with a grain of pepper...

It may be your recovery. I notice that my backups time code with 1970 ALL THE TIME. stopped using timestamps. But check in your recovery to see if you can adjust time.

Sent from my Nexus 5 using Tapatalk
The Following User Says Thank You to For This Useful Post: [ View ]
23rd April 2014, 04:13 AM   |  #3  
bariz143's Avatar
OP Senior Member
▂ ▃ ▅ ▆ █
Thanks Meter: 317
 
1,653 posts
Join Date:Joined: Dec 2009
More
Yeah I thought it was recovery to .tries philz, twrp and cwm without luck. The funny thing is cm11 based ROM don't have this bug and I have compiled both according to the guides

Sent from my AOSP on HammerHead using Tapatalk
23rd April 2014, 10:39 AM   |  #4  
rootSU's Avatar
Senior Member
Flag Oxenhope, West Yorkshire, UK
Thanks Meter: 12,247
 
23,252 posts
Join Date:Joined: Aug 2010
More
Quote:
Originally Posted by justinisloco

Im not the sharpest crayon in the classroom, so take this with a grain of pepper...

It may be your recovery. I notice that my backups time code with 1970 ALL THE TIME. stopped using timestamps. But check in your recovery to see if you can adjust time.

Sent from my Nexus 5 using Tapatalk

It's nothing to do with recovery. Recovery couldn't pick the time up because Qualcomm devices used a different method to record the time so for a long time, no one knew how to get this data into recovery.

This has been understood for a while now however, and it's the Qualcomm time daemon recording time in /data/system/time that can be used for time data however, with the build the OP has created, the time is not recording to that location.

Really what this thread needs to be asking is for anyone to point the OP to what a proper implementation of time daemon looks like I.e. the code


Sent from my Nexus 5 using Tapatalk
Last edited by rootSU; 23rd April 2014 at 10:45 AM.
The Following User Says Thank You to rootSU For This Useful Post: [ View ]
23rd April 2014, 01:12 PM   |  #5  
bariz143's Avatar
OP Senior Member
▂ ▃ ▅ ▆ █
Thanks Meter: 317
 
1,653 posts
Join Date:Joined: Dec 2009
More
Would be very appreciated if someone could pint me in the right direction.

Sent from my AOSP on HammerHead using Tapatalk
26th April 2014, 01:03 PM   |  #6  
bariz143's Avatar
OP Senior Member
▂ ▃ ▅ ▆ █
Thanks Meter: 317
 
1,653 posts
Join Date:Joined: Dec 2009
More
Anyone?

Skickat från min Nexus 5 via Tapatalk
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Nexus 5 Q&A, Help & Troubleshooting by ThreadRank