NanoClock: Yet another persistent clock - Page 12

NiLuJe · 02-08-2022, 10:01 AM

That's... strange

. Are you sure you don't have *both* NanoClock *and* MiniClock installed, somehow?

poczynek · 02-08-2022, 05:04 PM

Quote:

Originally Posted by NiLuJe

That's... strange

. Are you sure you don't have *both* NanoClock *and* MiniClock installed, somehow?

No definitely not because i reset the kobo and only installed NanoClock and that's all that is there in Add ons. It's not a huge deal just a bit weird.

NiLuJe · 02-08-2022, 05:37 PM

Reseted it how? Nothing short of a true, full, manual factory reset (i.e., via the button trickery during boot, or the dev menu) will truly clear everything off.

I don't really see any way of something like that happening unless you have multiple instances of *Clock running, and you *cannot* run two instances of NanoClock concurrently (it's a technical limitation, subsequent copies will abort on launch).

As for NanoClock itself, it also *cannot* merrily jump between state, it's a simple branch: it either uses the truetype font, or it doesn't.

NiLuJe · 02-08-2022, 05:38 PM

Another question: is the "behind" clock up to date, or is it stuck on the original date/time?

poczynek · 02-08-2022, 07:06 PM

Quote:

Originally Posted by NiLuJe

Another question: is the "behind" clock up to date, or is it stuck on the original date/time?

Good question - just checked now by pressing the screen and it is current time and date.

NiLuJe · 02-08-2022, 09:02 PM

Then than really looks like MiniClock + NanoClock running concurrently...

Try to enable debugging and checking the logs; and/or rebooting the device?

Deobulakenyo · 04-15-2022, 10:31 PM

I hope this gets updated for fw 4.32. ��

MGlitch · 04-16-2022, 12:05 AM

Quote:

Originally Posted by Deobulakenyo

I hope this gets updated for fw 4.32. ��

Have you tried using it? Not everything breaks with new firmware, even if it does need to be reinstalled.

Deobulakenyo · 04-16-2022, 03:28 AM

Quote:

Originally Posted by MGlitch

Have you tried using it? Not everything breaks with new firmware, even if it does need to be reinstalled.

Not yet, but with the experience i had before with fw updates, i do not want to mess up something if in case incompatibility arises

Phil_C · 04-16-2022, 10:41 AM

NanoClock continues to work perfectly after installing 4.32. Actually, I don't recall it ever being affected by any FW update.

NiLuJe · 04-16-2022, 01:05 PM

Yep, this should fundamentally never be affected by FW updates. The 4.31 experience was an oddity (and one that only applied to sunxi devices, anyway, where the fact that this even works at all is nothing short of a minor miracle).

DNSB · 04-16-2022, 02:22 PM

We don't believe in miracles. We just depend on them.

trampas · 04-18-2022, 04:40 AM

I got a Libra 2 last week to replace my Aura H2Oe2. Installed screensavers, extra fonts and my large custom dictionary, plus NanoClock to provide battery, date and time in Bookerly. I am on the latest firmware 4.32.19501. 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? An earlier comment seemed to imply that.

albare · 04-18-2022, 06:24 AM

I have 4.32 in Kobo Sage and no problems with nanoclock.

Enviado desde mi SM-A705FN mediante Tapatalk

NiLuJe · 04-18-2022, 09:36 AM

@trampas: Yup, that's mentioned in the README.

I'm vaguely hoping that the kernel shipped in FW 4.32+ fixes most (if not all, one can hope) of those issues, though.

(And apparently the Nia might have been affected, too? But since they sold, like, four of those, it's a bit hard to tell ^^).

04-18-2022, 04:40 AM	#178
trampas Member Posts: 12 Karma: 10 Join Date: Sep 2010 Device: Libra 2	Libra 2 freeze and reboot I got a Libra 2 last week to replace my Aura H2Oe2. Installed screensavers, extra fonts and my large custom dictionary, plus NanoClock to provide battery, date and time in Bookerly. I am on the latest firmware 4.32.19501. 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? An earlier comment seemed to imply that. Last edited by trampas; 04-18-2022 at 04:46 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Cover images not persistent	gogu1904	Kobo Reader	5	08-21-2020 10:55 AM
PW2 jailbreak not persistent	chrnit	Kindle Developer's Corner	3	01-06-2017 08:16 PM
Persistent Display?	jessie102	Sony Reader	2	03-08-2010 09:45 PM
Persistent WIFI connection.	tovarish	iRex	2	11-16-2009 03:30 AM

02-08-2022, 10:01 AM	#166
NiLuJe BLAM! 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	That's... strange . Are you sure you don't have both NanoClock and MiniClock installed, somehow?

02-08-2022, 05:37 PM	#168
NiLuJe BLAM! 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	Reseted it how? Nothing short of a true, full, manual factory reset (i.e., via the button trickery during boot, or the dev menu) will truly clear everything off. I don't really see any way of something like that happening unless you have multiple instances of Clock running, and you cannot* run two instances of NanoClock concurrently (it's a technical limitation, subsequent copies will abort on launch). As for NanoClock itself, it also cannot merrily jump between state, it's a simple branch: it either uses the truetype font, or it doesn't.

02-08-2022, 05:38 PM	#169
NiLuJe BLAM! 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	Another question: is the "behind" clock up to date, or is it stuck on the original date/time?

02-08-2022, 09:02 PM	#171
NiLuJe BLAM! 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 than really looks like MiniClock + NanoClock running concurrently... Try to enable debugging and checking the logs; and/or rebooting the device?

04-15-2022, 10:31 PM	#172
Deobulakenyo Guru Posts: 706 Karma: 2153490 Join Date: Aug 2021 Location: Stupid Philippines Device: Kobo Libra 2, Boyue Likebook P78	I hope this gets updated for fw 4.32. ��

04-16-2022, 10:41 AM	#175
Phil_C Addict Posts: 274 Karma: 391602 Join Date: Oct 2009 Location: Chicago, IL USA Device: Sony PRS-350; Kobo Clara HD; Kobo Clara 2E; Kobo Clara BW	NanoClock continues to work perfectly after installing 4.32. Actually, I don't recall it ever being affected by any FW update.

04-16-2022, 01:05 PM	#176
NiLuJe BLAM! 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	Yep, this should fundamentally never be affected by FW updates. The 4.31 experience was an oddity (and one that only applied to sunxi devices, anyway, where the fact that this even works at all is nothing short of a minor miracle).

04-16-2022, 02:22 PM	#177
DNSB Bibliophagist Posts: 46,267 Karma: 168983734 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	We don't believe in miracles. We just depend on them.

04-18-2022, 06:24 AM	#179
albare Connoisseur Posts: 62 Karma: 3010 Join Date: Feb 2019 Device: kobo h2o	I have 4.32 in Kobo Sage and no problems with nanoclock. Enviado desde mi SM-A705FN mediante Tapatalk

04-18-2022, 09:36 AM	#180
NiLuJe BLAM! 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	@trampas: Yup, that's mentioned in the README. I'm vaguely hoping that the kernel shipped in FW 4.32+ fixes most (if not all, one can hope) of those issues, though. (And apparently the Nia might have been affected, too? But since they sold, like, four of those, it's a bit hard to tell ^^).

Advert

Advert