Firmware 4.33.19611

[rtiangha]

Yeah, they're screenshots and because I use kepubify rather than Calibre these days, I don't have the option to send greyscale covers.

[xyclonei]

Originally Posted by rtiangha

Yeah, they're screenshots and because I use kepubify rather than Calibre these days, I don't have the option to send greyscale covers.

I too use kepubify so I run covergen to convert cover thumbnails to grayscale and fix the aspect ratio.

[JSWolf]

Other then the missing demo slides, is there any reason to install 4.33.19611 vs the previous 4.33 firmware?

[Quoth]

Originally Posted by JSWolf

Other then the missing demo slides, is there any reason to install 4.33.19611 vs the previous 4.33 firmware?

I had to revert two Sages from 4.33.19608 to 4.32.x because parts of handwriting would go invisible while writing (though there) on Advanced Notebook and you'd have to tap cancel and repeat for Advance Notebook export (in notebook or parent My Notebooks).

The 4.33.19611 seems to work OK on the Sage.

The 4.33.19608 is fine on the Elipsa and in fact it has no 4.33.19611 version.

I've not checked out my granddaughter's Nia which is on 4.32.x and never got the 4.33.19608 version

It's curious which four models so far got 4.33.19611: Libra2, Sage, Clara HD and Nia.
Yet not the original Libra, nor Forma nor Elipsa.
See https://pgaskin.net/KoboStuff/kobofirmware.html

[Sirtel]

Eh. I'm still on 4.32. Just haven't felt like upgrading and no burning need to do so either.

[DrChiper]

Originally Posted by compurandom

Probably because these are raw screen dumps taken internally, and kobo's gui is actually color even though the HW doesn't support it (yet).

How are "raw screen dumps taken internally" actually works? The only possibility I'm aware of is using NickleMenu with settings like:

menu_item : main : Screenshot : nickel_setting : toggle : screenshots

[NiLuJe]

Both the fb and its QImage (or whatever Qt thingy the QPA uses, cba to check) backing store are @ 32bpp (e.g., RGBA).

So whether you screenshot via Nickel (Qt) or fbgrab (fb), you'll get color (unless you use a sane setup with proper cover thumbnail dithering ;p).

This is not true for KOReader, where we swap to grayscale (so does Plato, on *almost* every device. IIRC, the exception is the Clara, because kernel issues).

[rtiangha]

Originally Posted by DrChiper

How are "raw screen dumps taken internally" actually works? The only possibility I'm aware of is using NickleMenu with settings like:

menu_item : main : Screenshot : nickel_setting : toggle : screenshots

That's how I did it.

Basically, the Kobo outputs graphics in color, but of course the eink display is greyscale. It's the same as taking a color cable TV signal and putting it on a black-and-white TV. The TV can read the color signal, but it'll still look black-and-white.

[rtiangha]

Originally Posted by xyclonei

I too use kepubify so I run covergen to convert cover thumbnails to grayscale and fix the aspect ratio.

Ok, question about that. I get that I can run covergen -rg and it'll convert all my covers to greyscale. Presumably, whenever I add a new book, I would run covergen -g. But is it smart enough to know only to convert the new book, or does it have to scan the entire device first to find it? Is it fast? My only concern is that I have 4,000 books and so scanning the entire device each time something new is added will add up in terms of time quite quickly.

[xyclonei]

Originally Posted by rtiangha

Ok, question about that. I get that I can run covergen -rg and it'll convert all my covers to greyscale. Presumably, whenever I add a new book, I would run covergen -g. But is it smart enough to know only to convert the new book, or does it have to scan the entire device first to find it? Is it fast? My only concern is that I have 4,000 books and so scanning the entire device each time something new is added will add up in terms of time quite quickly.

Covergen seems smart enough to check whether the files have been processed previously.

The first run did take a few minutes, but all successive runs were near instantaneous for 3300+ books.

Also, it only works on JPEG covers as far as my experiences go. @geek1011, any idea if it works for PNG covers?

[DNSB]

Originally Posted by JSWolf

Other then the missing demo slides, is there any reason to install 4.33.19611 vs the previous 4.33 firmware?

Not really. The only change I can see is allowing the slideshow folder to survive updates.

If the slideshow folder has been deleted, to regenerate the slideshow folder will require a factory reset. If you have the slideshow folder in a backup, you can copy it to the Kobo ereader but since exiting demo mode is equivalent to a sign out, not something many would want to do everyday.

[JSWolf]

Originally Posted by DNSB

Not really. The only change I can see is allowing the slideshow folder to survive updates.

If the slideshow folder has been deleted, to regenerate the slideshow folder will require a factory reset. If you have the slideshow folder in a backup, you can copy it to the Kobo ereader but since exiting demo mode is equivalent to a sign out, not something many would want to do everyday.

So a Kobo is easy to take out of demo mode yet a Kindle is rather difficult.

[Quoth]

Originally Posted by Quoth

I had to revert two Sages from 4.33.19608 to 4.32.x because parts of handwriting would go invisible while writing (though there) on Advanced Notebook and you'd have to tap cancel and repeat for Advance Notebook export (in notebook or parent My Notebooks).

The 4.33.19611 seems to work OK on the Sage.

The 4.33.19608 is fine on the Elipsa and in fact it has no 4.33.19611 version.

Wrote too soon. Massive fading out on half the page, not fixed by Refresh. Export didn't seem to finish, but cancel and repeat worked.
So back to 4.32.x on the Sages tomorrow.

It's intermittent and only affects writing in or exports of Advanced Notebooks. Everything else is fine!

[Quoth]

Originally Posted by Sirtel

Eh. I'm still on 4.32. Just haven't felt like upgrading and no burning need to do so either.

Seems a good plan for Sage anyway!

[DrChiper]

Originally Posted by rtiangha

That's how I did it.

Well, does not work for me on Libra 2, even with explicitly sending the cover pages in color via the following KoboTouch driver configuration: