Instructions for patching firmware 4.17.13694

[rAntonov]

Originally Posted by droopy

... Love getting new firmware. It makes me feel like my device is getting better.

It does, doesn't it? I don't know what has gotten into the KOBO devs but my first batch Aura One feels like a much better brand new now than the brand new it was when I first got it. If that makes sense

[Sirtel]

Originally Posted by IanScuffling

Yes, the good old placebo effect!

Hmmm I am always holding my breath and fearing the appearance of new bugs. Even with Kindles (which rarely have bugs) and all the more so with Kobo. I don't think I'm going to update my Libra quite yet.

[pickyaxe]

(deleted)

[emacsomancer]

Originally Posted by NiLuJe

@forster01: You can pretty much forget everything after the code block and the following sentence .

Essentially, that boils down to:

* Open .kobo/Kobo/Kobo eReader.conf in any half-decent text/code editor. Whatever you're already using to tweak the kobopatch YAML should be good enough.
* Scroll to bottom (if there's no bottom and you only see a single interminable line, your editor failed at being half-decent ^^).
* Append

[FeatureSettings]
ExcludeSyncFolders=\\.(?!kobo|adobe).*?

* Save, exit & eject/unplug safely .

I think because Nickel wants to relook at the sdcard, my on-to-read-time has become rather long for some reason recently. Is there an easy way to extend this to make Nickel ignore the (external) sdcard more generally?

[NiLuJe]

Originally Posted by emacsomancer

I think because Nickel wants to relook at the sdcard, my on-to-read-time has become rather long for some reason recently. Is there an easy way to extend this to make Nickel ignore the (external) sdcard more generally?

Not this way, it's already a RE fragment tacked on to the mountpoint.

Disabling the SD card would probably inolve mangling the udev scripts, and that feels way more cumbersome and clunky than simply popping out the card from the reader?

[filchef]

Originally Posted by Bald Eagle

Thank you! With that information I have been able to recreate my cyrillic layout for the A1 (the key values differ somewhat from the official ones).
The offsets for the 3rd and 4th row have been streamlined and are now consecutive:

Spoiler:

Cyrillic Keyboard (GloHD/ClaraHD/AuraOne/H2O2):
- Enabled: yes
- PatchGroup: Keyboard alternatives
## Replaces keys on the Extended Latin keypad with Cyrillic alternatives.
##
## Note that after the device boots, the keypad might just show blank squares
## until after the first book has been opened.
## Also note that long-pressing keys on the base keypad will no longer show
## the appropriate list of Extended Latin keys.
#
# Replace layout sign
- FindBaseAddressString: "ÉÀÇ"
- ReplaceString: {Offset: 0, Find: "ÉÀÇ", Replace: "АБВ"}
# Change keyboard layout
- FindBaseAddressString: "ý\0\0ÿ\0\0š\0\0ž\0\0"
# Top row, left to right (10 keys):
- ReplaceString: {Offset: 0x00, Find: "ý\0", Replace: "ё"}
- ReplaceString: {Offset: 0x04, Find: "ÿ\0", Replace: "э"}
- ReplaceString: {Offset: 0x08, Find: "š\0", Replace: "ä"}
- ReplaceString: {Offset: 0x0C, Find: "ž\0", Replace: "ö"}
- ReplaceString: {Offset: 0x10, Find: "æ\0", Replace: "ü"}
- ReplaceString: {Offset: 0x14, Find: "œ\0", Replace: "µ"}
- ReplaceString: {Offset: 0x18, Find: "þ\0", Replace: "ю"}
#- ReplaceString: {Offset: -56, Find: "ß\0", Replace: ","}
- ReplaceString: {Offset: 0x1C, Find: "ij\0", Replace: "х"}
- ReplaceString: {Offset: 0x20, Find: "ŀ\0", Replace: "ъ"}
# Second row, left to right (10 keys):
- ReplaceString: {Offset: 0x28, Find: "à\0", Replace: "й"}
- ReplaceString: {Offset: 0x2C, Find: "á\0", Replace: "ц"}
- ReplaceString: {Offset: 0x30, Find: "â\0", Replace: "у"}
- ReplaceString: {Offset: 0x34, Find: "ä\0", Replace: "к"}
- ReplaceString: {Offset: 0x38, Find: "ã\0", Replace: "е"}
- ReplaceString: {Offset: 0x3C, Find: "å\0", Replace: "н"}
- ReplaceString: {Offset: 0x40, Find: "è\0", Replace: "г"}
- ReplaceString: {Offset: 0x44, Find: "é\0", Replace: "ш"}
- ReplaceString: {Offset: 0x48, Find: "ê\0", Replace: "щ"}
- ReplaceString: {Offset: 0x4C, Find: "ë\0", Replace: "з"}
# Third row, left to right (10 keys):
- ReplaceString: {Offset: 0x50, Find: "ò\0", Replace: "ф"}
- ReplaceString: {Offset: 0x54, Find: "ó\0", Replace: "ы"}
- ReplaceString: {Offset: 0x58, Find: "ô\0", Replace: "в"}
- ReplaceString: {Offset: 0x5C, Find: "ö\0", Replace: "а"}
- ReplaceString: {Offset: 0x60, Find: "õ\0", Replace: "п"}
- ReplaceString: {Offset: 0x64, Find: "ø\0", Replace: "р"}
- ReplaceString: {Offset: 0x68, Find: "ì\0", Replace: "о"}
- ReplaceString: {Offset: 0x6C, Find: "í\0", Replace: "л"}
- ReplaceString: {Offset: 0x70, Find: "î\0", Replace: "д"}
- ReplaceString: {Offset: 0x74, Find: "ï\0", Replace: "ж"}
# Fourth row, left to right (8 keys):
- ReplaceString: {Offset: 0x78, Find: "ù\0", Replace: "я"}
- ReplaceString: {Offset: 0x7C, Find: "ú\0", Replace: "ч"}
- ReplaceString: {Offset: 0x80, Find: "û\0", Replace: "с"}
- ReplaceString: {Offset: 0x84, Find: "ü\0", Replace: "м"}
- ReplaceString: {Offset: 0x88, Find: "ñ\0", Replace: "и"}
- ReplaceString: {Offset: 0x8C, Find: "ç\0", Replace: "т"}
- ReplaceString: {Offset: 0x90, Find: "đ\0", Replace: "ь"}
- ReplaceString: {Offset: 0x94, Find: "ł\0", Replace: "б"}

Can I use this patch for my Kobo Aura HD 6.8" N204 New ebook reader onyx book 1440x1080 256PPI eReader e-ink with Light touch e-books Reader likebook libros which will arrive early April.

[JSWolf]

Originally Posted by filchef

Can I use this patch for my Kobo Aura HD 6.8" N204 New ebook reader onyx book 1440x1080 256PPI eReader e-ink with Light touch e-books Reader likebook libros which will arrive early April.

No you cannot.