K5 FW 5.x ScreenSavers Hack

[NiLuJe]

@digital_carver: There should be a "Not enough space left on device" visible in the MRI log, though . But good point nonetheless, I updated the docs .

@koudou: You *definitely* should see the name and progress of each and every package installed through MRI. The ScreenSavers install just happen to be pretty fast on a PW2, so it's easy to miss if you're looking away .

A for the rest, I definitely didn't get your "switch off/backlight/switch on/restart" thing, so that might need some more details (feel free to PM me in French if you prefer).

At a quick glance, I don't see anything in 5.6.2.x that would mess things up, so you might want to try to:
* Uninstall the ScreenSavers hack
* Manually remove the linkss folder
* Install the ScreenSavers hack

*Without* trying to set it up of put any of your own images in at this point.

If you still see the default screensavers after that, PM me the system logs (search for ;dm in the Homescreen's search bar, and send me the system logs that'll dump in documents).

[Ruskie_it]

Originally Posted by koudou

@eschwartz

I reinstalled python.
In fact, when I put several packages in MR, it gives on the bottom screen message only the name of the first package and never give the names of other packages. It looks like there are installed either (as there is nothing left in MR folder), etc ...

But security, I reinstalled python, and still same behavior.

As you suggested, I waited 5 minutes after restart (in fact 15 mn). But still the error the first time I launch KUAL. Then, the second time, it's ok.

==============
It is a never ending search to get things working while new versions of system appears. Amazon is not fair with customers : there are helpful things for clients they do not develop (time, money ?), like customisation of screensavers, battery status, ...
The reaction of Amazon is to try to forbid these tiny things by investing ressources to not allow these modifications. They should better put these ressources to integrate the modifications to their system.

Because if I had the screensaver, battery status and some little adjustments by Amazon, I never Jailbreaked my kindle, and just used the options of the basic software.

I bought a kindle at full price to Amazon. And I just need some normal functions they did not put in it. And I do not understand why Amazon, not only do not give it to me, but more, is trying to forbid other to give it to me.

Michel

The error with first launch of kual is expected. Didn't matter how long you wait before launching it the first time, doesn't matter what you do after the restart of the device and the first launch of kual (well, almost, but nothing related to the high level usage), the first time it will ALWAYS fail. It is expected. It related to cache loading, but niluje could explain this better. Simple version is just that: it is expected and you have to live with it, there's nothing wrong in this behaviour.

[NiLuJe]

If you use gawk and have a relatively light extensions folder (and/or are using a PW2/KT2/KV), it might *NOT* crash, but, yeah, roughly expected because of the time constraints enforced upon us by the Kindlet framework and the cost of bootstrapping everything on cold caches.

[koudou]

@Ruskie_it

Thank you for the information about the error that is not an error. Error messages are always unbalancing.

@KiLuJe

I am puzzled : I didn't noticed that you were living in Paris and that you are probably French !!!

I followed your advice and it worked :

- uninstall (I used the unistall.bin of the hack package)
- delete linkss folder
- install back the hack (I used MR)
- unplug the device (if not, we are back with the default screensavers)
- restart

Thank you to everybody for your efficient help


Michel

[knc1]

Originally Posted by koudou

@KiLuJe

I am puzzled : I didn't noticed that you were living in Paris and that you are probably French !!!

Yup, he is just faking this English stuff (and doing a very good job of it, languages are part of his 'day job').

Originally Posted by koudou

I followed your advice and it worked :

- unplug the device (if not, we are back with the default screensavers)

That was the key step, but there have been so many comments posted about unplugging the device that nobody bothered to mention it again.

[NiLuJe]

@koudou/@knc1: Yup, I keep my beret, my baguette and my glass of red in the back ^^.

Yeah, the 'unplug' thing finally made its way to the first post in multiple places, so we do tend to forget about it once again .

Nice to have a confirmation that all is well on 5.6.2.1 though .

[eschwartz]

And randomly back to KUAL again...

I restart surprisingly often, basically because I use skipstone heavily until it crashes and brings down the framework. So I also restart KUAL from a cold cache surprisingly often.

KT here, with gawk and 3.5 pages of KUAL entries plus submenus. KUAL usually crashes first time, but every once in a while I don't load KUAL for a minute or two, and it starts smoothly.

[NiLuJe]

Yep, waiting for the initial load at framework startup to die down helps, too .

[Barty]

I finally have a reason to update my jb'ed PW2. (I'm still on 5.4.3.2) The new paper white software improves on text layout, giving you more text on screen and less empty space. See

https://youtu.be/b01XPj1zHVI

Assuming this makes its way down to the PW2, can I be hopeful that future update will leave my jailbreak intact?

[eschwartz]

No guarantees. But the jailbreak usually survives an update, since it is "bridged" in /var/local which firmware updates don't overwrite.

Amazon could theoretically include code in the next firmware update which deletes the bridge file for the express purpose of destroying the jailbreak.
Whether that will happen? Remains to be seen. They haven't yet, so probably not.

[knc1]

Originally Posted by Barty

I finally have a reason to update my jb'ed PW2. (I'm still on 5.4.3.2) The new paper white software improves on text layout, giving you more text on screen and less empty space. See

https://youtu.be/b01XPj1zHVI

Assuming this makes its way down to the PW2, can I be hopeful that future update will leave my jailbreak intact?

No need to wait, install KOreader now.
That will give you better display usage right now, on everything except DRM'd books.

- - - -

@eschwartz :
They had better not, at least in the USA, the contents of /var/local belong to the user and for Amazon (or any other hacker) to change that computer information that belongs to someone else would be a criminal act.

I am watching for just such mistake by Amazon, rough draft of complaint in-hand.

[eschwartz]

In what way is /var/local ours? I understand that is where a lot of our data is kept (e.g. the Content Catalog) but does that really mean we have the right to any file there, even the stuff which "shouldn't" ever be there? Because we also placed the /usr/bin/ symlinks for python/linkss/other, and those get wiped already.

Besides for the school of thought that says the device is ours and therefore it's all ours.

[knc1]

The **content** of /var/local is "ours" under the same reasoning that content of /mnt/us is "ours".

User/usage specific configuration data locally generated by and for the benefit of the owner. Legally, "private computer system data".

Linking to something other than our own data (in USA, data and computer executables are different thingies) is probably not covered by the protections given "private data".

Durn...
I sure do wish I owned a law firm or two with time on their hands.

I know the other "its ours because its ours" can also be done, I had a tiny part in breaking up the telephone monopoly in the USA.
It only takes cubic money for the legal process costs.

[theodo]

hi
on a paperwhite I was not "maintaining" for some time (B024; FW 5.3.8.1) I have realized that the Screensaver hack is not working...
I have updated the jailbreak (from Snapshots) and kindlet, so the Collection Manager is working but python and linkss are not updateable /grayed out...in the linkss folder I see the readme showing it is Version 0.7.....(I don't have the uninstaller) for the py I'm not sure ...should be also around 2013 (Version 2.7)....how can I rectify this?
Thanks a lot

[eschwartz]

If it stopped working, did you get an over-the-air update?