eventHandler - easy way to run scripts on boot and screensaver on/off events

[dos1]

I've just created a small package for Kindle Touch and Paperwhite.
(please note that it's untested on Touch, but it should work)

I don't know if anything like that already exists. I just created it for myself and now decided to learn how to package stuff with kindletool

It's a very simple shell script used to run other shell scripts on particular events - boot, suspend or resume. Boot is self-explanatory, suspend is going to screen saver and resume is returning from screen saver.

After installing eventHandler you'll see a scripts directory created in your user partition. It contains three subdirectories - boot, suspend and resume. When event occurs, eventHandler runs all scripts in directory matching given event.

It's simple as that This gives you possibility to run simple scripts without having to install usb networking and other advanced stuff. You'll just need a jailbreak.

Installing is easy: just put install file in root directory of user partition and select "Update your Kindle" from Settings screen. Uninstalling follows the same pattern.

Package contains also few scripts used by me which can be taken as examples:

Spoiler:

screensaver changes behavior of screen saver rotating from ordered to random. Please note that it expects all wallpapers to be named like bg_medium_ss01.png, with leading zero if number is smaller than 10. Should be put under resume directory.
NOTE: Of course it will only work when Special Offers are disabled. If you have SO Kindle, please don't ask how to remove ads. Figure it by yourself or pay Amazon to remove them. Thank you.

wpa-eap can be used to support WPA-EAP WiFi network with client certificate, like one on my university. You'll need to adapt settings to your configuration - passphrase, paths to certificates etc. Should be put under both boot and resume directory.

rss can be used to emulate push-to-Kindle functionality from Amazon, but using your own server. It allows you for instance to synchronize your Kindle with automatically generated RSS feeds from Calibre without duplicated entries, like it happens when using Amazons e-mail pushing. It uses titlebar notifications and checks for timestamp to minimize battery usage on each resume, so it won't synchronize when not needed. Again, you'll need to configure it. It will work without any changes, but you probably don't want to synchronize with my feeds (I left my configuration to allow you checking by yourselves how it should be configured on the server). It stores files in /mnt/us/documents/RSS

Please note that example scripts are only tested on Paperwhite.

NOTE: eventHandler runs all your scripts as root, so be careful with what you include in your scripts! Running "rm -rf /" isn't probably a good idea

If you have Kindle Touch or Kindle Paperwhite, install kindle5 version.
If you have non-touch Kindle 4, install kindle4 version.
Please note that Kindle 4 version is untested!

Enjoy!

[edit]
Updated to 0.11 version which should fix bug reported by stepk and which brings (untested) install files for Kindle 4 (non-touch).

[edit]
Updated to 0.2 version which now works properly with magnetic cover.

[qlob]

It's almost like Kite! (but lacking in the launching scripts from the home screen area...)

Looks fancy though... It would be cool to write this for the K3 or K4 as well.

[stepk]

Thanks for this. Unfortunately install.sh fails on my KT because it assumes that /usr/local exists, while it really doesn't - on my almost untouched KT.

[twobob]

I had an issue in DIAGS where it (booting diags) would clean down my /usr/local

Never not had one. Good point though.

best to do a [ -e ] or z or f or whatever I suppose

YAY CORNER CASES!

[dos1]

Originally Posted by stepk

Thanks for this. Unfortunately install.sh fails on my KT because it assumes that /usr/local exists, while it really doesn't - on my almost untouched KT.

Should be now fixed, could you try again please?

BTW. I've included version for Kindle 4, could someone test if it works? (note that example scripts probably won't work without adjusting)

[stepk]

OK, it's working now, thanks.
How do you generate the server content for the rss feed script? I mean, do you run the calibre client on a debian box and save generated .pobi files to the http server, or do you run calibre as a content server?

[dos1]

Originally Posted by stepk

OK, it's working now, thanks.
How do you generate the server content for the rss feed script? I mean, do you run the calibre client on a debian box and save generated .pobi files to the http server, or do you run calibre as a content server?

I have installed Calibre on my VPS and created cron jobs for updating pobi files in specified directory, which is exported to the world via rsync daemon.

[dos1]

0.2 version is now up - I've fixed a bug which prevented scripts from being launched when using magnetic cover. Enjoy!

[twobob]

ROCK HANDS!!!

[Vava]

Thanks you for this package !
I have an issue with the startup script. I would like to run a web browser (this one https://www.mobileread.com/forums/sho...d.php?t=210210) at startup. The application is well opened but few secondes later the classic menu comes back. When I launch it from the suspend or resume script, it works fine. My first guess was that the browser finished his launching before the Kindle. Did you ever notice this kind of problem ?

[thomass]

Originally Posted by Vava

The application is well opened but few secondes later the classic menu comes back.... My first guess was that the browser finished his launching before the Kindle.

you can try to use a pause function (sleep) on the script.

[Vava]

I did but it seems that the browser begin his launching anyway, then the function sleep hold and at the end the menu shows up. (I place the sleep function before my call to the browser)

[Vava]

Hi ! I would use the event handler to switch from normal mode to standby mode, standby mode to normal mode, etc ... But the script in the folder "suspend" only partially executed and I do not get out of standby mode. Any ideas?

Here are the contents of my scripts.
"resume":

#!/bin/sh

echo >> /mnt/us/scripts/logs.txt

date >> /mnt/us/scripts/logs.txt
echo Kindle awakes >> /mnt/us/scripts/logs.txt

date >> /mnt/us/scripts/logs.txt
# enable WiFi
echo enable WiFi : >> /mnt/us/scripts/logs.txt
lipc-set-prop com.lab126.cmd wirelessEnable 1
lipc-get-prop com.lab126.cmd wirelessEnable >> /mnt/us/scripts/logs.txt
# sleep
echo sleep during 10 secondes >> /mnt/us/scripts/logs.txt
sleep 10

date >> /mnt/us/scripts/logs.txt
# calendar update
echo calendar update >> /mnt/us/scripts/logs.txt
/mnt/us/extensions/WebLaunch/bin/start.sh &

date >> /mnt/us/scripts/logs.txt
# delay nedeed to do the update
echo sleep during 10 secondes >> /mnt/us/scripts/logs.txt
sleep 10

date >> /mnt/us/scripts/logs.txt
# disable WiFi
echo disable WiFi >> /mnt/us/scripts/logs.txt
lipc-set-prop com.lab126.cmd wirelessEnable 0
lipc-get-prop com.lab126.cmd wirelessEnable >> /mnt/us/scripts/logs.txt

# sleep
echo sleep during 1 secondes >> /mnt/us/scripts/logs.txt
sleep 1

date >> /mnt/us/scripts/logs.txt
# go to screenSaver mode (even if the screen doesn't change)
echo go to screenSaver mode >> /mnt/us/scripts/logs.txt
lipc-set-prop com.lab126.powerd powerButton 0

"suspend":

#!/bin/sh

echo >> /mnt/us/scripts/logs.txt

date >> /mnt/us/scripts/logs.txt
echo Kindle falls asleep >> /mnt/us/scripts/logs.txt

date >> /mnt/us/scripts/logs.txt
# EXECUTION STOPS HERE
# synchro each hour
echo Kindle pending awakening (during 1 hour) >> /mnt/us/scripts/logs.txt
# sleep 3600
sleep 10

# awakening
date >> /mnt/us/scripts/logs.txt
# out of screenSaver mode
echo out of screenSaver mode >> /mnt/us/scripts/logs.txt
lipc-set-prop com.lab126.powerd powerButton 0

[knc1]

Short answer: PEBCAK

Longer answer (but not all inclusive):

1) "sleep" is a shell command, not a system command.
It only effects the execution path of the script that contains it.

2) Where / How are these scripts being called?

3) If you do succeed in putting the processor to sleep, then you need a hardware event from some hardware that is still running to wake it.

4) Writing less than a full erase block of data to flash will cause the "short write" to be cached (somewhere, there are several places) in the system or within the flash chip's controller itself.

Shutting down the power to the flash and its internal controller before it completes one of its erase and re-program functions (while the operation is in progress) will at best result in a corrupted, non-recoverable, erase (storage) block in the flash. At worse, a corrupted, non-recoverable internal control structure (then it is unsolder flash chip, solder in a new one time).

You really should try to understand the system and its hardware before trying to take control of it outside of its normal dependence system.

PS: You are in the wrong thread.
This thread is about responding to system events, not about trying to manufacture them.
If you can't find a thread about your subject here, start your own, they are cheap here.

[Vava]

1) Yes, and that's how I want to use it

2) These scripts are called by the eventHandler (that's why I posted a reply instead of create a new thread)

3) Ok, that's what I would like to know. That means there is no chance I succeed to came back from standby mode without an external intervention ?

4) I do not see why it's dangerous. I thought that I was only sending the same command that the system send by pressing the physical button.