Instructions for patching firmware 3.11.0

[Hypernova]

Originally Posted by GeoffR

I think any problem will be triggered when the settings (Aa) menu is opened, or possibly when the dropdown menu for choosing the font family is opened.

I dont know what form the problem will take though, it might be something obvious like a crash, or something minor like not choosing the correct default font for a Japanese book, or it might corrupt some memory and cause a problam later on.

Ok. Thanks for the answer. I'm doing a replacement for my H2O so I might give it a try before I send the old one back. Will report if I do so.

[icallaci]

Using #5 for my H20, and it is PERFECT. Thanks so much, GeoffR.

[icallaci]

Originally Posted by icallaci

Using #5 for my H20, and it is PERFECT. Thanks so much, GeoffR.

Oops, not quite perfect. I just ran across a line that only showed the top 1/3 of the letters. So I uncommented the line that reduces the footer and changed -7px to 2px (making sure to put a space where the "-" was). NOW it is perfect. No cut off letters. The specific choices and examples you provide make it easier to figure out what I should change to affect particular areas of the footer. Thanks again.

[tshering]

@GeoffR
Could you please add a warning against using a file path that contains one or more ampersands to the instructions for windows users. Ampersands in the path name do not only break the current script, but might even cause data loss under certain conditions.

[GeoffR]

Originally Posted by tshering

@GeoffR
Could you please add a warning against using a file path that contains one or more ampersands to the instructions for windows users. Ampersands in the path name do not only break the current script, but might even cause data loss under certain conditions.

Done, thanks.

[GeoffR]

Originally Posted by velkro2

Is there any form to set sharpness always in maximum value (with no relation with weight)?
In firmware versions until 3.1.1, sharpness and weight settings were independent. I always set sharpness on maximum. I think the transition between pages looks to be faster. Is there any pach to recover that feature in the new firmware?

Originally Posted by PeterT

I know we've shown in the past that collection of full stats on kEpubs is controlled by what location they are stored in; Kobo downloaded material stored in .Kobo directory structure records stats, side loaded material stored elsewhere do not store stats.

This seems to suggest that there is a check on location being done. Any chance of a patch to change this, to re-enable stats regardless of location?

These would both be good patches to have, the sharpness patch probably wouldn't be too difficult (I haven't managed to find it yet though), but the in-book stats for kepub -- I don't even know where to begin looking.

[aceflor]

Originally Posted by GeoffR

These would both be good patches to have, the sharpness patch probably wouldn't be too difficult (I haven't managed to find it yet though), but the in-book stats for kepub -- I don't even know where to begin looking.

Oh yes, a sharpness patch would be fantastic !!!

[Anak]

Strings:

• libnickel.s0.1.0.0
• libadobe.so
• librmsdk.so.1.0.0
• nickel

I removed most of the "unreadable" strings, like

.text:0065214C        00000006 C 1Fzh8j

to reduce the file sizes of the text files.

[dmapr]

Originally Posted by GeoffR

These would both be good patches to have, the sharpness patch probably wouldn't be too difficult (I haven't managed to find it yet though), but the in-book stats for kepub -- I don't even know where to begin looking.

The sharpness patch would make me upgrade from 3.1

[traycold]

hi GeoffR,
any chance to have this patch for custom auto-off timeout for 3.11?
Also, do you think it is possible to overcome limit of 255 minutes?
Ideally, I would like to set 1 day(=1440 min) or 2 days(=2880 min).

I already tried what is suggested here, but apparently doesn't work:

1. set AutoOffMinutes=1440 in the "Kobo eReader.conf" file
2. reboot
3. read something, without opening setting page
4. put in stand-by
5. wait..

and the kobo shut down within some hours (don't know exactly when but definitely in no more than 2-3 hours after stand-by).

All this on Kobo Glo, firmware 3.11.

[DNSB]

Originally Posted by traycold

hi GeoffR,
any chance to have this patch for custom auto-off timeout for 3.11?
Also, do you think it is possible to overcome limit of 255 minutes?
Ideally, I would like to set 1 day(=1440 min) or 2 days(=2880 min).

I already tried what is suggested here, but apparently doesn't work:

1. set AutoOffMinutes=1440 in the "Kobo eReader.conf" file
2. reboot
3. read something, without opening setting page
4. put in stand-by
5. wait..

and the kobo shut down within some hours (don't know exactly when but definitely in no more than 2-3 hours after stand-by).

All this on Kobo Glo, firmware 3.11.

Out of curiosity, why would you want to see the power off timeout to such a long period? Personally, I set power off to never and sleep to 15 minutes and don't see that much of a hit on my battery life.

As for the 255 minutes limit, I'd suspect the code uses a single byte to store a binary value for the timeout in minutes so 255 would be the maximum. Setting 1440 is likely to get it evaluated mod 255 so the timeout would be 165 minutes (2 hours 45 minutes).

[JSWolf]

Speaking of the sleep timer, can I set it to 30 minutes?

[jackie_w]

Originally Posted by JSWolf

Speaking of the sleep timer, can I set it to 30 minutes?

Settings for Sleep (in mins) are: 5, 10, 15, 30, 45, 60, Never
Settings for Power off (in mins) are also: 5, 10, 15, 30, 45, 60, Never

[JSWolf]

Originally Posted by jackie_w

Settings for Sleep (in mins) are: 5, 10, 15, 30, 45, 60, Never
Settings for Power off (in mins) are also: 5, 10, 15, 30, 45, 60, Never

Thanks. That's perfect. 30 minutes should do just fine. My T1 uses 10 minutes and I cannot change it. That can be too short sometimes.

[jackie_w]

Originally Posted by JSWolf

Thanks

You're welcome. Have you hit the 'Buy' button yet?