Instructions for patching firmware 3.15.0

[freekobo]

Originally Posted by Nick_1964

Be very sure that is not in the .css of the book, if they have top,left,right and bottom marges set,you can't change it in the reader.
You can use patches to adjust them but if u have a book without the marges,it isn't always centered.
Look at the code in the .css of a random book I opened, with that code,you will never use the full screen so u have to remove that part out of the book.

@page { 
   margin-left: 1em; 
   margin-right: 1em;
	margin-top: 1em;
	margin-bottom: 1em;
}

ohhhh that's it! Thanks!

[kaito]

Is there a way to make the initial box for the pop-up dictionary bigger? I would like to see as much of the whole entry as possible without having to swipe through the different pages or press&hold on the word yet again to see the full page.

Also, since I'm using multiple English dictionaries (as Deutsch and Italiano etc), is there a way to patch out the footer copyrights of those dictionaries (since they aren't correct and they just cause the # of pages to view to increase and usually the last page is just the useless footer). Patching the name of the Dictionary itself would also be nice (English 2, Websters, Chambers, ...)

[RichSun]

Is there any way to customize the page controls so that you can assign behaviors to specific regions?

Specifically, I just want to replace all page back taps with page forward taps. I page back so rarely and I can use a swipe action to do that so I would prefer to just have all tap regions do a page forward.

Are there any notes anywhere such that I can learn how to create my own custom patches?

[surquizu]

Originally Posted by kaito

Is there a way to make the initial box for the pop-up dictionary bigger? I would like to see as much of the whole entry as possible without having to swipe through the different pages or press&hold on the word yet again to see the full page.

Tshering solution in: https://www.mobileread.com/forums/sho...&postcount=141

Specifically I think it is sufficient to add these two patches in the files of metazoa patches (v.3.15.0):

in libnickel.so.1.0.0.patch:

<Patch>
patch_name = `relleno_ventana`
patch_enable = `yes`
replace_string = BCCF90, `#textEdit {\n\tmin-height: 150px;\n\tmax-height: 150px;\n\tmin-width: 515px;\n\tmax-width: 515px;\n}\n\n#textEdit[qApp_deviceIsPhoenix="true"] {\n\tmin-height: 190px;\n\tmax-height: 190px;\n\tmin-width: 550px;\n\tmax-width: 550px;\n}\n\n#textEdit[qApp_deviceIsDragon="true"] {\n\tmin-height: 235px;\n\tmax-height: 235px;\n\tmin-width: 930px;\n\tmax-width: 930px;\n}`, `#textEdit {\n\tmin-height: 290px;\n\tmax-height: 290px;\n\tmin-width: 575px;\n\tmax-width: 575px;\n}\n\n#textEdit[qApp_deviceIsPhoenix="true"] {\n\tmin-height: 371px;\n\tmax-height: 371px;\n\tmin-width: 550px;\n\tmax-width: 550px;\n}\n\n#textEdit[qApp_deviceIsDragon="true"] {\n\tmin-height: 533px;\n\tmax-height:533px;\n\tmin-width: 930px;\n\tmax-width: 930px;\n}`
</Patch>

in nickel.patch (new file in metazoa patches):

<Patch>
patch_name = `Ventana_diccionario`
patch_enable = `yes`
replace_string = 4C1AA, `#InlineDictionaryView {\n\tmin-width: 500px;\n\tmax-width: 500px;\n\tmin-height: 220px;\n\tmax-height: 220px;\n}\n#InlineDictionaryView[qApp_deviceIsPhoenix="true"] {\n\tmin-width: 650px;\n\tmax-width: 650px;\n\tmin-height: 280px;\n\tmax-height: 280px;\n}\n#InlineDictionaryView[qApp_deviceIsDragon="true"] {\n\tmin-width: 980px;\n\tmax-width: 980px;\n\tmin-height: 350px;\n\tmax-height: 350px;\n}\n`, `#InlineDictionaryView {\n\tmin-width: 560px;\n\tmax-width: 560px;\n\tmin-height: 330px;\n\tmax-height: 330px;\n}\n#InlineDictionaryView[qApp_deviceIsPhoenix="true"] {\n\tmin-width: 650px;\n\tmax-width: 650px;\n\tmin-height: 410px;\n\tmax-height: 410px;\n}\n#InlineDictionaryView[qApp_deviceIsDragon="true"] {\n\tmin-width: 980px;\n\tmax-width: 980px;\n\tmin-height: 580px;\n\tmax-height: 580px;\n}\n`
</Patch>

[barobach_so]

hi
dear GeofR I know its old topic but there is no new firmware for kobo touch so please look at this in kobo 3.11 firmware pach topic

[GeoffR]

Originally Posted by freekobo

Would it be possible to add a disable pinch to change font size on epubs for this version? The check box isn't working in this version(bug)

Here is an update of a patch from earlier firmware that was used to disable pinch and zoom before Kobo added the option to turn it off in the reading settings. I can't test it as I don't have an Aura:

Disable pinch-to-zoom font resizing: (paste into libnickel.so.1.0.0.patch)

Spoiler:

<Patch>
patch_name = `Disable pinch-to-zoom font resizing`
#
# Prevents the pinch gesture resizing the font when reading k/epubs (on Aura
# or other devices with a multitouch kernel). Pinch to zoom images still works.
#
patch_enable = `yes`
replace_bytes = 919C48, 04 46 2D ED 04 8B, BD E8 F0 8F 00 46
</Patch>

[freekobo]

Originally Posted by GeoffR

Here is an update of a patch from earlier firmware that was used to disable pinch and zoom before Kobo added the option to turn it off in the reading settings. I can't test it as I don't have an Aura:

Disable pinch-to-zoom font resizing: (paste into libnickel.so.1.0.0.patch)

Spoiler:

<Patch>
patch_name = `Disable pinch-to-zoom font resizing`
#
# Prevents the pinch gesture resizing the font when reading k/epubs (on Aura
# or other devices with a multitouch kernel). Pinch to zoom images still works.
#
patch_enable = `yes`
replace_bytes = 919C48, 04 46 2D ED 04 8B, BD E8 F0 8F 00 46
</Patch>

Tested and working, perfectly on my Aura.
Thank you very much
Question; How is it that you make these patches? Do you use a special program to find the code to patch or something?

[arasyi]

Is it possible to increase the sleep and power-off timeouts to 1 day?
I have tried changing the value in libnickel.so.1.0.0.patch but I got the error that replace_int only accepts values between 0 and 255.

[traycold]

Originally Posted by arasyi

Is it possible to increase the sleep and power-off timeouts to 1 day?
I have tried changing the value in libnickel.so.1.0.0.patch but I got the error that replace_int only accepts values between 0 and 255.

Not possible. In the code the timeouts are encoded as integer (max 255 i.e. about 4 hours and 15 minutes), so even in case the patch would not check the max value and would allow rewriting the file .so, strange things would occur at runtime.

[kaito]

Originally Posted by surquizu

Tshering solution in: https://www.mobileread.com/forums/sho...&postcount=141

Specifically I think it is sufficient to add these two patches in the files of metazoa patches (v.3.15.0):

Thanks for this. I had to change the 533 height in the libnickel patch to 460 or the text would overflow the box and be hidden under the border, but other than that it works.

Any idea where the dictionary names are stored? I can't find the word "Italiano" (or a proper Deutch/Portugese string) anywhere in nickel or libnickel.

[GeoffR]

Originally Posted by arasyi

Is it possible to increase the sleep and power-off timeouts to 1 day?
I have tried changing the value in libnickel.so.1.0.0.patch but I got the error that replace_int only accepts values between 0 and 255.

The code that the `Custom Sleep/Power-off timeouts` patch changes can only use values from 0-255. Although the register used to hold the timeout value is 32-bit and can hold much larger values, the code uses a 16-bit 'thumb' instruction to load the register, and there isn't room to use a wider instruction in the patch. It could be that the timeout function can accept larger values, but there is no way to load those larger values without re-writing the code.

[Nick_1964]

2 questions/remarks
By accident, I loaded an kepub and discovered (patched Glo HD 3.15 ) that the bottom margin of a kepub with the patch is smaller then with an epub.
It is a patched firmware, but let say in an epub there is about 7 mm between the latest line and the page xx of xx and with kepub it is about 4 mm.
Is there a way to adjust the default patch for the custom footer a bit so it comes with epub near the kepub margin ?

And a remark/warning.
The patch which disable the automatic update works well, BUT :
I sold both my Glo and Aura HD (for 2 glo HD) and used the firmware default setting to wipe out the device.
But when turned on, the device asked for the settings like language,time,wifi and then it tried to download the new firmware and that was blocked.
Then both devices went into a kind of bootloop,they keep rebooting and try to download the new firmware, when I pressed cancel it says that it needs the upgrade and asked for the desktop software.
But that doesn't recognise both readers, so I ended up with carefull opening both and use flash software to restore the images.
So before hitting the factory default button (device info,restore factory settings) be sure that you disable the patch and apply it,otherwise you are in trouble.
The setting itself is very useful to prevent the device from updating but especially with the Aura HD (it takes for ages before rebooting and retry) it looks like the firmware updates are also removed when you go back to factory default otherwise I don't understand why the devices tries to download an update while the latest firmware was already installed.

[GeoffR]

Originally Posted by Nick_1964

2 questions/remarks
By accident, I loaded an kepub and discovered (patched Glo HD 3.15 ) that the bottom margin of a kepub with the patch is smaller then with an epub.
It is a patched firmware, but let say in an epub there is about 7 mm between the latest line and the page xx of xx and with kepub it is about 4 mm.
Is there a way to adjust the default patch for the custom footer a bit so it comes with epub near the kepub margin ?

That could be caused by a couple of things:

• @page doesn't work in kepubs, so if the book contains a @page margin it will show in the epub but not in the kepub.

• The kepub reader has a bug that makes some absolute lengths too small, so if the book has a body or paragraph margin specified in pt, mm, etc. then it will be smaller in kepubs than in epubs.

Edit: Could it also just be that the kepub header is a different size to the epub top margin? The text will not line up the same at the bottom of the page unless it starts in exactly the same position at the top of the page.

And a remark/warning.
The patch which disable the automatic update works well, BUT :
I sold both my Glo and Aura HD (for 2 glo HD) and used the firmware default setting to wipe out the device.
But when turned on, the device asked for the settings like language,time,wifi and then it tried to download the new firmware and that was blocked.
Then both devices went into a kind of bootloop,they keep rebooting and try to download the new firmware, when I pressed cancel it says that it needs the upgrade and asked for the desktop software.
But that doesn't recognise both readers, so I ended up with carefull opening both and use flash software to restore the images.
So before hitting the factory default button (device info,restore factory settings) be sure that you disable the patch and apply it,otherwise you are in trouble.
The setting itself is very useful to prevent the device from updating but especially with the Aura HD (it takes for ages before rebooting and retry) it looks like the firmware updates are also removed when you go back to factory default otherwise I don't understand why the devices tries to download an update while the latest firmware was already installed.

Thanks, I'll add a warning about that to the patch. I don't understand why it would happen though, as the factory reset should restore the factory firmware from the recovery partition which would wipe out any patches.

[davidfor]

Originally Posted by GeoffR

Thanks, I'll add a warning about that to the patch. I don't understand why it would happen though, as the factory reset should restore the factory firmware from the recovery partition which would wipe out any patches.

A factory reset should wipe it out. But, logging out of the Kobo account could hit the problem Nick describes. I would have expected it to be OK, but it depends on how the patch worked. If it sets the version number higher than any available, it should be OK. But, if it changes the URL or something so that the server can't be contacted, it might cause this.

[GeoffR]

Originally Posted by davidfor

A factory reset should wipe it out. But, logging out of the Kobo account could hit the problem Nick describes. I would have expected it to be OK, but it depends on how the patch worked. If it sets the version number higher than any available, it should be OK. But, if it changes the URL or something so that the server can't be contacted, it might cause this.

I think the patch just scrambles the URL for the firmware update. I'll add a warning about logging out too.

Edit: The `Block WiFi firmware upgrade` patch changes this string:

https://api.kobobooks.com/1.0/UpgradeCheck/%1/%2/%3/%4/%5

to this:

https://api.kobobooks.com/1.0/UpgradeCheck/%1/%2/k/99.9/5