Instructions for patching firmware 4.24.15676 - Page 2

Ripplinger · 09-26-2020, 09:35 PM

Quote:

Originally Posted by jackie_w

I had a similar issue myself with the new Navbutton labels being in the way of MiniClock in the bottom right corner.

It's solved now with @geek1011's latest (experimental, not yet released) version of NickelMenu but, before that was an option, I made a quick and dirty patch for nickel.yaml which caused all 4 Navbutton labels to be displayed white-on-white, i.e. "invisible labels". You would still see the 4 icons. I could post that here if it would be of any use to you?

It doesn't look bad as it is now for me, the clock just covers the text "More", but the full icon shows and can be accessed just hitting the hamburger. While it's not perfectly aligned as it is when within a book, it's only 3 pixels too high so doesn't look bad for as little time as I spend on the homescreen. I'll leave well enough alone with Miniclock versions since it now works perfectly for me (I'm using v20200202).

Terisa de morgan · 09-27-2020, 07:32 AM

I have a "small" problem:

Spoiler:

Terisa de morgan · 09-27-2020, 07:33 AM

The problem is when I add different dictionaries, but as I can copy them manually, no problem at all.

geek1011 · 09-27-2020, 08:10 AM

Quote:

Originally Posted by Terisa de morgan

I have a "small" problem:

Spoiler:

That's because I currently read the entire file into memory.

I'll fix and release that next week (if you want to do it, it's just using os.Open to open the file, the file .Stat to get the size for the tar header, then io.Copy for writing to the tar).

That dictionary is quite large (638 MB). Does it have images?

Mrs_Often · 09-27-2020, 11:08 AM

Quote:

Originally Posted by geek1011

On Linux, you may have to press Ctrl+H to show the .kobo folder.

And on Mac, you may have to press Shift+Command+.

Terisa de morgan · 09-27-2020, 12:33 PM

Quote:

Originally Posted by geek1011

That's because I currently read the entire file into memory.

I'll fix and release that next week (if you want to do it, it's just using os.Open to open the file, the file .Stat to get the size for the tar header, then io.Copy for writing to the tar).

That dictionary is quite large (638 MB). Does it have images?

No, it has not images but a looooot of definitions (Oxford Old English). I've already copied it directly, as it's going to be maintained between patches, so no problem from my side.

Mrs_Often · 09-28-2020, 09:57 AM

Is there something we can do about the (ugly) imbalanced header/footer spacing? I've already enabled the Reduce new header/footer height patch, but there is still a lot of space left at the bottom. Attached are images comparing the same page in firmware 4.9.x and 4.24.15676 in a (real) kepub. I much prefer the 4.9.x layout where there is a little more space at the top and almost none at the bottom. 4.24.x layout is the other way around, which just feels upside down for me.

Additionally, strangely, some pages seem to render 26 lines while others render 27. It doesn't seem to be a widow/orphan thing, because the page with 26 lines ends with a single line from a new paragraph... ?! Any ideas?

Thanks

EDIT: Sorry for the messy pics, I haven't got screenshots enabled

NiLuJe · 09-28-2020, 10:19 AM

@Mrs_Often: This may not actually be relevant, because I don't use the footer & header *at all*, but see my notes on a possibly related subject here.

NOTE: I haven't actually *read* in Nickel in quite a while, so this may be somewhat outdated.

JSWolf · 09-28-2020, 10:37 AM

Quote:

Originally Posted by Mrs_Often

Is there something we can do about the (ugly) imbalanced header/footer spacing? I've already enabled the Reduce new header/footer height patch, but there is still a lot of space left at the bottom. Attached are images comparing the same page in firmware 4.9.x and 4.24.15676 in a (real) kepub. I much prefer the 4.9.x layout where there is a little more space at the top and almost none at the bottom. 4.24.x layout is the other way around, which just feels upside down for me.

Additionally, strangely, some pages seem to render 26 lines while others render 27. It doesn't seem to be a widow/orphan thing, because the page with 26 lines ends with a single line from a new paragraph... ?! Any ideas?

Thanks

EDIT: Sorry for the messy pics, I haven't got screenshots enabled

No need to be sorry. They are good pictures to show what you are talking about.

I know what's going on in the middle and right photos.

In the middle, the is not enough space between the last line and the footer to add another line. So that space will not be the same as the header where the top line starts at the same place.

The one on the right is the old widows and orphans issue. There is patch or a configuration (in the .conf file0 option. But, some eBooks do specify widows and orphans of 2 and the only way to fix that is to edit the CSS as long as the eBook has no DRM.

jackie_w · 09-28-2020, 10:58 AM

Quote:

Originally Posted by Mrs_Often

Is there something we can do about the (ugly) imbalanced header/footer spacing? I've already enabled the Reduce new header/footer height patch, but there is still a lot of space left at the bottom. Attached are images comparing the same page in firmware 4.9.x and 4.24.15676 in a (real) kepub. I much prefer the 4.9.x layout where there is a little more space at the top and almost none at the bottom. 4.24.x layout is the other way around, which just feels upside down for me.

Additionally, strangely, some pages seem to render 26 lines while others render 27. It doesn't seem to be a widow/orphan thing, because the page with 26 lines ends with a single line from a new paragraph... ?! Any ideas?

If you haven't already, have a look at the other header/footer patch in nickel.yaml Reduce top/bottom page spacer. You can have both patches enabled.

@geek1011 has a nifty demo tool for looking at the effects of some of these patches. I'll post a link in a minute when I find it.

Mrs_Often · 09-28-2020, 11:00 AM

Thank you both for your quick replies!

Quote:

Originally Posted by NiLuJe

@Mrs_Often: This may not actually be relevant, because I don't use the footer & header *at all*, but see my notes on a possibly related subject here.

NOTE: I haven't actually *read* in Nickel in quite a while, so this may be somewhat outdated.

Hmmmm that sounds... really annoying.

The tweak you're commenting on is for the Reduce top/bottom page spacer patch right? I'd like to try setting 'it' to 0, like you suggest in your comments. But as far as I understand it that patch is only for when the "Chapter progress" / "Book progress" reading settings options are off... or would it also make a difference when they are on?

Quote:

Originally Posted by JSWolf

No need to be sorry. They are good pictures to show what you are talking about.

I know what's going on in the middle and right photos.

In the middle, the is not enough space between the last line and the footer to add another line. So that space will not be the same as the header where the top line starts at the same place.

Thanks

I've just tried all sorts of different line heights to see how close to the footer the last line can get... but even the closest is still further away from the footer than the top line is from the header. See new pics, with 28 and 33 lines. The one with 33 lines has a few pixels of the next line showing, I assume that's a nice visualisation of the minimum space between the last line and the footer.

Quote:

The one on the right is the old widows and orphans issue. There is patch or a configuration (in the .conf file0 option. But, some eBooks do specify widows and orphans of 2 and the only way to fix that is to edit the CSS as long as the eBook has no DRM.

Ah oh. I vaguely recall something about an old widows/orphans issue but never knew the details because I never came across it myself. I also thought I already had configuration in the Kobo eReader.conf file but I cannot find it now. Could you specify so I can put it (back) in?
The book in question is a real kepub synced to/from Kobo, so I don't think I can change the CSS.

Mrs_Often · 09-28-2020, 11:02 AM

Quote:

Originally Posted by Mrs_Often

But as far as I understand it that patch is only for when the "Chapter progress" / "Book progress" reading settings options are off... or would it also make a difference when they are on?

Quote:

Originally Posted by jackie_w

If you haven't already, have a look at the other header/footer patch in nickel.yaml Reduce top/bottom page spacer. You can have both patches enabled.

Oooh so it would work! I'll have a go

Quote:

@geek1011 has a nifty demo tool for looking at the effects of some of these patches. I'll post a link in a minute when I find it.

Thanks!

jackie_w · 09-28-2020, 11:08 AM

@Mrs_Often, Here's the link.

Perhaps, what I said earlier was a bit misleading. You can have both patches enabled simultaneously, but the patch Reduce top/bottom page spacer effects are visible when the header and/or footer is disabled.

Mrs_Often · 09-28-2020, 01:34 PM

Quote:

Originally Posted by jackie_w

@Mrs_Often, Here's the link.

Oooh very nifty indeed! Thanks!

Quote:

Perhaps, what I said earlier was a bit misleading. You can have both patches enabled simultaneously, but the patch Reduce top/bottom page spacer effects are visible when the header and/or footer is disabled.

Ah yes that makes sense. What a shame... the main reason for me to finally update all the way from 4.9.x are the separate header & footer: I want to see pages of total book pages in the footer, and in 4.9.x I regularly checked how many minutes were left in the chapter through the menu, so having that in the header is extremely convenient. The new (for me) navigation tabs are a bonus.

But if I can't get used to the unbalanced text distance from the header/footer I might just have to go back to 4.9.x after all*. Poo. I'll wait to decide until geek1011 decides/judges the two requested patches (Discover tab -> Pocket tab; frontlight ≥ 1%) though. Those could just about convince me to stay

(Although I do spend more time reading than on the home screen... hmmm

)

*Rather off topic by now, but does anyone know if I can do that safely without resetting first? Sideloading 4.24.x over 4.9.x didn't go too smoothly: the update worked fine, but then I couldn't open the library. Whenever I tried to open it (with or without patches on), the ereader just froze for several minutes and then restarted eventually. (The database was not corrupt, according to Kobo plugin in Calibre.) I had to go back to 4.9.x and properly update via WiFi before it worked.

jackie_w · 09-28-2020, 04:16 PM

Quote:

Originally Posted by Mrs_Often

Additionally, strangely, some pages seem to render 26 lines while others render 27. It doesn't seem to be a widow/orphan thing, because the page with 26 lines ends with a single line from a new paragraph... ?! Any ideas?

I meant to reply to this earlier. It's not just widows/orphans which can cause a variable number of lines per page. In addition I think widows/orphans are ignored in kepubs.

It will also happen if the book's CSS styling for its standard paragraph has a non-zero top margin (however small). Compare the vertical gap between
- lines 1 and 2 of the same paragraph
- the last line of one paragraph and the first line of the next paragraph

If they're different then the number of visible lines-per-page will be more on a page containing just one very long paragraph versus a page full of conversational dialogue with a lot of short paragraphs.

The first line of every page always starts in exactly the same place but the last line on each page is going to vary in the scenario I outlined above.

To compensate you might want to reduce the height even further in the Reduce new header/footer height patch. What values are you currently using and for which device?

09-27-2020, 07:32 AM	#17
Terisa de morgan Grand Sorcerer Posts: 6,233 Karma: 11768331 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	I have a "small" problem: Spoiler: runtime: out of memory: cannot allocate 638025728-byte block (1090355200 in use) fatal error: out of memory runtime stack: runtime.throw(0x64a905, 0xd) /usr/local/go/src/runtime/panic.go:774 +0x64 runtime.largeAlloc(0x26076314, 0x11360101, 0x44b283) /usr/local/go/src/runtime/malloc.go:1140 +0x108 runtime.mallocgc.func1() /usr/local/go/src/runtime/malloc.go:1033 +0x39 runtime.systemstack(0xe32f90) /usr/local/go/src/runtime/asm_386.s:399 +0x53 runtime.mstart() /usr/local/go/src/runtime/proc.go:1146 goroutine 1 [running]: runtime.systemstack_switch() /usr/local/go/src/runtime/asm_386.s:360 fp=0x11437a24 sp=0x11437a20 pc=0 x44e200 runtime.mallocgc(0x26076314, 0x608240, 0x1, 0x0) /usr/local/go/src/runtime/malloc.go:1032 +0x684 fp=0x11437a78 sp=0x11437 a24 pc=0x40b0c4 runtime.makeslice(0x608240, 0x26076314, 0x26076314, 0x114823dc) /usr/local/go/src/runtime/slice.go:49 +0x4f fp=0x11437a8c sp=0x11437a78 pc=0x43b1af bytes.makeSlice(0x26076314, 0x0, 0x0, 0x0) /usr/local/go/src/bytes/buffer.go:229 +0x69 fp=0x11437ac0 sp=0x11437a8c pc=0x4c1ed9 bytes.(Buffer).grow(0x114aed04, 0xf0, 0xf0) /usr/local/go/src/bytes/buffer.go:142 +0x11c fp=0x11437ae8 sp=0x11437ac0 pc=0x4c199c bytes.(Buffer).Write(0x114aed04, 0x118381b4, 0xf0, 0xf8, 0xf0, 0x0, 0x0) /usr/local/go/src/bytes/buffer.go:172 +0xb5 fp=0x11437afc sp=0x11437ae8 pc=0x4c1b95 compress/flate.(huffmanBitWriter).write(...) /usr/local/go/src/compress/flate/huffman_bit_writer.go:136 compress/flate.(huffmanBitWriter).writeCode(0x118381a0, 0x8002d) /usr/local/go/src/compress/flate/huffman_bit_writer.go:347 +0x15b fp=0x1 1437b24 sp=0x11437afc pc=0x4df89b compress/flate.(huffmanBitWriter).writeTokens(0x118381a0, 0x11582000, 0x4001, 0 x4001, 0x12b6a900, 0x11e, 0x11e, 0x17174300, 0x1e, 0x1e) /usr/local/go/src/compress/flate/huffman_bit_writer.go:583 +0xa2 fp=0x11 437b4c sp=0x11437b24 pc=0x4e06a2 compress/flate.(huffmanBitWriter).writeBlock(0x118381a0, 0x11582000, 0x4001, 0x 4001, 0xd100, 0x1154916d, 0x403e, 0x6e93) /usr/local/go/src/compress/flate/huffman_bit_writer.go:495 +0x312 fp=0x1 1437bb0 sp=0x11437b4c pc=0x4dff62 compress/flate.(compressor).writeBlock(0x13364000, 0x11582000, 0x4000, 0x4001, 0xd1ab, 0x3, 0x0) /usr/local/go/src/compress/flate/deflate.go:170 +0xa0 fp=0x11437bd4 sp=0 x11437bb0 pc=0x4dbb60 compress/flate.(compressor).deflate(0x13364000) /usr/local/go/src/compress/flate/deflate.go:506 +0x661 fp=0x11437c08 sp= 0x11437bd4 pc=0x4dcc41 compress/flate.(compressor).write(0x13364000, 0x11cfdc00, 0x60d384, 0x38b984, 0 x60d584, 0xfc8ca35a, 0x1147ad60) /usr/local/go/src/compress/flate/deflate.go:551 +0x69 fp=0x11437c24 sp=0 x11437c08 pc=0x4dd1c9 compress/flate.(Writer).Write(...) /usr/local/go/src/compress/flate/deflate.go:709 compress/gzip.(Writer).Write(0x1144ef50, 0x11a7c000, 0x60d384, 0x60d584, 0x0, 0 x0, 0x15) /usr/local/go/src/compress/gzip/gzip.go:196 +0xbd fp=0x11437cac sp=0x114 37c24 pc=0x4eb7bd archive/tar.(regFileWriter).Write(0x114040e0, 0x11a7c000, 0x60d384, 0x60d584, 0 x20676e69, 0x656c6966, 0xa) /usr/local/go/src/archive/tar/writer.go:497 +0xdc fp=0x11437cd0 sp=0x114 37cac pc=0x4d107c archive/tar.(Writer).Write(0x114b6840, 0x11a7c000, 0x60d384, 0x60d584, 0x0, 0x1 1468660, 0x30) /usr/local/go/src/archive/tar/writer.go:435 +0x57 fp=0x11437cfc sp=0x114 37cd0 pc=0x4d0da7 main.(KoboPatch).ApplyFiles(0x114aed00, 0x0, 0x0) /drone/src/kobopatch/kobopatch.go:579 +0x398 fp=0x11437e50 sp=0x11437cfc pc=0x5a8ed8 main.main() /drone/src/kobopatch/kobopatch.go:171 +0xa0d fp=0x11437fb0 sp=0x11437e50 pc=0x5a2f4d runtime.main() /usr/local/go/src/runtime/proc.go:203 +0x1e6 fp=0x11437ff0 sp=0x11437fb0 pc=0x42c0c6 runtime.goexit() /usr/local/go/src/runtime/asm_386.s:1325 +0x1 fp=0x11437ff4 sp=0x11437ff 0 pc=0x44fb61

09-28-2020, 09:57 AM	#22
Mrs_Often Wizard Posts: 1,775 Karma: 2694823 Join Date: Dec 2011 Location: The Netherlands Device: Kobo Touch, Glo, Clara HD	Is there something we can do about the (ugly) imbalanced header/footer spacing? I've already enabled the Reduce new header/footer height patch, but there is still a lot of space left at the bottom. Attached are images comparing the same page in firmware 4.9.x and 4.24.15676 in a (real) kepub. I much prefer the 4.9.x layout where there is a little more space at the top and almost none at the bottom. 4.24.x layout is the other way around, which just feels upside down for me. Additionally, strangely, some pages seem to render 26 lines while others render 27. It doesn't seem to be a widow/orphan thing, because the page with 26 lines ends with a single line from a new paragraph... ?! Any ideas? Thanks EDIT: Sorry for the messy pics, I haven't got screenshots enabled Attached Thumbnails Last edited by Mrs_Often; 09-28-2020 at 10:02 AM.

09-28-2020, 11:08 AM	#28
jackie_w Grand Sorcerer Posts: 6,212 Karma: 16534894 Join Date: Sep 2009 Location: UK Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3	@Mrs_Often, Here's the link. Perhaps, what I said earlier was a bit misleading. You can have both patches enabled simultaneously, but the patch Reduce top/bottom page spacer effects are visible when the header and/or footer is disabled. Last edited by jackie_w; 09-28-2020 at 11:12 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Instructions for patching firmware 3.13.1	GeoffR	Kobo Developer's Corner	56	07-01-2016 09:59 AM
Instructions for patching firmware 3.16.10	GeoffR	Kobo Developer's Corner	12	08-14-2015 03:40 AM
Instructions for patching firmware 3.16.0	GeoffR	Kobo Developer's Corner	74	08-12-2015 02:12 PM
Instructions for patching firmware 3.12.1	GeoffR	Kobo Developer's Corner	56	03-20-2015 05:14 AM
Instructions for patching firmware 3.3.x, 3.4.x, 3.5.x	GeoffR	Kobo Developer's Corner	285	08-27-2014 10:06 AM

09-27-2020, 07:33 AM	#18
Terisa de morgan Grand Sorcerer Posts: 6,233 Karma: 11768331 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	The problem is when I add different dictionaries, but as I can copy them manually, no problem at all.

09-28-2020, 10:19 AM	#23
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Mrs_Often: This may not actually be relevant, because I don't use the footer & header at all, but see my notes on a possibly related subject here. NOTE: I haven't actually read in Nickel in quite a while, so this may be somewhat outdated.

Advert

Advert