Kobo Patcher

[DNSB]

Originally Posted by ectoplasm

Nice, now I'm less concerned about getting an unwanted update to 2.9.x on my HD. Hopefully the "Wi-Fi insomnia" and "Fix page breaks bug" patches can also be included.

For the Fix Page Breaks", the address to change for 2.9.0 is D2559E and for 2.8.1b, the address is BE76DE.

With 2.8.1, I was using the alternate method which I'm not sure fixed the long paragraph bug but did save me from some of the orphaned lines at the end of chapters. To revert to the standard method remove the # from in front of the first replace_bytes = and add it before the second replace_bytes.

The ebook I used for testing was "The Cossacks" by Leo Tolstoy as translated by Louise and Aylmer Maude which was downloaded from Gutenberg.

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

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

Regards,
David

[PeterT]

I've updated the initial post in this thread to include links to the 2.8.1B and 2.9.0 patches.

[Nick_1964]

Originally Posted by bartbrat

Luckily, user Akorx was kind enough to share the original 2.8.1 version. It works great, you can easily downgrade.

I uploaded it for the people who would also like to use the patch.

https://dl.dropboxusercontent.com/u/...date-2.8.1.zip

Just put it in the .kobo directory ?

[Quexos]

You can't just put a downgrade in the .kobo directory you must first do a factory reset, right ?
Someone savvy please confirm.

Originally Posted by Nick_1964

Just put it in the .kobo directory ?

[bartbrat]

Originally Posted by Quexos

You can't just put a downgrade in the .kobo directory you must first do a factory reset, right ?
Someone savvy please confirm.

Yes, fortunately you can! Just unzip and put the files in the .kobo directory, and it will update/downgrade to the old version of 2.8.1. It worked perfectly for me. Good luck!

[ShellShock]

A downgrade may work or may brick your reader, requiring a factory reset anyway.

[Mora]

I only need the unused white space to be gone at the bottom. Or have the page number really small so its still readable but barely. That is for kobo glo 2.8.1b.

[DNSB]

Originally Posted by Nick_1964

Just put it in the .kobo directory ?

Unpack the file and copy the upgrades directory and the KoboRoot.tgz and manifest.md5sum files to the .kobo directory.

I tried on one Glo that updated to 2.8.1b and it reverted to 2.8.1 without requiring a factory reset so you may want to try downgrading without doing the factory reset.

Regards.
David

[buffaloseven]

For those who find that the footer text is too close to the bottom [at least on the Glo], I gave something a little try and it's worked beautifully for me, so I thought I'd share here.

This isn't rocket science or anything, but noticing that it's all just plain old CSS, I thought I'd just add a bit of padding to the footer element, and it works perfectly. This will probably only work with the V7 syntax for the footer resizing since it leaves plenty of space for additional text.

* {
    height: 30px;
    font-size: 20px;
    qproperty-footerMargin: 40;
    padding-bottom: 8px;
}

I added in the qproperty-footerMargin parameter because the chapter titles wouldn't show in kepubs without it. 40 is based off the new proportions W.R.T. the default values: 110 * (30 / 82) ~= 40. Lastly I added a bit of padding to the bottom. Around 8px looks good on the Glo (at least to my eyes).

This has allowed me to gain a couple lines of text while maintaining fairly decent asthetics on the footer element. If you're on a Glo, the actual code you'd want to use in the patcher is:

* {\n\theight: 30px;\n\tfont-size: 20px;\n\tqproperty-footerMargin: 40;\n\tpadding-bottom: 8px;\n}

[jackie_w]

@buffaloseven,
Interesting, thanks

Did you try varying the height value in your testing at all? When I installed v07 originally I tried a few different values but I didn't seem to notice any difference in the resulting footer height. I wasn't sure whether also enabling the 'fix page breaks bug' option might be interfering in some way.

[Nick_1964]

I use for my Kobo Aura HD now the following settings:

# 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: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 40px;\n\tmax-height: 40px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 70px;\n\tmax-height: 70px;\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: 31px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`

and it leaves about 7 mm blanc space, then the text page nn of nn with underneed a 2 mm blanc line, don't know how to make a screenshot, but this works fine, thanks to jackie_w who pointed it out, changed values about 10 times and it is now perfect.
(Hope there will be an option in the future to have a little clock at the bottom line, right to the page nn of nn text, that would be great ! )

[buffaloseven]

Yeah, I spent a few hours fiddling with numbers. For the most part, if you want any significant amount of extra text on the screen you really have to shrink the footer ( < 20px ) because odds are your font size will be large enough that you actually need quite a of space for more than an extra line or two. It's still noticable, though, and I quite like the slightly smaller bottom footer. Here's how it looks on a .kepub sent from Calibre using jgougen's driver with my above settings:

[Nick_1964]

@buffaloseven how to make a screenshot on the AuraHD ?

[buffaloseven]

Originally Posted by Nick_1964

@buffaloseven how to make a screenshot on the AuraHD ?

Details on enabling it are here: https://www.mobileread.com/forums/sho...&postcount=13; it takes over your power switch, so if you don't have a sleep cover you may want to only enable it from time to time and not leave it enabled.

[Nick_1964]

Originally Posted by buffaloseven

Details on enabling it are here: https://www.mobileread.com/forums/sho...&postcount=13; it takes over your power switch, so if you don't have a sleep cover you may want to only enable it from time to time and not leave it enabled.

Interesting..so every time you move the power switch it makes a screenshot ? I will look at this in my conf file,because I could not understand if the screenshot option already is in there and just had to put into true,or it needs to be added... wiki option seems interesting to !

Found it.. great
This is my reading screen: