I have a perfectly working update_*.bin to install Aeris' menu on my Kindle Touch.
Complete with upstart job to activate it.
And if I use kterm to perform an `initctl restart aeris_menu`, the menu even activates and all.
BUT, the upstart job which I tried starting after lab126_gui, framework, and pillow, is still firing off too soon (before the GUI is available to accept the inserted HTML). So it is basically useless as is.
Does anyone have any idea how I can tell it to run at the right time? Because I cannot figure out what upstart job is associated with the right point in the device's initiation sequence.
Or should I give up and install a crontab to hammer away every minute or two?
...
@
encol,
Kindlets are not firmware or device-specific. All the touchscreen devices use the same KDK 2.
Something like Collections Manager needs to be recompiled with the appropriate firmware-specific libraries, only because it actually uses java classes from the framework and therefore needs firmware-specific adapters to hook into obfuscated and decompiled .jars because Amazon is being evil.
Which is totally different (and is actually a source code update).
Instead, it appears Amazon finally killed off
Kindlet support in the Oasis firmware for good.
