MobileRead Forums - View Single Post

lineage · 11-20-2012, 07:04 PM

In case anyone else finds this thread while hunting down timezones..

I also found my timezone was GMT offset by 3:02. This is an unregistered kindle 4 touch.

I connected over the USB net interface with ssh and tried the following;

I replaced the tz file with the one from my main linux distro (arch). I have a slight worry that its a much more complex file, but the kindle seems happy with it so far. Initially I just moved the tz file to tz.was and the time then looked to be in straight UTC.

I then used

Code:

ntpdate 192.168.15.1

to get the time from my connected linux machine then

Code:

hwclock -w

to write the time to the h/ware. Not sure if thats needed, but the hw time from

Code:

hwclock -r

was showing 1970.. At that point date returned a sensible time but the book reader still had the 3:02 offset. That seems to be stored in

Code:

/var/local/java/prefs/com.amazon.ebook.framework/prefs

There were 2 entires that had the offset in, device.tz.lasttz and the device.tz.ltosec which seems to be a seconds offset equal to 3:02. I edited the file with vi.

After that a reboot and all seems sane. At least for now.

11-20-2012, 07:04 PM	#9
lineage Member Posts: 1 Karma: 10 Join Date: Nov 2012 Device: kindle 4 touch	In case anyone else finds this thread while hunting down timezones.. I also found my timezone was GMT offset by 3:02. This is an unregistered kindle 4 touch. I connected over the USB net interface with ssh and tried the following; I replaced the tz file with the one from my main linux distro (arch). I have a slight worry that its a much more complex file, but the kindle seems happy with it so far. Initially I just moved the tz file to tz.was and the time then looked to be in straight UTC. I then used Code: ntpdate 192.168.15.1 to get the time from my connected linux machine then Code: hwclock -w to write the time to the h/ware. Not sure if thats needed, but the hw time from Code: hwclock -r was showing 1970.. At that point date returned a sensible time but the book reader still had the 3:02 offset. That seems to be stored in Code: /var/local/java/prefs/com.amazon.ebook.framework/prefs There were 2 entires that had the offset in, device.tz.lasttz and the device.tz.ltosec which seems to be a seconds offset equal to 3:02. I edited the file with vi. After that a reboot and all seems sane. At least for now.