View Single Post
Old 04-21-2022, 01:21 AM   #188
MGlitch
Wizard
MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.
 
Posts: 2,857
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
From the first page of this thread:

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.

Knowing NiLuJe it's unlikely this process has changed, unless something Kobo did made it so it had to change. But since you should be able to do all of those steps still, I don't think Kobo changed anythign that would require you to do more.
MGlitch is offline   Reply With Quote