View Single Post
Old 07-17-2016, 05:43 PM   #21
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
You assume correctly, that that is not what I was trying to figure out.

KindleMenu is still incompatible with the newer firmwares, in the sense that the kindlemenu/bin/shortcut.sh script does not successfully tell pillow to register swipes on the statusbar...
Manually launching kindlemenu/bin/kindlemenu.sh should still cause KindleMenu to appear even without swiping. But that is not nearly as helpful.

...

All I did was register an upstart job to activate the shortcut.

If you can fix the extension, then restart the framework to trigger the upstart job (one-time reboot is easiest) then KindleMenu will officially work on the KOA.

But that will take someone who owns one of the fw5.6.5 devices in question to inspect how pillow interacts on the new firmware.

Since it is just the shortcut that was reported inoperable, the problem probably lies in the lipc call to com.lab126.pillow interrogatePillow
eschwartz is offline   Reply With Quote