Mod Version Of ClockWorkMod Recovery for Racer

[Guest t0mm13b]

Almost.... hmmmm.... wonder what's that about - why jumping twice....

Thinking aloud here.... ignore me :P

This is what's its doing....

• KEY_POWER press event injected
  
• KEY_POWER release event injected
  
• KEY_POWER syn event injected
  

into /dev/input/event3.

For every key used, a press and a release is sent, then a syn, to indicate that the keystroke is finished....

Wonder is it because of too many events injected that causes the darn thing to jump....

Need to google on this one.... as /dev/input/event3 is more trickier than I bargained....

[Guest t0mm13b]

Okie....

It seems that the default code for the KEY_POWER as per default Linux-wide is 116

#define KEY_POWER               116     /* SC System Power Down */

But... In Linux/Android land, in the context of the Racer, that code has been re-defined! As per post#113, the screenshot of the evtest for /dev/input/event3, the code for power key, is 142 which is shown, and somewhat, it appears to be correct and disagrees with what I have been using.... In other words, I was using 116 for KEY_POWER, 142 is what I think should be using... There is debugging information activated in place for the purpose of debugging it... To obtain the log do this:

adb pull /tmp/recovery.log ./recovery_log.txt

Can you

1. Press all the icon keys and report back as usual
   
2. Enclose the contents of recovery_log.txt to see what's going on...
   
3. And finally give this a spin.... :D
   

Let me know how you get on? :)

Cheers,

B)

recovery_powerkey_event3_debug.zip

[Guest Racerboy]

before installing latest recovery

recovery_log.txt

recovery_powerkey_event3_debug

recovery_log.txt

Edited September 24, 2011 by Racerboy

[Guest Racerboy]

recovery_powerkey_event3_debug

• Icon with Plus on it - (for Select to go down a sub-level) - Work? not working
• Icon with Up arrow - (to move up the menu bar) Work? yes
• Icon with Down arrow - (to move down the menu bar) Work? yes
• Icon with Left Arrow - (to go back up a level) Work? yes
• Icon with Fingerprint and a minus sign through it (increase sensitivity) - Work? doesnt seem to make any difference
• Icon with Fingerprint and a plus sign through it (decrease sensitivity) - Work? doesnt seem to make any difference
• Icon with Fingerprint - (resets to default sensitivity) Work? doesnt seem to make any difference

power button when held down is selecting things (tapping does nothing)

Edited September 24, 2011 by Racerboy

[Guest t0mm13b]

Okie.... Sensitivity is working but do not think you're doing it enough.... as per the log...

W:ReadTouchSensitivityData: Could not open /cache/recovery/touchsens.dat - WTF!

mtd: successfully wrote block at c5bb400000000

I:Set boot command ""

W:minui: ev_get(...) - Decreased sensitivity to 21

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (21)

W:minui: ev_get(...) - Decreased sensitivity to 20

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (20)

W:minui: ev_get(...) - Resetted sensitivity to 22

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (22)

W:minui: ev_get(...) - Resetted sensitivity to 22

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (22)

W:minui: ev_get(...) - Increased sensitivity to 23

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (23)

W:minui: ev_get(...) - Increased sensitivity to 24

W:WriteTouchSensitivityData: bytesWritten = 1

W:WriteTouchSensitivityData: Successfully written to /cache/recovery/touchsens.dat (24)

As for the power button... something is amiss...

W:minui: ev_get(...) - Injecting key-press(142) on icon #0

W:minui: ev_get(...) - Successfully injected key-pressed(142) on icon #0

W:minui: ev_get(...) - Injecting key-sync(142) on icon #0

W:minui: ev_get(...) - Successfully injected key-sync(142) on icon #0

W:minui: ev_get(...) - Injecting key-release(142) on icon #0

W:minui: ev_get(...) - Successfully injected key-released(142) on icon #0

W:minui: ev_get(...) - Injecting key-sync(142) on icon #0

W:minui: ev_get(...) - Successfully injected key-sync(142) on icon #0

W:minui: ev_get(...) - Injecting key-press(142) on icon #0

tapping on the icon with plus, which is what the power key's code is 142 as shown above in the excerpt from the log, and is injected into /dev/input/event3, which is not doing anything... yet pressing the power button is selecting things... which is somewhat....I find mysterious?! :huh:

I keep finding myself referring to the previous screenshots in post#113 to make sure I am not missing anything....

This is getting frustrating.....

Will keep rooting around to see if I can think of anything else.... :D

Edit: Just looking at it again and realized from post#113...

event2 had reaction with power button only when going to sleep or waking

Do you think this is where I should be injecting into instead of event3?

Edited September 24, 2011 by t0mm13b

[Guest Racerboy]

i wish i could help more :unsure: i`m sure it would be alot easier if you had the device in front of you :P

[Guest Racerboy]

Edit: Just looking at it again and realized from post#113...

Do you think this is where I should be injecting into instead of event3?

i`m game if you are, give it a shot you never know :)

[Guest t0mm13b]

i wish i could help more :unsure: i`m sure it would be alot easier if you had the device in front of you :P

:lol:

I wish.....

Will keep hammering at this....

Okie.... 50|50 gamble.... will recompile and get this power key injected into event2?

Yes/No? :P

:D

[Guest Racerboy]

yes what is their to lose :D :blink: :rolleyes:

[Guest Racerboy]

btw which deadlink kernal you using ? racer-kernel-2.6.32.9#64-by-deadlink is latest but dont have source code

[Guest t0mm13b]

btw which deadlink kernal you using ? racer-kernel-2.6.32.9#64-by-deadlink is latest but dont have source code

Using 4pda's cm7 kernel :)

B)

[Guest t0mm13b]

power button did not return a value on event1 but end call did

event2 had reaction with power button only when going to sleep or waking

event3 reacted everytime i pressed the power button

There is a niggling doubt about this.... :unsure:

/dev/input/event2 is the touchscreen reading events.... so how could it be reading the power button only?

[Guest Racerboy]

ok i`ll redo the tests just to be sure about things, back in abit

[Guest Racerboy]

event0 all virtual keys, home,menu,back and the main touch screen

event1 virtual home,menu,back. hard keys vol- vol+ make call,end call

event2 only output is when the phone is awake, sleeps no output

only power button reacts, 2 results everytime you press power button,wake,sleep

[Guest t0mm13b]

Okie, by the off chance, and am genuinely curious as to how you got the home/back key on evtest /dev/input/event1

What physical hardware keys do you have on it?

For the blade, we have Home key, Menu Key and back key....

I could reprogram it to use the home key instead of power button, and make it more consistent with what's on the blade?

What do you think?

:)

[Guest Racerboy]

physicals on racer are:

power button on the top

vol- vol+ on the right side of phone

make call (green phone symbol) and end call (red phone symbol)

home, menu and back are all virtual keys in the middle between make call/end call and the main touch screen

sounds a good idea if it works :P

[Guest t0mm13b]

Okie,

This recovery now has the selection button (what you were used to in stock cwm as power key to select) its redefined as hitting the 'home' key instead...

The icon with the plus now matches that of the home key event... so....

Let me know how you get on :)

recovery_redefined.zip

[Guest Racerboy]

Okie,

(what you were used to in stock cwm as power key to select) its redefined as hitting the 'home' key instead...

cwm stock config

• Icon with Plus on it - (for Select to go down a sub-level) - Work? yes but selects a different option other than whats been highlighted
• Icon with Up arrow - (to move up the menu bar) Work? yes
• Icon with Down arrow - (to move down the menu bar) Work? yes
• Icon with Left Arrow - (to go back up a level) Work? yes
• Icon with Fingerprint and a minus sign through it (increase sensitivity) - Work? dont know
• Icon with Fingerprint and a plus sign through it (decrease sensitivity) - Work? dont know
• Icon with Fingerprint - (resets to default sensitivity) Work? dont know

home,menu,back do not work

power button when held selects things, but now like the + virtual it selects things that havent been highlighted, ie i want advanced it selects backup and restore :blink: :blink:

[Guest t0mm13b]

cwm stock config

• Icon with Plus on it - (for Select to go down a sub-level) - Work? yes but selects a different option other than whats been highlighted
• Icon with Up arrow - (to move up the menu bar) Work? yes
• Icon with Down arrow - (to move down the menu bar) Work? yes
• Icon with Left Arrow - (to go back up a level) Work? yes
• Icon with Fingerprint and a minus sign through it (increase sensitivity) - Work? dont know
• Icon with Fingerprint and a plus sign through it (decrease sensitivity) - Work? dont know
• Icon with Fingerprint - (resets to default sensitivity) Work? dont know

home,menu,back do not work

power button when held selects things, but now like the + virtual it selects things that havent been highlighted, ie i want advanced it selects backup and restore :blink: :blink:

Woooachhh!!! wtf ... :blink:

lmao.... this racer is certainly beating me.... :D

Okie... am taking a break and a rest from this.... :)

Need to figure this out.... B)

[Guest Racerboy]

ok m8 but take your time, no rush, whenever you get more recoverys to test i`ll test them no probs :P

[Guest t0mm13b]

ok m8 but take your time, no rush, whenever you get more recoverys to test i`ll test them no probs :P

Thanks once again :) Have a good evening/night ;)

Will be in touch soon B)

[Guest equiliym]

there must be a conflict between end call and power button i think, make call has no function at all and end call/power button basically are the same, if you can get select working with the make call button it MAY take the conflict/same function what the other to hard key buttons have :blink: or something like that :lol:

^ this.. this is why we had 'power button ends call' option on in accessibility for a while, those two buttons are a total mess.. hold down end call button and it will open phone options menu /same thing as power button/ for restarting/shutting down the phone.. might be a driver issue, touch_to_key i think manages call buttons..

[Guest Racerboy]

^ this.. this is why we had 'power button ends call' option on in accessibility for a while, those two buttons are a total mess.. hold down end call button and it will open phone options menu /same thing as power button/ for restarting/shutting down the phone.. might be a driver issue, touch_to_key i think manages call buttons..

touch_to_key is a program to make the soft keys vibrate when the phone has loaded to desktop if i`m not mistaken, whether the key mapping issue in recovery is to do with the kernal or not idk, but plz if you have any ideas/changes feel free to contribute :) as you can see from the thread its been very experimental and considering t0mm13b hasnt got the Racer to hand and working in the blind to a point (i`ve been testing all recoverys hes made) hes do a great job so far :) to get to where we are now....

Edited September 25, 2011 by Racerboy

[Guest t0mm13b]

Okie.... :D

From this point onwards this is going to be experimental and could de-stabilize the internals of recovery, as for the simple reason - to find out how to get the select (icon with plus) working. So I need you to keep an eye on the log file in /tmp/recovery.log.

Objective here is this: the recovery ui is defined by the racer as having those keys for selecting an item - KEY_CAMERA, KEY_CENTER, KEY_POWER and KEY_HOME (the KEY_HOME) I put into the stock cwm last night.

This will show up in the log like this:

recovery_ui: device_handle_key(...) - ....

The '....' will be written out based on the key press that is initiated. So focus on those four types of keys to see if they are actually doing something....

To get at the log do this:

adb pull /tmp/recovery.log ./recovery_log_debug.txt

recovery_redefined_debugging.zip

[Guest Racerboy]

recovery_log_debug.txt

W:recovery_ui: device_handle_key(...) - KEY_HOME (102)

W:recovery_ui: device_handle_key(...)

• Icon with Plus on it - (for Select to go down a sub-level) - Work? yes but selects 2 steps up ie i want advanced it selects backup and restore so on and so on
• Icon with Up arrow - (to move up the menu bar) Work? yes
• Icon with Down arrow - (to move down the menu bar) Work? yes
• Icon with Left Arrow - (to go back up a level) Work? yes
• Icon with Fingerprint and a minus sign through it (increase sensitivity) - Work? doesnt seem to work but log says otherwise
• Icon with Fingerprint and a plus sign through it (decrease sensitivity) - Work? doesnt seem to work but log says otherwise
• Icon with Fingerprint - (resets to default sensitivity) Work? doesnt seem to work but log says otherwise
• end call hard key is same function as left arrow to go back 1 level
• make call does nothing
• power button when held only restarts phone
• home,menu,back soft keys have no function

recovery_log_debug.txt after more playing

Edited September 25, 2011 by Racerboy