Actually PM's are exactly the type of place for that stuff.
But there you go.
Extrapolating from
Quote:
LIPC
LIPC is essentially an inter-process communication tool. Processes can start other apps, send events to them, register listeners for events, etc. Internally, it is (seems to be) built on dbus. There are LIPC bindings for the higher-level layers as well, which for example enables a Webkit application (written in HTML+Javascript) to communicate with a Java service, or a native application, etc. Complex data structures are encoded as JSON.
[edit] Application registry
In fact, LIPC is an essential underpinning of the system. There is an SQLite database located at /var/local/appreg.db containing a lot of information about how the "wiring" is performed. (This DB seems to be the "union" of the files /var/local/reg/ServerConfig.db and /var/local/reg/prereg.db).
Below are excerpts from a dump of it. While not everything is fully understood yet, there are a few "educated guesses" added as comments:
|
and
Quote:
Starting arbitrary applications
lipc-set-prop com.lab126.appmgrd start app://com.lab126.booklet.settings?diagnosticMode=\;411 -- start settings activity. Because of the appended parameter, this goes directly to the 411 diagnostic screen (device info)
|
taken from
here
one could reasonably assume you are looking for an appended ie
command;pageturn , quite possibly obfuscated away somewhere in there.
PS. for the record it it far more polite to say "Dont PM me again" in a PM rather than for all and sundry to see... and the quote is -roughly- from the forum rules if I'm not mistaken (again)
Hope that helps, possibly won't : )