NanoClock: Yet another persistent clock

[nem]

Thanks for the feedback. I think i will just leave it where it is then.
It works nicely, and its good to keep track of time when reading at night. Hopefully no more 3am "surprises"

Thanks!

[Deobulakenyo]

Does this need to be updated for FW 4.31?

[albare]

I updated to 4.31 in Kobo sage and now don't work.


Enviado desde mi SM-A705FN mediante Tapatalk

[Deobulakenyo]

Originally Posted by albare

I updated to 4.31 in Kobo sage and now don't work.


Enviado desde mi SM-A705FN mediante Tapatalk

Have you tried this note from the dev of this?
"Note that, on the Sage, the same relative quirks as on the Elipsa apply (i.e., it takes two reboots to show up, and it's not as seamlessly baked into stock refreshes as on other devices)''

[albare]

Nanoclock work without problems in the previous firmware version.
I reinstall again nanoclock and reboot 3 or 4 times.
I can see nanoclock for 1 second but disappears and don't show again.

Enviado desde mi SM-A705FN mediante Tapatalk

[agugu]

Originally Posted by albare

Nanoclock work without problems in the previous firmware version.
I reinstall again nanoclock and reboot 3 or 4 times.
I can see nanoclock for 1 second but disappears and don't show again.

Enviado desde mi SM-A705FN mediante Tapatalk

Same sage,same situation.
What i do is to launch koreader then exit it.and nanoclock stays normal.
OK,you should operate this step each time the system reboots

[Deobulakenyo]

Dang. I cannot update my fw until i can have a working nanoclock version ��

[jackie_w]

Originally Posted by Deobulakenyo

Dang. I cannot update my fw until i can have a working nanoclock version

Why not? Your displayed details show that you have a Libra2. NanoClock has continued to work OK on fw 4.31.19086 for the devices on which I'd previously installed it (Libra2, Forma, ClaraHD). NanoClock and all its settings survived the upgrade. I didn't need to change anything.

However, I'm not going to claim that Sage owners reporting difficulties are wrong because I don't own one myself. I don't use KOReader so can't speak about that, either.

[NiLuJe]

I'll see if I have time to look into it tonight (don't hold you breath), but if anyone affected could get me verbose debug logs, that would greatly simplify the task .

(Wild guess: I suspect something may have been done to the boot anim and/or to the "pen" update mode, or a combination of both).

Like I said originally, the fact that this even works at all on sunxi is a minor miracle .

[NiLuJe]

Whelp, sunxi continues to impress... There's apparently a new and completely random race condition that appears to only happen during early boot.

A truly terrible workaround was implemented in FBInk, but this may also affect the fbdamage kernel module, so we may not be out of the woods yet...

Does this test build behave any better?

[albare]

I installed this new test version in Kobo sage and is doing the same. (I try to Reboot 3 times).
Nanoclock shows at start for 1 second down and right inverted, desapears and don't show again.



Enviado desde mi SM-A705FN mediante Tapatalk

[Steven Karp]

Can't believe it took me this long to find nanoclock. *sigh*

I've got it installed, displaying the info I want in the location I want. So that's cool.

But is there some way to see what the embedded fonts look like without connecting the device to my computer, editing the ini file, disconnecting, lather, rinse, repeat?

Basically, I want to find out which fonts are most aesthetically pleasing to me without having to audition each one individually.

Any suggestions?

[NiLuJe]

@Steven Karp: There may be an old screenshot buried in the old MiniClock thread that showcased some of them. Barring that, it's probably much faster to just play with the `fbink` binary in an SSH shell. (Or not, since, you know, requires a shell ;p).

[NiLuJe]

Released v0.11.1!

This is mainly a hotfix to alleviate some of the issues unearthed by FW 4.31.19086.

This was only tested on a Sage. Stuff may still be broken on the Elipsa: I currently don't have time to update/test on that device.

This does *nothing* for the potential issues on the Libra 2, and the issues are so severe there that it may prevent you from booting your device. Do *NOT* install this on a Libra 2 until https://github.com/koreader/koreader/issues/8414 is fixed (if ever, as I do not have access to that device myself).

I assume the sky did not fall on earlier devices like it did on those two, so earlier devices should be safe .

[Deobulakenyo]

Originally Posted by NiLuJe

Released v0.11.1!

This is mainly a hotfix to alleviate some of the issues unearthed by FW 4.31.19086.

This was only tested on a Sage. Stuff may still be broken on the Elipsa: I currently don't have time to update/test on that device.

This does *nothing* for the potential issues on the Libra 2, and the issues are so severe there that it may prevent you from booting your device. Do *NOT* install this on a Libra 2 until https://github.com/koreader/koreader/issues/8414 is fixed (if ever, as I do not have access to that device myself).

I assume the sky did not fall on earlier devices like it did on those two, so earlier devices should be safe .

So uninstalling nanoclock on the libra 2 will really remove all nanoclock files and settings on the device or do i need to factory reset to remove them?