KUAL: Kindle Unified Application Launcher (v2.7)

[knc1]

Originally Posted by nasser

Installed v2.1..

Now.. where do i get to see a changelog..?

In addition to the above, see NiLuJe's most recent USBnetworking package - it uses the new menu features (you may have to read his *.json file to see the how the field names are used).

[NiLuJe]

@twobob: There's an up to date detailed Changelog in the resource folder in the sources . [can't figure out how to link to a file @HEAD and not a specific commit via bitbucket, so, err, here, but at HEAD]

And as knc1 said, check out stepk's examples (linked in the what's new wiki page, which also describes those changes in details), or any of my hacks, most of them make extensive use of the new parser features . (The cake goes to the K5 Fonts hack, with a completely dynamic menu built on demand at runtime).

[ixtab]

@NiLuJe: https://bitbucket.org/ixtab/kindlela....txt?at=master

[NiLuJe]

@ixtab: Ha! Thanks .

[knc1]

For anyone who hasn't been following closely here:

nasser has been writing buttons for useful things found that are lacking buttons.

Whoot! A new volunteer button author. Taking on a chore that needs doing.

[twobob]

Originally Posted by ixtab

@NiLuJe: https://bitbucket.org/ixtab/kindlela....txt?at=master

thanks I'll link that in the top post.

[GoSharks]

Okay, there REALLY needs to be some fanfare for this roll-out!

Thanks just doesn't quite say it!!

(question... The new azw2 file is still named KindleLauncher-2.0.azw2....should it be KindleLauncher-2.1.azw2?)

Welcome back twobob!

[ixtab]

Yeah, the naming of the file may be somewhat confusing if you don't know where it stems from. The "1.0" and "2.0" refer to the Kindlet specification version that the Kindle must be running, not to the KUAL version. The old and new devices use different and utterly incompatible Kindlet versions - that's also the reason why there are two different .azw2 files.

[stepk]

Re what's new in 2.1, I think I committed "menu collation" between 2.0 and 2.1, so that counts as a new feature, too. Menu collation, unless disabled in KUAL.cfg, groups separate json menus that share the same top menu name under - you guessed it - that top menu name. In adding this feature I thought we could define a common top menu structure, i.e., System, Network, Games, etc. and button developers could graft their buttons under the most pertinent entry, for instance, the firewall button under Network, etc. Sort of like the linux system menu categories. That's just and idea. I used menu collation to add extra KUAL features under the KUAL menu entry, things like setting sorting modes, replacing the store button on KT, and more.

The button package is attached to this post. Unzip it in /mnt/us on your kindle. You only need the KUAL-add-ons folder. See also this other post.

PSA: All downloads have been moved to the Snapshots thread!

[GoSharks]

Originally Posted by ixtab

Yeah, the naming of the file may be somewhat confusing if you don't know where it stems from. The "1.0" and "2.0" refer to the Kindlet specification version that the Kindle must be running, not to the KUAL version. The old and new devices use different and utterly incompatible Kindlet versions - that's also the reason why there are two different .azw2 files.

Thanks for the clarification...I absolutely have no idea where any of this 'stems' from , but I'm sure glad all of you do!

[stepk]

The release archives include an old KUAL.cfg file. Here's a link to the latest one
https://bitbucket.org/ixtab/kindlela....cfg?at=master
When you upgrade from an earlier version to 2.1 check if /mnt/us/extensions/KUAL.cfg exists and if it does you may want to amend it with the new KUAL.cfg in the above link. No action is necessary if /mnt/us/extensions/KUAL.cfg isn't there.
Twobob, you may want to replace the file in the release archives.

[NiLuJe]

@stepk: Ooh, speaking of, I *think* you link to your fork, which is a private repo, so the source tree isn't actually accessible .

[stepk]

Originally Posted by NiLuJe

@stepk: Ooh, speaking of, I *think* you link to your fork, which is a private repo, so the source tree isn't actually accessible .

thanks NiLuJe. I attached the archive to my message.

[fradeve]

Hi guys,
sorry for boring you with these problems and thanks to devs and community for bringing us this great piece of software.

I'm trying to install KUAL 2.1 on Kindle Touch 5.3.2.1 jailbreaked using the latest Kubrick yesterday.

Installing the KindleLauncher-2.0.azw2 in "documents" folder gives me error about "test device", so I tried to install prerequisites, following these steps:

1 - Helpers

I've placed the "helper" dir under FAT-ROOT/extensions/helper

2 - First method
Just tried regular prerequisites, installing them one at a time; tried the following couples:

update_k4_ALL_devcerts_install.bin
update_k4_ALL_kindlet_jailbreak_install.bin

update_k5_ALL_PW_ALL_devcerts_install.bin
update_k5_ALL_PW_ALL_kindlet_jailbreak_install.bin

Every time, even inverting the order of bin installs, it complains me with "UPDATE ERROR: 3".

3 - Second method

So, I've tried the alternative comprehensive bins, from here:

https://www.mobileread.com/forums/sho...67&postcount=2

Tried to install:

update_kindlet-dev-20130710-k4-ALL_install.bin
update_kindlet-dev-20130710-k5-ALL_install.bin

But it gives me the same error as above.

Notes

• I have full SSH over USB and WiFi access
  
• I move bins in Kindle using SSH over WiFi, because even when moving them in FAT-ROOT using USB, the "Update software" in menu doesn't seem to be active (so using WiFi is easier); I install them simply rebooting the Kindle.

Any hint?

[ixtab]

Install prerequisites one at a time. Install them by choosing "Update Your Kindle" from the Settings menu, NOT "Restart". You can try a thousand times - "Restart" will NEVER work to install these update packages.

If you copy the files via SSH, "Update Your Kindle" will remain grayed out though. See here for a solution.

PS: You could have easily found this out yourself by searching this forum (or google) for "update error 003" or similar. It has been explained dozens of times.