[Kindle Touch]Remapping Home Button key?

[acemutha]

Hi Guys,
my Kindle Touch had the power button defective on arrival. I have already JB it and see that running

[root@kindle powerd]# lipc-set-prop com.lab126.powerd wakeUp 1

will work.
However I would like to avoid connecting it to a pc to awake it from sleep mode.
Do you know if it is possible to assign the previous command to the Home Button (the only one working on my Kindle) together with the regular one:

lipc-set-prop com.lab126.appmgrd start app://com.lab126.booklet.home

Playing with lipc I found out that putting kindle on and off from sleep state can also be done repeating twice the same command via:

lipc-set-prop com.lab126.powerd powerButton 0
or 
lipc-set-prop com.lab126.powerd powerButton 1

Thanks in advance.

[dasmoover]

You can write a small script that checks `showlog | tail -n 10` for "lipc-set-prop com.lab126.appmgrd start app://com.lab126.booklet.home" and then execute "lipc-set-prop com.lab126.powerd wakeUp 1" when caught.

[geekmaster]

Originally Posted by dasmoover

You can write a small script that checks `showlog | tail -n 10` for "lipc-set-prop com.lab126.appmgrd start app://com.lab126.booklet.home" and then execute "lipc-set-prop com.lab126.powerd wakeUp 1" when caught.

I only see "booklet.home" events when my touch is awake (not in screensaver mode).

When I press Home while it is awake, I get a pair of events in the log:

lipc_id=com.lab126.booklet.home,state=GO_SENT

followed by:

lipc_id=com.lab126.booklet.home,state=STARTED

I do not find the search string that you suggested anywhere in my logs.

When I press Home while not awake, no new events go into the log.

[ixtab]

Instead of showlog, you could try to run a little background script which monitors udev events. Here's some sample output (pressing the home button, followed by the power button).

[root@kindle root]# udevadm monitor --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [1326350407.129921] change   /devices/platform/whitney-button/input/input3 (input)
UDEV  [1326350412.356096] online   /devices/virtual/misc/yoshibutton (misc)

Update: here's some more verbose log.

Spoiler:

[root@kindle root]# udevadm monitor --property
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1326351109.292268] change /devices/platform/whitney-button/input/input3 (input)
UDEV_LOG=3
ACTION=change
DEVPATH=/devices/platform/whitney-button/input/input3
SUBSYSTEM=input
PRODUCT=19/1/1/100
NAME="whitney-button"
PHYS="whitney-button/input0"
EV==3
KEY==40 0 0 0
MODALIAS=input:b0019v0001p0001e0100-e0,1,kramlsfw
SEQNUM=2575

UDEV [1326351109.293482] change /devices/platform/whitney-button/input/input3 (input)
UDEV_LOG=3
ACTION=change
DEVPATH=/devices/platform/whitney-button/input/input3
SUBSYSTEM=input
PRODUCT=19/1/1/100
NAME="whitney-button"
PHYS="whitney-button/input0"
EV==3
KEY==40 0 0 0
MODALIAS=input:b0019v0001p0001e0100-e0,1,kramlsfw
SEQNUM=2575

KERNEL[1326351125.994871] online /devices/virtual/misc/yoshibutton (misc)
UDEV_LOG=3
ACTION=online
DEVPATH=/devices/virtual/misc/yoshibutton
SUBSYSTEM=misc
DEVNAME=yoshibutton
SEQNUM=2576
MAJOR=10
MINOR=158

UDEV [1326351125.995789] online /devices/virtual/misc/yoshibutton (misc)
UDEV_LOG=3
ACTION=online
DEVPATH=/devices/virtual/misc/yoshibutton
SUBSYSTEM=misc
DEVNAME=yoshibutton
SEQNUM=2576
MAJOR=10
MINOR=158

This could also allow you to check if your power button is really broken, or if there's possibly just some configuration oddity (probably unlikely though). In any case, if I were you, I'd return the device to Amazon for exchange if the power button is broken. Keep in mind that if it doesn't work, you have to be extremely careful not to brick your device, because it's often enough the only button you have left once it is broken. Just saying.

[geekmaster]

Originally Posted by ixtab

Instead of showlog, you could try to run a little background script which monitors udev events.

Like the lipc event monitoring, udev events are only occuring when the kindle is awake.

When not awake, the power button is the only one to generate a udev event, and with that not working, you still need to wake it with usbnet.

[acemutha]

Thank you all for the suggestions. The reason why I decided to to return it is that I am currently in Italy and sending it back is not very convenient.
I will then use usbnet to awake it.

[geekmaster]

Originally Posted by acemutha

Thank you all for the suggestions. The reason why I decided to to return it is that I am currently in Italy and sending it back is not very convenient.
I will then use usbnet to awake it.

If it is a bad button, perhaps you could replace it with a similar switch.