Clara Display time when reading

[Terisa de morgan]

Originally Posted by LucyOne

The position works with the other fonts.

Check with other position (0,0) as I think the size (24) is quite big (in my case, 8 matches my footer font).

I cannot post my cfg file (it's inside my ereader and I'm at work now), but I can try it this night. After some faults, I have ChareInk working without moving the font from its place.

[LucyOne]

Yes, it must have been the size, I underestimated the value. It works now!

[frostschutz]

glad you got it sorted while I was having me beauty sleep :-)

[LucyOne]

@frostschutz: I only hope you look as good as your miniclock on my Clara now

I did some finetuning and got it aligned with the page margins in the lower left corner, where I wanted it.

x=47
y=1403
Font: GentiumBookBasic
Size: 9.5

[NiLuJe]

You can chop that down to 9, we only support integers .

(In fact, this will *fail* in FBInk >= 1.9.0, because of stricter input validation).

Found trailing characters (.5) behind value '9' assigned from string '9.5' to an option (t:size) expecting an unsigned short int.

[MGlitch]

I can't be 100% sure, but I think this hijacks the ability to turn nightmode on/off, I can't disable nightmode using brightness anymore (I haven't removed the MiniClock as I generally don't switch anyway). Just looking to see if this is normal, or if something else is going on with my Kobo Forma.

[frostschutz]

Well, I'm clueless. It only passively reads the config file you point it to, without modifying the file. I don't see nightmode doing anything weird with inotify so - it should not be possible for MiniClock to influence behavior of other mods.

[MGlitch]

I'll tinker with my nightmode settings, I didn't think this mod would do it, but it was the last mod I'd installed after getting Nightmode going.

Thanks for clearing up any doubt though

[jackie_w]

Originally Posted by MGlitch

I can't be 100% sure, but I think this hijacks the ability to turn nightmode on/off, I can't disable nightmode using brightness anymore (I haven't removed the MiniClock as I generally don't switch anyway). Just looking to see if this is normal, or if something else is going on with my Kobo Forma.

NightMode (using the 100% toggle) with Miniclock is working fine for me on a ClaraHD. I won't have time to install it on my Forma until this evening.

One thing you could try. Nothing to do with Miniclock, but I have noticed previously that sometimes Nightmode's slide-to-100% brightness does not always take effect until you close the light pop-up.

[MGlitch]

Originally Posted by jackie_w

One thing you could try. Nothing to do with Miniclock, but I have noticed previously that sometimes Nightmode's slide-to-100% brightness does not always take effect until you close the light pop-up.

That did the trick. Odd that sliding had always worked for me before, but I can live with this toggle too since I'll be reading in white on black most of the time anyway.

[jackie_w]

Originally Posted by MGlitch

Odd that sliding had always worked for me before

And it probably will again. I've never been able to detect a pattern of when it does/doesn't work just by waiting long enough.

[Ripplinger]

When I use nightmode by setting the light to 100% (or any percent, doesn't matter), the clock doesn't always have the white text on black. Sometimes it will start out correctly on the first page, but when I change the page, it reverts back to normal black text on white. This is on a Glo HD.

I'm not sure if I'm doing something wrong between the nightmode and miniclock patches, or if it's not reliable in nightmode. Or maybe just not reliable on a Glo HD? I don't use nightmode often, so it's not a deal breaker at all, I'd live with it for the convenience of the clock.

[LucyOne]

I've turned on nightmode on my Clara HD, unfortunately, the miniclock does not invert colours. It stays black on white background.

This is my nightmode.ini:

Spoiler:

# config file for kobo-nightmode

[state]
invertActive = no # yes / no
retainStateOverRestart = no # yes / no

[control]
longPressDurationMS = 800 # time in milliseconds to toggle (1000 = 1 second)
debug=no # yes/no to enable/disable debug logging

[nightmode]
refreshScreenPages = 3 #force refresh every X pages
#forceSWInvert = true #force SW invert mode (default: false)

[brightness]
1percentPatch = yes # yes / no : Nickel set brightness to 2% even when on UI it is set to 1%
# this patch will force brightenss to 1% when:
# - it was set to 1%, then it was set to 0% (for instance: stand-by) then changed again to "what Nickel says is 2%"
# - it was set to 3%, then it was set to 1% then changed again to "what Nickel says is 2%"
timeout = 5 # time in seconds, after brightness is set (and maintained) to a given level, to toggle the action set to that level
# switch device off
7 = echo -ne "\xfe\x0f\xc5\x54\xff\x6a\x0d\x00\x01\x00\x74\x00\ x01\x00\x00" > /dev/input/event0
# put device in standby
8 = echo -ne "\xf0\x0f\xc5\x54\x3c\xe0\x0d\x00\x01\x00\x74\x00\ x01\x00\x00\x00\xf1\x0f\xc5\x54\x8e\xe3\x02\x00\x0 1\x00\x74\x00\x00\x00\x00\x00" > /dev/input/event0
# when brightness is set to 11% : special action, toggle night toggleNightMode
100 = toggleNightMode
99 = enableNightMode
98 = disableNightMode
#20 = dmesg > /mnt/onboard/.kobo/dmesg_$(date +%s).log &
#30 = mv -f /mnt/onboard/.kobo/screenInv.so /root/screenInv.so >/dev/null 2>&1
#50 = hwclock -w -u
#98 = touch /mnt/onboard/.kobo/switchoff/test0.log &
#99 = /mnt/onboard/.kobo/switchoff/test.sh &
#some examples of invoking any script when brightness is set to X% for at least TIMEOUT seconds
#4 = touch /mnt/onboard/hello.world
#5 = touch /mnt/onboard/hello.world.async &

[frostschutz]

@LucyOne:

I think you have to set retainStateOverRestart to yes

otherwise it will always say invertActive = no and miniclock looks for invertActive = yes

@Ripplinger:

could it be the same issue?

otherwise the only thing I can think of... miniclock checks the timestamp of the file, and only looks at the file again if the timestamp changes. and that timestamp does not have microsecond resolution, but is actually a 1-second or even 2-second window.

So if you somehow manage to turn it on and off again in quick succession, miniclock might be stuck on the wrong value. I'll have to do some more testing if this is actually a case.

[LucyOne]

@Frostschutz: Setting retainStateOverRestart to yes didn't help, unfortunately.

Edit 2: It works now after a reboot. Thanks a lot!