Author Topic: Datentime Enhancement (Read 9514 times)

Jon_J · « **Reply #15 on:** March 13, 2007, 10:15:38 pm »

OK, I did this again, but this time I selected London 0 GMT
now the clock on the taskbar and the clock in datentime are showing as different (6 hours difference)
When I reboot, my time is correct.
Now I don't have to re-set my clock after each reboot.

But, I don't live in London, I live near Chicago or in the -6 GMT timezone (Saskatchewan)

EDIT: I tried this several times.
I set the zone to London 0 GMT, set the time, rebooted. the clock stayed correct to my time.
Then I set the zone to Saskatchewan -6 GMT, set the clock, and rebooted, the time is off by -6 hours again.
So I tried this again several times and I cannot get my clock to stay at correct time.
The only zone that works for me is London -0 GMT
EDIT2:
I just remembered I do have a modified mb-applet-clock made by daniel3000
https://www.oesf.org/forums/index.php?showt...ndpost&p=153012
It allows you to set options in ~/.matchbox/mbdock.session
I have mine set so it shows AM and PM like this:
mb-applet-clock -m -p 8
-m makes it show AM and PM
-p 8 makes the clock display smaller

Maybe this is what is causing me all my problems with time zones as I have posted about here and tryannozaurus.
I might need to remove those settings and go back to the old mb-applet-clock
It's hard for me to read a 24 hour clock, I always have to subtract 12 from anything higher than 13 O-clock.

Antikx · « **Reply #16 on:** March 14, 2007, 02:09:39 am »

I noticed my time was wrong after a resume today.
This time I stopped atd, ran ntpdate, restarted atd and so far so good.
I haven't tried rebooting yet.
EDIT: I just rebooted and it looks like I need to reset the time.
I should add that I haven't flashed to the latest and greatest yet. I'm one version behind now.

Jon_J · « **Reply #17 on:** March 14, 2007, 02:15:16 am »

my clock is fine if I don't reboot, but meanie mentions it is good to reboot pdaxii13 after installing/uninstalling stuff because it checks your disk and some other things on reboot and cleans up some other things. Can you tell I'm not too good at Linux terminology?

Antikx · « **Reply #18 on:** March 14, 2007, 02:30:43 am »

You're doing great man, don't worry about it.
I understand what you mean.

Meanie · « **Reply #19 on:** March 14, 2007, 08:51:39 am »

there was a problem with the way the datentime script worked. it assumes there is no timezones, only local time = gmt 0, but i hacked that

daniel3000 · « **Reply #20 on:** March 14, 2007, 09:58:25 am »

Quote

Great work based on my old crappy code - I still hate the fact that we made anything in python. One day we might get all the apps to be native c.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156054\"][{POST_SNAPBACK}][/a][/div]

Hi Laze,

I must say, it's not that bad than these tools are written in Python.
That way, it is relatively easy, even without much Python knowledge, to modify them slightly.

daniel

Jon_J · « **Reply #21 on:** March 15, 2007, 09:54:18 am »

The new datentime isn't working for me as I thought, I posted about this in the pdaxii13 thread for the spitz version.
https://www.oesf.org/forums/index.php?showt...ndpost&p=156323
I installed meanie's new datentime_1.0.8_armv5tel.ipk
Yesterday, I set the zone, then set the time, then rebooted.
I did the above twice, and my time remained correct.
This morning (next day) I rebooted and my panel clock lost 6 hours (again) just like it was doing several days ago.
I'm not sure what is going wrong, in the meantime, I'll have to resort to using London's timezone. (-0 GMT)
EDIT:
I just set the timezone to London and the clock inside datentime changed to my correct time, but the clock on the panel is off by -6 hours.
Whenever I would set the zone for my area, as previously, the clock in datntime would NOT move, and the panel clock would match the clock inside datentime.
Notice the 2 different actions?
1. Setting the zone to -0 GMT moves the clock in datentime
2. Setting the zone to -6 GMT does NOT move the clock in datentime. (It doesn't matter if the clock is actually correct or not, it doesn't move like in first example)

Antikx · « **Reply #22 on:** March 15, 2007, 10:33:33 am »

Sorry if you've tried this already, but have you tried not using the gui, and deleting /etc/localtime then recreating the symlink?

Jon_J · « **Reply #23 on:** March 15, 2007, 10:40:08 am »

I did the below before I installed the new datentime ipk
I renamed the /etc/localtime symlink, then created a new one that points to /usr/share/zoneinfo/America/Chicago
I had the same problem as always. Doing that didn't help, I was still loosing 6 hours when I rebooted.

Jon_J · « **Reply #24 on:** March 15, 2007, 10:50:54 am »

I may have found a problem, but I don't know the exact solution.
When I use the datentime GUI and set my zone to London, and look at the properties of this symlink /ect/localtime, it says it's linked to /usr/share/zoneinfo/London
When I use the datentime GUI and set my zone to Saskatchewan (which is -6 GMT) and I check the properties of the symlink /ect/localtime, it says it's linked to /usr/share/zoneinfo/MST7MDT
Where did Saskatchewan go, isn't it supposed to be linked to Saskatchewan??
EDITED out typing errors

Antikx · « **Reply #25 on:** March 15, 2007, 04:37:01 pm »

I was born and raised in Saskatchewan and I must finally admit that we are part of a world-wide time chaos conspiracy project.
In all seriousness I think that is the code for Sask time.
http://www.google.ca/search?hl=en&q=%2BMST...nG=Search&meta=

Jon_J · « **Reply #26 on:** March 15, 2007, 06:11:18 pm »

I just have to accept that using London -0 GMT is my only choice, otherwise I'll have to reset my clock after each reboot.

Antikx · « **Reply #27 on:** March 15, 2007, 10:02:37 pm »

Quote

I just have to accept that using London -0 GMT is my only choice, otherwise I'll have to reset my clock after each reboot.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156445\"][{POST_SNAPBACK}][/a][/div]

I've been resetting my time after a reboot since I first started using pdaXrom so I guess it doesn't bother me too much.
I forget, when using Cacko, does it keep the time after a reboot?

Jon_J · « **Reply #28 on:** March 15, 2007, 10:07:25 pm »

yes Cacko and sharp do keep time on reboot.
pdaxii13 is supposed to keep the time the same after reboot, but for some reason mine doesn't.
I do have a modified mb-applet-clock that uses changeable settings from ~/.matchbox/mbdock.session
It's in this post. https://www.oesf.org/forums/index.php?showt...12&#entry153012

Meanie · « **Reply #29 on:** March 15, 2007, 10:30:41 pm »

my date/time is remembered most the time after reboot unless it locks up and you have to reset it.

but how often do you actually need to reboot your Z? once a month? I just suspend/resume and it is so much more responsive after I fixed the multiple rotations from executing after a resume...

actually, make sure you do have the latest datentime.py file. installing a new package without removing the older version sometimes does not work. even though it tells you that you got the new package installed, you still have the old files...

when you run datentime.py from a terminal, you should see the date and time printed twice, once in GMT0 and once in your timezone...

News:

Author Topic: Datentime Enhancement (Read 9514 times)