Instructions for patching firmware 3.19.5761 - Page 7

JSWolf · 08-17-2016, 03:22 PM

I am thinking of giving kepub a try. Which patches should I apply to fix up kepub. Not going to go full screen at first but might later.

davidfor · 08-17-2016, 10:25 PM

Quote:

Originally Posted by JSWolf

I am thinking of giving kepub a try. Which patches should I apply to fix up kepub. Not going to go full screen at first but might later.

Absolutely none. To begin with. Read a couple and work out what YOU think is wrong and then find the patches that fix your problems.

And sorry, there isn't a patch to set the correct reading order for Discword

JSWolf · 08-18-2016, 02:04 AM

Quote:

Originally Posted by davidfor

Absolutely none. To begin with. Read a couple and work out what YOU think is wrong and then find the patches that fix your problems.

And sorry, there isn't a patch to set the correct reading order for Discword

Date published is the correct Discworld reading order.

GeoffR · 08-18-2016, 03:41 AM

Quote:

Originally Posted by JSWolf

I am thinking of giving kepub a try. Which patches should I apply to fix up kepub. Not going to go full screen at first but might later.

I agree with davidfor, try reading a few KePubs and then see if there are patches to change the things you don't like. But keep in mind that some of the patches you are already using might affect KePubs too.

But in case you are interested these are the patches I use. (E = affects ePub, K = affects KePub, EK = affects both.)

`Default ePub monospace font (Courier)` (E)
`My 15 line spacing values` (EK)
`Custom left & right margins` (EK)
`Custom font sizes` (EK)
`Freedom to advanced fonts control` (EK)
`ePub fixed/adjustable top/bottom margins` (E)
`Custom page refresh options (1,2,4,8,16,32,64,128)` (EK)
`Custom kepub default margins` (K)
`Set kepub hyphenation` (K*)
`Fix three KePub fullScreenReading bugs` (K)
`Force user line spacing in KePubs` (K*)
`Un-force font-family override p tags (std epubs)` (E)
`Always display chapter name on navigation menu` (EK)
`Un-Force user font-family in KePubs` (K)
`KePub full justification default` (K*)

(I read sideloaded ePubs and synced KePubs full-screen, with text fully justified and hyphenated. Before sideloading ePubs I always set the body margins to zero and strip any page-template.xpgt stylesheet. This together with the `Custom kepub default margins` and `ePub fixed/adjustable top/bottom margins` patches gives the same full-screen page margin size in both KePubs and ePubs.)

(Edit: The only KePubs I read are ones synced from Kobo, if I was sideloading KePubs I probably wouldn't use the `Force user line spacing in KePubs`, `Set kepub hyphenation`, or `KePub full justification default` patches (marked K*) but instead edit the book's stylesheet only when necessary.)

icallaci · 08-18-2016, 10:38 AM

Jon, I just yesterday decided to try a kepub for the first time, and I think I prefer it to epub. I did a factory reset, loaded the latest firmware (leaving it unpatched), then read for an hour and couldn't stand the huge bottom margin, so I re-applied the patches I had been using with epubs. I love it! Footnotes are SO much easier to use, I like being able to see how much time is left in a chapter (as well as the entire book), and zooming images so that I can actually see them is wonderful. I even like the header (with the book title) displayed. I think the larger devices allow enough text on the screen so that I am not constantly turning pages, so SOME whitespace is now acceptable to me, whereas before I hated any extra whitespace at all. Anyway, I'd be interested to hear if you like kepubs better than epubs. I think I am a convert.

rossy77 · 08-23-2016, 06:48 AM

Hi all,
I'm new to kobo modification and I'm going to try this tonight..does this mod cause changes in the battery life?thanks
Rossella

JSWolf · 08-23-2016, 08:44 AM

Quote:

Originally Posted by rossy77

Hi all,
I'm new to kobo modification and I'm going to try this tonight..does this mod cause changes in the battery life?thanks
Rossella

These patches do not effect the life of the battery.

Koleff · 09-05-2016, 11:17 AM

I've recently came into possession of a N905B and tried to update it from 3.8 directly to 3.19.5761. I did as the instructions said and finally transferred the .tgz to the .kobo directory, ejected and disconnected the device. Half an hour later it is still on the loading screen, so I'm guessing something didn't work out. Any ideas?

rtiangha · 09-05-2016, 02:54 PM

Quote:

Originally Posted by Koleff

I've recently came into possession of a N905B and tried to update it from 3.8 directly to 3.19.5761. I did as the instructions said and finally transferred the .tgz to the .kobo directory, ejected and disconnected the device. Half an hour later it is still on the loading screen, so I'm guessing something didn't work out. Any ideas?

I've actually wondered about this. Can you jump directly from more than one version to another, or do you have to go incrementally? I assume there's a reason why the OS does multiple firmware upgrade checks when you factory reset...?

davidfor · 09-05-2016, 07:42 PM

Quote:

Originally Posted by Koleff

I've recently came into possession of a N905B and tried to update it from 3.8 directly to 3.19.5761. I did as the instructions said and finally transferred the .tgz to the .kobo directory, ejected and disconnected the device. Half an hour later it is still on the loading screen, so I'm guessing something didn't work out. Any ideas?

As you are posting in a the patch thread, does that mean you patched the 3.19.5761 and installed that over 3.8? If so, I'm not surprised it didn't work. You should upgrade to the desired firmware and then put the patches on.

At this point, you will probably have to do a factory reset and start again.

Quote:

Originally Posted by rtiangha

I've actually wondered about this. Can you jump directly from more than one version to another, or do you have to go incrementally? I assume there's a reason why the OS does multiple firmware upgrade checks when you factory reset...?

The Kobo devices are designed to be updateable from any version to any later version. After a factory reset, my Touch goes from 1.9.11 to whatever is the latest available version. So, this works as long as you don't mess it up, you can go to whatever version you want.

GeoffR · 09-05-2016, 11:16 PM

From the top of the first post:

Quote:

Originally Posted by GeoffR

Before starting:

1. Make sure your Kobo ereader is already running firmware version 3.19.5761 (0e028f3185). If not, then you need to upgrade before applying this patch.

GeoffR · 09-09-2016, 02:37 AM

I had to re-think the line spacing patch because of changes in firmware 4.0, and the result is that there is now room for a lot more line spacing values. The patch below uses a slider with 24 values, but I could probably increase that to 40 values if necessary. I've tested it on my Glo and it seems to work as before, but if you use it then let me know if you come across any problems.

These two patches are the same except for the example line spacing values. Choose one to replace the `My 15 line spacing values` patch in libnickel.so.1.0.0. As always, it is best to customise the replacement values to suit your particular device and reading preferences.

`My 24 line spacing valies` with example values to suit higher-dpi devices (AuraHD/H2O/GloHD) or large reading font sizes:

Spoiler:

Code:

<Patch>
patch_name = `My 24 line spacing values` 
patch_enable = `yes`
#
## This patch changes the values on the line spacing adjustment slider,
## increasing the number of spacing options from 15 to 24, and allowing
## much narrower spacing values to be set.
##
## 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 customise the replacement values at the bottom of this patch to
## avoid those problems, or else simply refrain from selecting narrowest
## line spacings when reading KePubs.
#
# reposition code that uses r6, initialise r6
replace_bytes = 616E2C, 00 23 00 22 C3 F6 F0 73, 58 F8 06 60 7E 60 00 26
# loop to load 14 vals from new table
replace_bytes = 616E34, 20 46 58 F8 06 60, 20 46 04 A1 31 44
replace_bytes = 616E3A, 07 F1 08 01, FC F5 B6 E8
replace_bytes = 616E3E, C7 E9 02 23 7E 60, 08 36 70 2E F7 D1
# jump over new table, 8-align new table
replace_bytes = 616E44, FC F5 B0 E8, 88 E0 00 BF
# new table: 14 8-aligned doubles
replace_bytes = 616E48, 6B A3 D3 E9 00 23 07 F1, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E50, 80 01 20 46 61 E9 1C 23, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E58, FC F5 A6 E8 68 A3 D3 E9, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E60, 00 23 07 F1 80 01 20 46, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E68, 61 E9 1A 23 FC F5 9C E8, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E70, 65 A3 D3 E9 00 23 07 F1, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E78, 80 01 20 46 61 E9 18 23, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E80, FC F5 92 E8 43 F2 33 33, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E88, 4F F0 33 32 C3 F6 F3 73, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E90, 07 F1 80 01 20 46 61 E9, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E98, 16 23 FC F5 86 E8 5C A3, 00 00 00 00 00 00 F0 3F
replace_bytes = 616EA0, D3 E9 00 23 07 F1 80 01, 00 00 00 00 00 00 F0 3F
replace_bytes = 616EA8, 20 46 61 E9 14 23 FC F5, 00 00 00 00 00 00 F0 3F
replace_bytes = 616EB0, 7C E8 00 23 00 22 C3 F6, 00 00 00 00 00 00 F0 3F
# 616EB8 - 616F58 unused
# initialise r6
replace_bytes = 616F58, C4 F2, 00 26
# loop to load 10 vals from old table
replace_bytes = 616F5A, 08 03 07 F1 80 01, 20 46 26 A1 31 44
replace_bytes = 616F60, 20 46 61 E9, FC F5 22 E8
replace_bytes = 616F64, 02 23 FC F5 20 E8, 08 36 50 2E F7 D1
# continue at 616F6A
#
#
# 24 values for replacement, change these to suit:
# (1.0 is the smallest value used by the unpatched firmware.)
#
replace_float = 616E48, 1.0, 0.76
replace_float = 616E50, 1.0, 0.78
replace_float = 616E58, 1.0, 0.8
replace_float = 616E60, 1.0, 0.82
replace_float = 616E68, 1.0, 0.84
replace_float = 616E70, 1.0, 0.86
replace_float = 616E78, 1.0, 0.88
replace_float = 616E80, 1.0, 0.9
replace_float = 616E88, 1.0, 0.92
replace_float = 616E90, 1.0, 0.94
replace_float = 616E98, 1.0, 0.96
replace_float = 616EA0, 1.0, 0.98
replace_float = 616EA8, 1.0, 1.0
replace_float = 616EB0, 1.0, 1.02
replace_float = 616FF8, 1.05, 1.05
replace_float = 617000, 1.07, 1.07
replace_float = 617008, 1.1, 1.1
replace_float = 617010, 1.35, 1.15
replace_float = 617018, 1.7, 1.2
replace_float = 617020, 1.8, 1.25
replace_float = 617028, 2.2, 1.3
replace_float = 617030, 2.4, 1.35
replace_float = 617038, 2.6, 1.4
replace_float = 617040, 2.8, 1.5
</patch>

`My 24 line spacing valies`, with example values to suit lower-dpi devices (Touch/Mini/Glo/Aura) or smaller reading font sizees:

Spoiler:

Code:

<Patch>
patch_name = `My 24 line spacing values` 
patch_enable = `yes`
#
## This patch changes the values on the line spacing adjustment slider,
## increasing the number of spacing options from 15 to 24, and allowing
## much narrower spacing values to be set.
##
## 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 customise the replacement values at the bottom of this patch to
## avoid those problems, or else simply refrain from selecting narrowest
## line spacings when reading KePubs.
#
# reposition code that uses r6, initialise r6
replace_bytes = 616E2C, 00 23 00 22 C3 F6 F0 73, 58 F8 06 60 7E 60 00 26
# loop to load 14 vals from new table
replace_bytes = 616E34, 20 46 58 F8 06 60, 20 46 04 A1 31 44
replace_bytes = 616E3A, 07 F1 08 01, FC F5 B6 E8
replace_bytes = 616E3E, C7 E9 02 23 7E 60, 08 36 70 2E F7 D1
# jump over new table, 8-align new table
replace_bytes = 616E44, FC F5 B0 E8, 88 E0 00 BF
# new table: 14 8-aligned doubles
replace_bytes = 616E48, 6B A3 D3 E9 00 23 07 F1, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E50, 80 01 20 46 61 E9 1C 23, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E58, FC F5 A6 E8 68 A3 D3 E9, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E60, 00 23 07 F1 80 01 20 46, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E68, 61 E9 1A 23 FC F5 9C E8, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E70, 65 A3 D3 E9 00 23 07 F1, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E78, 80 01 20 46 61 E9 18 23, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E80, FC F5 92 E8 43 F2 33 33, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E88, 4F F0 33 32 C3 F6 F3 73, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E90, 07 F1 80 01 20 46 61 E9, 00 00 00 00 00 00 F0 3F
replace_bytes = 616E98, 16 23 FC F5 86 E8 5C A3, 00 00 00 00 00 00 F0 3F
replace_bytes = 616EA0, D3 E9 00 23 07 F1 80 01, 00 00 00 00 00 00 F0 3F
replace_bytes = 616EA8, 20 46 61 E9 14 23 FC F5, 00 00 00 00 00 00 F0 3F
replace_bytes = 616EB0, 7C E8 00 23 00 22 C3 F6, 00 00 00 00 00 00 F0 3F
# 616EB8 - 616F58 unused
# initialise r6
replace_bytes = 616F58, C4 F2, 00 26
# loop to load 10 vals from old table
replace_bytes = 616F5A, 08 03 07 F1 80 01, 20 46 26 A1 31 44
replace_bytes = 616F60, 20 46 61 E9, FC F5 22 E8
replace_bytes = 616F64, 02 23 FC F5 20 E8, 08 36 50 2E F7 D1
# continue at 616F6A
#
#
# 24 values for replacement, change these to suit:
# (1.0 is the smallest value used by the unpatched firmware.)
#
replace_float = 616E48, 1.0, 0.7
replace_float = 616E50, 1.0, 0.725
replace_float = 616E58, 1.0, 0.75
replace_float = 616E60, 1.0, 0.775
replace_float = 616E68, 1.0, 0.8
replace_float = 616E70, 1.0, 0.825
replace_float = 616E78, 1.0, 0.85
replace_float = 616E80, 1.0, 0.875
replace_float = 616E88, 1.0, 0.9
replace_float = 616E90, 1.0, 0.925
replace_float = 616E98, 1.0, 0.95
replace_float = 616EA0, 1.0, 0.975
replace_float = 616EA8, 1.0, 1.0
replace_float = 616EB0, 1.0, 1.025
replace_float = 616FF8, 1.05, 1.05
replace_float = 617000, 1.07, 1.07
replace_float = 617008, 1.1, 1.1
replace_float = 617010, 1.35, 1.15
replace_float = 617018, 1.7, 1.2
replace_float = 617020, 1.8, 1.25
replace_float = 617028, 2.2, 1.3
replace_float = 617030, 2.4, 1.35
replace_float = 617038, 2.6, 1.4
replace_float = 617040, 2.8, 1.5
</patch>

Quentin · 11-13-2016, 05:46 PM

Hi im new to this and have no idea what happens if i do this but it sounds interesting
and im not sure so im going to ask it can i after i installed the firmware and decide go back to the normal kobo operating system and completely delete the firmware off my e-reader is that possible or not you can't go back after i installed this?
please reply

jackie_w · 11-13-2016, 07:17 PM

Quote:

Originally Posted by Quentin

Hi im new to this and have no idea what happens if i do this but it sounds interesting
and im not sure so im going to ask it can i after i installed the firmware and decide go back to the normal kobo operating system and completely delete the firmware off my e-reader is that possible or not you can't go back after i installed this?
please reply

The end of post #1 in this very thread tells you how to restore your device to the default firmware.

PeterT · 11-13-2016, 10:05 PM

Remember, you're actually running the original code, just with a few patches installed to it.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Instructions for patching firmware 3.17.3	GeoffR	Kobo Developer's Corner	60	09-17-2015 05:35 PM
Instructions for patching firmware 3.17.0	GeoffR	Kobo Developer's Corner	49	08-16-2015 05:20 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.11.0	GeoffR	Kobo Developer's Corner	226	06-01-2015 05:32 AM
Instructions for patching firmware 3.8.0	GeoffR	Kobo Developer's Corner	92	10-22-2014 07:22 AM

08-17-2016, 03:22 PM	#91
JSWolf Resident Curmudgeon Posts: 79,566 Karma: 145863177 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	I am thinking of giving kepub a try. Which patches should I apply to fix up kepub. Not going to go full screen at first but might later.

08-18-2016, 10:38 AM	#95
icallaci Guru Posts: 817 Karma: 6528026 Join Date: Sep 2012 Device: Kobo Elipsa	Jon, I just yesterday decided to try a kepub for the first time, and I think I prefer it to epub. I did a factory reset, loaded the latest firmware (leaving it unpatched), then read for an hour and couldn't stand the huge bottom margin, so I re-applied the patches I had been using with epubs. I love it! Footnotes are SO much easier to use, I like being able to see how much time is left in a chapter (as well as the entire book), and zooming images so that I can actually see them is wonderful. I even like the header (with the book title) displayed. I think the larger devices allow enough text on the screen so that I am not constantly turning pages, so SOME whitespace is now acceptable to me, whereas before I hated any extra whitespace at all. Anyway, I'd be interested to hear if you like kepubs better than epubs. I think I am a convert.

08-23-2016, 06:48 AM	#96
rossy77 Junior Member Posts: 1 Karma: 10 Join Date: Aug 2013 Device: Kobo Touch	Hi all, I'm new to kobo modification and I'm going to try this tonight..does this mod cause changes in the battery life?thanks Rossella

09-05-2016, 11:17 AM	#98
Koleff Junior Member Posts: 1 Karma: 10 Join Date: Sep 2016 Device: kobo N905B	I've recently came into possession of a N905B and tried to update it from 3.8 directly to 3.19.5761. I did as the instructions said and finally transferred the .tgz to the .kobo directory, ejected and disconnected the device. Half an hour later it is still on the loading screen, so I'm guessing something didn't work out. Any ideas?

11-13-2016, 05:46 PM	#103
Quentin Junior Member Posts: 1 Karma: 10 Join Date: Nov 2016 Device: kobo glo hd	Hi im new to this and have no idea what happens if i do this but it sounds interesting and im not sure so im going to ask it can i after i installed the firmware and decide go back to the normal kobo operating system and completely delete the firmware off my e-reader is that possible or not you can't go back after i installed this? please reply

11-13-2016, 10:05 PM	#105
PeterT Grand Sorcerer Posts: 13,430 Karma: 78880114 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Remember, you're actually running the original code, just with a few patches installed to it.

Advert

Advert