[Miscellaneous Android Development] bigrammy:
Touch Function in Recovery

Hi All,

Due to our problem of a non functioning touch screen in recovery and post regarding this problem in various threads I thought it might be better to try keep all this stuff in one thread. :eek:

Rather than start a new thread I think it will be best just to continue this one as It's now quite since [MENTION=5186178]carliv[/MENTION] recovery was released :)

So I have not been idle on this problem and I will share what I know thus far so others have no need to go over old ground looking for fixes :crying:

My setup:

With carliv CWM recovery and AromaFM installed I have almost full adb in recovery :good:

Entering AromaFM will give you some extra adb functions such as getevent and sendevent :good:

Now to explain what happens during boot up. :eek:

The input driver gt9xx registers its input_devs with the kernel input manager by a call to input_device_register. Doing so will automatically create a sysfs entries (symbolic links) for the device in /sys/class/input, and character device entries, which in turn will be picked up by ueventd to create corresponding /dev/input/event## entries.

INFO SOURCE HERE

CODE KEY

Red= While in Recovery Mode

Blue= While in Fully booted System Mode

Ok so knowing what we now know from the "What happens durining boot up" lets see our outputs via adb shell.

First lets see the /sys/class/input then /dev/input/ then a getevent -S just to be sure.

[COLOR="Red"]~ # ls /sys/class/input/
ls /sys/class/input/
event0 event1 event2 event3 event4 input0 input1 input2 input3 input4 mice

~ # ls /dev/input/
ls /dev/input/
event0 event1 event2 event3 event4 mice

~ # getevent -S
getevent -S
add device 1: /dev/input/event4
name: "m_alsps_input"
add device 2: /dev/input/event3
name: "m_acc_input"
add device 3: /dev/input/event2
name: "ACCDET"
add device 4: /dev/input/event1
name: "hwmdata"
could not get driver version for /dev/input/mice, Not a typewriter
add device 5: /dev/input/event0
name: "mtk-kpd"[/COLOR]

So from this we can see only 6 input drivers have registered with the input_device_register

ACCDET Explained Here Headset

m_alsps_input

m_acc_input

hwmdata These are explained Here

mtk-kpd = our hard keys Volume +/- and Power key

So NO touch screen to be seen as far as our board is concerned we do not have a touch screen connected to the phone. :(

Typing cat /proc/interrupts from adb shell gives us ALL cpu interrupts

[COLOR="Red"]~ # cat /proc/interrupts
cat /proc/interrupts
CPU0
29: 363737 - arch_timer
30: 0 - arch_timer
96: 0 - mtk_cpuxgpt0
97: 0 - mtk_cpuxgpt1
98: 0 - mtk_cpuxgpt2
99: 0 - mtk_cpuxgpt3
100: 0 - mtk_cpuxgpt4
101: 0 - mtk_cpuxgpt5
102: 0 - mtk_cpuxgpt6
103: 0 - mtk_cpuxgpt7
104: 35369 - musb-hdrc.0.auto
110: 0 - mtk-thermal
111: 893 - mtk-msdc
112: 955 - mtk-msdc
116: 7 - 11007000.I2C0
117: 56 - 11008000.I2C1
118: 0 - 11009000.I2C2
123: 1 -
150: 0 - 1100a000.SPI1
157: 4 - ptp
165: 0 - mt_emi_mpu, devapc
171: 0 - CCIF0_AP
174: 0 - Afe_ISR_Handle
175: 169487 - mtk_cmdq
177: 0 - m4u
179: 0 - m4u
184: 0 - mt-gpt
193: 0 - pmic_wrap
194: 976 - mtk-kpd
195: 0 - SPM
196: 0 - SPM
197: 0 - SPM
198: 0 - SPM
199: 0 - SPM
200: 0 - SPM
201: 0 - SPM
202: 0 - SPM
206: 0 - MD32 IPC_MD2HOST
209: 0 - DISPSYS
216: 169489 - DISPSYS
217: 169486 - DISPSYS
218: 508443 - DISPSYS
219: 0 - DISPSYS
220: 0 - DISPSYS
223: 169486 - DISPSYS
227: 1 - DISPSYS
238: 0 - Vcodec
240: 0 - jpeg_enc_driver
243: 0 - jpeg_dec_driver
244: 0 - Vcodec
247: 0 - MJC
251: 0 - ISP
254: 0 - ISP
255: 0 - ISP
256: 0 - camera-fdvt
257: 1 - 13040000.MALI
258: 0 - 13040000.MALI
259: 0 - 13040000.MALI
264: 0 - MD_WDT
265: 0 - CLDMA_AP
268: 0 - BTCVSD_ISR_Handle
272: 0 - CIRQ
302: 1 mt-eint
FIQ: fiq_glue
IPI0: 0 CPU wakeup interrupts
IPI1: 0 Timer broadcast interrupts
IPI2: 4548 Rescheduling interrupts
IPI3: 5 Function call interrupts
IPI4: 1 Single function call interrupts
IPI5: 0 CPU stop interrupts
IPI6: 0 CPU backtrace
Err: 0[/COLOR]

I have probed and tested to no avail and the touch driver is simply not there :rolleyes:

So why is it there after boot up :confused:

Obviously something is registering the gt9xx driver with the kernel after boot up :cyclops:

Theories are welcome as to what and how it's registered and I am still digging around I think it will be something really rather simple maybe an .apk like one of the launcher3.apk's in /custom and /system/private-app but I need to unpack them and take a look.

I will update the post with the above adb call's when booted to system for comparison. :o

[MENTION=5186178]carliv[/MENTION]

[MENTION=4893922]codelover[/MENTION]

[MENTION=4478781]yuweng[/MENTION]

[MENTION=4056517]HypoTurtle[/MENTION] [MENTION=4830320]BachMinuetInG[/MENTION]