Instructions for patching firmware 3.3.x, 3.4.x, 3.5.x

[zufre]

Would it be possible to add the modifications for bad eyes to the patches?
https://www.mobileread.com/forums/sho...nary+font+size
The dictionary fonts are too tiny...
Regards!

[GeoffR]

Originally Posted by zufre

Would it be possible to add the modifications for bad eyes to the patches?
https://www.mobileread.com/forums/sho...nary+font+size
The dictionary fonts are too tiny...
Regards!

It should be possible to apply both sets of patches: apply the bad eyes ones first, zip the resulting KoboRoot.tgz into kobo-update-3.3.0.zip (or whatever the firmware version is), and use that zip for applying these patches.

It should work the other way around too.

Edit: Sorry, I didn't think about the bad eyes patches not using librmsdk.so.1.0.0, so it is not that simple.

[GeoffR]

I have the patches for firmware 3.4.1, but I haven't tested any of them as I haven't installed this firmware version on my Glo.

If anyone wants to test them, send me a PM with your email address. But be prepared for the possibility that your device could do a spontaneous factory reset. (This happened to me recently when testing a faulty patch.)

The code modified by the line-spacing patches has changed quite a bit in 3.4.1, that is the main one I am concerned about.

[tshering]

Originally Posted by zufre

Would it be possible to add the modifications for bad eyes to the patches?
https://www.mobileread.com/forums/sho...nary+font+size
The dictionary fonts are too tiny...
Regards!

The proper solution would be to convert the Modification for bad eyes patches to the Metazoa format and run it with GeoffR's package. But I am too busy to do this now. For the time being you can try this work around (for Windows only). Be aware, that I did not check if it really works, and try it on your own risk (Actually, there is not much risk, I guess. The only thing that can happen is that it does not work).
I provide two files conf_librmsdk.txt, and nickel.patch in the uploaded archive.

• copy librmsdk.so.1.0.0 (extract it form kobo-update-3.3.0.zip) and conf_librmsdk.txt to KBPatcher07\3.3.0_source\
• double click on KBPatcher07\3.3.0.bat
• if there are any kobo-update-3.3.0.zip, KoboRoot.tgz, KoboRoot.tar, librmsdk.so.1.0.0, libnickel.so.1.0.0 from earlier patching processes in patch_kobo_33\3.3.0_source\, delete them
• find KoboRoot.tgz in KBPatcher07\3.3.0_target\ and copy it to patch_kobo_33\3.3.0_source\
• copy nickel.patch to patch_kobo_33\3.3.0_source\
• double click on patch_kobo_33\3.3.0.bat

Note: If both patching processes address the same data, the second one will fail. The only overlapping patches that I am aware of are the ones related to the footer and header. So you have to disable them in one patch at least.

The whole process is less complicated than what the description suggests.

[GeoffR]

This patch sets the kepub reader default margins, i.e. the margins that are used when the adjustment slider is at the far left position. I haven't tested every permutation, but it seems to affect the following margins:

- kepub minimum left/right margins in normal reading mode
- kepub minimum left/right and top/bottom margins in full-screen reading mode

The example values in the patch make the minimum kepub left/right margins similar to the default epub margins. If you set the patch values to zero and remove any margins from the book itself, then the text will go to the very edge (and in full-screen reading mode, to the very top/bottom) of the screen.

firmware 3.3.0:

Spoiler:

<Patch>
patch_name = `Customise kepub reader default margins`
patch_enable = `yes`
# Device = Kraken/Phoenix, Type = pocket article or non-Japanese kepub
replace_int = 6142F4, 25, 10
# Device = Kraken/Phoenix, Type = Japanese kepub
replace_int = 6142F6, 45, 25
# Device = Other, Type = Any
replace_int = 614304, 20, 10
</Patch>

firmware 3.3.1:

Spoiler:

<Patch>
patch_name = `Customise kepub reader default margins`
patch_enable = `yes`
# Device = Kraken/Phoenix, Type = pocket article or non-Japanese kepub
replace_int = 614D8C, 25, 10
# Device = Kraken/Phoenix, Type = Japanese kepub
replace_int = 614D8E, 45, 25
# Device = Other, Type = Any
replace_int = 614D9C, 20, 10
</Patch>

firmware 3.4.1:

Spoiler:

<Patch>
patch_name = `Customise kepub reader default margins`
patch_enable = `yes`
# Device = Phoenix, Type = pocket article or non-Japanese kepub
replace_int = 619DB6, 25, 10
# Device = Phoenix, Type = Japanese kepub
replace_int = 619DB8, 45, 25
# Device = Other, Type = Any
replace_int = 619DBC, 20, 10
</Patch>

Edit: I'd be interested to hear how this patch works on devices other than the Glo: In particular, does it make the Aura's font cut-off problem worse?

[violent23]

Originally Posted by GeoffR

Edit: I'd be interested to hear how this patch works on devices other than the Glo: In particular, does it make the Aura's font cut-off problem worse?

I have an Aura (3.3.0) and am willing to test this. Should I disable the other "Custom left & right margins" from the libnickel.so to implement this one?

*edit - Okay so I tested with the "Custom left & right margins" off and this seems to work a treat. No more cut off text with "F" or with Italics. On top of that the margin goes right to the edge of the screen on the lowest setting. Great job!

Can I turn back on the "Custom left & right margins" without effecting this patch or should I leave it off?

[GeoffR]

Originally Posted by violent23

I have an Aura (3.3.0) and am willing to test this. Should I disable the other "Custom left & right margins" from the libnickel.so to implement this one?

*edit - Okay so I tested with the "Custom left & right margins" off and this seems to work a treat. No more cut off text with "F" or with Italics. On top of that the margin goes right to the edge of the screen on the lowest setting. Great job!

Can I turn back on the "Custom left & right margins" without effecting this patch or should I leave it off?

Thanks for testing on the Aura. It is fine to use both margins patches together.

[GeoffR]

I've included the patches for firmware 3.4.1 in patch_kobo_34.zip attached to post #1.

For 3.4.1 I've reworked the reading footer patch to make it easier to customise, and removed the example for disabling the footer altogether as this is superceded by the new full-screen reading mode.

[Loamaro]

I found here a new patch `Customise PinchGestureRecognizer`? What is its purpose? This patch is compatible with Kobo Glo?

[GeoffR]

Originally Posted by Loamaro

I found here a new patch `Customise PinchGestureRecognizer`? What is its purpose? This patch is compatible with Kobo Glo?

This patch won't have any effect unless you have an Aura, or have installed the multitouch kernel image from this thread. It lets you change some of the parameters for the pinch-to-zoom gesture. I don't know what the parameters do, but I guess from the name that TriggerTolerance might be the amount of movement needed to trigger the zoom function. If anyone tries it out, let us know what you find.

[violent23]

Originally Posted by GeoffR

I've included the patches for firmware 3.4.1 in patch_kobo_34.zip attached to post #1.

For 3.4.1 I've reworked the reading footer patch to make it easier to customise, and removed the example for disabling the footer altogether as this is superceded by the new full-screen reading mode.

So can 3.4.1 be loaded onto the Aura to take advantage of this new full-screen reading mode? How does one enable fullscreen reading mode once on 3.4.1?

[GeoffR]

Originally Posted by violent23

So can 3.4.1 be loaded onto the Aura to take advantage of this new full-screen reading mode?

The full-screen mode was new in firmware 3.3.0. See this thread for how to activate it.

It is an experimental feature and there are still a few glitches: the font cut-off problem occurs when reading kepubs in full-screen mode, but reading epubs seems to be fine. The kepub reader adjusts the top/bottom margins automatically in full-screen mode, but you can get the same feature for epubs with the `ePub adjust top/bottom margins` patch.

[violent23]

Originally Posted by GeoffR

The full-screen mode was new in firmware 3.3.0. See this thread for how to activate it.

It is an experimental feature and there are still a few glitches: the font cut-off problem occurs when reading kepubs in full-screen mode, but reading epubs seems to be fine. The kepub reader adjusts the top/bottom margins automatically in full-screen mode, but you can get the same feature for epubs with the `ePub adjust top/bottom margins` patch.

Ah okay, thanks for the tip. I did go to the link but all it says is to "Add the following lines to the config file", what config file are they talking about?

Also I update to 3.4.1 and was looking to install your patches but I can not get the 3.4.1.sh to work as there is no 3.4.1_source folder created resulting in no KoboRoot.tgz to use. I am still able to create one for 3.3.0 so I don't think it is an issue on my end.

[GeoffR]

Originally Posted by violent23

Ah okay, thanks for the tip. I did go to the link but all it says is to "Add the following lines to the config file", what config file are they talking about?

The device's config file ".kobo/Kobo/Kobo eReader.conf"

Also I update to 3.4.1 and was looking to install your patches but I can not get the 3.4.1.sh to work as there is no 3.4.2_source folder created resulting in no KoboRoot.tgz to use. I am still able to create one for 3.3.0 so I don't think it is an issue on my end.

3.4.1 has only been released for the Mini, it should work on other mark 4 hardware -- Glo, Aura HD, newer Touch models -- but I don't know what it would do on other devices, I'd be wary about using it on the Aura.

[scoky]

Originally Posted by GeoffR

This patch sets the kepub reader default margins, i.e. the margins that are used when the adjustment slider is at the far left position. I haven't tested every permutation, but it seems to affect the following margins:

- kepub minimum left/right margins in normal reading mode
- kepub minimum left/right and top/bottom margins in full-screen reading mode

The example values in the patch make the minimum kepub left/right margins similar to the default epub margins. If you set the patch values to zero and remove any margins from the book itself, then the text will go to the very edge (and in full-screen reading mode, to the very top/bottom) of the screen.

firmware 3.3.0:

Spoiler:

<Patch>
patch_name = `Customise kepub reader default margins`
patch_enable = `yes`
# Device = Kraken/Phoenix, Type = pocket article or non-Japanese kepub
replace_int = 6142F4, 25, 10
# Device = Kraken/Phoenix, Type = Japanese kepub
replace_int = 6142F6, 45, 25
# Device = Other, Type = Any
replace_int = 614304, 20, 10
</Patch>

firmware 3.3.1:

Spoiler:

<Patch>
patch_name = `Customise kepub reader default margins`
patch_enable = `yes`
# Device = Kraken/Phoenix, Type = pocket article or non-Japanese kepub
replace_int = 614D8C, 25, 10
# Device = Kraken/Phoenix, Type = Japanese kepub
replace_int = 614D8E, 45, 25
# Device = Other, Type = Any
replace_int = 614D9C, 20, 10
</Patch>

firmware 3.4.1:

Spoiler:

<Patch>
patch_name = `Customise kepub reader default margins`
patch_enable = `yes`
# Device = Phoenix, Type = pocket article or non-Japanese kepub
replace_int = 619DB6, 25, 10
# Device = Phoenix, Type = Japanese kepub
replace_int = 619DB8, 45, 25
# Device = Other, Type = Any
replace_int = 619DBC, 20, 10
</Patch>

Edit: I'd be interested to hear how this patch works on devices other than the Glo: In particular, does it make the Aura's font cut-off problem worse?

So in normal reading mode, can the top and bottom margin of kepubs be changed?
In full screen mode, .kepub.epub has some bugs like font cut-off.