NanoClock: Yet another persistent clock

[trampas]

It must have been in the README that I read it. I am on 4.32 already so this is a big shame as I love the results from miniclock/nanoclock. I have used miniclock for years but it doesn't work well with buttons as nanoclock does, and I really don't want to do any more fiddling. Happy to do testing if you need it though.

[frostschutz]

Originally Posted by trampas

Three or four times while reading, the Libra 2 has frozen and then after about 30 seconds rebooted. I uninstalled NanoClock and all has been well since (fingers crossed). Could there be Libra 2/NanoClock issues?

For my random reboots (they happen without any mods installed), using devmodeon, Force Wifi On helped, but it's a battery drain.

I haven't yet had the chance to test with 4.32 more extensively. It rebooted twice when disconnecting USB cable, and funnily enough, USB connection is when the Libra 2 shuts down Wifi, even with Force Wifi On.

So maybe it's wifi related or just something else not getting enough power at the right time, pulling the entire system down with it. But that's just a wild guess...

I have nothing on this issue, no logs no kernel messages... maybe I need a serial console for this thing.

[NiLuJe]

Yeah, we'd either need pstore support in the kernel or a serial console, as it's just a kernel hang that trips the watchdog reset, and the whole thing never happens while plugged in or with Wi-Fi enabled, so SSH over Wi-Fi/USBNet is out :/.

@frostschutz: Huh. I seemed to remember being able to keep Wi-Fi on during USBMS w/ ForceWifi?

[Deobulakenyo]

Nano lock for whatever reason disappears whenever i remove my Libra 2 in Calibre after connecting to it ang updating the database after eject.

Connecting it to the PC and ejecting it via Windows File Explorer (not using Calibre) doesn't mess it up.

It has been like this ever since. Even in fw 4.30.

[NiLuJe]

That's... mildly interesting .

As usual, the answer is: debug logs or it didn't happen .

[jackie_w]

Originally Posted by NiLuJe

That's... mildly interesting .

I have a Libra2 on fw 4.32. I don't remember seeing any problems with NanoClock after disconnecting USB - either via calibre or via Win10. I just confirmed by trying both.

I'm not trying to imply that @Deobulakenyo isn't having problems, just that it's not universal.

[Deobulakenyo]

Originally Posted by NiLuJe

That's... mildly interesting .

As usual, the answer is: debug logs or it didn't happen .

I have been asking before how to get the debug logs so i can post it here.

I will also take a video of the libra 2 screen next time and will show you.

Sometimes i need to reboot my device up to six times for nanoclock to show again.

[MGlitch]

From the first page of this thread:

Originally Posted by NiLuJe

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.

[DNSB]

Originally Posted by MGlitch

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 anything that would require you to do more.

As it says in the nm_nanoclock file: Dump NanoClock's log to a file, because Dev mode log dumps are now encrypted :/.

[Deobulakenyo]

Being a non-techy person, some of what was posted recently is like reading hieroglyphs for me. Sorry it is my fault for not understanding whether the instructions still stands or it was changed or how the shell access work and dumping the encrypted file works.

[NiLuJe]

Flip those two keys to true in your config, do stuff (ideally stuff that breaks ^^), then connect the device to your computer again to get me the .adds/nanoclock/nanoclock.log file .

EDIT: Reading the description (I, err, don't remember the code. This was added as a last resort hack, it's not bullet proof nor particularly well thought out ), you might actually need to do this in *three* steps: flip both settings in the config; eject; do stuff; flip the debug switch *only* in the config; eject; plug again to get updated log.

If possible, the NickelMenu approach described above or in the other thread might be slightly less cumbersome (because, yeah, the stock devmode approach mentioned earlier is no longer viable).

[Deobulakenyo]

Here is the log (attached) this was generated after connecting to Calibre, importing a kepub book on Libra 2, device updated the books on my device, then nanoclock disappears on my device. then i generated the log via nickelmenu

This is the log's last part:

	Also found a crash log from: 2022-04-22 19:08:22.000000000

./bin/luajit: lib/inifile.lua:60: attempt to index a nil value
stack traceback:
	lib/inifile.lua:60: in function 'parse'
	./nanoclock.lua:363: in function 'handleNickelConfig'
	./nanoclock.lua:422: in function 'reloadNickelConfig'
	./nanoclock.lua:295: in function 'setupInotify'
	./nanoclock.lua:892: in function 'waitForEvent'
	./nanoclock.lua:1234: in function <./nanoclock.lua:1217>
	[C]: at 0x0001b1f5

Note: I just put an extension .txt file for the log to be uploaded

[NiLuJe]

Huh, that's... interesting. That would imply there's suddenly an orphaned (outside of any section) key/value pair at the top of Nickel's config.

I'll fix the parser to handle that more gracefully, thanks .

[NiLuJe]

And released version 0.11.2, which should fix the crash mentioned above .

[Deobulakenyo]

Originally Posted by NiLuJe

And released version 0.11.2, which should fix the crash mentioned above .

Thank you but...

Still happens. after importing a book via calibre using USB connection, nanoclock disappears

Using Kobo Uncaged, nanoclock works fine after disconnecting via KU in the device or ejecting via Calibre