Font, ScreenSaver & USBNetwork Hacks for Kindle 2.x, 3.x & 4.x

[nubreader]

@NiLuJe

i am on 3.0.1 have always use the autoreboot function
am in the midst of d/l the attachment to try. will keep u updated.

one second,

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

so after applying this update.
it will ensure that, the framework and the hack will be "OFFLINE" when we do file switching?

[NiLuJe]

@nubreader: Okay, but did you ever try to do a proper full restart when you had this issue? (The point being that, for some reason, on fw 3.x, the framework restart done by the autoreboot feature isn't enough... ).

Because, AFAICT, that would be one other way to workaround this, make the autoreboot feature do a full restart when running fw 3.x... . But I'd like to be sure, and no one gave me a clear answer on this yet .

[nubreader]

@NiLuJe

can't remember.. i panicked a little

I'm running 3.0.1. I got it to work with serif but not sans serif. But the fonts looked terrible. I hate Droid and its fonts, and they looked really pathetic on the K3. I tried Segoe UI font. It looked better but it still looked like it wasn't rendering correctly. It looked like a bitmapped font! Worst of all was the blank screens. I decided it isn't worth the hassle so I uninstalled and I'm not going to try it again.

The screensaver hack works great though.

[NiLuJe]

@nubreader: Yeah, I imagine . That's why I went the package way first, it should be completely "scary screen" free .

@jswinden: Yeah, the rendering engine settings are now pretty unforgiving to crappy hinting in fonts... Unless you know how to tweak them and are willing to spend possibly quite a bit of time with trial and error, it's harder to get a 'nice' rendering on the first try. And even then, it's a matter of taste in how you prefer your fonts to look (ie. the endless fuzzy vs. crisp battle ^^).

[nubreader]

@NiLuJe

i received an update not successful U600 error when i try installing the
update_font_pkg_0.N_k3w.bin

[NiLuJe]

@nubreader: Okay, trying new things at 4 AM might not be the best idea for me...

I'll check if I can catch the stupid mistake... ^^

EDIT: Yup, caught it. Stupid mistake, indeed. Will fix that ASAP .

[nubreader]

Originally Posted by NiLuJe

@nubreader: Okay, trying new things at 4 AM might not be the best idea for me...

I'll check if I can catch the stupid mistake... ^^

dun worry mate!
thanks for the help and have a good rest.. for myself, i'm heading for work
in an hour.. so... see u later

[NiLuJe]

Okay, fixed, and I updated the Fontin package in the post on the previous page .

[nubreader]

i have been wondering is it is due to the fonts on
http://charles-reace.com/Kindle_Hacks/fonts/
that is causing the bug.

Originally Posted by NiLuJe

Okay, fixed, and I updated the Fontin package in the post on the previous page .

will try that tonight

[NiLuJe]

Nope, it's not the fonts themselves (at least not in this case ^^).

[nubreader]

Originally Posted by NiLuJe

Nope, it's not the fonts themselves (at least not in this case ^^).

@NiLuJe

is the fonts folder inside /linkfonts/ suppose to contain this much fonts after the initial installation?

if yes, all i need to do is to, replace and overwrite the 12 custom fonts from the downloaded zip and eject+reboot.
that is all there is to see the new fonts right?

*am just double confirming the steps* tho i doubt i am following wrongly


ok, am off to work.. see u tonight

[NiLuJe]

@nubreader: Yep, that's all the default fonts. And there was a bunch of new ones for CJK/I18N support with the K3 .

And yes, you only overwrite our 12 (or 2 or 14 for CJK/I18N, but in your case that doesn't apply) custom fonts .

And then eject, and reboot (And that's where apparently, the autoreboot of the hack isn't enough sometimes on a K3, so, let's say: full restart (either soft (via the Settings menu) if you can, or hard)) .

[gargoyle67]

@NiLuJe, Thanks for your time and effort, Should I uninstall the old font hack before trying the new one on the other page ?

[Tvangeste]

@NiLuJe

I looked into SSHD over Wi-FI not starting automatically, and here are my findings so far:

1. Renaming DISABLED_auto to auto *does* work, in a sense that it starts the scripts automatically.

2. Starting SSHD automatically does *not* work. Well, it works every other restart. Looks like a bug/feature in usbnetwork script, since it simply toggles SSHD status, depending on the pid file (if it present or not). With hard resets, the pid file is being left there, and the script simply tries to turn off the sshd during the startup, once it sees the pid file. And it removes the pid file, so the next restart leads to SSHD started. So, this thing toggles Most probably, usbNetwork script needs to be changed to accomodate auto-starting of SSHD *every* time.

3. Even when SSHD server starts, it is impossible to connect to it via Wi-Fi, since for some unknown to me reason the iptables are *not* updated with proper rule. I see in the logs that "tweaking iptables config" is present, but it doesn't work for some reason (or the rules being changed somewhere later on again).

Manually entering:

iptables -A INPUT -i wlan0 -p tcp --dport ssh -j ACCEPT

makes it possible to connect to SSHD.

This 3rd point needs a bit more investigation on why the iptables are not properly updated. Maybe too early in the boot process?

UPDATE: I verified that iptables call from usbnetwork script does succeed and it does update the iptables rules, but it seems that they are being changed later on somewhere/somehow.

UPDATE #2: I updated /etc/sysconfig/iptables file, added that wlan0 rule there, and now SSHD access is not filtered out anymore. Good! At least, a workaround for now.