MobileRead Forums - View Single Post - Font, ScreenSaver & USBNetwork Hacks for Kindle 2.x, 3.x & 4.x

NiLuJe · 09-29-2010, 09:56 PM

@nubreader: Yeah, a restart, soft or hard, whatever you can do

.

UPDATE: Infos/Files added to first post.

But, okay, because this is starting to bug me, to everyone having difficulty with the grubby hands of the fw 3.x framework that doesn't want to let the font files go (and add fuse doing its best not to break anything on top of that, and, bingo, weirdness ensue!), let's try this:

This is the Fontin set, but as an update file. That should ensure that:

1/ The framework is down when we switch the files
2/ The hack is down when we switch the files

That *should* eliminate the weird behaviour that some of you have seen... If it does help, I'll repackage some of the fonts like that, and add another post on how to package fonts yourself... And on the plus side, you shouldn't need to do any kind of restart after that, because the update process will have taken care of it

.

But, still, without resorting to this, a full restart *should* fix the issue...

(And, FYI, I never exactly encountered this myself... I did encounter weird framework+fuse behaviour, but that was before the fonts hack (ie. double/ghost book entries because I moved a book file at the wrong time, the framework failing to open the *default* fonts when switching font families in the [Aa] menu...) Fun times!).

Also, to those of you having issues switching fonts, what fw version are you using? 3.0? 3.0.1? 3.0.2?

09-29-2010, 09:56 PM	#720
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	@nubreader: Yeah, a restart, soft or hard, whatever you can do . UPDATE: Infos/Files added to first post. But, okay, because this is starting to bug me, to everyone having difficulty with the grubby hands of the fw 3.x framework that doesn't want to let the font files go (and add fuse doing its best not to break anything on top of that, and, bingo, weirdness ensue!), let's try this: This is the Fontin set, but as an update file. That should ensure that: 1/ The framework is down when we switch the files 2/ The hack is down when we switch the files That should eliminate the weird behaviour that some of you have seen... If it does help, I'll repackage some of the fonts like that, and add another post on how to package fonts yourself... And on the plus side, you shouldn't need to do any kind of restart after that, because the update process will have taken care of it . But, still, without resorting to this, a full restart should fix the issue... (And, FYI, I never exactly encountered this myself... I did encounter weird framework+fuse behaviour, but that was before the fonts hack (ie. double/ghost book entries because I moved a book file at the wrong time, the framework failing to open the default fonts when switching font families in the [Aa] menu...) Fun times!). Also, to those of you having issues switching fonts, what fw version are you using? 3.0? 3.0.1? 3.0.2? Last edited by NiLuJe; 09-30-2010 at 05:57 PM. Reason: Added to first post.