KUAL: Kindle Unified Application Launcher (v2.7)

[NiLuJe]

Updated the first post to (hopefully), make it slightly less useless for people with a KOA2 and/or running FW 5.9.x.

@coplate/@knc1: Ping me if anything seems off, I've probably mucked up something .

[Ruskie_it]

Originally Posted by NiLuJe

Updated the first post to (hopefully), make it slightly less useless for people with a KOA2 and/or running FW 5.9.x.

@coplate/@knc1: Ping me if anything seems off, I've probably mucked up something .

Just to add my story in case you're interested.
- I have firmware 5.9.5.1 on a PW3 (previously jailbroken). With the old fw (5.8.something) everything worked fine.
- Before upgrading, I applied latest Jb (downloaded approximately 16 hours ago, 8am CET). Beware non "hotifx" version, the "pure" jailbreak.
- Updated fw, the jailbreak survived: I put all the plugin I use in mrpi and used the ;log mrpi command.
- Everything re-applied successfully, the SS worked ok, etc. etc.
- But the KUAL booklet didn't work (the usual error). No restart or anything workd
- Then I downloaded 15 minutes ago the jb again and used ;log mrpi to apply the hotfix_jb. Application successful, I restarted, everything ok but still KUAL did not work
- Then I re-downloaded 10 minutes ago the KUAL archive again and used ;log mrpi to install KUAL once more - this time the version you uploaded a few time ago
- Applied the update file and voilà: KUAL runs again

[Antinoos]

Originally Posted by Ruskie_it

- But the KUAL booklet didn't work (the using ok but still KUAL did not work
- Then I re-downloaded 10 minutes ago the KUAL archive again and used ;log mrpi to install KUAL once more - this time the version you uploaded a few time ago
- Applied the update file and voilà: KUAL runs again

That's just the standard way if using an updated KUAL and/or MRPI package.

In such cases, I'm deleting the content in /extensions/MRInstaller completely first, then repalce it with the newly distributed version from scratch. (The difference: in /extensions/MRInstaller/data reside the bin tools for the three main generations of supported devices in their archived raw version - the respective /bin/ and /lib/ subdirs are empty at first.) Entering ";log mrpi" does the magic of installing the updated MRPI binaries first: Now the /extensions/MRInstaller/data/ subdir is empty, but in .../bin/<Kindletype> and .../lib/<Kindletype> you will find the updated binaries.

The next step is a clean install of (updated) KUAL through this updated MRPI; also using the ";log mrpi" search bar command. Then KUAL will run smooth.

That was easy...

[Ruskie_it]

Originally Posted by Antinoos

That's just the standard way if using an updated KUAL and/or MRPI package.

Yep, I know, I was just reporting that the very latest build is okay (on PW3) while the previous (dated a few hours before if I'm not wrong) wasn't.

[NiLuJe]

@Ruskie_it: There's been no significant change to KUAL (or its packaging process) since the v2.7.3 snapshot (that one included). All changes up to 2.7.11 are documentation updates.

The 'old' one is 2.7/2.7.2.

@Antinoos: You don't need to clear the MRPI folder, the layout has never changed, and never will, and the binaries get updated no matter what .

(Yes, that's unlike gawk, where you do need to manually delete the currently installed binary for the install button to actually show).

[unouno]

My device is a jailbroken KT3 and recently updated to FW 5.9.5.1, where JB survives and screen-saver hack was successfully re-installed, however, KUAL is not.

Installation itself seems to be successful (logfile attached), but when I tapped KUAL in the library, only blank screen appeared and nothing more happened, allowing me only to reboot the device.

In "document" folder of the device is there a file named "KUAL.kual" which has no contents (file size is 0kb).

Does someone have any suggestion?

[coplate]

Originally Posted by unouno

My device is a jailbroken KT3 and recently updated to FW 5.9.5.1, where JB survives and screen-saver hack was successfully re-installed, however, KUAL is not.

Installation itself seems to be successful (logfile attached), but when I tapped KUAL in the library, only blank screen appeared and nothing more happened, allowing me only to reboot the device.

In "document" folder of the device is there a file named "KUAL.kual" which has no contents (file size is 0kb).

Does someone have any suggestion?

Its pretty much a known issue, I'm not working on the fix anymore, because I got back into some other hobbies, but here was my attempt at fixing it - it works, but it's not pretty.


https://www.mobileread.com/forums/sh...d.php?t=294765

[unouno]

Originally Posted by coplate

Its pretty much a known issue, I'm not working on the fix anymore, because I got back into some other hobbies, but here was my attempt at fixing it - it works, but it's not pretty.


https://www.mobileread.com/forums/sh...d.php?t=294765

It works! Thank you!

[NiLuJe]

@unouno: You'll notice that this very issue is specifically covered in the first post... Just sayin'...

[unouno]

Originally Posted by NiLuJe

@unouno: You'll notice that this very issue is specifically covered in the first post... Just sayin'...

@NiLuJe Thank you! I'm ashamed that I've failed to find that.

[pewpawpew]

hey I didn't use my pw3 for some time and now I realized that my kual had stopped working. I got it working again by installing it with mrpi but I still have the old kual document in my library that I just can't seem to get rid of.. deleting it on my pc doesn't work and I can't long press it either - any ideas what i could try?

[knc1]

Try reading the guidelines about not double posting.

[pewpawpew]

Originally Posted by knc1

Try reading the guidelines about not double posting.

no need to be so negative about it - I just figured not everybody is gonna look inside this thread so I decided to make a thread describing my issue

[NiLuJe]

@pewpawpew: You figured wrong .

We have a notification system in place, and any thread where I'm the main maintainer means I get an email as soon as a new message shows up.

[pewpawpew]

Originally Posted by NiLuJe

@pewpawpew: You figured wrong .

We have a notification system in place, and any thread where I'm the main maintainer means I get an email as soon as a new message shows up.

well I did think that the creators/maintainers or whatever will see it either way but the rest of the community might not and perhaps some user found a way to get rid of it ^^