Instructions for patching firmware 4.7.10413

[Terisa de morgan]

Originally Posted by GeoffR

The new patch works differently, you only need to change the last replace_int line.

(The value used by the timer is actually in milliseconds, but numbers larger than 255 are encoded in a complicated way, so with the old patch it was necessary to specify a different 4-byte sequence for 3000, 5000, etc. The new patch takes a smaller number in seconds, which can be entered as a plain integer, and multiplies it by 1024 to get an approximation of the timer value in milliseconds. The first replace_bytes line is just to set up this code to do the multiplication.)

(Edit: And if you are wondering why multiply by 1024 instead of 1000? 4 bytes is not enough space to load a multiplicand and load a multiplier and perform a normal multiplication. But there is a trick for multiplying by powers of 2 using a logical-shift-left instruction that doesn't require loading the multiplier. 1024 = 2 to the 10th power.)

Thank you for the explanation, I was curious too.

[chrisridd]

There's a spelling error in one of the patch titles:

Increase size of chaper progress chart in Kepub

The spelling error doesn't affect anything.

Thanks for all the updates!

[oren64]

Originally Posted by chrisridd

There's a spelling error in one of the patch titles:

Hmm... the original name was `Chapters progress increasing size in Kepub`, GeoffR change the name to `Increase size of chaper progress chart in Kepub`.

EDIT: I think the original name also have spelling error.

[geek1011]

Originally Posted by oren64

Hmm... the original name was `Chapters progress increasing size in Kepub`, GeoffR change the name to `Increase size of chaper progress chart in Kepub`.

EDIT: I think the original name also have spelling error.

The first one is grammatically incorrect, and the second one has a spelling error, and a slight grammatical error. It should be: `Increase size of Kepub chapter progress chart`

[SaraOliveira]

Hi!

First of all, thank you for the excellent work.
and I would like to know : Any improvement on 'libadobe'?

[icallaci]

I upgraded and patched my new Limited Edition Aura One with exactly the same files as I used on my regular (8gb) Aura One (fw 4.7.10413), but the Limited Edition seems to selectively ignore some of the patches. Specifically, only full paragraphs are displayed on each page. If there is not enough room to display an entire paragraph, then a huge blank space is left on the screen, and the new paragraph begins on the next page. If there is enough room to include a full paragraph, then the patches do seem to work because the text goes all the way to the bottom of the screen, but ONLY if an entire paragraph fits. I'm not sure where the problem lies, but I am reading kepubs (not full-screen), and wonder if anyone else is experiencing the same thing?

[jackie_w]

Originally Posted by icallaci

If there is not enough room to display an entire paragraph, then a huge blank space is left on the screen, and the new paragraph begins on the next page. If there is enough room to include a full paragraph, then the patches do seem to work because the text goes all the way to the bottom of the screen, but ONLY if an entire paragraph fits. I'm not sure where the problem lies, but I am reading kepubs (not full-screen), and wonder if anyone else is experiencing the same thing?

It sounds like what you'd expect to see in a book whose CSS has big values for widows and orphans, although I do have a vague memory that someone posted that widows/orphans don't work in kepubs.

Have you tested viewing several different books on the new KA1 or compared exact same book/same page using same font and size on your 2 different KA1s?

[icallaci]

Originally Posted by jackie_w

It sounds like what you'd expect to see in a book whose CSS has big values for widows and orphans, although I do have a vague memory that someone posted that widows/orphans don't work in kepubs.

Have you tested viewing several different books on the new KA1 or compared exact same book/same page using same font and size on your 2 different KA1s?

I thought it might be the widows/orphans thing, but I checked the book's CSS and it's clean. Then I compared the same book on the regular KA1 vs the Limited Edition (using the same font, etc.), and the regular KA1 displays it perfectly..Same book, same firmware, same patches (in fact, the same generated kobo.tgz file), same settings, different results. I even reloaded the book AND the patches on both readers in case I had changed something somewhere, but got the same result. I'm willing to wait for new firmware in the hope that Kobo will sync things up between all the Mark 6 devices, if that's what the issue is. Kind of a pain but hopefully it will get sorted out. Thanks.

[jackie_w]

@icallaci,

I know you said you normally read kepubs but have you also tried looking at a standard epub (the same one) on both devices, to see if you get the same problem?

[icallaci]

Originally Posted by jackie_w

@icallaci,

I know you said you normally read kepubs but have you also tried looking at a standard epub (the same one) on both devices, to see if you get the same problem?

If I get some time, I'll give it a try, but I'm getting ready to travel for the holidays (not one of my smarter decisions, but oh, well). I'm tempted to leave it alone until the next firmware update to see if the problem persists.

[GeoffR]

Originally Posted by icallaci

Specifically, only full paragraphs are displayed on each page. If there is not enough room to display an entire paragraph, then a huge blank space is left on the screen, and the new paragraph begins on the next page. If there is enough room to include a full paragraph, then the patches do seem to work because the text goes all the way to the bottom of the screen, but ONLY if an entire paragraph fits. I'm not sure where the problem lies, but I am reading kepubs (not full-screen), and wonder if anyone else is experiencing the same thing?

I have seen this happen in the KePub reader when a very narrow line spacing is used. Try increasing the line spacing and see if the problem goes away.

[davidfor]

Originally Posted by icallaci

I thought it might be the widows/orphans thing, but I checked the book's CSS and it's clean. Then I compared the same book on the regular KA1 vs the Limited Edition (using the same font, etc.), and the regular KA1 displays it perfectly..Same book, same firmware, same patches (in fact, the same generated kobo.tgz file), same settings, different results. I even reloaded the book AND the patches on both readers in case I had changed something somewhere, but got the same result. I'm willing to wait for new firmware in the hope that Kobo will sync things up between all the Mark 6 devices, if that's what the issue is. Kind of a pain but hopefully it will get sorted out. Thanks.

Did you see this problem on the Aura ONE LE with firmware 4.7.10364? There are differences between the firmware versions and they are related to the Aura ONE LE. I wouldn't have expected a difference like this, but it could be part of the reason that 4.7.10413 hasn't been released to the Aura ONE LE.

Kobo have said they will sync things up with the next firmware release. But, if you want to make sure something like this is fixed, you need to report it to Kobo.

[icallaci]

Originally Posted by GeoffR

I have seen this happen in the KePub reader when a very narrow line spacing is used. Try increasing the line spacing and see if the problem goes away.

Well, well, well! That did the trick. I was sure I used the same settings on the two readers, but just one tick higher on the line-spacing in the Limited Edition made the problem go away. I suspect the problem is related to the particular embedded font in this book (Charis SIL), which has very wide leading anyway. I had to set the line spacing to about 80% of maximum, but I can live with that, especially since I tested some other books without the Charis font and the problem is not as apparent.

Thank you, GeoffR!

ETA: I've never seen this particular problem with line-height before. Previously, if the line-height was too narrow, I'd see a partial line of type at the bottom and/or top of the page. But this time the entire paragraph was moved to the following page. I learned something new today, so that's a good thing.

[icallaci]

Originally Posted by davidfor

Did you see this problem on the Aura ONE LE with firmware 4.7.10364? There are differences between the firmware versions and they are related to the Aura ONE LE. I wouldn't have expected a difference like this, but it could be part of the reason that 4.7.10413 hasn't been released to the Aura ONE LE.

Kobo have said they will sync things up with the next firmware release. But, if you want to make sure something like this is fixed, you need to report it to Kobo.

I updated to 4.7.10413 immediately, so I never tested the LE with 4.7.10364. I feel a little embarrassed that the answer was so simple (increase the line height), but maybe it's an attempt by Kobo to eliminate the partial lines of text that used to appear when the line height was too narrow. (Although I did go and fiddle with the line height again and the partial lines of text showed up again, but only at one particular line height.) Anyway, it's all good now. Thanks again.

[davidfor]

Originally Posted by icallaci

I updated to 4.7.10413 immediately, so I never tested the LE with 4.7.10364.

OK, but I've been waiting for a comment about something from someone with an LE and 4.7.10364

I feel a little embarrassed that the answer was so simple (increase the line height), but maybe it's an attempt by Kobo to eliminate the partial lines of text that used to appear when the line height was too narrow. (Although I did go and fiddle with the line height again and the partial lines of text showed up again, but only at one particular line height.) Anyway, it's all good now. Thanks again.

I occasionally see the partials, but, only if the book embeds Charis SIL or a variant. If it bugs me, or the book doesn't really need the font, I'll choose one of the Kobo fonts.