BackDoorLock hack - prevents silent updates

[twobob]

Gah. let me go test that.

[twobob]

I can confirm this is not working. MEH! Why?? I was using this for something else no problems... anyways I can only apologise. for wasted time.

Alternatives:

[root@kindle root]# restart pillow
Works fine as a replacement.

or alternately the more horrid.

[root@kindle root]# lipc-set-prop com.lab126.appmgrd start app://com.lab126.brow
ser 2> /dev/null; usleep 500000; lipc-set-prop com.lab126.appmgrd start app://co
m.lab126.booklet.home 2> /dev/null

also does the job.

my sincere apologies to dsmid. : (
Head-scratching here.

Bad twobob. Bad twobob

[twobob]

maybe the powerd fiddle is the best solution then in the interim. *sad face*

[knc1]

Or just give in to what works - write a text document, forget about eipc calls.

Also, that way you don't "force yourself on the user" - the user can choose to look at the document when, and if, they want to.

(Which is why I am not immediately opening my reports. This status shit isn't important enough to be slapping the user in the face with it.)

[twobob]

heh. or push to one liner via eips 2 38 "thing"

I just feel bad because I ripped that straight out of something from "before" that "worked" without testing it.

Bad twobob *sad face*

[dsmid]

Don't worry twobob, that's what it takes to improve things.
The only one who doesn't do anything wrong is the one who isn't doing anything at all.
I can't even count how many times I did such mistake myself
No harm done.

I went with the "restart pillow" solution. If there's anything wrong with it I'll revert to the powerd fiddle.

[dsmid]

Originally Posted by knc1

Or just give in to what works - write a text document, forget about eipc calls.

Also, that way you don't "force yourself on the user" - the user can choose to look at the document when, and if, they want to.

(Which is why I am not immediately opening my reports. This status shit isn't important enough to be slapping the user in the face with it.)

Hey, I am not forcing anything on the user. Selecting the "Lock state" menu item is completely voluntary. I suppose when user activates "Lock state" he/she actually wants to see the results without unnecessary delay. That's how an interactive interface should work IMHO. After 10 seconds it's gone and no harm to your beloved Kindle done.

In fact there already is (from version 4) an option to save the report to a document. Everything is a matter of opinion and all users don't have the same needs.
For example I find writing the report to a document more intrusive that displaying it on the screen because I have to take an additional action to get rid of it afterwards.
Nevertheless, to satisfy your needs, version 6 has now an option not to display anything on the screen, just drop an empty file noeips to /extensions/backdoorlock/ . Be sure to create /document/backdoorlock folder in that case.

[dsmid]

Version 6

• Problem with the screen refresh after lock state report should be fixed now on KT and KPW.
• Creating an empty file named noeips in folder /extensions/backdoorlock/ will suppress any output to the screen.

[Yolina]

Originally Posted by dsmid

Version 6
Problem with the screen refresh after lock state report should be fixed now on KT and KPW.

Indeed working fine on the PW.

[twobob]

Updated docs to reflect your new work.

https://www.mobileread.com/forums/sho...7&postcount=25

[dsmid]

Can someone with KPW and Back Door Lock installed & active make a simple test for me, please ?
I need you to install/uninstall anything with "Update Your Kindle" and then take a look at update.log if the installation was detected by Back Door Lock.
Look for this message:

Immediate update (i.e. initiated by user), proceeding...

[xtine]

Originally Posted by dsmid

Can someone with KPW and Back Door Lock installed & active make a simple test for me, please ?
I need you to install/uninstall anything with "Update Your Kindle" and then take a look at update.log if the installation was detected by Back Door Lock.
Look for this message:

Immediate update (i.e. initiated by user), proceeding...

I have the backdoorlock installed using the update bundle. I uninstalled the Screensaver hack but didn't get the message you were looking for (I assume it's supposed to pop up as a document?) Just to be sure, I also checked the backdoorlock folder under documents and didn't find anything.

When I re-installed the Screensaver hack, I still got nothing.

Not sure if I'm doing it right though?

[dsmid]

There should be a file named update.log in the backdoorlock folder.
Some information is written to it everytime a KUAL script is executed or an update attempt is detected.
Do you use Back Door Lock within KUAL ?

[xtine]

No, but I could give it a try. Do I need to uninstall the update bundle first?

[dsmid]

Originally Posted by xtine

Do I need to uninstall the update bundle first?

No, you don't.

You can give it a try but I think that if you are not able to find update.log after installing a bundle, then Back Door Lock does not work on KPW at all
/usr/sbin/updatewait is still there but it is not called by the framework anymore... Damn.