K5 FW 5.x ScreenSavers Hack - Page 88

NiLuJe · 08-31-2014, 03:09 PM

@cbraun: Nope, just KUAL (and MKK, if need be), no need to touch anything else.

cbraun · 08-31-2014, 04:56 PM

Installed the MKK, then KUAL, (all from your latest snapshots). MKK installed correctly (version K5-ALL-install), but when KUAL icon is pressed (version 2.0.azw2 of KUAL in documents folder) , I get an application error "the selected application could not be started. Please try again".

Read the FAQ, but don't seem to find this error.

I did not uninstall the screen saver hack, so the screen saver extension are in the extensions folder (anyway, it does not look as if the app is running yet, so I suspect that I am not at that point anyway).

Sorry if this is already covered in an existing thread, but I cant find it. Thanks for your help anyway!!

eschwartz · 08-31-2014, 06:21 PM

Quote:

Originally Posted by cbraun

Installed the MKK, then KUAL, (all from your latest snapshots). MKK installed correctly (version K5-ALL-install), but when KUAL icon is pressed (version 2.0.azw2 of KUAL in documents folder) , I get an application error "the selected application could not be started. Please try again".

Read the FAQ, but don't seem to find this error.

I did not uninstall the screen saver hack, so the screen saver extension are in the extensions folder (anyway, it does not look as if the app is running yet, so I suspect that I am not at that point anyway).

Sorry if this is already covered in an existing thread, but I cant find it. Thanks for your help anyway!!

That means KUAL crashed. Just try again.

This often happens immediately after the Kindle is restarted.

NiLuJe · 08-31-2014, 06:42 PM

@cbraun:

What @eschwartz said. (Technically, KUAL doesn't crash, but gets killed by the framework: a Kindlet has 2s flat to start, which can be hard on KUAL with cold caches and the device busy in the background. Enabling gawk can help a bit, but it's still tricky right at startup with the device busy.)

cbraun · 08-31-2014, 06:48 PM

Quote:

Originally Posted by eschwartz

That means KUAL crashed. Just try again.

This often happens immediately after the Kindle is restarted.

Thank you eschwartz, trying and trying and trying harder.

Same outcome.

KUAL icon shows new and active. When clicked, changes to "opening" at the same time as the application error is displayed. close the error box and KUAL returns to "active" after a few seconds.

Any other ideas?

cbraun · 08-31-2014, 07:00 PM

Quote:

Originally Posted by NiLuJe

@cbraun:

What @eschwartz said. (Technically, KUAL doesn't crash, but gets killed by the framework: a Kindlet has 2s flat to start, which can be hard on KUAL with cold caches and the device busy in the background. Enabling gawk can help a bit, but it's still tricky right at startup with the device busy.)

Thank you - The error message is displayed nearly immediately after I try to open KUAL, not 2 seconds after. Would that indicate another issue??

NiLuJe · 08-31-2014, 07:14 PM

@cbraun: Argh, right, you downgraded, my bad. Kindlets (all of them, official ones included) are broken on your specific model before FW 5.4.5. You'll have to update to be able to use KUAL.

cbraun · 09-01-2014, 02:45 AM

OK - cool. Yes, I had to downgrade to jailbreak.

I assume that I can now upgrade back to 5.4.5.1, and leave Python, KUAL. MKK and screensaver in place without having to install a bridge first (I dont see one in your snapshots anyway) .

I seem to have read that the bridge is included in your latest JB v0.12 I installed, but I thought I would check with you first.

Thank you

knc1 · 09-01-2014, 05:45 AM

Quote:

Originally Posted by cbraun

- - - -

I seem to have read that the bridge is included in your latest JB v0.12 I installed, but I thought I would check with you first.

Thank you

It is.
It has been for some time, since v1.7 (I assume that v0.12 is a typo).

What you may have read is that MKK will now also be installed and restored.
(if *latest* translates to 08/26/2014 or later.)

For more details, see the: README.txt file in the *.tar.xz snapshot tarball.

@NiLuJe:
You have to rename that file to: "DoNotReadThis_YouWillGoBlind.txt"
or maybe:
"SexOnYourKindle.txt"

Where did I put that link to the Twilight Zone intro?

The *.tar.xz archive contains two *.zip archives -
The **contents** of the *.zip archives are date-time stamped 7 hours **after** the outer *.tar.xz archive was created.

Perhaps nobody stole your laptop recently, it may have just finally fallen through that local time warp.

Have you looked for it in tomorrow yet?
(If you hack'd that time warp a bit, perhaps you could read what you will be typing tomorrow.)

NiLuJe · 09-01-2014, 10:51 AM

@knc1:

. I'll fire up the DeLorean! (Joking aside, the timestamps look fine on my end, but the timestamps of the outer file *might* be tweaked depending on where you are (it's hosted in an OpenStack container supposedly automagically mirrored all around the world, so said mirrors and/or browsers might be doing weird stuff with the timestamps).

@cbraun: As knc1 said, the bridge has been included for a good long while, what's new (in this iteration of the JB, at least), is MKK being bundled with it, and that's only with the last couple of snapshots [which you probably used, since you have a 'new' 4GB device]).

You *will* have to reinstall Python & the ScreenSavers hack after the update though

.

knc1 · 09-01-2014, 12:20 PM

It might be some sort of anti-virus inspector taking apart and putting the archives back together.

I suppose OpenStack doesn't want their system used for virus distribution.

cbraun · 09-01-2014, 06:32 PM

Quote:

Originally Posted by NiLuJe

You *will* have to reinstall Python & the ScreenSavers hack after the update though

.

Thank you - I'm nearly there...

I now have 5.4.5.1 firmware, still JB, KUAL, Python and ScreenSavers hack. Waterstone button enabled...getting your famous NiLuJe screensaver (which I can change although it's quite nice

)

but... neither "cover" nor "last" modes seem to work.

I have auto, beta, cover, mounted_ss and mounted_custom_ss in the linkss folder. (I did wait several minutes in "cover" mode with no success)
Should these work with the Waterstone workaround?

NiLuJe · 09-01-2014, 07:12 PM

@cbraun: Yep, you just need to restart the device for the cover mode to take

.

cbraun · 09-02-2014, 03:18 AM

Quote:

Originally Posted by NiLuJe

@cbraun: Yep, you just need to restart the device for the cover mode to take

.

Restart from Setting, not restart the framework from KUAL of course. I'm all setup now. All I need to do now is to hack the magnets in my cover so that I can occasionally see the screensavers.

knc1, eschwartz, thank you very much for your time and replies.
NiLuJe, of course, this is a lot of amazing work. Thank you again.

Next challenge for me: brick it and get back on the forum.
Do you think I can do this on my own!?

knc1 · 09-02-2014, 11:08 AM

You could put a small "magnetic short" on the inside of the cover -

A soft steel strip from something, just hide and fasten with some tape on inside of cover.
It should not need to be very big, it is a tiny sensor you are blocking.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problem installing Kindle ScreenSavers Hack	ratchetclank	Kindle Developer's Corner	3	12-30-2015 09:59 PM
Is it impossible to hack screensavers in K4 4.1?	nonfactor	Kindle Developer's Corner	1	07-04-2012 07:17 PM
Help! Used screensaver hack- now all collections gone and no screensavers!!!	kuklachica	Amazon Kindle	1	01-16-2011 08:17 PM
Is a hack necessary to add screensavers?	mldavis2	Amazon Kindle	4	10-29-2010 05:34 PM
Hack for screensavers on Kindle 2	KookyKathy	Introduce Yourself	5	01-09-2010 11:16 PM

08-31-2014, 03:09 PM	#1306
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@cbraun: Nope, just KUAL (and MKK, if need be), no need to touch anything else.

08-31-2014, 04:56 PM	#1307
cbraun Junior Member Posts: 8 Karma: 10 Join Date: Aug 2014 Device: PW2	Installed the MKK, then KUAL, (all from your latest snapshots). MKK installed correctly (version K5-ALL-install), but when KUAL icon is pressed (version 2.0.azw2 of KUAL in documents folder) , I get an application error "the selected application could not be started. Please try again". Read the FAQ, but don't seem to find this error. I did not uninstall the screen saver hack, so the screen saver extension are in the extensions folder (anyway, it does not look as if the app is running yet, so I suspect that I am not at that point anyway). Sorry if this is already covered in an existing thread, but I cant find it. Thanks for your help anyway!!

08-31-2014, 06:42 PM	#1309
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@cbraun: What @eschwartz said. (Technically, KUAL doesn't crash, but gets killed by the framework: a Kindlet has 2s flat to start, which can be hard on KUAL with cold caches and the device busy in the background. Enabling gawk can help a bit, but it's still tricky right at startup with the device busy.)

08-31-2014, 07:14 PM	#1312
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@cbraun: Argh, right, you downgraded, my bad. Kindlets (all of them, official ones included) are broken on your specific model before FW 5.4.5. You'll have to update to be able to use KUAL.

09-01-2014, 02:45 AM	#1313
cbraun Junior Member Posts: 8 Karma: 10 Join Date: Aug 2014 Device: PW2	OK - cool. Yes, I had to downgrade to jailbreak. I assume that I can now upgrade back to 5.4.5.1, and leave Python, KUAL. MKK and screensaver in place without having to install a bridge first (I dont see one in your snapshots anyway) . I seem to have read that the bridge is included in your latest JB v0.12 I installed, but I thought I would check with you first. Thank you

09-01-2014, 10:51 AM	#1315
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@knc1: . I'll fire up the DeLorean! (Joking aside, the timestamps look fine on my end, but the timestamps of the outer file might be tweaked depending on where you are (it's hosted in an OpenStack container supposedly automagically mirrored all around the world, so said mirrors and/or browsers might be doing weird stuff with the timestamps). @cbraun: As knc1 said, the bridge has been included for a good long while, what's new (in this iteration of the JB, at least), is MKK being bundled with it, and that's only with the last couple of snapshots [which you probably used, since you have a 'new' 4GB device]). You will have to reinstall Python & the ScreenSavers hack after the update though .

09-01-2014, 12:20 PM	#1316
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	It might be some sort of anti-virus inspector taking apart and putting the archives back together. I suppose OpenStack doesn't want their system used for virus distribution.

09-01-2014, 07:12 PM	#1318
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@cbraun: Yep, you just need to restart the device for the cover mode to take .

09-02-2014, 11:08 AM	#1320
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	You could put a small "magnetic short" on the inside of the cover - A soft steel strip from something, just hide and fasten with some tape on inside of cover. It should not need to be very big, it is a tiny sensor you are blocking.

Advert

Advert