Kobo Patcher

[Quexos]

Well at first sight, I can see that you returned the hash sign that causes the "page x of y" to appear.
Also I noticed you changed the 60 60 10 values to "default" which is 82 82 110
Let me try it to see what it looks like ...

Originally Posted by jackie_w

I see a few problems and will explain later if you like, but in the meantime try this one instead. Rename attachment to kpg.conf first.

[jackie_w]

Originally Posted by Quexos

Well at first sight, I can see that you returned the hash sign that causes the "page x of y" to appear.

Have I misunderstood? I thought you wanted a reduced bottom margin and the page x of y text.

[Quexos]

You understood correctly. I was just stating what changes I could spot on that kpg.conf that you sent me, before I tried it. And now I did try it and ...

Yep you pinned it !
This time the text is as full screen as possible with a little bit of space for the "page x of y" feature. Thank you very much
How did you do it, I mean the 60 60 10 value is replaced by the default one, is that what did the trick or is there something else ?

In other words, what did I do wrong ?

Originally Posted by jackie_w

Have I misunderstood? I thought you wanted a reduced bottom margin and the page x of y text.

[jackie_w]

Originally Posted by Quexos

You understood correctly. I was just stating what changes I could spot on that kpg.conf that you sent me, before I tried it. And now I did try it and ...

Yep you pinned it !
This time the text is as full screen as possible with a little bit of space for the "page x of y" feature. Thank you very much

Thank goodness for that!

Originally Posted by Quexos

How did you do it, I mean the 60 60 10 value is replaced by the default one, is that what did the trick or is there something else ?

The problem you had with 60 60 10 is this:
Each one of the Patcher options in kpg.conf is made up of 3 parts separated by commas

• Position to make changes,
• Old_value,
• New_value

The Footer patch is particularly hard to read. It's much easier to see on the other patches.

You had made changes to both Old_value (where you typed the 60 60 10) and New_value. So when the Patcher program was searching for Old_value it was never found -- hence 'nothing happened'.

[DNSB]

Originally Posted by Quexos

It appears my device shows this software version, the figures between the brackets are not the same as yours so I think it would be wise for me not to use the file you generated.

2.8.1 (b2co5cda0e) 7/15/13

Also I have tried different values to replace the 60 60 10 figures and it changed absolutely nothing, at least I did not see any change. I wonder why they have a patch with changeable values if they don't change anything in the display of the text?
I'm at a loss as to what to do so if there is no other solution I will simply go back to the original change where I had a full screen text with no "page x of y" at the bottom, at least with that, the wasted space issue is no more.

Thanks for your help and let us hope some future version of this patch will fix this.

For the older versions of the patchers, the modifications were done to the full string so you saw it twice. For version 7 patch, the 60 60 10 values are no longer used.

In version 7, the section from the replace_zlib = 1205FF4, to the `ReadingFooter A-OTF Gothic MB101 Pr6N;\n}`, is what the patcher expects to see in the libnickel.so.1.0.0 and, you will notice is the same for either removing the footer or decreasing the footer height. If you modify this, the patcher should throw up an error.

For version 7, the modifications are done by modifying the section at the end of each line:

`* {\n\theight: 5px;\n\tfont-size: 1px;\n\tcolor: transparent;\n}\n\n` is for the no footer and as you can see sets the footer height to 5 pixels, the footer font size to 1 pixel and then sets the whole thing transparent.

`* {\n\theight: 25px;\n\tfont-size: 20px;\n}\n\n` is for the decreased footer. In the example above, the height is set to 25 pixels and the font size to 20 pixels.

If you modify the in use find string, kpg.exe will toss up an error message such as:

kpg.exe
Kobo Patch Generator ver. 1.3 (c) 2013 MZ

Loading config file ...
OK

Checking config syntax ...
OK

Loading file for patching ...
OK

Applying patches ...
        Applying patch [Custom reading footer style] ...
1206002 51 b1

Data for replace in libnickel.so.1.0.0 and kpg.conf does not match!
libnickel.so.1.0.0 is already patched or from the wrong firmware version.
Replace: replace_zlib = 1206002, ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nRead
ingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproper
ty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footer
Margin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 30px;\n}\n\n
[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}, * {\n\thei
ght: 30px;\n\tfont-size: 25px;\n}\n\n

Regards,
David

[Quexos]

Oh I see. Well I'm very slowly (and after reading what you said more than one time) starting to understand. But it does not strike me as logical though.
You see, if as you say, the first part (Disable footer) is for a result where there is no footer anymore then WHY does it still have a value to define a footer ? in this case 5px, 1px and transparent ?
Logic tells me that I don't even need the second part then (the part called "decreased footer") since I could change 5, 1, transparent to, for example 20, 14, black.
Of course I won't do that, if this now works, I won't go look for problems that need not be. It's just that these files seem unnecessarily complicated.

Originally Posted by DNSB

For version 7, the modifications are done by modifying the section at the end of each line:

`* {\n\theight: 5px;\n\tfont-size: 1px;\n\tcolor: transparent;\n}\n\n` is for the no footer and as you can see sets the footer height to 5 pixels, the footer font size to 1 pixel and then sets the whole thing transparent.

`* {\n\theight: 25px;\n\tfont-size: 20px;\n}\n\n` is for the decreased footer. In the example above, the height is set to 25 pixels and the font size to 20 pixels.

[jackie_w]

Originally Posted by Quexos

Oh I see. Well I'm very slowly (and after reading what you said more than one time) starting to understand. But it does not strike me as logical though.
You see, if as you say, the first part (Disable footer) is for a result where there is no footer anymore then WHY does it still have a value to define a footer ? in this case 5px, 1px and transparent ?

I think it isn't really 'disabled', it has been made so tiny (1px) and transparent (invisible) that you can't see it. For all practical purposes - the same thing.

Originally Posted by Quexos

Logic tells me that I don't even need the second part then (the part called "decreased footer") since I could change 5, 1, transparent to, for example 20, 14, black.

You are correct, you only need one of them. This is effectively what you did by typing the # as the first character of either line 10 or line 12. The # makes the line into a 'comment' rather than an 'instruction', i.e it is ignored by the program.

Originally Posted by Quexos

Of course I won't do that, if this now works, I won't go look for problems that need not be.

Always a Good Plan

[Quexos]

In any case, a big thanks to Jackie_w and DNSB
This settles the issue for my Glo

Now for my AuraHD I think I'm screwed for the time being. You see I just updated the software cause I was on 2.5.1 which, we found throughout this thread is not compatible with the patch, to 2.8.1
Unfortunately I just noticed it has installed 2.8.1 (b2c05cda0e, 9/20/13) which according to some posts is not compatible with the patch.

So it turns out that Kobo not only never cared to fix this wasted space issue by themselves, but they also are trying to prevent patch makers like our Russian friend to help us out with this issue.
Is the Kobo management plain evil or what ?

[PeterT]

Bites tongue and avoids a reply

[DNSB]

Originally Posted by Quexos

Oh I see. Well I'm very slowly (and after reading what you said more than one time) starting to understand. But it does not strike me as logical though.
You see, if as you say, the first part (Disable footer) is for a result where there is no footer anymore then WHY does it still have a value to define a footer ? in this case 5px, 1px and transparent ?
Logic tells me that I don't even need the second part then (the part called "decreased footer") since I could change 5, 1, transparent to, for example 20, 14, black.
Of course I won't do that, if this now works, I won't go look for problems that need not be. It's just that these files seem unnecessarily complicated.

I tried setting the value to 0 and it didn't work though the result was "interesting". A 5 pixel height on my Aura HD gives me about .5mm for the footer height (10.4 pixels/mm). As for the dual setting, you could just change the first setting to set the height and font size and remove the transparent. Perhaps Metazoa thought it was easier to do it with two separate entries.

Regards,
David

[Mora]

Originally Posted by Quexos

In any case, a big thanks to Jackie_w and DNSB
This settles the issue for my Glo

Now for my AuraHD I think I'm screwed for the time being. You see I just updated the software cause I was on 2.5.1 which, we found throughout this thread is not compatible with the patch, to 2.8.1
Unfortunately I just noticed it has installed 2.8.1 (b2c05cda0e, 9/20/13) which according to some posts is not compatible with the patch.

So it turns out that Kobo not only never cared to fix this wasted space issue by themselves, but they also are trying to prevent patch makers like our Russian friend to help us out with this issue.
Is the Kobo management plain evil or what ?

I just got a kobo glo and its running 2.8.1 b2c05cda0e. I really want to get rid of the gigantic space that it leaves unused. It goes from 1024 to 920...

Do you know if there will be an update for this f/w too?

[Cap.T]

I don't know if that's possible but I think you could just download the other 2.8.1 firmware and downgrade to that manually. There are links to the firmware posted here. But first somebody here that knows more about that should confirm that such a downgrade is possible.

[DNSB]

Originally Posted by Cap.T

I don't know if that's possible but I think you could just download the other 2.8.1 firmware and downgrade to that manually. There are links to the firmware posted here. But first somebody here that knows more about that should confirm that such a downgrade is possible.

Downloading the older firmware from the links posted is not possible since the new 2.8.1 firmware file has replaced the old firmware file on Kobo's servers. Downgrading to the older 2.8.1 does work if you have access to the older firmware file.

Regards,
David

[Nick_1964]

Long time not being on this forum.
I applied the patch to my kobo aura HD but i would love it when the "page 26 of ..." is placed a bit higher, it now almost dissapear from the screen.
I made the txt a bit bigger and my cfg file look like this:

# Kobo Patch Generator config file
# firmware ver. 2.8.1
# (c) 2013 MZ
#

<Patch>
patch_name = `Custom reading footer style`
patch_enable = `yes`
# Disable footer example
#replace_zlib = 1205FF4, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[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`
# Decrease footer example
replace_zlib = 1205FF4, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `* {\n\theight: 35px;\n\tfont-size: 30px;\n}\n\n`
</Patch>

<Patch>
patch_name = `My line spacing values` 
patch_enable = `yes`
# Internal checks bypass
replace_float = 6857E0, 1.225, 0.1
replace_float = 685820, 1.225, 0.1
# Values for replace
replace_float = 1201A58, 1.3,   0.8
replace_float = 1201A60, 1.35,  0.85
replace_float = 1201A68, 1.4,   0.9
replace_float = 1201A70, 1.6,   0.95
replace_float = 1201A78, 1.775, 1.0
replace_float = 1201A80, 1.9,   1.05
replace_float = 1201A88, 2.0,   1.1
replace_float = 1201A90, 2.2,   1.15
replace_float = 1201A98, 3.0,   1.2
</Patch>

<Patch>
patch_name = `Wi-Fi insomnia`
patch_enable = `no`
replace_bytes = 704678, 11 B9, 00 46
</Patch>

<Patch>
patch_name = `Freedom to advanced fonts control`
patch_enable = `yes`
replace_bytes = 892894, 2C F4 52 EE, 3C F4 4C E9
replace_bytes = 982714, 70 F7 E0 E3, 00 46 00 46
replace_bytes = 984166, 6E F7 B8 E6, 00 46 00 46
</Patch>

<Patch>
patch_name = `Custom fonts sizes`
patch_enable = `yes`
# Values for replace
replace_int = F773F8, 12, 15
replace_int = F773FC, 14, 16
replace_int = F77400, 16, 17
replace_int = F77404, 17, 18
replace_int = F77408, 18, 19
replace_int = F7740C, 19, 20
replace_int = F77410, 20, 21
replace_int = F77414, 21, 22
replace_int = F77418, 22, 23
replace_int = F7741C, 24, 24
replace_int = F77420, 25, 25
replace_int = F77424, 26, 26
replace_int = F77428, 28, 27
replace_int = F7742C, 32, 28
replace_int = F77430, 36, 29
replace_int = F77434, 40, 30
replace_int = F77438, 44, 31
replace_int = F7743C, 46, 32
replace_int = F77440, 48, 33
replace_int = F77444, 50, 34
replace_int = F77448, 52, 35
replace_int = F7744C, 54, 36
replace_int = F77450, 56, 37
replace_int = F77454, 58, 38
</Patch>

<Patch>
patch_name = `Custom left & right margins`
patch_enable = `yes`
# Values for replace
replace_int = 1201AA4, 02, 01
replace_int = 1201AA8, 04, 02
replace_int = 1201AAC, 06, 03
replace_int = 1201AB0, 08, 04
replace_int = 1201AB4, 10, 05
replace_int = 1201AB8, 12, 06
replace_int = 1201ABC, 14, 07
replace_int = 1201AC0, 16, 08
</Patch>

<Patch>
patch_name = `Remove system fonts in Reader list`
patch_enable = `no`
replace_bytes = 96A94E, 60 F7 7E E7, 00 46 00 46
</Patch>

<Patch>
patch_name = `Brightness fine control`
patch_enable = `yes`
replace_int = 82DFCC, 10, 01
replace_int = 82DFFC, 10, 01
</Patch>

<Patch>
patch_name = `Cyrillic keyboard`
patch_enable = `no`
# Enable uppercase for [ß] key
replace_bytes = 7FBCA2, 00 24, 01 24
# Replace layout sign
#replace_bytes = F63FD0, C3 89 C3 80 C3 87, D0 90 D0 91 D0 92
replace_string = F63FD0, `ÉÀÇ`, `абв`
# Change keyboard layout
replace_utf8chars = F645D4, `æ`, `й`
replace_utf8chars = F64464, `àèìòùáéíóú`, `цукенгшщзх`
replace_utf8chars = F645F8, `ý`, `ъ`
replace_utf8chars = F645D8, `œ`, `ф`
replace_utf8chars = F644B0, `âêîôû`, `ывапр`
replace_utf8chars = F6448C, `äëïöüÿ`, `олджэё`
replace_utf8chars = F644C4, `ã`, `я`
replace_utf8chars = F644A8, `ñõ`, `чс`
replace_utf8chars = F645FC, `å`, `м`
replace_utf8chars = F64434, `ß`, `и`
replace_utf8chars = F644A4, `ç`, `т`
replace_utf8chars = F64600, `đøij`, `ьбю`
replace_utf8chars = F645E8, `ł`, `.`
</Patch>

<Patch>
patch_name = `Allow download all in Browser`
patch_enable = `yes`
replace_bytes = 93F4F4, B1 F7 EC E0, 01 20 01 20
</Patch>

<Patch>
patch_name = `Fix page breaks bug`
patch_enable = `yes`
replace_bytes = C13B6E, E8 D0, E8 E7
#Alternative method
#replace_bytes = C13B6E, E8 D0, 00 46
</Patch>

<Patch>
patch_name = `Margins fine tuning`
patch_enable = `no`
# Initial replaces
replace_bytes = 848E86, 19 46, 00 21
replace_bytes = 848E88, 1A 46, 00 22
# Values for replace
# Left margin
replace_int = 848E86, 0, 10
# Top margin
replace_int = 848E88, 0, 10
</Patch>

So a little bit of white under the "page .. of .." would be nice ( place it a little bit higher ) would be fantastic, can anyone help me ?

[Quexos]

What date comes after b2c05cda0e, cause you did not specify. If it's 9/20/13 then you will have to wait (like me for my AuraHD) for a future patch that works on this evil update (update made with no other purpose than to block users from having what they want).
Also I don't understand what you mean by "from 1024 to 920" ?

Originally Posted by Mora

I just got a kobo glo and its running 2.8.1 b2c05cda0e. I really want to get rid of the gigantic space that it leaves unused. It goes from 1024 to 920...

Do you know if there will be an update for this f/w too?