Clara HD Display time when reading

[frostschutz]

Originally Posted by Gibbo

pity you have to remove the USB every time to make a change

if you install a telnet/ftpd package you could do it through wifi and no usb at all

[davidfor]

Originally Posted by frostschutz

There's nothing in this (or any other) addon that makes it survive factory resets. Sounds like in your case only the user partition was formatted, but addons are installed to the system partition. That's not a factory reset (one that also reverts to factory firmware).

As of firmware 4.15.x, the factory reset from the Device info page changed. It doesn't wipe the root partition any more. The manual methods should still do it, or, do it from the Developers options page if you have devmode on.

[NiLuJe]

@davidfor: Thanks for the quick recap, I did not remember which method did what .

----

Yeah, running fbink manually in a shell will save you *tons* of time .

For the bottom corner enthusiasts, don't forget that you can pass *negative* values (to x & y; and top & left for opentype), which should help position stuff on bottom edges without having to know the screen resolution...

EDIT: I don't recall if this is exposed in miniclock, but FBInk now supports setting the opentype size in pixels, which makes what I detailed in my previous paragraph even more trivial, since everything is now in the same unit, so you won't have to figure (or compute) the point to pixel conversion yourself .

(Although, you can: px = dpi/72 * pt).

[Katsunami]

Hi This clock mod is great. I've wanted something like this since my first Kindle. I often read on public transport, and I know at which time the train or bus is at the stop I need to get out. This clock option now makes bringing up the menu all the time unnecessary. Great mod.

I've installed the clock mod and the invert screen patch.

If I invert the screen, should the clock mod be picking this up? The clock mod seems to have night mode support.

When the screen is inverted, the clock has a white background and black letters, on a black screen. I left it at the default settings:

nightmode_file=/mnt/onboard/.kobo/nightmode.ini
nightmode_key=invertActive
nightmode_value=yes

Should I be doing something else, or is this support for some other night mode? (Maybe a native / built in night mode in one of the readers newer that the KA1; don't know if one of them has such a mode.)

If the clock can't detect the inverted screen (triggered by the Invert Screen option which replaces the Show EPUB Numbers option in the menu), then it's fine with me. It's just a tiny white patch in the top left.

I should have installed both the clock mod (didn't know it even existed until today) and the Invert Screen patch a long time ago.

[jackie_w]

Originally Posted by Katsunami

I've installed the clock mod and the invert screen patch.

If I invert the screen, should the clock mod be picking this up? The clock mod seems to have night mode support.

When the screen is inverted, the clock has a white background and black letters, on a black screen. I left it at the default settings:

nightmode_file=/mnt/onboard/.kobo/nightmode.ini
nightmode_key=invertActive
nightmode_value=yes

If you're saying you've installed the 'Replace adobe page numbers toggle with invert screen' patch in geek1011's kobopatch system then the lines you'll need for the miniclock.cfg file are

# NightMode support:
#
nightmode_file=/mnt/onboard/.kobo/Kobo/Kobo eReader.conf
nightmode_key=InvertScreen
nightmode_value=true

[Katsunami]

Originally Posted by jackie_w

If you're saying you've installed the 'Replace adobe page numbers toggle with invert screen' patch in geek1011's kobopatch system then the lines you'll need for the miniclock.cfg file are

# NightMode support:
#
nightmode_file=/mnt/onboard/.kobo/Kobo/Kobo eReader.conf
nightmode_key=InvertScreen
nightmode_value=true

I should have known. Thanks (No quotes necessary for the file with the space in it? I'll see )

It works, thanks

[jsessions]

What a handy addon MiniClock is and very easy to install!

Makes my Clara HD just that little bit more useable.

My thanks to developer(s)

[NiLuJe]

@frostschutz: I, err, *may* have done nasty things to MiniClock... ;p.

I randomly remembered an idea @sherman initially floated a year ago about running the FBInk CLI tool as a daemon, and sending it data via a named pipe.
So, I did that ;p.

Then I also tried the "sentinel pixel" checking I was talking about a few pages back (to avoid basically printing the same string two or three times w/ the delay handling), and that appeared to work ^^.

Still on the menu is checking the defaults on a Forma re: whitelist & co, but that's for tomorrow .

[frostschutz]

Originally Posted by NiLuJe

I randomly remembered an idea @sherman initially floated a year ago about running the FBInk CLI tool as a daemon, and sending it data via a named pipe.
So, I did that ;p.

That's great, thanks.

Would you like to take over the MiniClock?

[NiLuJe]

@frostschutz: I'd unfortunately be somewhat ill-suited for the task: I don't actually use it ;p.

This was just a fun trial by fire for the feature .

[NiLuJe]

So, here's an "updated" version that makes use of the trick discussed earlier, as well as implementing a few other often-requested features, and possibly having better handling of devices with pageturn buttons.

Configs should be compatible, but do review the updated example, especially if you're curious about the actual changes .
I completely stripped the builtin patch codepath, so Libra/Forma users who use buttons will have to use the relevant kobopatch patch!

That's the only gotchas I can think of, so, brave testers welcome ;p.

----

(The following comments refer to the original test release and are now mostly outdated).

EDIT: And of course, 5min later I remember that I forgot to check straight ePubs, aaaaaand, yep, we're too fast. Yet another proof that ePub performance is subpar.

EDIT²: Fixed it :/.

EDIT³: Now ignores gyro events by default, to prevent them from feeding the cooldown (c.f., the new graylist option).

[Fozkas]

It's been working fine in my Libra with the buttons.

It takes 3 or 4 page turns untill it appears (could be on the first but i couldn't figure out where to setup that)

Whats new on this patch? (Sorry, I didn't understand)

[NiLuJe]

@Fozkas: Internal shenanigans, mainly (allegedly to avoid repetitive and unnecessary work, especially as far as truetype fonts are concerned) .

The user-facing bits are frontlight support, and a few new config keys & examples related to positioning.

Also, just updated the package above, because of course reading ePub is terrible, and I'd forgotten to test that.

[Fozkas]

Originally Posted by NiLuJe

@Fozkas: Internal shenanigans, mainly (allegedly to avoid repetitive and unnecessary work, especially as far as truetype fonts are concerned) .

The user-facing bits are frontlight support, and a few new config keys & examples related to positioning.

Also, just updated the package above, because of course reading ePub is terrible, and I'd forgotten to test that.

Thanks!!!

[jackie_w]

Originally Posted by NiLuJe

In the meantime, here's a test package, as I've finished testing on my end, and nothing horrible happened ^^.

Configs should be compatible, but do review the updated example .
I completely stripped the patch codepath, so Libra/Forma users who use buttons will have to use the not-yet-in-a-release relevant kobopatch patch .

That's the only gotchas I can think of, so, brave testers welcome ;p.

EDIT: And of course, 5min later I remember that I forgot to check straight ePubs, aaaaaand, yep, we're too fast. Yet another proof that ePub performance is subpar.

EDIT²: Fixed it :/.

EDIT³: Now ignores gyro events by default, to prevent them from feeding the cooldown (c.f., the new graylist option).

Hi NiLuJe,

I installed this new version a few days ago on a ClaraHD and a Forma. I also have the new kobopatch "Don't grab exclusive access to event0" enabled.

On the whole it seems to be working OK except that on the Forma I have, more than once, found this file present /.addons/miniclock/debuglog.txt. I'm not sure why because my miniclock.cfg file is set to debug=0. I'd care less about this if the Forma didn't import it as a new book after a disconnect.

Can you shed any light?

ETA: I don't have the file anymore but I think the content was something like

"-- sentinel pixel hasn't been updated, delay -- 2"

ETA2: Correction, the (unwanted) debuglog.txt is being created on both the Forma and the ClaraHD.