Kobo Patcher

[icallaci]

Originally Posted by jackie_w

Try changing the end part from

`* {\n\theight: 30px;\n\tfont-size: 25px;\n}\n\n`

to

`ReadingFooter {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`

The Footer height can be increased/decreased by changing the two 50px values. The size of the 'Page x of y text' can be inc/dec by changing the font-size: 26px value.

Jackie, that fixed it perfectly! The 50px min and max is just what I wanted. Thank you!

[jackie_w]

Originally Posted by icallaci

Jackie, that fixed it perfectly! The 50px min and max is just what I wanted. Thank you!

Glad to hear it

Like you, I've never found that changing the height value, in Metazoa's default kpg.conf, did anything useful. Just FYI, the 'ReadingFooter method' is the way he used to suggest in the original version of the Patcher.

[icallaci]

Originally Posted by jackie_w

Glad to hear it

Like you, I've never found that changing the height value, in Metazoa's default kpg.conf, did anything useful. Just FYI, the 'ReadingFooter method' is the way he used to suggest in the original version of the Patcher.

That is good info to know. I am delighted with my patched Kobo Aura HD.

[icallaci]

I'm trying to understand how the patches work. In looking at what jackie_w suggested above, I ended up with code that looks like this:

[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `ReadingFooter {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`

Is there a reason why tfont-size and tfont-family are duplicated? Should I edit this to remove the duplicates? If yes, what should the final code look like (so I don't screw up what seems to be working just fine)?

[jackie_w]

Each Patch is of the format

replace_type = location, `old value`, `new value`

and means (I think): At this location replace the old value with the new value using the replace_type coding magic method.

In your example above you seem to have part of the `old value` combined with the `new value`

[DNSB]

Originally Posted by icallaci

I'm trying to understand how the patches work. In looking at what jackie_w suggested above, I ended up with code that looks like this:

[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `ReadingFooter {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`

Is there a reason why tfont-size and tfont-family are duplicated? Should I edit this to remove the duplicates? If yes, what should the final code look like (so I don't screw up what seems to be working just fine)?

The original MZ patcher replaced the entire zlib compressed string hence the duplicated string where you modified the second string. This could lead to issues where the compressed replacement string was longer than the original string. The later version replaced the device dependent strings with a simple universal replacement string. You will notice the current version has two end strings, the first of which under the 'disable footer' sets the footer to 5 pixels with 1 pixel text and makes it transparent.

`* {\n\theight: 5px;\n\tfont-size: 1px;\n\tcolor: transparent;\n}\n\n`

while the second 'decrease footer' sets the height to 25 pixels and the font size to 20 pixels in the example below.

`* {\n\theight: 25px;\n\tfont-size: 20px;\n}\n\n`


The \n and \t character pairs represent a new line and a tab character while the star is a wild card. As jackie_w says, you can change the values in there or add other values such as setting the font used (see the Japanese example in the original style as an example0.

In your case, something like:

`* {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tfont-size: 26px;\n}\n\n`

might be useful though I suspect simply setting the height to 50 pixels would have the same effect.

Regards,
David

[icallaci]

Originally Posted by DNSB

The original MZ patcher replaced the entire zlib compressed string hence the duplicated string where you modified the second string. This could lead to issues where the compressed replacement string was longer than the original string. The later version replaced the device dependent strings with a simple universal replacement string. You will notice the current version has two end strings, the first of which under the 'disable footer' sets the footer to 5 pixels with 1 pixel text and makes it transparent.

`* {\n\theight: 5px;\n\tfont-size: 1px;\n\tcolor: transparent;\n}\n\n`

while the second 'decrease footer' sets the height to 25 pixels and the font size to 20 pixels in the example below.

`* {\n\theight: 25px;\n\tfont-size: 20px;\n}\n\n`


The \n and \t character pairs represent a new line and a tab character while the star is a wild card. As jackie_w says, you can change the values in there or add other values such as setting the font used (see the Japanese example in the original style as an example0.

In your case, something like:

`* {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tfont-size: 26px;\n}\n\n`

might be useful though I suspect simply setting the height to 50 pixels would have the same effect.

Regards,
David

Thank you for explaining that, David. I am fiddling around with different settings to see what effect they have. It's starting to make sense.

[Nick_1964]

Mine for the Aura HD is (2.8.1) :

Spoiler:

# 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}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 31px;\n\tfont-family: Amasis;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`

It keeps the footer in Amasis font, because when you change the font, the page xx of xx line becomes very ugly, when you change the font in the reader settings the font of the footer changes with the same font.
Also I discovered that when you patch the first time, the footer is out of place, when you go to the book, settings,change the margin slider,set it back,then end, it is just in place.
With the above settings there is a bit of white space under the line page xx of xx and it doesn't matter anymore which reading font you take,the footer stays in amasis.

[Lyn2012]

After spending the day getting Crossover to work and then investigating the Patcher, I have managed to use the info in post #539 to successfully patch my Aura. Thank you to everyone who has posted information in this thread - and also to those who offered to run the patch for me.

Like icallaci, I would like to have a small space between Page x of y and the bottom of the screen. I've been following the recent posts but have still not been able to work out which part I should change, and what values I should use for the 6" Aura (Phoenix?). Please can somebody help?

This is the current line of code

replace_xor_58 = 13FA550, `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: 15;\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: 25px;\n\tfont-size: 20px;\n}\n\n`

[jackie_w]

Originally Posted by Lyn2012

Like icallaci, I would like to have a small space between Page x of y and the bottom of the screen. I've been following the recent posts but have still not been able to work out which part I should change, and what values I should use for the 6" Aura (Phoenix?). Please can somebody help?

I like to use the same kpg.conf for both my Glo and my AuraHD, so this is what I use for the line you asked about (fw 3.1.0). It gives a little bit more space under 'Page x of y' than the default. The Aura6" has the same resolution as the Glo, so hopefully it should be OK.

The red bits are those specific to the Aura6" (aka "phoenix"). Hopefully you should be able to copy/paste the whole string from this post.

replace_xor_58 = 13FA550, `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: 15;\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}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 40px;\n\tmax-height: 40px;\n\tqproperty-footerMargin: 15;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 50px;\n\tmax-height: 50px;\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}`

[norbusan]

Hi

anyone found the WiFi Insomnia switch for 3.1.0 already?

[icallaci]

Originally Posted by jackie_w

Each Patch is of the format

replace_type = location, `old value`, `new value`

and means (I think): At this location replace the old value with the new value using the replace_type coding magic method.

In your example above you seem to have part of the `old value` combined with the `new value`

Oops, Jackie, somehow I missed your post until now. Your explanation makes things much clearer in my poor, muddled head. I was terrified to change anything at first, but I have been fiddling with the patches all day without turning my Aura HD into a doorstop, so your help is very much appreciated. Thank you.

[GeoffR]

Originally Posted by norbusan

anyone found the WiFi Insomnia switch for 3.1.0 already?

Here is the Wifi insomnia patch for 3.1.0 (d1b2f00933), I haven't tested it because I don't know exactly what it is supposed to do, so post here with the result if you try it.

Spoiler:

# Firmware 3.1.0 (d1b2f00933)
<Patch>
patch_name = `Wi-Fi insomnia`
patch_enable = `yes`
replace_bytes = 7CEC04, 11 B9, 00 46
</Patch>

[Danger]

Thought I would post my settings for the page # display. Been playing around with this for a few days now and finally have it where I want it for my Glo:

{\n\tmin-height: 30px;\n\tmax-height: 30px;\n\tqproperty-footerMargin: 30;\n\theight: 30px;\n\tpadding-bottom: 4px;\n\tfont-size: 20px;\n}

[Lyn2012]

Originally Posted by jackie_w

I like to use the same kpg.conf for both my Glo and my AuraHD, so this is what I use for the line you asked about (fw 3.1.0). It gives a little bit more space under 'Page x of y' than the default. The Aura6" has the same resolution as the Glo, so hopefully it should be OK.

The red bits are those specific to the Aura6" (aka "phoenix"). Hopefully you should be able to copy/paste the whole string from this post.

replace_xor_58 = 13FA550, `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: 15;\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}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 40px;\n\tmax-height: 40px;\n\tqproperty-footerMargin: 15;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 50px;\n\tmax-height: 50px;\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}`

Fantastic, thank you so much jackie_w. Now I can see which code applies to the Aura it makes much more sense, I just couldn't work it out before.