Instructions for patching firmware 4.18.13737

[GERGE]

Originally Posted by Semwize

try

Spoiler:

Custom font sizes:
  - Enabled: no
  - Description: |
      Changes the range of sizes on the font size slider so that there are more of
      the small sizes and fewer of the large sizes.
      With this patch enabled you will not be able to select the very large font
      sizes, but will be able to make finer adjustment to the smaller sizes.
    # Font sizes depend on the device's screen resolution. Unpatched, the sizes
    # increase in steps of 1 from the smallest size up to size 22, then in steps
    # of 2 up to size 50, then in steps of 4 up to the largest size:
    #
    #  AuraOne/Forma: 18px - 194px (55 sizes)
    #  GloHD/ClaraHD: 14px - 150px (48 sizes)
    #  AuraHD/H2O:    12px - 150px (50 sizes)
    #  Glo/Aura:      12px - 122px (43 sizes)
    #  Touch/Mini:    12px - 90px  (35 sizes)
    #
    # The example replacement values in this patch result in the following ranges,
    # with increases in steps of 1 from the smallest size up to size 44, then
    # steps of 2 up to size 68, then steps of 4 up to the largest size:
    #
    #  AuraOne/Forma: 18px - 132px (55 sizes)
    #  GloHD/ClaraHD: 14px - 108px (53 sizes)
    #  AuraHD/H2O:    12px - 108px (55 sizes)
    #  Glo/Aura:      12px - 88px (50 sizes)
    #  Touch/Mini:    12px - 80px (48 sizes)
    #
    # Start with this font size: (AuraOne/Forma, GloHD/ClaraHD, Others)
  - ReplaceInt: {Offset: 0x90D66C, Find: 18, Replace: 18}
  - ReplaceInt: {Offset: 0x90D518, Find: 14, Replace: 14}
  - ReplaceInt: {Offset: 0x90D654, Find: 12, Replace: 12}
    #
  - ReplaceInt: {Offset: 0x90D540, Find: 21, Replace: 43} # Add font sizes in increments of 1 until this size exceeded}
  - ReplaceInt: {Offset: 0x90D546, Find: 22, Replace: 44} # Continue from this font size}
  - ReplaceInt: {Offset: 0x90D556, Find: 49, Replace: 67} # Add font sizes in increments of 2 until this size exceeded}
  - ReplaceInt: {Offset: 0x90D560, Find: 50, Replace: 68} # Continue from this font size}
    #
    # Add font sizes in increments of 4 until this size exceeded:
    # (AuraOne/Forma, AuraHD/H2O/GloHD/ClaraHD, Glo/Aura, Touch/Mini)
  - ReplaceInt: {Offset: 0x90D670, Find: 195, Replace: 132}
  - ReplaceInt: {Offset: 0x90D528, Find: 150, Replace: 108}
  - ReplaceInt: {Offset: 0x90D68E, Find: 122, Replace: 88}
  - ReplaceInt: {Offset: 0x90D68A, Find: 90,  Replace: 80}

Works with Libra. Offsets are the same.

[NiLuJe]

@GERGE: Which ones? (I'd assume the H2O ones, but who knows... ;p).

[Semwize]

Originally Posted by NiLuJe

@GERGE: Which ones? (I'd assume the H2O ones, but who knows... ;p).

I also think that the AuraHD/H2O/Libra, but...

[JSWolf]

Any chance we could get the portrait/landscape button back? Thanks.

[geek1011]

Originally Posted by JSWolf

Any chance we could get the portrait/landscape button back? Thanks.

This has already been done in v53: https://github.com/geek1011/kobopatc...c5165a879e62dd

[geek1011]

Originally Posted by GERGE

Works with Libra. Offsets are the same.

Are you sure? I did see some code changes there, and that code doesn't usually change unless there is a new device. I haven't actually read through it yet, though.

[JSWolf]

Originally Posted by geek1011

This has already been done in v53: https://github.com/geek1011/kobopatc...c5165a879e62dd

Thanks!

Is there anything else to be done to v53?

[geek1011]

Originally Posted by JSWolf

Thanks!

Is there anything else to be done to v53?

See the release notes: https://github.com/geek1011/kobopatc...leases/tag/v53.

[JSWolf]

Originally Posted by geek1011

See the release notes: https://github.com/geek1011/kobopatc...leases/tag/v53.

Thanks. Is there a time frame when V53 mark 2 will be released with the new commits?

One other question for now. has the larger sleep timer been fixed for 4.18? It did not work for 4.17.x.

[geek1011]

Originally Posted by JSWolf

Thanks. Is there a time frame when V53 mark 2 will be released with the new commits?

One other question for now. has the larger sleep timer been fixed for 4.18? It did not work for 4.17.x.

You mean v54, as the versions are all incremental. And I haven't decided when to make the release yet, as I prefer larger releases if possible.

About the sleep patch, read through the issue on GitHub and the patch description. Basically, the patch itself isn't broken, but at larger intervals, other things may interfere with it.

[Dirk-71]

Is there a chance we get 24 line spacing? It doesn't seem that GeoffR will catch up!?

[DNSB]

Originally Posted by Dirk-71

Is there a chance we get 24 line spacing? It doesn't seem that GeoffR will catch up!?

Given that GeoffR hasn't been on Mobileread for the last 2 months, it does seem likely that someone else may have to take over the patches he maintained until/if real life gets out of his way.

[JSWolf]

Originally Posted by DNSB

Given that GeoffR hasn't been on Mobileread for the last 2 months, it does seem likely that someone else may have to take over the patches he maintained until/if real life gets out of his way.

Does anyone know if GeoffR is OK? I did send him a PM earlier this month and no reply.

[geek1011]

Originally Posted by DNSB

Given that GeoffR hasn't been on Mobileread for the last 2 months, it does seem likely that someone else may have to take over the patches he maintained until/if real life gets out of his way.

Yes, I've been maintaining most of his patches for a while (even before he disappeared), except for some of the largest ones (which I don't use or completely understand). I'll probably update the 24 line spacing values myself when I get around to it.

[Alanon]

A quick question for those in the know. I'm trying to make text display as similarly as possible in epubs and kepubs. The files are pre-processed in Calibre to eliminate potentially problematic margins, paragraph spacing, etc, yet I'm still seeing differences in epub/kepub with identical font settings and pages full of clean, plain text.

In reading through the patches, I found this warning, which seems to describe what I'm seeing:

Beware that the KePub reader has problems with its page break position when narrow line spacings are selected, depending on which font is used. You can increase the replace_float values at the bottom of each patch to avoid those problems, or else simply refrain from selecting narrowest line spacings when reading KePubs.

I do use very low line height, and the top line is often "fringed" in kepubs, with what seems to be a large empty space at the bottom, fit for at least another line of text. Even in larger values, when the edge fringing is gone, the bottom space often remains, and this seems to be the same regardless of the fonts used?

In the absence of the 24-line patch, I have modified the 10 spacing values patch to reflect the range that I'm used to, but the kepub reader seems to dislike pretty much anything below 0.9? Is there a known minimum line height that the kepub reader can handle? In previous versions I used the adjustable margins patch and that seemed to work like a charm. Now I'm using epub fixed top/bottom margins with kepub default margins to try and even out the text rendering, which seems to be giving me these results.

Am I missing something, or is that just the way it is?