Mobileread
Pocketbook (Inkpad 3) clock stopping
#1  zslengyel 04-19-2019, 04:35 PM
Hello, I'm just curious whether anyone else has experienced this: since several weeks the clock in my PB-IP3 (with the latest fw) does not work, time does not move forward at all, it only gets actualized when I sync the device, then it remains in one place again. I haven't seen this reported on any PB related forums, and the only thing that has changed on my device was that I have updated koreader, so I suspect it has something to do with this issue. BTW this behaviour has started around the time this (otherwise very cool) fix has been implemented: https://github.com/koreader/koreader-base/commit/5cce44682599de3daab08b770a251c3f25dfc6f8
Have you seen anything like this? Were you able to solve it? I don't want to report an issue before I am sure it really is koreader-related, but I also don't want to make a factory reset without believing it could really help.
Thanks for any answers!
Reply 

#2  Frenzie 04-19-2019, 05:32 PM
If you mean the clock in KOReader, perhaps you'd best make sure Settings → Status bar → Auto refresh time is checked? Or does it also not update when changing pages?
Reply 

#3  zslengyel 04-19-2019, 05:39 PM
Thank you for your answer, but it surely isn't a display thing: it doesn't update when changing pages, but it also does not update at all while outside of koreader, the system clock itself is broken (that's why I'm not 100% sure it's related to koreader).
Reply 

#4  NiLuJe 04-19-2019, 06:08 PM
Yeah, we're definitely not handling time-keeping ourselves, we're just displaying what the system tells us. If it's broken, we display broken stuff .

TL;DR: Yeah, probably not our bug. If it behaves the same way in vanilla software after a full reboot of the device, probably not anyone's bug, either .
Reply 

#5  Frenzie 04-20-2019, 02:46 AM
If the clock itself is broken I'm 99.999 % sure it's not related to KOReader.

(I've never really heard of a broken clock before…)
Reply 

#6  pazos 04-20-2019, 04:09 PM
I found something similar on other freescale socs. If date is too old (say 2005) the rtc won't tick. You won't find this behaviour often because the hwclock will drain a bit of battery to keep the time in sync, but if the battery is really empty this can happen.

I'm not sure if Pocketbook has a menu to set date & time from its gui. For Cervantes (which can run with KOReader only) a workaround is -> https://github.com/koreader/koreader/blob/master/platform/cervantes/koreader-standalone.sh#L10-L15
Reply 

#7  NiLuJe 04-20-2019, 05:58 PM
Huh.

On a K2, the clock will drop back to epoch I you drain the battery, but it will keep ticking .
Reply 

#8  Frenzie 04-21-2019, 05:43 AM
Yeah, all clocks I'm familiar with will drop back to some date that makes sense to them (whether it's 1900, 1970, 1980, 2005 or 2010), although of course it's always possible they do it through software like @pazos.

Btw, why 2010 and not 2018 or 2019? :P
Reply 

#9  bachvarov 06-05-2019, 05:32 PM
I have exactly the same issue after installing koreader. My system clock no longer works. I formatted everything and reflashed but it still does not work. Any ideas?
Reply 

Today's Posts | Search this Thread | Login | Register