Instructions for patching firmware 3.3.x, 3.4.x, 3.5.x

[muness]

What happened to the patch for disabling the footer? Is that no longer necessary because there's a built-in setting for it now? If so, where is it?

Sorry if this is obvious... I am out of date on these patches and searching this thread, the old patch thread and the 3.3.0/3.5.0 threads didn't turn up anything.

[DNSB]

Originally Posted by muness

What happened to the patch for disabling the footer? Is that no longer necessary because there's a built-in setting for it now? If so, where is it?

Sorry if this is obvious... I am out of date on these patches and searching this thread, the old patch thread and the 3.3.0/3.5.0 threads didn't turn up anything.

If you add the following lines to the .kobo/Kobo/Kobo eReader.conf files, you will get a new entry in the reading settings page in settings called page layout. Removing the checkmark for Show header and footer: will allow you to disable the header/footer.

[FeatureSettings]
FullScreenReading=true

Use a Unix end of line aware editor (I use Notepad++). If the [FeatureSettings} line already exists, simply add the FullScreenReading=true line below it.

On an Aura HD, the reading settings page looks okay but some comments that on other Kobo ereaders, the settings page get messy with that setting taking up extra space.

Regards,
David

[GeoffR]

I've updated patch_kobo_35.zip in post #1 to include the old page breaks patch for 3.5.0, and the old disable reading footer patch for 3.4.1 and 3.5.0.

The page breaks bug is fixed in firmware 3.5.0, but the `Fix page breaks bug` patch also has the side effect of disabling widows/orphans processing which could still be useful if you are reading DRM epubs or don't use Calibre for sideloading. (DRM-free epubs can have the widows/orphans settings set automatically using the "Modify CSS" feature of the KoboTouch driver in Calibre).

Starting in firmware 3.3.0 there is an experimental full-screen reading mode which can be activated by adding "FullScreenReading=true" to the [FeatureSettings] section of the device's .conf file and selecting an option from the Reading Settings menu. However the full-screen mode still has a few issues that affect kepubs, so the `Disable reading footer` patch might still be useful for those reading kepubs.

[PeterT]

As i've warned elsewhere, there are issues with ePubs and the FullScreenReading settings too; I've documented an example of text going AWOL on a Glo with that setting enabled.

[muness]

Thanks for the answer the FullScreenReading hidden option. Since I use an AuraHD with ePubs that'll likely work fine for me. Will revert the the patch (thanks @GeoffR for adding it to the OP zip!) if I experience any issues.

[PeterT]

See https://www.mobileread.com/forums/sho...1&postcount=58 for a test document and the rough settings where I've seen issues.

[Nick_1964]

I gonna travel trough all the patch things but I already know that I need help with the part of the Decrease footer example for Aura HD which is now.

Spoiler:

replace_xor_9C = 13FD538, `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: 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}\x00`
</Patch>

So before I even gonna try, is 3.5.0 worth all the troubles... I don't mind the "light" bug...

[GeoffR]

Originally Posted by Nick_1964

So before I even gonna try, is 3.5.0 worth all the troubles... I don't mind the "light" bug...

I am using 3.5.0, but 3.4.1 was better in my opinion. There are some problems with the new RMSDK in 3.5.0 which affect reading epubs and pdfs: it is slower than the old one and although it fixes some old bugs it also has some new ones.

If you upgrade to 3.4.1 or 3.5.0, PM me and I'll show you how to change your custom footer to suit the new patch layout. Once you have an example it should be easier to customise in the future.

[Nick_1964]

Originally Posted by GeoffR

I am using 3.5.0, but 3.4.1 was better in my opinion. There are some problems with the new RMSDK in 3.5.0 which affect reading epubs and pdfs: it is slower than the old one and although it fixes some old bugs it also has some new ones.

If you upgrade to 3.4.1 or 3.5.0, PM me and I'll show you how to change your custom footer to suit the new patch layout. Once you have an example it should be easier to customise in the future.

If you advice me to upgrade to 3.4.1 in stead of 3.5.0 I will follow your advice, but I thought the RMSDK was only for kepubs ?
I only read sideloaded epub's, there is no company here that offers kepubs only kobo's expensive shop, that I don't use, and I always have to edit my books with Sigil and that doesn't work with kepubs.
I have kept all the patch lay outs you made for me,but I don't see a pattern in it.. but I am a dyslectic 50 year old one that try to follow everything in a language that I have only one year of lessons in it...
Dyslectic in a form that my mind doesn't see letters at all, but pictures, so I can read very fast but comparing codes with + or ' and / and thinks like me is the same as 2 pictures of the same and seek the 7 differences between them
So if your advice is, go to 3.4.1 I would gladly send you my config file of 3.1.1, then I read back to see what patcher I have to use because I now downloaded the conf files and firmware for 3.5.0.
So before bothering you with a PM, please confirm that with sideloaded epubs 3.4.1 is better and I gladly send you my conf file.. wish I could pay you on some way, I feel a bit helpless and when someone like you offer this now for the 3th time the firmware changes, I feel guilty as... well you know..

[GeoffR]

Originally Posted by Nick_1964

If you advice me to upgrade to 3.4.1 in stead of 3.5.0 I will follow your advice, but I thought the RMSDK was only for kepubs ?

The new RMSDK in 3.5.0 is for epubs, it adds some capabilities to the epub reader, but also makes it less responsive. I find swipes are still okay, but taps and long-presses are slower, especially in books which have very long chapters. But your experience might be different, it will depend on which features you use and what sort of things bother you.

I'll PM you with your footer patches for 3.4.1 and 3.5.0.

[violent23]

Originally Posted by GeoffR

I've updated patch_kobo_35.zip in post #1 to include the old page breaks patch for 3.5.0, and the old disable reading footer patch for 3.4.1 and 3.5.0.

The page breaks bug is fixed in firmware 3.5.0, but the `Fix page breaks bug` patch also has the side effect of disabling widows/orphans processing which could still be useful if you are reading DRM epubs or don't use Calibre for sideloading. (DRM-free epubs can have the widows/orphans settings set automatically using the "Modify CSS" feature of the KoboTouch driver in Calibre).

Starting in firmware 3.3.0 there is an experimental full-screen reading mode which can be activated by adding "FullScreenReading=true" to the [FeatureSettings] section of the device's .conf file and selecting an option from the Reading Settings menu. However the full-screen mode still has a few issues that affect kepubs, so the `Disable reading footer` patch might still be useful for those reading kepubs.

Thanks for re-adding Disable reading footer. I had been meaning to make a post on here asking if you could add it back in as I can not stand the cut off setting with the FullScreenReading=true. Your work definitely makes using the Kobo so much better. Thanks!

[Nick_1964]

Originally Posted by GeoffR

The new RMSDK in 3.5.0 is for epubs, it adds some capabilities to the epub reader, but also makes it less responsive. I find swipes are still okay, but taps and long-presses are slower, especially in books which have very long chapters. But your experience might be different, it will depend on which features you use and what sort of things bother you.

I'll PM you with your footer patches for 3.4.1 and 3.5.0.

And they work !! just thinking here, is the patch_name = `Fix page breaks bug`any use for me.
( it is now disabled )
Basic: I use only sideloaded epubs.
I don't use any other part, with the things you change the pages are filled to 7 mm of the bottom, and the page xx of xx is floating maybe 5 mm from the bottom in nice Amasis font.
I use calibre for putting the Amasis font in the book ( I like it the most) and convert them so the font is inserted into the book, with an extra setting at the conversion at the part of look and behaviour, insert extra .css: body {line-height: 1.2; widows: 0; orphans: 0;} ( see picture I try to add at this message )

I use the device for what it is,reading, I only read sideloaded epubs, so do I have to enable the patch Fix page breaks bug ???

I just like to have my ebooks "clean" so every line start at the left, I don't want the text stretched so the whole line is filled... if there are only 4 words on a line it is okay with me, I have a tablet for internet and I don't play games, it is a E-Reader.
So.. does the patch helps me or is it not needed because Calibre handles the Widows and Orphans ?

Also here ( https://www.mobileread.com/forums/sho...&postcount=272 ) someone says that Kobo has retracted 3.5.0. ?

Again: https://www.mobileread.com/forums/sho...&postcount=284

So it seems that hacking 3.5.0. was a waiste of time ?

[GeoffR]

Originally Posted by Nick_1964

I use the device for what it is,reading, I only read sideloaded epubs, so do I have to enable the patch Fix page breaks bug ???

If you have widows:0;orphans:0; set with Calibre then the `Fix page breaks bug` patch isn't needed at all.

[DNSB]

Originally Posted by GeoffR

If you have widows:0;orphans:0; set with Calibre then the `Fix page breaks bug` patch isn't needed at all.

I'd recommend setting widows: 1; and orphans: 1;. With 0/0, I get the occasional end of chapter issue where a few lines show on a page and then the last few lines on the next page. With the newer edits where I went to 1/1, I haven't seen that problem so I think there may be a connection though it was random enough that I can't be certain.

Regards,
David

[Jellby]

A widows/orphans value of 0 is invalid according to the CSS spec, and should be ignored (and then the default value will be used). To all effects, a value of 1 is equal to "disable".