Clara HD Display time when reading

[NiLuJe]

@LucyOne: I assume you restarted the device after changing that setting?

[MGlitch]

Is it intended that this shows up when the Kobo is sleeping?

Specifically, I've noticed that when I put my Kobo to sleep the time doesn't appear but will pop up a short time later (within a minute). I'm not sure if it updates the time or displays the last time it had.

I'm guessing that when it goes to sleep the Kobo is still running some processes even after the light turns off and the screen changes. I didn't notice this under 4.11.11911 but I may have missed it as the screensaver I user could make the time a bit hard to spot.

[frostschutz]

Yes, it takes a while for it to actually go to sleep, so MiniClock might still manage to update the clock once. Other hacks like the random screensaver are only possible because the device is still awake for a short while when going to sleep. This time is a lot shorter when you poweroff.

[Ripplinger]

Originally Posted by frostschutz

I think you have to set retainStateOverRestart to yes

@Ripplinger:

could it be the same issue?

It more consistently starts in the correct white text on black. When I flipped pages though it reverted back to black text on white. Flipped back the few pages to where I started and it was again correct white on black. And oddly after that point it's staying correct with white on black when I flip pages in either direction.

Really odd, but for the most part, it seems to be working quite well.

Edit: After playing with it back and forth more, it seems that the clock switching back to it's correct state just takes a bit more time. When I switched the reader back to normal reading black on white, the incorrect white on black clock stayed. Just looked at it awhile thinking what to try next and it flipped to the correct display of black on white. Took maybe 10 seconds. So patience (my lack of) just seems to be the only issue!

[MGlitch]

One last (maybe) question/request can this be made to work with the page buttons as well?

[frostschutz]

difficult for me to test since the only button on the h2o is the power button. and if I remember correctly, nickel even blocks access to that (have to patch nickel to get access). do buttons on the forma work the same way? (event0, event1, other?)

you can probably make it work indirectly by setting a higher update frequency but I don't know what that will do to energy consumption ^^;

[MGlitch]

Originally Posted by frostschutz

difficult for me to test since the only button on the h2o is the power button. and if I remember correctly, nickel even blocks access to that (have to patch nickel to get access). do buttons on the forma work the same way? (event0, event1, other?)

you can probably make it work indirectly by setting a higher update frequency but I don't know what that will do to energy consumption ^^;

How can I find out how the buttons are treated? I don’t have shell access or really anything beyond what the kobo can do out of the box save for patches and a few mods (night mode, and your clock and screensaver ones).

I’ll happily test stuff. I can tweak the update frequency easily enough

[frostschutz]

Hmmm, should be event0... I could make it use that but then it would no longer react to touchscreen pageflips. To support both I need to do some multiplexing between two input devices, well no biggie either but...

...this 5-minute-miniclock hack is getting out of hand LOL

[jackie_w]

Originally Posted by frostschutz

...this 5-minute-miniclock hack is getting out of hand LOL

No good deed goes unpunished

[boriar]

Originally Posted by frostschutz

...this 5-minute-miniclock hack is getting out of hand LOL

But you have BIG hands, isn't it?

[MGlitch]

Originally Posted by frostschutz

Hmmm, should be event0... I could make it use that but then it would no longer react to touchscreen pageflips. To support both I need to do some multiplexing between two input devices, well no biggie either but...

...this 5-minute-miniclock hack is getting out of hand LOL

Wasn’t it already pointed out that users interest is inversely proportionate to the amount of time initially allocated for a project?

Take your time though I appreciate all the hard work you do on these mods which make Kobo an even better device.

[frostschutz]

@MGlitch: Well, I'll look into adding button support but it won't happen tomorrow. Until then you can just try setting update frequency to 1 or 2 instead of the default 60. That makes for a, well, very aggressive miniclock I guess but, it would show up and maybe that's what counts for now?

[LucyOne]

With the new landscape mode patch my Clara HD is almost the perfect device for me.
I've noticed, though, that in landscape mode, the miniclock is shown in the ASCI font in the upper left corner of the screen (as held when reading).
In portrait mode the miniclock is displayed in TTF in the lower left corner, as I prefer it.

My values are offset_x=46, offset_y=1405.

Any idea what is happening here?

[frostschutz]

well, miniclock has no clue about portrait/landscape mode. it just knows to show at offset.

as said before, there are two sets of settings, one for bitmap (offset_xy) and one for truetype (truetype_xy).

if the truetype has an error (bad font, bad offset, bad other option) it will fall back to bitmap mode.

so you might have to check if your truetype_* settings are correct for landscape mode.

(there is at the moment no way to set more than one offset to support both portrait and landscape with truetype font, or to detect that condition)

[LucyOne]

I see. I would like to keep the truetype settings for portrait mode.
What would be the correct values then to display the miniclock in the lower left corner in bitmap?