K5 FW 5.x ScreenSavers Hack

[Brynwall]

Hey all, I think I found the problem with the images. There were invisible files that matched the image names that stopped working. Once I deleted those the images were working fine.

[knc1]

Originally Posted by Brynwall

Hey all, I think I found the problem with the images. There were invisible files that matched the image names that stopped working. Once I deleted those the images were working fine.

Invisible files on FAT32?

What where you viewing the Kindle's directory with?

[Brynwall]

Originally Posted by knc1

Invisible files on FAT32?

What where you viewing the Kindle's directory with?

I was using my Mac and I have it set to show all hidden files.

[knc1]

Originally Posted by Brynwall

I was using my Mac and I have it set to show all hidden files.

Ah, must be a fluky MacOS vfat driver artifact.

[Brynwall]

Originally Posted by knc1

Ah, must be a fluky MacOS vfat driver artifact.

I'm betting it is more of an El Capitan issue; I've never seen this problem before I upgraded...

[knc1]

Originally Posted by Brynwall

Hey all, I think I found the problem with the images. There were invisible files that matched the image names that stopped working. Once I deleted those the images were working fine.

When I first replied to this post, I was only thinking 'Linux' because:
*) It is what I use everyday
*) I did not think that its vfat driver supported the fat 'hidden' and 'system' attributes.

2) Evidently it does:
https://blogs.gnome.org/diegoe/2012/...s-on-gnulinux/
But you have to have mtools installed to deal with them (at least with very old kernels).

1) Poster is using MacOS X, which is another can of worms:
http://superuser.com/questions/17512...ernal-drive-on

B) - I need a better memory
A) - I should have asked "What OS?" Duh....

= = = =

Since there can be three different types (or sources) of

Hidden Files

...

1) Linux/*nix style :
This is a matter of tradition, files that begin with '.' are normally not shown.
But a file beginning with a '.' and one which does not (and are otherwise the same in case and capitalization) are different filenames - one can't 'hide' the other.

So - not that type of hidden file.

2) MacOS X resource forks -
Following the *nix tradition (which MacOS X is), a file with a resource fork gets its resource fork copied to fat(12, 16, 32) as a distinctively named file.
http://superuser.com/questions/17512...ernal-drive-on

So - not that type of hidden file.

3) DOS/Windows (native fat-12, -16, -32) style :
No tradition needed here, the filesystems have both 'hidden' and 'system' attribute bits.
I.E: they are attribute bits - they are **not** part of the filename.

So - the 'hidden' files in this post must have been this system's idea of 'hidden' (a file attribute).

Only older versions of Linux (which the Kindle was before 5.6.x) requires a special add-in utility to deal with them (I don't know off-hand if the Kindles have that mtools utility installed).

Although I would expect lsattr to show 'system' and 'hidden' attributes on a fat(12, 16, 32) filesystem and chattr should be able to change them.
But their man pages make no mention of how fat(12, 16, 32) are handled.

I'll have to check if that is supported/used in the newer (5.6.x) series firmware (which uses a much newer 3.0.x series kernel).

Hmm....
I seem to recall that long ago, Lab126 built a kernel with selinux support (file system attributes on steriods) but never used them (thank the gods).

Maybe they have done that (again) and this time have the mount options of the fat-32 partition on the Kindle set to respect them.

Drat!
Something else that needs to be checked about the 5.6.x series firmware(s).

[kathees]

Hi,

Just installed the latest version (0.24.N) in my Kindle Touch (4th Gen - Firmware 5.3.7.3) and have some questions. I wanted to use the cover feature so first installed the python followed by the screensaver.

Once the install is done inside the linksys folder I show a empty file named "auto". I never show any file called "autoreboot" the guide talking a lot about. I copied the "auto" file and renamed to "cover" and full restarted the Kindle. Bad, I still see the default screensaver.

So then I delete the "cover" file and copy some images and restarted the kindle again. Wow, now I can see my custom screensavers.

1) Is it necessary to always have the "auto" file in-order for this hack to work?
Yes, it enables the hack

2) Where is the "autoreboot" file guide mentions a lot about? Or you meant the "auto" file?
I think in new versions not installed by default. Need to create the file ourself

3) AutoReboot feature doesn't seem to work even if I put another file called "reboot". I put it along with the default "auto" file. But my images didn't really appear even after disconnect the Kindle and wait a minute. But when I restart the kindle using "Settings->Restart" they do appear....

May be I should delete the "auto" file and just have a simple file called "reboot"?
Didn't work because I didn't had the "autoreboot" file. Both files are required

4) For "random" and "shuffle" guide explicitly say we need to put them along the "auto" file. So let's say I don't want both and just require my screenshots to appear in the order? Can I delete that "auto" file?
No, file "auto" always required. If we only have this file screensavers will cycle in the default order

5) To use "cover"/"last" should I delete the "auto" file and just keep a single file?
No, as mentioned above "auto" file always required. Not sure why I saw the default screensavers before. Now I can see the cover nicely

Thanks for the great work and sharing with us.

[eschwartz]

The easiest way of keeping straight which files need to be there, is to install KUAL (Kindle Unified Application Launcher) and use the KUAL extension installed with the screensavers hack.

[kathees]

Originally Posted by eschwartz

The easiest way of keeping straight which files need to be there, is to install KUAL (Kindle Unified Application Launcher) and use the KUAL extension installed with the screensavers hack.

Hi,

Thanks for the suggestion. I just installed Kula and tried the various options. Managed to find the answers to my question.

Just reporting my findings in case anyone needs as reference. The usage of files are as below.

1) auto - Must have. This is the one enabled the hack
2) autoreboot - Enables the auto reboot feature. But does not trigger the reboot yet
3) reboot - Must put this along with autoreboot for a framework restart to be happened next time you unplug the Kindle
4)cover/last/random/shuffle - These files and other new files for the options like personal info works as intended. But all of these must have the "auto" file along with them.

Hope it helps anyone who get confused about the files as did.
Again, thanks a lot for the great work. Now I'm enjoying my own photos..

[abheybir]

Under FAQ it is mentioned that " On FW >= 5.6.5, be aware that we currently cannot process KFX books". Does it mean it normally works on 5.6.5???

But i guess no jailbreak is still available for the same, how can it be installed over firmware 5.6.5???

[knc1]

Originally Posted by abheybir

Under FAQ it is mentioned that " On FW >= 5.6.5, be aware that we currently cannot process KFX books". Does it mean it normally works on 5.6.5???

But i guess no jailbreak is still available for the same, how can it be installed over firmware 5.6.5???

No, there is an equals sign in the statement.

There is a jailbreak available, the serial port jailbreak.

[NiLuJe]

@abheybir: As @knc1 said, -gte (greater than or equal). Besides, the KFX thing is fixed in current snapshots anyway .

[lresende]

aadsf

[eschwartz]

Use the hotfix linked in the Jailbreak thread, then use the latest version of KUAL + MrPI (MobileRead package Installer).

[knc1]

Originally Posted by eschwartz

Use the hotfix linked in the Jailbreak thread, then use the latest version of KUAL + MrPI (MobileRead package Installer).

We need a rubber stamp for that one.
It is getting to be almost like the: "Recharge the battery" answer once was.

Hmm...
FGA #11