View Single Post
Old 06-19-2021, 11:36 AM   #21
Phil_C
Addict
Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.
 
Phil_C's Avatar
 
Posts: 277
Karma: 391602
Join Date: Oct 2009
Location: Chicago, IL USA
Device: Sony PRS-350; Kobo Clara HD; Kobo Clara 2E; Kobo Clara BW
Quote:
Originally Posted by NiLuJe View Post
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.
I attached the only log file I see after following your instructions. (I added a .txt extension so it would be allowed here.)
Attached Files
File Type: txt log-2021.06.19-10.07.51.txt (81.6 KB, 308 views)
Phil_C is offline   Reply With Quote