Instructions for patching firmware 3.12.0

[GeoffR]

Originally Posted by jshzh

This is a dumb question. I don't know which software to use for opening and editing the .patch files in Windows. I could open them and make changes with notepad. Is that okay?

It is okay to use Notepad to edit the .patch files.

It is just the files that the firmware itself reads, such as "Kobo eReader.conf", that you should avoid using Notepad for.

[JSWolf]

Originally Posted by GeoffR

What is the reason for having min-height larger than max-height?

The reason is that it was a mistake. But, it works. The page number is small and the text goes right down to it. I should probably swap the numbers and see if it still works the same.

[Nick_1964]

Originally Posted by GeoffR

With patch32lsb v0.10 the addresses can be found automatically for some patches, so there might be no need to change anything at all in the patch for it to work with the next firmware version.



I haven't seen anything like that happen, but some strange things can happen if there is a typo in the footer patch and one of the replacement strings is too short.

It is the glo ( having it on both my Glo's ) it only happens when the Glo went empty or after a reset.
This is the section:

Spoiler:

# libnickel.so.1.0.0 in firmware 3.11.0 (4d8eac1207)

#
# The following two patches are alternatives, don't enable both at once.
#

<Patch>
patch_name = `Disable reading footer`
patch_enable = `no`
replace_string = DBDBFC, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 105;\n}\n\nReadingFooter[qApp_deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n}\n\nReadingFooter[qApp_deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 170;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[qApp_deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[qApp_deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[qApp_localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `* {\n\theight: 5px;\n\tfont-size: 1px;\n\tcolor: transparent;\n}\n\n`
</Patch>

<Patch>
patch_name = `Freedom to advanced fonts control`
patch_enable = `yes`
#
# This patch allows the advanced font options (weight/sharpness adjustments)
# to be used with sideloaded fonts too.
#
# WARNING: IT IS NOT SAFE TO ENABLE THIS PATCH IF YOUR DEVICE IS SET TO A
# JAPANESE LOCALE OR IF ANY JAPANESE BOOKS ARE OPENED.
#
# VolumeManager.isJapanese() --> False
replace_bytes = 68F4B4, 95 F5 48 EF, 00 20 00 20
# N3FontTypeUtil.setupMonotypeDropdown(a,b)
# --> N3FontTypeUtil.setupDropdown(UNDEFINED,a,b)
replace_bytes = 7E7FAE, 58 46 51 46, 59 46 52 46
replace_bytes = 7E7FB2, 35 F4 B2 E9, 4B F4 42 EC
# N3FontTypeController.setupAdvancedOption --> NOP
replace_bytes = 94CE12, FA F6 34 E7, 00 46 00 46
replace_bytes = 94EEB8, F8 F6 E0 E6, 00 46 00 46
</Patch>


<Patch>
patch_name = `Custom reading footer style`
patch_enable = `yes`
replace_string = DBDBFC, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 105;\n}\n\nReadingFooter[qApp_deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n}\n\nReadingFooter[qApp_deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 170;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[qApp_deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[qApp_deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[qApp_localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 105;\n}\n\n* {\n\tfont-size: 16px;\n\tpadding-bottom: 0px;\n\tmargin-top: 0px;\n\t/*font-family:none;*/\n}\n\n[qApp_localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`
#
# Uncomment the replace_string lines of one of the examples below, comment out
# the rest. If you choose to make further changes to the examples, BE CAREFUL
# NOT TO ALTER THE LENGTH OF THE REPLACEMENT STRINGS! (Add or remove spaces if
# necessary to keep the total length the same.)
#
# Example for Nick's Glo:
replace_string = DBDC0D, `min-height: 70px;`, `min-height: 40px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 40px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 105;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 28px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom: 7px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top:10px;`
#
# Example for Nick's Aura HD:
#replace_string = DBDC0D, `min-height: 70px;`, `min-height: 40px;`
#replace_string = DBDC20, `max-height: 70px;`, `max-height: 40px;`
#replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 170;`
#replace_string = DBDC58, `font-size: 16px;`, `font-size: 32px;`
#replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom: 9px;`
#replace_string = DBDC80, `margin-top: 0px;`, `margin-top: 7px;`
#
# Uncomment one of the following if you wish the footer to use a fixed font.
# (And enable one of the Custom header style patches below using the same font.)
#
replace_string = DBDC92, `/*font-family:none;*/`, `font-family: Amasis;`
#replace_string = DBDC92, `/*font-family:none;*/`, `font-family: Avenir;`
#replace_string = DBDC92, `/*font-family:none;*/`, `font-family: Georgia;`
#
</Patch>

Originally Posted by jshzh

This is a dumb question. I don't know which software to use for opening and editing the .patch files in Windows. I could open them and make changes with notepad. Is that okay?

I use Notepad ++
The normal notepad doesn't handle line endings okay and when the reader reads files that are handled with the normal Notepad it can crash. (The patch files are not read by the reader so they can be safely done with normal Notepad.)
Safe as Encode in UTF-8 without BOM in options (but as far as I know Notepad++ recognize the file style and does that automatically)

[GeoffR]

Originally Posted by Nick_1964

It is the glo ( having it on both my Glo's ) it only happens when the Glo went empty or after a reset.

The patch looks okay (for 3.11.0). The only thing I can think is that if by reset you mean a pinhole reset, then doing a pinhole reset can prevent the database and config file and some other things being saved properly before the device restarts (it is like turning your PC off at the wall without shutting down properly), so after the reset the device might revert to using old settings for the book.

[Nick_1964]

Originally Posted by GeoffR

The patch looks okay (for 3.11.0). The only thing I can think is that if by reset you mean a pinhole reset, then doing a pinhole reset can prevent the database and config file and some other things being saved properly before the device restarts (it is like turning your PC off at the wall without shutting down properly), so after the reset the device might revert to using old settings for the book.

It is allso when the device stopped from sleep and the battery is down, and you have to load it first before you can use it, like a reboot of a computer.
I can't make a picture of it right now,she use it during her nightshifts.
But the "page xx of xx is almost completely under the bezel and the used fontsize is almost 50 % bigger then it must be.
I think for almost sure that I can reproduce it by just sending the patch file ( KoboRoot.tgz ) to the .kobo directory and let it restart.

[GeoffR]

Originally Posted by Nick_1964

It is allso when the device stopped from sleep and the battery is down, and you have to load it first before you can use it, like a reboot of a computer.
I can't make a picture of it right now,she use it during her nightshifts.
But the "page xx of xx is almost completely under the bezel and the used fontsize is almost 50 % bigger then it must be.
I think for almost sure that I can reproduce it by just sending the patch file ( KoboRoot.tgz ) to the .kobo directory and let it restart.

The extra large footer font size is something that happens when one of the replacement strings in the footer patch is too short, which causes the footer CSS to be truncated.

You patch looks OK, but perhaps there is a problem with spaces being lost during cut-and-paste? E.g. the `font-family: Amasis;` replacement string you are using needs to have two spaces between font-family: and Amasis;

Edit: Since you can reproduce the problem, I'd try using the example reading footer patch without any changes and see if that fixes it, and if not then try it without the reading footer patch at all and see if that fixes it. Then we'll have a better idea where the problem is.

Edit2: (If there is a short replacement string in the patch then the extra large font size should happen all the time, not just after a reboot. That makes me think there is something more going on than just the footer patch.)

[boriar]

@GeoffR
Can you said me where to get kpg.exe?

[sage79]

I notice that when i enable 10 line space and custom font dimension, when i open a book or when a chapeter changes, line space decreases so i have to refresh font and line options. is there a solution?
thanks

[GeoffR]

Originally Posted by boriar

@GeoffR
Can you said me where to get kpg.exe?

Version 12 is at http://rghost.net/53295702, I don't know if it is the latest version though.

[GeoffR]

Originally Posted by sage79

I notice that when i enable 10 line space and custom font dimension, when i open a book or when a chapeter changes, line space decreases so i have to refresh font and line options. is there a solution?
thanks

Is there the same problem with the 15 line spacing values patch?

Does the line spacing go to the smallest setting on the slider after after opening a book? I think this means that the line spacing setting for the book in the device's database doesn't match any of the settings available on the slider. It can happen if the book was opened first without the line spacing patch, and then again with the patch, but after that the new setting should be saved. But if the database is corrupt and the book settings are not able to be saved then it might cause the problem you see. You can check the database with the KoboUtilities Calibre plugin, or with the sqlite command PRAGMA integrity_check;

[sage79]

i try to reset the database. yes it is the same with 15 space values.

[sage79]

nothing. i have deleted my account and recreated but same bug.

[boriar]

Originally Posted by GeoffR

Version 12 is at http://rghost.net/53295702, I don't know if it is the latest version though.

Thanks! Do this program more or less the same of your?

[GeoffR]

Originally Posted by boriar

Thanks! Do this program more or less the same of your?

Yes, but kpg.exe only patches libnickel.so.1.0.0, to patch other libraries you would need to rename files and build KoboRoot.tgz manually.

There are some differences in the format of the patches too, but the attachment in post #2 has the libnickel patches in a format for use with kpg.exe.

[GeoffR]

Originally Posted by sage79

nothing. i have deleted my account and recreated but same bug.

Have you edited any of the patches? If so then PM me a copy of the .patch file and I'll see if I can spot anything out of place.

Does the problem happen in kepubs or epubs or both? Full-screen mode or normal mode?

Could it be a faulty book, or does it happen in every book?