Quote:
|
Originally Posted by Quoth
On the really old Kindles you could edit a prefs file (which setting was destroyed if you selected a margin on the GUI).
|
I used to use that on my Kindle Keyboard and to be able to fix that overwritten-by-UI problem (when other people mess with my Kindle)
without using a computer I had a script (for whatever was the name at the time for "script launcher" thing that offered creating shortcuts using keyboard buttons) that used
sed to re-edit that prefs file
Quote:
|
Originally Posted by Quoth
It's not the only daft thing Amazon has done with Kindles.
|
And since fw 5.10.x or thereabouts they even made it so that reducing margins via editing hardcoded values inside JAR files doesn't work... probably there is duplicate or triplicate code in some new files and those "legacy" ones we the "power users" have known and modified past ~10 years are overridden somewhere else.
That was 1 of 2 things that pushed me into using KOReader + epub when I bought PW5 instead of combination of "patched" stock reader (with non-CSS approach to reducing margins) + KFX book format that was the combo I've used on my PW3 (that I've intentionally kept on firmware 5.8.11 until the day I've sold it).
The second thing was not being able to redefine font sizes for KFX books by using "CONTENT_FONT_RAMP" file in similar way that "FONT_RAMP" does for KF8 / AZW3 books... since that also requires editing JAR files to enable parsing of CONTENT_FONT_RAMP and me not having an answer to the question
"would PW5 with its locked bootloader and secure boot thing even boot after user has edited existing system files?" and PW5's board not having serial pads and me already having bricked one PW5 unit while trying to deal with missing "Book Cover" option / toggle in Device Settings... I've decided that safest and financially sound approach would be to just use KOReader instead on the replacement PW5 unit.
And since I've read comments of bunch of PW5 owners having they devices stuck in bootloop and even if just one of those comments has reported that bootloop / brick has occurred when PW5 froze while it was left in standby with KOReader opened I'm being extra paranoid and don't keep KOReader running on my PW5 all the time but exit out of KOReader every time I'm finished reading for that day.