"date" reports correct time zone and time; UI reports a time several hours off
 

I pushed a file from /usr/share/zoneinfo to my kindle's /var/local/system/tz file. It shows the time zone I want when I run "date" on it, but the Kindle's time (in the UI) is several hours off. What's wrong?

For the record, this Kindle is not registered to Amazon.

Set BOTH the system time and the hardware clock.
Both set to the same (GMT) time.

?? Is the "several hours off" happen to be your offset from TZ-0?

I'll give an example. From my Linux machine, I push my Los_Angeles (PDT) zoneinfo file to /var/local/system/tz:
On my Kindle, I run ntpdate to sync the time:
I check the date on the Kindle:
The time and time zone is correct. On the Kindle UI, I press the Menu button, and it reports 11:17 PM instead of the 4:17 PM on the system time. If I write the current time to the hardware clock (hwclock -w), the time in the UI remains the same.

And after you do a re-start? (Which should not be required)

And my earlier question - how many hours off is that time displayed in the UI?

Yeah, it gets tricky sometimes.

Cf. /usr/sbin/setdate && /usr/sbin/settz && /usr/sbin/updatetime

The K5 ;st shortcut calls setdate with the wanted time in the %s format. (use date -D "inputfmt" +outputfmt "time" to convert, or use the output of a full fledged date from a proper Linux system).

Same problem here : Paperwhite not keeping Time

The problem has already been covered.

I want to set the date via NTP with a correct zoneinfo file :p I could fidget with "date -s MMDDhhmm[[CC]YY][.ss]", but that just feels gross working as a sysadmin :p

I don't want to register the Kindle with Amazon.

/usr/sbin/updatetime is Amazon's wrapper around ntp, IIRC.

Install the KUAL.ntpdate button.
Change the time server(s) or time server network(s) as desired per the directions.

Right ! Your off by the gmt offset in the two readings.
Being a sysadmin, you can probably fix that better than we could. ;)

... this method has always worked for me:
https://wiki.mobileread.com/wiki/Kind..._the_time_zone

That's what I mentioned in my original post. The time is still incorrect on the Kindle's UI.

Try rebooting your Kindle. And maybe try symlinking the /etc/localtime file directly to the timezone file, instead of indirectly via /var/local/system/tz.

I just tried it again on a Kindle Touch, and it worked again as expected (but only after a reboot, not immediately via SSH - not even if restarting the framework).

EDIT: Yep... you're right. Even after setting up everything correctly, the K4 will simply stick to displaying UTC in the user interface. I guess "inability to show the correct timezone" is just one more thing to complain about to Amazon CS. I'm personally not terribly surprised.

Ah, phooey.
Lab126 forgot the -u option use in their testing and/or scripting.
And that crew **gets paid** to turn out this stuff!

@ixtab: Any chance that Java is somewhere maintaining its own idea of the date/time/tz without reference to the system/hardware clocks?
I.E: A module that should only be used on systems that do not have hardware date/time?

Hmm...
I guess I could re-write the ntpdate button to store local time in the hardware of the K4.
But that seems kind of like a kludge to me.

Nothing specific that I'd know of. But (even without being able to provide exact code), something like "get current time, and display it as Zulu time" should be straightforward to code.

It doesn't really make sense, but it's seemingly what they did. Maybe because they didn't even ship the files required to support time zones in the first place, so they assumed the only "existing" TZ would be UTC anyway?

"Who needs more than one timezone anyway? Or, for that matter, who needs the correct date and time on an e-book reader?"

:smack: