View Single Post
Old 11-29-2016, 12:31 PM   #26
shamanNS
Wizard
shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.
 
Posts: 1,125
Karma: 12345678
Join Date: Feb 2010
Location: Serbia
Device: Kindle PW5, Kobo Libra 2, Kindle PW1
I had it on my old PW1 firmware 5.4.4 IIRC. Do any of you people that have that problem use: fonts hack OR have redefined 8 font sizes in Aa menu (eather by using FONT_RAMP thing or by editing the jar files on earlier firmwares that don't support FONT_RAMP) OR screensaver hack, or combination of 2 or more.

My PW1 had all of the them (font sizes and margins were changed by editing .jar file(s) ) and it started doing 2 things around the same time:

1) the problem described above (missing page content on render)
2) if book chapter starts with long epigraph or similar couple of long paragraphs that are using italics and font that is smaller than the base font size the book would crash the reader if I'm using 1st or 2nd font size option in Aa menu, and Kindle wouldn't open that book until I open another book and make the font size bigger (I mainly read using one of the 2 smallest font sizes in Aa menu, on crash I would change the font size to something like the 4th of 5th option and that would allow me to open the "problematic book" and page forward past that smaller font section after which I could return font size to 1st or 2nd... until next such section where it would again crash )

On my PW3 (still on firmware 5.6.5) I'm using fonts hack, FONT_RAMP thing and screensaver hack (so no edited system jar files on that Kindle) and thus-far never had either of two mentioned problems. Both Kindles are using the same custom font.
shamanNS is offline   Reply With Quote