K5 FW 5.x ScreenSavers Hack

[TaoManJoe]

@NiLuJe - Yes

[NiLuJe]

@TaoManJoe: Hmm, then we'll take a page from Mr Proper's book:

* If you don't have one already, make a backup of your custom screensaver images.
* Delete the linkss folder from your Kindle.
* On the off-chance that something wonky's going on with your jailbreak version, reinstall the latest JailBreak.
* Restart your device.
* Run the latest uninstaller for the ScreenSavers hack.
* Run the latest installer for the ScreenSavers hack.
* And *STOP*. At no point should you try to inject your custom images (yet).

And report what happens then .

[GoSharks]

Delete---listen to NiLuJe

edit: I think I'm going to take a speed typing class! Good morning (for me) NiLuJe!!

[NiLuJe]

@GoSharks: . Although you'll notice that I tend to cheat by posting something, then editing and fleshing it out approximately seven billion times .

[TaoManJoe]

Assuming this is the latest Jailbreak, and assuming this is the latest screensavers hack I have executed the steps you laid out, making sure to always unplug from the USB before restarting or installing/uninstalling.

Now when I turn off my Kindle I get one of the various Kindle supplied screensavers, and after trying multiple power downs I see that I am shuffling through them.

[NiLuJe]

@TaoManJoe: Huh. And I'm assuming this isn't a Special Offers or Waterstones device?

Could you PM me a log dump? (search for ;dm in the Homescreen, and zip up the three txt files that'll generate in the documents folder).

And that's on a PW2 on 5.4.3.2, correct?

[TaoManJoe]

@NiLuJe sorry, just new around here and not sure where everything is. I do appreciate your help very much. I went into the Kindle root (is that the Homescreen?) and searched for ;dm and got nothing. And I don't know what PM is.

Yes it's a PW2 on 5.4.3.2

[NiLuJe]

@TaoManJoe: Sorry, I meant on the device itself, on the Homescreen (the screen with your list of books/covers), pull up the search bar by touching the looking glass icon, and searching for ;dm there. It'll churn for a while (without sending you the usual "Search Result" page), and three new files should pop up. Plug your device, zip up those three files (they're in the documents folder), and either upload them somewhere and send me a link over private message (better, since the logs are very verbose, and you might not want the whole world to have access to those), or just attach them to an answer here.

[TaoManJoe]

thx - done

[NiLuJe]

@TaoManJoe: Okay, the last package I see getting run is the ScreenSavers uninstall, which, for once, is consistent with the behaviour you're describing .

(i.e. I don't see the last two steps of my post #1097).

So, yeah, run *installer* this time, without touching the linkss folder yet.

[TaoManJoe]

Ok. Now when I turn it off I get The Screensavers Hack has been successfully installed! with your name.

[TaoManJoe]

Great! I subbed my screensaver for yours, did a restart, and now it works! Thank you. Is there any clean up I need to do on my Kindle after all that? Appreciate very much!

[NiLuJe]

@TaoManJoe: Nope, everything should be good now .

[GoSharks]

Originally Posted by NiLuJe

@TaoManJoe: Nope, everything should be good now .

Curious.... is your thinking that there was something 'wonky' in the linkss folder and since it doesn't get deleted automatically on an uninstall / reinstall that it kept cropping up? In essence, was the cure the deletion of the linkss folder and a reinstall?

[NiLuJe]

@GoSharks: Yup.

From what I gathered from the logs, the initial culprit seems to have been a snafu in cover mode: cache hit at boot on the last book opened (possibly inaccurate because of date/time issue, hence always the same across reboots), and that cached cover was broken (which, in a perfect world, should never happen with stuff generated by the hack, I can only think of an issue because of a weird/broken source image, or a bug in IM).

The log didn't go that far back, so the fact that I saw mostly cover mode logs might be a complete coincidence .

I'm not sure switching to and fro cover mode would have helped anyway, nothing is ever deleted, so the broken image always has ways to get back in the pool.