Kindle firmware 5.8.5.0.2

[Barty]

Originally Posted by Axanar

I am the wrong person to ask. I was curious myself because Isamilis claimed to be able to still use USE_ALT_FONTS. After grep'ing through the entire amazon directory of the kindle firmware (PW2 here) I found no traces of anything that loads or tests for USE_ALT_FONT. With other words it shouldn't be working at all. But let's wait what Isamilis has to say.

Yes, excuse me, I @ the wrong person.

[Isamilis]

Originally Posted by Doitsu

I always thought that the USE_ALT_FONTS method doesn't work with PW2, PW3, Voyage and Oasis. (I use the font hack on my jail-broken PW2 to override code2000). I've got a couple of questions:

1. What font do you use as the replacement font and what are the file names of the Regular, Bold and Italic fonts that you use?

> I copied the regular font for the Bold and Italic. It seems, all of those three must be available

2. Did you change the stylesheet in your books so that it looks for your replacement font?

> No I didn't change the stylesheet.

[Isamilis]

Hi,

Yes sure. The difference between custom font and default font is very noticeable. Usually I didnt reboot, just close the book and wait about 5 minutes, and reopen the book.

FYI, I have done this on 2 PW3 and 1 Voyage (all of them are 5.6.x). I read this method from googling.

Originally Posted by Barty

@Axanar: this may be a dumb question but are you sure it is actually using your font? If you rename USE_ALT_FONTS and the fonts folder and reboot does it revert to the ugly font?

[Doitsu]

Originally Posted by Isamilis

Hi,

Yes sure. The difference between custom font and default font is very noticeable. Usually I didnt reboot, just close the book and wait about 5 minutes, and reopen the book.

FYI, I have done this on 2 PW3 and 1 Voyage (all of them are 5.6.x). I read this method from googling.

Could you please provide more detailed information?
What was your replacement font, how did you name the font files and where did you put them?

[shamanNS]

Ok, I did a quick test. It works (for some fonts) but either it's buggy or it uses some kind of whitelist for family names. Didn't work with "Charis SIL Modified", my mod of Palatino (reduced line height/ descender property) and couple of random Windows fonts.

Like, "Adobe Garamond Pro" and "Minion Pro" are displayed correctly but for fonts that don't get used/recognized correctly those paragraphs are displayed using sans serif font (probably Helvetica). Custom fonts themselves are of serif type.

Naming (probably) needs to be the same as for fonts hack (Name-Regular, Name-BoldItalic, ...). You dump the ttf files inside "fonts" folder in Kindle drive root, and in CSS classes just use font-family: "Adobe Garamond Pro";. No need to embed fonts or use @font-face to declare it using "src: blabla.ttf".

.f_garamond {
display: block;
font-family: "Adobe Garamond Pro";
margin: 0;
}

Restart Kindle after adding new font files.

Tested on PW3 fw 5.6.5 (jailbroken and with fonts hack installed) with an .azw3 file.

[doctoralvarez]

Originally Posted by cvkemp

I have updated my voyage, and pw2 not seen any thing new.

Also is KUAL working on PW?? Somewhere else I´ve read not working KUAL and something else (some files?) ???

[odamizu]

After updating to 5.8.5.0.2, my Oasis has starting missing paragraphs. A screen will show the top half of the page, with the bottom half blank. Going forward one screen then back again will restore the full page. This happens sporadically.

At first I thought it was a problem with the ebook (epub converted to azw3 using KindleGen), but then it happened with two more ebooks. Looking at the html in each book reveals nothing unusual.

Restarting my Oasis will temporarily fix it, but then it will start happening again with greater and greater frequency until I restart again.

I have just reset my Oasis and will see if that helps, but wondering if anyone else is experiencing this. This has never happened to me before on my Oasis or Voyage. Just started with this latest update.

Thanks for any insights.

[NullNix]

Originally Posted by odamizu

After updating to 5.8.5.0.2, my Oasis has starting missing paragraphs. A screen will show the top half of the page, with the bottom half blank. Going forward one screen then back again will restore the full page. This happens sporadically.

I see the same thing. It's clearly a bug. (For me, it happens intermittently and is always refreshed by switching pages, with no increasing frequency over time.)

[septentrion]

Originally Posted by odamizu

After updating to 5.8.5.0.2, my Oasis has starting missing paragraphs. A screen will show the top half of the page, with the bottom half blank. Going forward one screen then back again will restore the full page. This happens sporadically.

It happens with my Voyage, not often enough to bother me. I hadn't realised ti might be caused by the latest software update.

[NullNix]

Originally Posted by septentrion

It happens with my Voyage, not often enough to bother me. I hadn't realised ti might be caused by the latest software update.

I never saw it before 5.8.5.*, so I'd bet it's a regression somewhere in there, indeed.

[shamanNS]

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.

[odamizu]

Originally Posted by NullNix

I never saw it before 5.8.5.* ...

Same here.

Originally Posted by shamanNS

... 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 ...

Nope. No jailbreak, no hacks of any kind. Just straight vanilla Oasis.

Trying to decide whether to try to go back to the previous firmware, if that's even possible. At one point the other night it was happening every few pages.

[tomsem]

No problems with my Voyage, but I do not know when 5.8.5.0.2 showed up (it came OTA, not because I downloaded .bin etc.). So maybe I need to say 'no problems so far'.

[doctoralvarez]

Originally Posted by tomsem

No problems with my Voyage, but I do not know when 5.8.5.0.2 showed up (it came OTA, not because I downloaded .bin etc.). So maybe I need to say 'no problems so far'.

Thanx 4 info

[mathil]

My PW3 is jailbroken with the font hack installed, and I haven't seen that problem so far.