View Single Post
Old 06-21-2021, 02:09 PM   #46
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
There we go, released v0.9.9.

As mentioned above, minor logging & documentation tweaks to make the aforementioned "ninja sleep" behavior clearer .

----

FWIW, I played a bit with *detecting* those and doing something (e.g., a tiny indicator that the clock is frozen), but it's mildly tricky, a lot race-y, somewhat intrusive, and the behavior is aggressive and predictable enough that it wouldn't serve much purpose anyway, as you can just assume that the device goes to bed ~5s after a page turn .

For curious people, all those experiments are in the public git history, and the final code was actually logically "sane", and actually achieved completely breaking the standby feature, thanks to the simple fact that the EPDC is itself a wakeup source, so catching the ninja in the act and sending a clock update right at that moment effectively *prevents* the suspend from succeeding. This isn't very nice though, and effectively launches Nickel into a repeated race with us to retry to suspend every 5s, which is why I dropped it .

Last edited by NiLuJe; 06-21-2021 at 05:12 PM.
NiLuJe is offline   Reply With Quote