Kobo Patcher

[DNSB]

Originally Posted by Prestidigitweeze

Anyway, enough procrastination about last revisions. Back to editing the pieces I have to read.

What??? You're actually going to use an ereader to read a book?

Regards,
David

[Prestidigitweeze]

Originally Posted by doubleshuffle

Well, good luck for your reading!

Thanks for that, DS.

It's fairly clear I'll eventually have to get a tablet for doing readings. None of the e-ink e-readers I've used at performances have been reliable. The Aura looked beautiful but died as I was reading and I had revive it (though, luckily, not restart it). And while I can always ad lib when that happens, I was being video'd, as usual, and it's too bad that the reading couldn't flow exactly like the piece when I know clips will appear on youtube.

I have another reading on October 5, which I'm dreading only because I won't be able to solve the hardware issue before then. Something like the Nexus 7.2 might do when Black Friday's in effect.

Anyway. Back to the patch:

I'm thinking of trying the modifications which DSNB posted a few pages back, only with full footers enabled.

What are you people using for plugins with Calibre? I have to be quite careful or the Kobo ePub Extended plugin does things to the footers that make my Aura HD freeze. I'm not that fond of kepub books anyway, and the patch doesn't like them, either, so I might go back to the earlier Kobo plugin.

[Quexos]

Ok I would like to try this patch and I'm still trying to figure this out.
But this patch seems to be made for versions 2.6.1 and 2.8.1

The thing is I'm on 2.5.1 in both my Glo and Aura HD so which version should I use please ?

Ok since no one answered I tried the 2.6.1 patch on my 2.5.1 Glo, now It's rebooting but it's taking an extremely long time to reboot as I have the Glo smiley face with the 5 blinking dots under it which you have when simply booting the device. it's just doing that, I fear it might be stuck in the booting process, what should I do ?
I'll just wait a little and if nothing happens then I guess I'll have to force it to shut down somehow, then what should I do ?

[buffaloseven]

I believe you're going to need some help from the gurus here. Since you applied it to the 2.5.1 firmware, you've likely corrupted it and I'd be surprised if it boots at all. I believe there are a couple people here (maybe davidfor?) that can help you restore your readers.

[tshering]

You can only do a factory reset. Here is how to do it on the Touch. For the Glo it is the same, but one has to use the light button instead of the home button.
None of these patches works for 2.5.1!

[Quexos]

That guide is for the touch and I'm on the Glo.
I checked the Glo page at the kobo website and to do a factory reset I must go into the menu of the Glo, but I can't access the menu anymore since it's on a booting loop and never completing the booting sequence.

I think my Glo is screwed :-(

Originally Posted by tshering

You can only do a factory reset. Here is how to do it on the Touch. For the Glo it is the same, but one has to use the light button instead of the home button.
None of these patches works for 2.5.1!

[tshering]

Originally Posted by Quexos

That guide is for the touch and I'm on the Glo.
I checked the Glo page at the kobo website and to do a factory reset I must go into the menu of the Glo, but I can't access the menu anymore since it's on a booting loop and never completing the booting sequence.

I think my Glo is screwed :-(

You can use the guide for the Touch, but since the Glo does not have a home button, you must use the light button instead.

[Quexos]

Ok the light button and it worked, I really thought my Glo was done for.
This is very annoying cause I must do the entire set-up again but compared to the possibility of a dead Glo this is rather good news.

Now if I may add my 2 cents, a BIG LETTER WARNING in this guide would be helpful to noobs that tinker. Using ANY other version than 2.6.1 or 2.8.1 will screw your device with a hard reset being the only option ... or something.

When I'm done resetting, I should upgrade to the latest firmware but if that latest firmware is not 2.8.1 but something more recent I suppose I should not use it or risk what just happened to me today.

Does anyone know what is the latest firmware that I'll get if I update today ?

Originally Posted by tshering

You can use the guide for the Touch, but since the Glo does not have a home button, you must use the light button instead.

[tshering]

Originally Posted by Quexos

When I'm done resetting, I should upgrade to the latest firmware but if that latest firmware is not 2.8.1 but something more recent I suppose I should not use it or risk what just happened to me today.

This is correct.

Originally Posted by Quexos

Does anyone know what is the latest firmware that I'll get if I update today ?

2.8.1.

[Quexos]

Ok finally after a long process of re-setting my reader and getting my stuff back in, I tried the 2.8.1 on my 2.8.1 reader and after finally finding the values advised somewhere in this thread (the 60 60 10) I can say my reader looks great and there is no more wasted space.

So what I did is I put "no" to all other fields of values in the kpg.conf file because I'm not sure what they do.
Am I assuming correctly that "no" means this patch stuff does not change or interfere with my reader ?

As for the "yes" where I changed the values to 60 60 10, can someone tell me exactly what those refer to ? I mean if I want more or less space at the upper part of my screen, which value do I change and in what direction (more than 60 or less to increase space?)

And finally the only detail that would make me totally happy is about the page count at bottom that is now gone. Probably ruled by some field where I put "no" but which ? and what values make it back, higher, lower, smaller, bigger ?

That should be all for me

[the_doc]

I dunno, maybe you could activate the "showing the lateral number of page" option in epubs.

[DNSB]

For anyone using firmware 2.8.1 who does a factory reset, this is a rather important item to note:

Kobo has quietly updated the 2.8.1 firmware. If your ereader now show a software details of 2.8.1 (b2c05cda0e, 9/20/13), the libnickel.so.1.0.0 file has been changed. You can probably get away with using the libnickel.so.1.0.0 file supplied with the patcher -- keyword being probably but the new libnickel.so.1.0.0 will not work with the current patcher configuration file.

Regards,
David

[tshering]

Originally Posted by DNSB

If your ereader now show a software details of 2.8.1 (b2c05cda0e, 9/20/13), the libnickel.so.1.0.0 file has been changed. You can probably get away with using the libnickel.so.1.0.0 file supplied with the patcher -- keyword being probably

I guess Quexos is using a patched libnickel with the new FW. Quexos, could you please confirm this?

[Quexos]

If you're referring to my factory reset on my Glo after it bricked, it was due to my ignorance of this patch. I updated it when my Glo was using firmware 2.5.1.
After my factory reset, I updated my Glo to 2.8.1 and the patch was accepted (though I still don't understand it fully).
My firmware says: 2.8.1 (b2c05cda0e, 7/15/13)

I still would like to understand the values I entered, which are 60 60 10
I think I'd like my text a little close to the bottom and top (if I can't get page x of y back, there is no point for me to keep some blank up and down there)
So to that end should I increase that value (say 80 80 10) or decrease it (40 40 10 or even less) ?

Originally Posted by tshering

I guess Quexos is using a patched libnickel with the new FW. Quexos, could you please confirm this?

Thanks for the suggestion but I don't like the lateral page count.
Since I hear some in this thread talking about their page count at bottom still there (albeit with size issues) I wonder why mine disappeared altogether and what codes should I change to get it back.

Originally Posted by the_doc

I dunno, maybe you could activate the "showing the lateral number of page" option in epubs.

[DNSB]

Originally Posted by Quexos

If you're referring to my factory reset on my Glo after it bricked, it was due to my ignorance of this patch. I updated it when my Glo was using firmware 2.5.1.
After my factory reset, I updated my Glo to 2.8.1 and the patch was accepted (though I still don't understand it fully).
My firmware says: 2.8.1 (b2c05cda0e, 7/15/13)

I still would like to understand the values I entered, which are 60 60 10
I think I'd like my text a little close to the bottom and top (if I can't get page x of y back, there is no point for me to keep some blank up and down there)
So to that end should I increase that value (say 80 80 10) or decrease it (40 40 10 or even less) ?

You are currently on the version used by Metazoa's 2.8.1 patch. However, if you are using 60 60 10, that suggests that you are not using the most recent patcher (V7) so I'd recommend updating to that version -- check the first message for where to download that version. In the V7 patch configuration files, there are two options. The first option removes the footer more or less entirely while the second option gives a much smaller footer with the page numbers present.

If you look at the v7 configuration file, you'll see two lines starting with "replace_zlib = 1205FF4, `ReadingFooter {. The line above the first instance says disable footer example while the line above the second instance says decrease footer example.

To use the decrease footer, place a # before the first instance of replace_zlib = and remove the # before the second instance. To change the height of the footer, look at the last part of the second instance where it reads:

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

This sets the height to 25 pixels and the font size for the text to 20 pixels which works for my Aura. On the Glo with it's larger pixels, you might want to reduce those values to 18 and 14 as a starting point.

The earlier way of making changes which made changes for a specific device could and did run into issues where the changes meant the compressed code no longer fit into the space allocated. The new version does a wild card change for all devices using the * wild card and takes a lot less space.

Regards,
David