|
This also fixed my Lux 5. Thanks! Do be careful with the connector, its plastic cover can peel off.
Note this unit kept the correct date to within a day, with the time incrementing very slowly, appearing almost stuck. KoReader was never installed.
Thinking about it, one idea was the hardware clock producing ticks with random deviations. Over a longer period these could still average out. But this seems rather far fetched after +- 3 months.
Then it seems there are two variables keeping time, or parts thereof. Note time on linux (as used by PB readers) is usually expressed in seconds since "Epoch" (=1970). So keeping time involves incrementing a variable with these seconds. IIRC, sometimes this variable is split into a date and a hour part. The hour part can then be a smaller variable (i.e. <32-bits, with the full epoch time being 64-bits to account for dates after 2038).* An issue with the hour part could explain the UI and annotation date time issues.
As for the battery disconnect, it could reset a variable or the clock increment function**.
* reducing memory usage on embedded devices is a thing; but also consider backward compatibility with older devices.
** A signed vs unsigned integer issue? Both are represented differently IIRC.
|