Collections Manager

[eschwartz]

Originally Posted by PW_Owner

Hi eschwartz,

thanks for the link, but I couldn't wait for NiLuJe to test the patch.

I installed it and it looks like it is running. But I can't do a functionality test until I have access to my computer with calibre running....


Andreas

Yep, I didn't notice at first the new version was actually uploaded with the patch. I edited my post, probably while you were reading it.

You can still test the manual functionality while you wait...

[tweak4]

The update appears to work as a standalone for 5.4.3.2, but installing it seems to have broken the screensaver hack. I'll try to reapply it tonight after work, but I figured I'd at least mention that after updating the collection manager, by screensavers have reverted back to stock.

[knc1]

Originally Posted by tweak4

The update appears to work as a standalone for 5.4.3.2, but installing it seems to have broken the screensaver hack. I'll try to reapply it tonight after work, but I figured I'd at least mention that after updating the collection manager, by screensavers have reverted back to stock.

More likely - the update you reported receiving in your last post broke the screensavers (and other of our add-ins) -
A well known result of an OTA update.

Just follow the directions for recovering from an OTA update.
Also, consider installing the "Backdoor Lock" so you can control if/when Amazon destroys your Mobileread additions.

[eschwartz]

Originally Posted by knc1

More likely - the update you reported receiving in your last post broke the screensavers (and other of our add-ins) -
A well known result of an OTA update.

Just follow the directions for recovering from an OTA update.
Also, consider installing the "Backdoor Lock" so you can control if/when Amazon destroys your Mobileread additions.

You mean the update tweak4 got in May?
(It didn't sound like he was referring to an OTA update anyway... although the result does.)

Originally Posted by tweak4

My PW2 updated itself to 5.4.3.2 tonight, so I can also confirm that the collections manager will not work with this version either.

[NiLuJe]

Well, a Kindlet and the ScreenSavers hack are completely and utterly orthogonal, so I sure hope he got an OTA on the way, because that doesn't make any sense otherwise ;p.

[knc1]

Originally Posted by eschwartz

You mean the update tweak4 got in May?
(It didn't sound like he was referring to an OTA update anyway... although the result does.)

Nope - I replied to the wrong post.
The update that PW_Owner got OTA.

[NiLuJe]

Ok, here's a proxy release: 2.7.1

This new version brings support for FW 5.4.3.2 on the PW2, thanks to mhnotnot's contribution. Thanks!

I don't know if 5.4.3 is similar enough to work properly, and I think this doesn't handle 5.4.3.1 correctly, so if you're running one of those versions, please tell us about your experience, a fix might be trivial.

@ixtab & @mhnotnot: right now, the source lives as a bb fork here, and I'll send a PR as soon as everything is done .

EDIT: Done. If something broke, I'm probably solely responsible for it, so, yeah, tell me if something feels wonky .

Originally Posted by NiLuJe

Ok, here's a proxy release: 2.7.1

This new version brings support for FW 5.4.3.2 on the PW2, thanks to mhnotnot's contribution. Thanks!

I don't know if 5.4.3 is similar enough to work properly, and I think this doesn't handle 5.4.3.1 correctly, so if you're running one of those versions, please tell us about your experience, a fix might be trivial.

@ixtab & @mhnotnot: right now, the source lives as a bb fork here, and I'll send a PR as soon as everything is done .

EDIT: Done. If something broke, I'm probably solely responsible for it, so, yeah, tell me if something feels wonky .

What about Kindle Touch 5.3.7.1

[NiLuJe]

@DrPrince: Not supported right now, but supporting it *might* be trivial, provided Amazon wasn't completely evil.

If no-one has bothered to check before then, I'll try to remember that next time I update my Touch.

[NiLuJe]

Okay, I had time to check, and supporting 5.3.7.1 appears to be trivial, so, let's do it .

Do the same for 5.4.3.1, although I did *NOT* test it (unlike 5.3.7.1, which at a quick glance seems to be behaving okay).

[eschwartz]

Originally Posted by NiLuJe

Okay, I had time to check, and supporting 5.3.7.1 appears to be trivial, so, let's do it .

Do the same for 5.4.3.1, although I did *NOT* test it (unlike 5.3.7.1, which at a quick glance seems to be behaving okay).

Soo, time to upgrade then I guess.

Originally Posted by NiLuJe

Okay, I had time to check, and supporting 5.3.7.1 appears to be trivial, so, let's do it .

Do the same for 5.4.3.1, although I did *NOT* test it (unlike 5.3.7.1, which at a quick glance seems to be behaving okay).

Finally it is working... Many Thanks

[mthodmn101]

Got excited when i saw this was finally updated... but still not for my firmware... oh well, the wait continues

[knc1]

Originally Posted by NiLuJe

Okay, I had time to check, and supporting 5.3.7.1 appears to be trivial, so, let's do it .

(Sir) Elton John has a similar observation:

[tweak4]

Originally Posted by knc1

More likely - the update you reported receiving in your last post broke the screensavers (and other of our add-ins) -
A well known result of an OTA update.

Just follow the directions for recovering from an OTA update.
Also, consider installing the "Backdoor Lock" so you can control if/when Amazon destroys your Mobileread additions.

Just to be clear then, the OTA update broke the jailbreak. After updating, I reapplied the jailbreak and the screensaver mod and everything was back to normal.

Then, entirely separately, I updated my version of the collection manager, which re-broke the screensaver mod. However, re-installing the mod worked, and now I have an updated kindle that correctly runs the collections manager and uses my own customized screensaver images.