• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root time in cwm

cwhatever

cwhatever

Life Goes On
was wondering if anyone has had a problem with the time in cwm and if it can be fixed and how?? mine is off by quite a few hours and has always been since day one.
 
cwhatever said:
was wondering if anyone has had a problem with the time in cwm and if it can be fixed and how?? mine is off by quite a few hours and has always been since day one.
Click to expand...

time in clockworkmod? you cant see the time there
if your clock is off, it's probably your timezone.
look in settings, under Data and Time
 
Koumajutsu said:
time in clockworkmod? you cant see the time there
if your clock is off, it's probably your timezone.
look in settings, under Data and Time
Click to expand...

Looooooolz!
Get it?!
Clock.
Work.
Mod?
XD I think he's tugging our clocks man! XD
Haaha moddi g our clocks. XD
 
no , when i or anyone does a backup the first #'s are the date and the next set of #'s looks like the time hours mins and sec and mine if i do a backup at lets say 10pm mine will have tomorrows date on it when i did it today and the time (if the next set of #'s is time) starts all over and if i do lets say 4 bu's in one day the next #'s if i do them 2 hours apart those numers are 2 hours apart. I KNOW WE CAN'T SEE A CLOCK AND THE RUNNING CLOCK IS FINE. if wrong what are the next set of #'s and why if i make one early it will have tomorrows date on it?????


if it is time mine is in millitary time and never a bu past 24 always (0to 24)
 
Mine always shows 1970 as the year... LG Spectrum on mine, never even looked at the hour or minutes!

All of these backups were run in March the days are definitely off, I did not even buy this phone until March 12th or so.

a6f84186-a791-e2d5.jpg
 
if you look at your backups at least mine after the dat the 1st # never hier than 24 te2nd never higher than 60 and the 3rd never higher than 60 just like a clock if this is the case mine is off???
 
cwhatever said:
no , when i or anyone does a backup the first #'s are the date and the next set of #'s looks like the time hours mins and sec and mine if i do a backup at lets say 10pm mine will have tomorrows date on it when i did it today and the time (if the next set of #'s is time) starts all over and if i do lets say 4 bu's in one day the next #'s if i do them 2 hours apart those numers are 2 hours apart. I KNOW WE CAN'T SEE A CLOCK AND THE RUNNING CLOCK IS FINE. if wrong what are the next set of #'s and why if i make one early it will have tomorrows date on it?????


if it is time mine is in millitary time and never a bu past 24 always (0to 24)
Click to expand...

Remember that you can change it to what ever you want it to say . Just make sure there are no spaces in the title . :D

EDIT : You're correct . it's the date and military time .
 
finndo77 said:
Mine always shows 1970 as the year... LG Spectrum on mine, never even looked at the hour or minutes!
Click to expand...

the prevail has todays date and the 3' #s after it like 22.53.46
the whole saved folder in backup of cwm looks like this
(2012-03-07.22.19.52) right after the folder
 
finndo77 said:
Mine always shows 1970 as the year... LG Spectrum on mine, never even looked at the hour or minutes!

All of these backups were run in March the days are definitely off, I did not even buy this phone until March 12th or so.

a6f84186-a791-e2d5.jpg
Click to expand...



yours also has 4 numbers after date prevail or at least min has 3
 
ironmask said:
I did a backup yesterday and mine looks ok... somehow yours definitely is off...

ad3573cd-a9e0-1aeb.jpg
Click to expand...




yeh mine the date and time are working but off by like a few hours so if i make a backup late at night will be tomorrow and in a week if i need it will forget and look for the late night one and the one i want will have the next day on it so confusing
 
the next time someone who reads this thread if you think of it when making a backup after look and see if time matches the actual time you did it
 
cwhatever said:
the next time someone who reads this thread if you think of it when making a backup after look and see if time matches the actual time you did it
Click to expand...

Backing up now...

Weird it wrong on mine too, just ran a backup and none of my backups say April first... now I'm confused... lol
 
DaisFlaque said:
Backing up now...

Weird it wrong on mine too, just ran a backup and none of my backups say April first... now I'm confused... lol
Click to expand...


see those #'s are time and they are off and mine have been for a while and never even noticed till started paying attention to them for restore purposes
 
finndo77 said:
Mine always shows 1970 as the year... LG Spectrum on mine, never even looked at the hour or minutes!

All of these backups were run in March the days are definitely off, I did not even buy this phone until March 12th or so.

a6f84186-a791-e2d5.jpg
Click to expand...

This is clearly a bug in which the interpreting program (the file manager) believes the timestamp was stored in "ctime" format. Since this isn't general knowledge, this is what ctime is:

The ctime(), gmtime() and localtime() functions all take an argument of data type time_t which represents calendar time. When interpreted as an absolute time value, it represents the number of seconds elapsed since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).
Click to expand...

This is a very valuable for programming dates etc because it makes date math extremely easy. For example, I want to store when a program was first installed. I will use the ctime (absolute time? my terminology may be off) value, which at this very moment happens to be 1333337047. Lets say I want to compare this to when another event happened. Its time stamp is also in this format, but of course a different time. Instead of going through complicated date math, they would just find out the difference between the two dates and then convert that to a real date using a simple function.

Just giving the why. Now we need someone to track down the bug and fix it :)
 
Kamel said:
This is clearly a bug in which the interpreting program (the file manager) believes the timestamp was stored in "ctime" format. Since this isn't general knowledge, this is what ctime is:



This is a very valuable for programming dates etc because it makes date math extremely easy. For example, I want to store when a program was first installed. I will use the ctime (absolute time? my terminology may be off) value, which at this very moment happens to be 1333337047. Lets say I want to compare this to when another event happened. Its time stamp is also in this format, but of course a different time. Instead of going through complicated date math, they would just find out the difference between the two dates and then convert that to a real date using a simple function.

Just giving the why. Now we need someone to track down the bug and fix it :)
Click to expand...


that is what i am talking about!!!!!!!!!!!!!
 
wetbiker7 said:
Mine gives the correct date and time . Don't know why yours is off . Did you updated CWM with Hroarks update ?
Click to expand...

man i tried reflash and the update and nothing, today just flashed REDIT and is pretty cool(my favorite is the red and blue) also did update again and now time is right COOL!!!!!!!!!!!! thx man!!:D:D:D
 
cwhatever said:
man i tried reflash and the update and nothing, today just flashed REDIT and is pretty cool(my favorite is the red and blue) also did update again and now time is right COOL!!!!!!!!!!!! thx man!!:D:D:D
Click to expand...

No problem. I like the new theme by Gus is too ! I got to test it last night and been running it ever since . :D
 
You must log in or register to reply here.
Back
Top Bottom