MobileRead Forums - View Single Post

NiLuJe · 10-01-2013, 06:42 PM

@Barty: The keyword here being "k3". A whole 'nother beast than the K5

.

Although it did suffer from the exact same kind of issues, the impact, as you said, was limited to disrupting the UI at worse. (And the workaround was already the same: use a vanilla freetype build).

Hence my numerous warnings on both the K2/3/4 & K5 fonts hack docs. The issue is exacerbated with the K5 (and particularly the PW, since we can't kubrick it) because of the inability to recover from the 'Your Kindle Needs Repair' (YKNR) screen with a vanilla/nearly-vanilla device without resorting to opening it up, unlike the previous models, where the recovery was more easily accessible and/or a hard factory reset was a possibility.

10-01-2013, 06:42 PM	#189
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Barty: The keyword here being "k3". A whole 'nother beast than the K5 . Although it did suffer from the exact same kind of issues, the impact, as you said, was limited to disrupting the UI at worse. (And the workaround was already the same: use a vanilla freetype build). Hence my numerous warnings on both the K2/3/4 & K5 fonts hack docs. The issue is exacerbated with the K5 (and particularly the PW, since we can't kubrick it) because of the inability to recover from the 'Your Kindle Needs Repair' (YKNR) screen with a vanilla/nearly-vanilla device without resorting to opening it up, unlike the previous models, where the recovery was more easily accessible and/or a hard factory reset was a possibility. Last edited by NiLuJe; 10-01-2013 at 06:50 PM.