View Single Post
Old 07-20-2013, 07:48 AM   #4
aditya3098
Guru
aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.aditya3098 ought to be getting tired of karma fortunes by now.
 
Posts: 608
Karma: 1588610
Join Date: Jan 2012
Device: Kindle Scribe
Quote:
Originally Posted by ixtab View Post
Simple answer: you can't. Not on a K4.

As knc1 pointed out, on the K4, the entire UI lives inside a single jvm instance. A Kindlet doesn't get its own process, but it's simply another class that gets loaded and "brought to the front" - all of this is happening inside the single cvm process.

Note that on the K5, you can do something like /usr/bin/lipc-set-prop com.lab126.appmgrd start app://com.lab126.booklet.kindlet/mnt/us/documents/YourKindlet.azw2 - but not on the K4.
Correction:
/usr/bin/lipc-set-prop com.lab126.appmgrd start file:///mnt/us/documents/YourKindlet.azw2
aditya3098 is offline   Reply With Quote