[App]K3MusicManager

[digory]

Originally Posted by Kuja

*snip*
Of course the next step was having a look into "/var/local/java/keystore/" and voila, the whole content changed. There's no longer a developer.keystore, but instead "developer-application.keystore" and "application.keystore" (the new content of the folder "/var/local/java/keystore/" and the message in .azw format are attached to this post
*snip*

My Kindle Touch came with an application.keystore and a developer-application.keystore from shipping, although Firmware version is still 5.1.0. I wonder if that's the reason why I can't seem to get any Java application to work. Anybody figured out how to use these keystores?

[spl0it]

Originally Posted by digory

My Kindle Touch came with an application.keystore and a developer-application.keystore from shipping, although Firmware version is still 5.1.0. I wonder if that's the reason why I can't seem to get any Java application to work. Anybody figured out how to use these keystores?

Now it seems to that every time i connect to the interet (through wifi, I've got no 3G) the developer.keystore is deleted.
Probably removing autoupdating feature would help, as it's clearly the fault.

[knc1]

Originally Posted by spl0it

Now it seems to that every time i connect to the interet (through wifi, I've got no 3G) the developer.keystore is deleted.
Probably removing autoupdating feature would help, as it's clearly the fault.

There does seem to be the idea floating around Amazon that these machines still belong to them, even after they have sold it to someone else.

If (when) I buy a printed on paper book, I don't expect the publisher to come around and rip out pages while I am reading it, it is MINE!

[geekmaster]

Originally Posted by Kuja

At first: thank you for beeing the first one, who gives feedback
(until now the forum looked a bit dead to me )

I bumped your karma to 2600 as soon as I noticed this thread (and I check new threads several times per day). 2600 karma is an award for sharing things that add value to the kindle. It is also a famous "hacker number" that predates personal computers (and laid the foundation for apple computer).

[cyclops0000]

can someone pleeeaaaasssee release this for KT?

[chovan]

Originally Posted by Kuja

K3MusicManager - A GUI for MPlayer [Version 2.3]

(- Install kaffeine, because sleep mode causes mplayer to stop after a few seconds)

Don't think you need to use kaffeine just for this reason. Modify following codes in control.sh file in mplayer should do the work. And the screen save would be re-activated after you exit mplayer.

loadplaylist() {
if ! cmd “loadlist $1″; then
## $MPLAYER -loop 0 -playlist $1 &
( lipc-set-prop com.lab126.powerd preventScreenSaver 1; $MPLAYER -loop 0 -playlist $1; lipc-set-prop com.lab126.powerd preventScreenSaver 0 ) &
fi
}

[Chrishnaw]

Originally Posted by Kuja

K3MusicManager - A GUI for MPlayer [Version 2.3]

A normal Amazon-KDK-Kindlet isn't allowed to access the whole file system or even execute files so you need to grant special permissions:
- SSH into your Kindle and edit the file /opt/amazon/ebook/security/external.policy
- Add the following 4 lines to the block called 'grant signedBy "Kindlet" {' (this should be somewhere at the top)

Sorry to be a complete noob, but how on earth does one exactly "SSH into a Kindle"?

[knc1]

Originally Posted by Chrishnaw

Sorry to be a complete noob, but how on earth does one exactly "SSH into a Kindle"?

The SSH (Secure SHell) server (a service) is part of the USBnetworking package.

A SSH client is a part of both Linux and Mac installations.
On Windows (of course not included) the most often used client is PuTTY.

Follow the directions with the USBnetworking package to set up your Kindle.

Using an ssh client - lots of information about that on the 'net - including a long series of threads at this site. (set the index prefix filter to 'tutorial')

[mrstorey]

Hi Kuja and mods,

I hope it’s okay to ask this here.

I’ve recently got K3MusicManager 2.3 working on a jailbroken Kindle 3 / Kindle Keyboard. The original application itself hasn’t been changed: I’ve only re-signed and repackaged it so that it runs in my current setup.

I’m wondering whether it would be okay to share that re-signed package here for other people with old Kindles who might still find it useful.

To be clear, it wouldn’t be presented as a new version or an improved fork. It would be described as:

- the original K3MusicManager 2.3;
- re-signed and repackaged;
- no changes to the Java code or application features;
- tested on one jailbroken Kindle 3 / Kindle Keyboard;
- not exhaustively tested on other models or firmware versions.

I would include a short README explaining exactly what the package is, how it differs from the original release, what was tested, and the possible risks. I would also link back to this thread and give full credit to the original author.

I would not include any private signing key, keystore, password, personal files, device serial number, or identifying information.

Before uploading anything, Kuja - are you happy for this re-signed/repackaged binary to be shared? And could a moderator advise whether that would be acceptable under the forum rules, particularly since I couldn’t find a clear redistribution licence in the original documentation?

If redistribution isn’t appropriate, I’m happy to leave the binary private and share only the technical information about how I got it working.

Thanks for creating the app in the first place—it’s great to see it still working on an old Kindle.