Kindle Menu PREVIEW (for kindle PW)

[Aeris]

I'm working to make a new app launcher for kindle PW (and possibly Touch too, but can't test on it). Just want to share with you a screenshot of the current progress.

What does works: icons in the tray
What does almost work: app launchers. They launch scripts but something goes wrong while exectuing, and launched apps don't show. Hope to fix it soon

This App start in no time, being only a popup window. I'll add other apps and tray icons once I've fixed the critical bug (release must wait). There will be 12 app shortcuts in the first page; maybe other pages will be available too. And a link to the traditional KUAL app launcher for missing ones.
Will be hopefully provided also a script to repleace the store button with Kindle Menu.

Meanwhile, if you have ideas or suggestions feel free to ask!

[Aeris]

Bug details: it seems that from customDialogs don't works all these command that try to "open the screen". Neither the simplest light.sh doesn't work with nativeBridge.setLipcProperty( "com.lab126.system", "sendEvent", "; sh -c 'eips blabla; /usr/bin/light.sh'");

The only working that does "something" on screen is eips..

You can convince yourself by trying these commands:

WORKING COMMANDS:
lipc-set-prop com.lab126.system sendEvent "; sh -c 'eips blabla2'"

/usr/bin/light.sh

NOT WORKING:
lipc-set-prop com.lab126.system sendEvent "; sh -c '/usr/bin/light.sh'"

Scripts that doesn't interact with the screen seems to run well instead.

Hope that somebody could help me to find a workaround for this issue...

[eureka]

Wild guess: maybe your launcher is an "always on top"-like window (in other words, it's placed on top layer defined by window manager configuration file) and light.sh is just hidden under it?

eips works directly with framebuffer ("low-level" stuff), AFAIK, so window manager ("high-level" stuff) rules doesn't apply.

[Aeris]

Yes, I think is an "always on top"-like window, and also forbids to click around under it... but this would only explain the light.sh thing, not why all the other kual apps doesn't show Ah, with lipc-set-prop com.lab126.system sendEvent "; sh -c '/usr/bin/light.sh'" in terminal I was not talking about customDialog, so...

It seems that sh code runs in a particular enviroment that is different from the same commands running in kterm for example

[eureka]

OK, I think, I now understand your problem right:

lipc-set-prop com.lab126.system sendEvent "; sh -c '/usr/bin/xtestlab126 -d'"

doesn't show blank screen for drawing, while

/usr/bin/xtestlab126 -d

does.

Can't help with it, sorry, maybe it's time for searching for other solution.

[silver18]

Take this as a joke...
Try adding a small sleep before running anything that interacts with the screen.
It won't work, but it takes only a moment...

[twobob]

yup thats the one.

Also struggling to think of a solution..

lipc-set-prop com.lab126.system sendEvent "; sh -c ' eips `whoami` '"
does actually print "root"... so maybe its not the user level...

Ah the joy of "unspecified behaviour"

EDIT and...

[root@kindle root]# lipc-set-prop com.lab126.system sendEvent "; sh -c ' sleep 1
; eips `date | tr -d " "` '"

also works. (that sleep is just for you Silver :P)

The pattern appears to be that shells commands cant be invoked.. let me try a big binary direct..

[silver18]

This is the result of missing from the forum for a while...

[twobob]

nope. even shifting a binary to /usr/bin or /usr/sbin
- that requires no ancillary supporting libs doesn't help...

Mystery

[root@kindle root]# ls -al /usr/sbin/eips

-rwxr-xr-x 1 root root 52884 Jun 11 23:15 /usr/sbin/eips

[root@kindle root]# ls -al /usr/sbin/eazykeyboard

-rwxr-xr-x 1 root root 226286 Oct 28 20:00 /usr/sbin/eazykeyboard

look identical... could there be a whitelist???

EDIT: Ah yeah DISPLAY doh... also the eazykeyboard I was testing doesnt even work WITH that fix great :P doh!

[eureka]

This works fine:

lipc-set-prop com.lab126.system sendEvent "; DISPLAY=:0 /usr/bin/xtestlab126 -d &"

So, sh -c part is optional; to pass over blocking call use "&"; xtestlab126 specifically requires DISPLAY to being set. /usr/bin prefix is optional, but it's better to use absolute paths. As Aeris noted, execution environment is a bit different then default.

UPD: and /usr/bin/light.sh just invokes xtestlab126 -l.

[baf]

Aeris, Eureka!
Great discovery!

[Aeris]

YAYYYYYYY IT WORKSSSS! Eureka !!!!!!!!!!

[Aeris]

And it is really useful even while using USBNetwork!!

[twobob]

nice catch!

[eureka]

@Aeris, what user actions lead to showing the launcher? Do you start it from KUAL?