MobileRead Forums
Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner
Reload this Page KOA: Trouble with KUAL

Notices

Reply
 
Thread Tools Search this Thread
Old 11-04-2016, 11:34 AM   #1
ecostin
Enthusiast
ecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role model
 
Posts: 37
Karma: 160968
Join Date: Sep 2010
Location: Germany
Device: PRS-500-505-700, Kindle3, KT, KPW, KPW2, KV, KOA
KOA: Trouble with KUAL
I am probably just doing something wrong but ...

The device is Oasis with FW 5.8.5.0.1, jailbroken, with MRPI, KUAL and some extensions, say usbnet, installed from thread "Snapshots of NiLuJe's hacks". All good.

The problem is that using the extension menus via KUAL does not really work. For example, enabling usbnet + ssh via KUAL does nothing, while using the ;un search bar shortcut works.

Taking for example the USBNetwork menu item "** USBNetwork Status **", clicking it does nothing. Connect via ssh and executing the script manually displays the correct, expected message.

If I edit the menu.json file and remove the ""exitmenu": false," parameter, clicking the menu entry will exit KUAL and display the correct message. This applies to any KUAL extension, but ... it is a bit annoying to exit every time when running a command.

Anybody else facing this issue?

ecos
ecostin is offline   Reply With Quote
Old 11-04-2016, 11:59 AM   #2
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
KOA - you must be writing about the Booklet version of KUAL.
Which requires a re-install after any Amazon update.
Same rule as all update_*.bin packaged add-ins here.

A more general question:
Has everything in update_*.bin packages been re-installed after the most recent Amazon update?
If not, or if not sure - dump them all in /mrpackages and trigger MrPI with the ;log mrpi searchbar command (MrPI can do batch installs).

I am just guessing here, since this is the first report of this behavior, I don't have a KOA to attempt to duplicate your report, and the maintainer is away at school.
(That should be enough disclaimers, I think.)
knc1 is offline   Reply With Quote
Advert
Old 11-04-2016, 12:14 PM   #3
ecostin
Enthusiast
ecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role model
 
Posts: 37
Karma: 160968
Join Date: Sep 2010
Location: Germany
Device: PRS-500-505-700, Kindle3, KT, KPW, KPW2, KV, KOA
Yes, using the booklet version. Did everything from scratch today, went to factory / initial, then jb, then to the latest firmware version. Afterwards all packages were installed cleanly via MRPI. No issues except for the reported one.
ecostin is offline   Reply With Quote
Old 11-04-2016, 01:42 PM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ecostin View Post
Yes, using the booklet version. Did everything from scratch today, went to factory / initial, then jb, then to the latest firmware version. Afterwards all packages were installed cleanly via MRPI. No issues except for the reported one.
NiLuJe has it in one of his public repositories, if any 'java guru' wants to take a look at it.
We can't just diff the classes, because every build has different obfuscation.

It seems strange that something as basic as DCbooklet would change with only a x.x.x.0.1 change of version number, but maybe . . . .
(That is the foundation class of all "Device Control Booklets" - Including the home page.)

My KT3 (also an 8th. gen device) is running 5.8.5 -
I could update it and see if I can duplicate the problem, but NiLuJe will probably graduate before I have time to do that.

So it would be best if someone running 5.8.5.0.1 on an 8th gen device see if they can duplicate the problem described.
Last edited by knc1; 11-04-2016 at 01:46 PM.
knc1 is offline   Reply With Quote
Old 11-04-2016, 02:20 PM   #5
ecostin
Enthusiast
ecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role modelecostin is a good role model
 
Posts: 37
Karma: 160968
Join Date: Sep 2010
Location: Germany
Device: PRS-500-505-700, Kindle3, KT, KPW, KPW2, KV, KOA
There's no hurry with this, after all the reader works fine, just KUAL must exit when using any function
ecostin is offline   Reply With Quote
Advert
Old 11-04-2016, 02:40 PM   #6
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ecostin View Post
There's no hurry with this, after all the reader works fine, just KUAL must exit when using any function
That may be why there hasn't been any reports -
A first time user might not realize that it is not working the way that was intended.

It sounds like its support of 'suicide' kindlets has broken.
knc1 is offline   Reply With Quote
Old 11-04-2016, 05:52 PM   #7
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ecostin View Post
I am probably just doing something wrong but ...

The device is Oasis with FW 5.8.5.0.1, jailbroken, with MRPI, KUAL and some extensions, say usbnet, installed from thread "Snapshots of NiLuJe's hacks". All good.

The problem is that using the extension menus via KUAL does not really work. For example, enabling usbnet + ssh via KUAL does nothing, while using the ;un search bar shortcut works.

Taking for example the USBNetwork menu item "** USBNetwork Status **", clicking it does nothing. Connect via ssh and executing the script manually displays the correct, expected message.

If I edit the menu.json file and remove the ""exitmenu": false," parameter, clicking the menu entry will exit KUAL and display the correct message. This applies to any KUAL extension, but ... it is a bit annoying to exit every time when running a command.

Anybody else facing this issue?

ecos
On KT3, 5.8.5 -
SSHD down: The status message is there but the wrong sized font and placement on screen.
After enable usb network: No status message, SSHD still down (connect a USB cord and you see the USB storage area, which does not happen if SSHD is running)
start kTerm -
ps aux | grep 'ssh'
not found
ps aux | grep 'drop'
not found
It really isn't started, and the command failed.

Checked */extensions/MRInstaller/log - -
There where no problems recorded with the installation of USBNetworking.

long press of power button until the panel pops up (and the light flashes) -
tap 'restart' (A.K.A: reboot)
No change to the above behavior.

The problem was there on generation 8 devices (KT3, KOA) prior to 5.8.5.0.1
Meaning that 5.8.5.0.1 is only the first report, the problem was present on 5.8.5 or earlier.

Somebody with a generation 7 device (KV, KT2, PW3) using KUAL in Booklet form try the same things and report back please.
(The KUAL Booklet will run on ALL touchscreen devices. At least it is suppose to and USBnetworking is suppose to work on all those devices - at least if you install the correct package from the archive.)

= = = =

PW3: 5.6.1.1 - everything works
So check on 5.7.x and 5.8.y someone.

= = = =

First guess: Bit-Rot in the Kindlet launcher (which in this case is actually used as a booklet launcher)
Code:
161104:162620 appmgrd[1259]: I appmgr_registry:app_found_for_uri:lipc_app_id=com.mobileread.ixtab.kindlelauncher,executable=NONE:
161104:162620 appmgrd[1259]: I appmgr_history:NEW_APP:lipcId=com.mobileread.ixtab.kindlelauncher:
161104:162620 cvm[32528]: I BookletManager:StartingBooklet:booklet=com.mobileread.ixtab.kindlelauncher:
161104:162620 appmgrd[1259]: I appmgr_history:app_state_change:lipc_id=com.mobileread.ixtab.kindlelauncher,state=EXECUTED:
161104:162620 cvm[32528]: W def:lipc:method=LipcOpenEx service=com.mobileread.ixtab.kindlelauncher:Method has been deprecated.
161104:162620 cvm[32528]: I LipcSourceImpl:AddSource:src=com.mobileread.ixtab.kindlelauncher:Adding new Lipc source
161104:162620 cvm[32528]: I BookletManager:LoadedBooklet:booklet=com.mobileread.ixtab.kindlelauncher:
161104:162620 cvm[32528]: I lipc:evts:name=running, origin=com.lab126.booklet, fparam=com.mobileread.ixtab.kindlelaun:Event sent
161104:162620 appmgrd[1259]: I appmgr_lipc:set_appmgr_run_result:propName=runresult,buf=0:com.mobileread.ixtab.kindlelauncher:entry
161104:162620 appmgrd[1259]: I appmgr_history:app_state_change:lipc_id=com.mobileread.ixtab.kindlelauncher,state=REGISTERED:
161104:162620 cvm[32528]: I BookletImplementation:LifecycleEvent:stage=load:New Lifecycle event added
161104:162620 appmgrd[1259]: I appmgr_history:app_state_change:lipc_id=com.mobileread.ixtab.kindlelauncher,state=LOAD_SENT:
161104:162620 appmgrd[1259]: I lipc:evts:name=appStateChange, origin=com.lab126.appmgrd, fparam=com.mobileread.ixtab.kindlelaun:Event sent
161104:162620 cvm[32528]: I BookletImplementation:Loading:name=com.mobileread.ixtab.kindlelauncher:
161104:162620 appmgrd[1259]: I appmgr_lipc:set_appmgr_load_result:propName=loadresult,buf=7:0:entry
161104:162620 appmgrd[1259]: I appmgr_history:app_state_change:lipc_id=com.mobileread.ixtab.kindlelauncher,state=LOADED:
161104:162620 appmgrd[1259]: I lipc:evts:name=appStateChange, origin=com.lab126.appmgrd, fparam=com.mobileread.ixtab.kindlelaun:Event sent
161104:162620 cvm[32528]: I BookletImplementation:LifecycleEvent:stage=go:New Lifecycle event added
161104:162620 appmgrd[1259]: I appmgr_history:app_state_change:lipc_id=com.mobileread.ixtab.kindlelauncher,state=GO_SENT:
161104:162620 appmgrd[1259]: I lipc:evts:name=appStateChange, origin=com.lab126.appmgrd, fparam=com.mobileread.ixtab.kindlelaun:Event sent
161104:162620 appmgrd[1259]: I lipc:evts:name=appActivating, origin=com.lab126.appmgrd, fparam=0:Event sent
161104:162620 cvm[32528]: I BookletImplementation:Starting:name=com.mobileread.ixtab.kindlelauncher:
161104:162620 cvm[958]: W def:lipc:method=LipcOpenEx service=com.lab126.cvm:Method has been deprecated.
161104:162620 cvm[958]: E lipc:ds::Duplicate service name (com.lab126.cvm)
161104:162620 cvm[958]: C def:dbusi::Failed to init dbus
161104:162620 cvm[960]: W def:lipc:method=LipcOpenEx service=com.lab126.cvm:Method has been deprecated.
161104:162620 cvm[960]: E lipc:ds::Duplicate service name (com.lab126.cvm)
161104:162620 cvm[960]: C def:dbusi::Failed to init dbus
161104:162620 cvm[962]: W def:lipc:method=LipcOpenEx service=com.lab126.cvm:Method has been deprecated.
161104:162620 cvm[32528]: I BookletImplementation:SetTransientSearchMode::
161104:162620 cvm[962]: E lipc:ds::Duplicate service name (com.lab126.cvm)
161104:162620 cvm[962]: C def:dbusi::Failed to init dbus
161104:162620 cvm[32528]: I KindleFrameFactory:WindowAdded:title=L_A_N_application_ID_com.mobileread.ixtab.kindlelauncher_M_false_PC_T_RC_true:
161104:162620 cvm[963]: W def:lipc:method=LipcOpenEx service=com.lab126.cvm:Method has been deprecated.
161104:162620 cvm[963]: E lipc:ds::Duplicate service name (com.lab126.cvm)
161104:162620 cvm[963]: C def:dbusi::Failed to init dbus
161104:162621 winmgr[31603]: I lipc:evts:name=titleBarVisiblityChange, origin=com.lab126.winmgr, fparam=visible:Event sent
161104:162621 cvm[965]: W def:lipc:method=LipcOpenEx service=com.lab126.cvm:Method has been deprecated.
161104:162621 cvm[965]: E lipc:ds::Duplicate service name (com.lab126.cvm)
161104:162621 cvm[965]: C def:dbusi::Failed to init dbus
161104:162621 cvm[966]: W def:lipc:method=LipcOpenEx service=com.lab126.cvm:Method has been deprecated.
161104:162621 cvm[966]: E lipc:ds::Duplicate service name (com.lab126.cvm)
161104:162621 cvm[966]: C def:dbusi::Failed to init dbus
161104:162621 appmgrd[1259]: I appmgr_lipc:set_appmgr_go_result:propName=goresult,buf=7:0:entry
161104:162621 appmgrd[1259]: I appmgr_history:app_state_change:lipc_id=com.mobileread.ixtab.kindlelauncher,state=STARTED:
161104:162621 appmgrd[1259]: I lipc:evts:name=appStarted, origin=com.lab126.appmgrd, fparam=com.mobileread.ixtab.kindlelaun:Event sent
161104:162621 appmgrd[1259]: I lipc:evts:name=appStateChange, origin=com.lab126.appmgrd, fparam=com.mobileread.ixtab.kindlelaun:Event sent
And that is all the further I know how to go.
PS: To the JAVA Guri that takes this on - "cvm" IS Java SE8 (someone posted here, somewhere, that they wished the Kindles ram Java8 - well, at least on 5.8.5 they are - with hardware execution assist)

- - - - -

And it isn't just us -
Just read all the crashes, warnings, errors, etc. from the Lab126 code attempting to bring up the framework.
It takes 5.8.5 nearly a minute to re-start the framework.
Last edited by knc1; 11-04-2016 at 06:23 PM.
knc1 is offline   Reply With Quote
Reply

« Previous Thread | Next Thread »

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Tools Software Jailbreak for PW2, PW3, PW3W, KT2, KV, KOA and KT3 knc1 Kindle Developer's Corner 3376 05-31-2023 09:43 AM
USB OTG Mouse Support and page turn on PW3(possible KV/KOA) lucida Kindle Developer's Corner 104 01-01-2022 12:21 AM
Help a beginner with KUAL j0el Kindle Developer's Corner 8 11-04-2016 08:43 AM
alsaplayer 0.99.80 (K5 KUAL-V.1.1) twobob Kindle Developer's Corner 37 02-25-2015 07:50 PM
Kual y backdoorlock adegir1952 Amazon Kindle 3 06-14-2013 09:44 AM


All times are GMT -4. The time now is 03:15 AM.

Contact Us - FAQ - Guidelines - Privacy - Top

MobileRead.com is a privately owned, operated and funded community.