View Single Post
Posts: 6 | Thanked: 2 times | Joined on Feb 2013
#10
michaaa62,

Originally Posted by michaaa62 View Post
Towards b)
Did you by any chance do have the clock pull its time and date from the internet? While your custom script did prevent the manual setting first, there might be an essential setting missing

May be the update interval for HildonApplicationManager is set strangely? You might also use gconf-editor to look for that setting or the gconftool2 tool in X-Terminal.
Code:
gconftool -s --type int /apps/hildon/update-notifier/check_interval 100000
The clock just gets its info from the cell phone net. I don't have ntpd or anything like that installed because I don't leave the internet connection on most of the time, in order to save battery. I don't even really have a custom script to do this --- I literally just created an empty file called /var/dont_start_suw --- that 30osso_startup_wizard dealie (which is part of the default OS and normally runs the annoying dialogue and mucks up all my settings after I replace the battery) checks if that file is there and doesn't run if it is.

I checked the update interval for HAM as you suggested, and it was set to 1440, which is maybe a little shorter than it should be in these post-Nokia days, but not absurdly short. I tried setting it to 100000 as you suggested, but that didn't matter. I think my money is on actman doing something weird at this point, given the observation I reported in my previous comment.
 

The Following User Says Thank You to thebat137 For This Useful Post: