View Single Post
Old 06-19-2021, 12:08 AM   #19
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
Then it definitely works on my end, so, looks like it's debugging time ^^.

* Enable Developer mode on your device (just search for devmodeon)
* Set debug to 1 in nanoclock.ini
* Do a bunch of stuff for a while, ideally including letting it sit a few minutes on a page
* Connect your device to a computer over USB, and send me the most recent syslog file (they're dumped in the .kobo folder, if memory serves).
* (You can then disable developer mode by searching for, you guessed it, devmodeoff ).

That's the long way 'round. If you have shell access, just get me the output of logread | grep 'nanoclock\[[[:digit:]]\+\]' (you'll still need to enable debugging in nanoclock, obviously ;p).

I'll see how viable shoving that in a NickelMenu entry might be tomorrow, too.
NiLuJe is offline   Reply With Quote