Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
Page 1 of 4    1 23 >>
 
Post Reply+
Tip us?
 
tj_style 		Old
1st November 2011, 07:49 PM
#1  
tj_style's Avatar
Recognized Developer - OP
Thanks Meter 1311
Posts: 808
Join Date: May 2010
Location: Gadog - Bogor
Lightbulb [DEV]Porting Touchscreen driver for Android 4.0 (ICS) ROMS
This thread is general discussion for DEVs only about Touchscreen driver porting for Android 4.0 (ICS) ROMS..


I'm worry about the new methode of input processing on Android 3.x and 4.x.
So while waiting the AOSP source code of Android 4.0 (ICS) is released by Google, is better for we to start porting the Touchscreen driver to be compatible with Android 4.0 Build.

As we know, many developer have start to porting the ICS SDK to various devices,
but not all touchscreen devices will work.
lucky to have native touchscreen input working, also with multitouch capability..
And sometimes just have pointer input working, so we should to use 2 fingers for input operation.
But my device is end up with not working touchscreen or pointer input..

So, better for we discussing about porting the Touchscreen driver and configuration to make our Touchscreen device is recognized by Android 4.0 System.

For now, we don't have the libinput.so source code, so we focussing on kernel side and on *.idc files that placed on /system/usr/idc/

Actually I've success on modify my device touchscreen driver to work on ICS SDK ROMs, soon I will post all log and modification files.

Here is some P.O.C video:


My CSL Mi-410 (FIH-FB0) same like Huawei X6, Wellcom A99, Cherrymobile Magnum HD, is using BU21018MWV Touchscreen device from ROHM.
But I think it can be implementing on all Touchscreen devices driver.
And maybe other developers have other solution about how to make touchscreen device's recognized by ICS System, so we will discussing on this thread.

I will Separate the info based on touchscreen device vendor, like synaptic, atmel, cypress, etc.

G+: tjstyle Github: tjstyle Twitter: tj_style

Like my work? Please award it with some donation..
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7JHEY7QERQUWU
 
REPLY
The Following 12 Users Say Thank You to tj_style For This Useful Post: [ Click to Expand ]
 
tj_style 		Old
1st November 2011, 07:50 PM
(Last edited by tj_style; 3rd November 2011 at 02:32 AM.)
#2  
tj_style's Avatar
Recognized Developer - OP
Thanks Meter 1311
Posts: 808
Join Date: May 2010
Location: Gadog - Bogor
I fun with ICS SDK system Image and ramdisk, trying to booting up the ICS system on my CSL Mi-410.

But.. end up with not working touchscreen, see the logcat:

Code:
23:54:06.962 Info SystemServer 134  Input Method Service

23:54:06.962 Info EventHub 134  New device: id=8, fd=107, path='/dev/input/event2', name='bu21018mwvkey', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

23:54:06.962 Debug EventHub 134  No input device configuration file found for device 'bu21018mwv'.

23:54:06.962 Warning InputManagerService 134  Couldn't create dir.: /data/system/inputmethod

23:54:06.962 Info EventHub 134  New device: id=9, fd=114, path='/dev/input/event1', name='bu21018mwv', classes=0x15, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

23:54:06.962 Debug EventHub 134  No input device configuration file found for device 'fbx_kybd'.

23:54:06.962 Info EventHub 134  New device: id=10, fd=116, path='/dev/input/event0', name='fbx_kybd', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

23:54:06.962 Info InputReader 134  Device added: id=10, name='fbx_kybd', sources=0x00000101

23:54:06.962 Info InputReader 134    Touch device 'bu21018mwv' could not query the properties of its associated display 0.  The device will be inoperable until the display size becomes available.

23:54:06.962 Info InputReader 134  Device added: id=9, name='bu21018mwv', sources=0x00002103

23:54:06.962 Info InputReader 134  Device added: id=8, name='bu21018mwvkey', sources=0x00000101

23:54:06.962 Info InputReader 134  Device added: id=3, name='7k_handset', sources=0x80000101

23:54:06.962 Info SystemServer 134  Accessibility Manager

23:54:06.962 Info InputReader 134  Reconfiguring input devices.  changes=0x00000004

23:54:06.962 Info InputReader 134  Device reconfigured: id=9, name='bu21018mwv', surface size is now 480x800, mode is 3
So I try to place bu21018mwv.idc at /system/usr/idc/.

Reboot the phone and when come back to Lockscreen and see the logcat:

Code:
23:57:03.720 Info EventHub 134  New device: id=8, fd=110, path='/dev/input/event2', name='bu21018mwvkey', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

23:57:03.720 Info SystemServer 134  Input Method Service

23:57:03.720 Info EventHub 134  New device: id=9, fd=114, path='/dev/input/event1', name='bu21018mwv', classes=0x15, configuration='/system/usr/idc/bu21018mwv.idc', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

23:57:03.720 Debug EventHub 134  No input device configuration file found for device 'fbx_kybd'.

23:57:03.720 Warning InputManagerService 134  Couldn't create dir.: /data/system/inputmethod

23:57:03.720 Info EventHub 134  New device: id=10, fd=115, path='/dev/input/event0', name='fbx_kybd', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

23:57:03.720 Info InputReader 134  Device added: id=10, name='fbx_kybd', sources=0x00000101

23:57:03.720 Info InputReader 134    Touch device 'bu21018mwv' could not query the properties of its associated display 0.  The device will be inoperable until the display size becomes available.

23:57:03.720 Info InputReader 134  Device added: id=9, name='bu21018mwv', sources=0x00001103

23:57:03.720 Info InputReader 134  Device added: id=8, name='bu21018mwvkey', sources=0x00000101

23:57:03.720 Info InputReader 134  Device added: id=3, name='7k_handset', sources=0x80000101

23:57:03.720 Info InputReader 134  Reconfiguring input devices.  changes=0x00000004

23:57:03.720 Info InputReader 134  Device reconfigured: id=9, name='bu21018mwv', surface size is now 480x800, mode is 1
Good.. The Input manager is using bu21018mwv.idc..

I try to touch the screen with one finger, there is no logcat message, but when I touch the screen with two fingers lot of message are bouching on logcat:

Code:
23:59:12.875 Debug InputEventConsistencyVerifier 134  GenericMotionEvent: Pointer count is 2 but it should always be 1 for ACTION_HOVER_ENTER

23:59:12.875 Debug InputEventConsistencyVerifier 134    in Handler (android.view.ViewRootImpl) {415519f8}

23:59:12.875 Debug InputEventConsistencyVerifier 134    0: sent at 145547252000, MotionEvent { action=ACTION_HOVER_ENTER, id[0]=0, x[0]=140.25531, y[0]=118.25, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=290.7234, y[1]=284.2222, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=145547, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    -- recent events --

23:59:12.875 Debug InputEventConsistencyVerifier 134    1: sent at 122225749000, MotionEvent { action=ACTION_HOVER_EXIT, id[0]=0, x[0]=-0.68085104, y[0]=-38.694443, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=122225, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    2: sent at 122215617000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=83.06383, y[0]=331.44443, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=281.87234, y[1]=513.38885, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122215, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    3: sent at 122199870000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=84.42553, y[0]=332.1389, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=283.23404, y[1]=512.6944, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122199, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    4: sent at 122182414000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=85.78723, y[0]=332.1389, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=284.59573, y[1]=512.0, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122182, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    5: sent at 122157085000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=86.46808, y[0]=330.75, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=284.59573, y[1]=510.61108, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122157, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134  GenericMotionEvent: Pointer count is 2 but it should always be 1 for ACTION_HOVER_MOVE

23:59:12.875 Debug InputEventConsistencyVerifier 134    in Handler (android.view.ViewRootImpl) {415519f8}

23:59:12.875 Debug InputEventConsistencyVerifier 134    0: sent at 145547252000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=140.25531, y[0]=118.25, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=290.7234, y[1]=284.2222, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=145547, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    -- recent events --

23:59:12.875 Debug InputEventConsistencyVerifier 134    1: sent at 145547252000, MotionEvent { action=ACTION_HOVER_ENTER, id[0]=0, x[0]=140.25531, y[0]=118.25, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=290.7234, y[1]=284.2222, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=145547, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    2: sent at 122225749000, MotionEvent { action=ACTION_HOVER_EXIT, id[0]=0, x[0]=-0.68085104, y[0]=-38.694443, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=122225, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    3: sent at 122215617000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=83.06383, y[0]=331.44443, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=281.87234, y[1]=513.38885, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122215, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    4: sent at 122199870000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=84.42553, y[0]=332.1389, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=283.23404, y[1]=512.6944, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122199, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    5: sent at 122182414000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=85.78723, y[0]=332.1389, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=284.59573, y[1]=512.0, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x80000000, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=122182, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134  GenericMotionEvent: Pointer count is 2 but it should always be 1 for ACTION_HOVER_MOVE

23:59:12.875 Debug InputEventConsistencyVerifier 134    in Handler (android.view.ViewRootImpl) {415519f8}

23:59:12.875 Debug InputEventConsistencyVerifier 134    0: sent at 145568034000, MotionEvent { action=ACTION_HOVER_MOVE, id[0]=0, x[0]=137.5319, y[0]=121.02777, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=290.7234, y[1]=284.2222, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=145568, downTime=0, deviceId=9, source=0x1002 }

23:59:12.875 Debug InputEventConsistencyVerifier 134    -- recent events --
The messages is just say only ACTION_HOVER_ENTER, ACTION_HOVER_MOVE & ACTION_HOVER_EXIT.

And I think I need to send something like BTN_TOUCH and ABS_PRESSURE from kernel..

Now it's time to modify the touchscreen driver, this is what I've modify:

This is the original:
https://gist.github.com/1328331/5795...5d2ec41f469b7d
This is what i've modify:
https://gist.github.com/1328331/239f...c7d77f8d41d474

Compile the kernel, flash the new boot.img to my phone and remove the bu21018mwv.idc.

When i reboot the phone and come back to Lockscreen, try to touch and move with one, also with two finger, there is no bounching message again on logcat:

Code:
00:01:39.612 Info EventHub 134  New device: id=3, fd=103, path='/dev/input/event9', name='7k_handset', classes=0x81, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'proximity'.

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'light'.

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'orientation'.

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'accelerometer'.

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'bu21018mwvkey'.

00:01:39.612 Debug BluetoothAdapterStateMachine 134  PowerOff process message: 5

00:01:39.612 Info EventHub 134  New device: id=8, fd=110, path='/dev/input/event2', name='bu21018mwvkey', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'bu21018mwv-ics'.

00:01:39.612 Info SystemServer 134  Input Method Service

00:01:39.612 Info EventHub 134  New device: id=9, fd=111, path='/dev/input/event1', name='bu21018mwv-ics', classes=0x15, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:01:39.612 Debug EventHub 134  No input device configuration file found for device 'fbx_kybd'.

00:01:39.612 Warning InputManagerService 134  Couldn't create dir.: /data/system/inputmethod

00:01:39.612 Info EventHub 134  New device: id=10, fd=115, path='/dev/input/event0', name='fbx_kybd', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:01:39.612 Info InputReader 134  Device added: id=10, name='fbx_kybd', sources=0x00000101

00:01:39.612 Info InputReader 134    Touch device 'bu21018mwv-ics' could not query the properties of its associated display 0.  The device will be inoperable until the display size becomes available.

00:01:39.612 Info InputReader 134  Device added: id=9, name='bu21018mwv-ics', sources=0x00002103

00:01:39.612 Info InputReader 134  Device added: id=8, name='bu21018mwvkey', sources=0x00000101

00:01:39.612 Info InputReader 134  Device added: id=3, name='7k_handset', sources=0x80000101

00:01:39.721 Info InputReader 134  Reconfiguring input devices.  changes=0x00000004

00:01:39.721 Info SystemServer 134  Accessibility Manager

00:01:39.721 Info InputReader 134  Device reconfigured: id=9, name='bu21018mwv-ics', surface size is now 480x800, mode is 3
But the Touchscreen are now recognized as pointer, not as native touchscreen..

Click image for larger version Name: ss-noidc1.jpg Views: 830 Size: 16.3 KB ID: 769877Click image for larger version Name: ss-noidc2.jpg Views: 844 Size: 16.5 KB ID: 769878

And the last, i've place the bu21018mwv-ics.idc (just to make different name with original driver) to /system/usr/idc/

Reboot the phone, back to lockscreen, try to touch the screen, and here is the logcat:

Code:
00:08:01.750 Info EventHub 134  New device: id=3, fd=103, path='/dev/input/event9', name='7k_handset', classes=0x81, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:08:01.750 Debug EventHub 134  No input device configuration file found for device 'proximity'.

00:08:01.750 Debug EventHub 134  No input device configuration file found for device 'light'.

00:08:01.750 Debug EventHub 134  No input device configuration file found for device 'orientation'.

00:08:01.750 Debug EventHub 134  No input device configuration file found for device 'accelerometer'.

00:08:01.750 Debug EventHub 134  No input device configuration file found for device 'bu21018mwvkey'.

00:08:01.750 Debug BluetoothAdapterStateMachine 134  PowerOff process message: 5

00:08:01.750 Info EventHub 134  New device: id=8, fd=110, path='/dev/input/event2', name='bu21018mwvkey', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:08:01.750 Info SystemServer 134  Input Method Service

00:08:01.750 Info EventHub 134  New device: id=9, fd=114, path='/dev/input/event1', name='bu21018mwv-ics', classes=0x15, configuration='/system/usr/idc/bu21018mwv-ics.idc', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:08:01.750 Warning InputManagerService 134  Couldn't create dir.: /data/system/inputmethod

00:08:01.750 Debug EventHub 134  No input device configuration file found for device 'fbx_kybd'.

00:08:01.750 Info EventHub 134  New device: id=10, fd=116, path='/dev/input/event0', name='fbx_kybd', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

00:08:01.750 Info InputReader 134  Device added: id=10, name='fbx_kybd', sources=0x00000101

00:08:01.750 Info InputReader 134    Touch device 'bu21018mwv-ics' could not query the properties of its associated display 0.  The device will be inoperable until the display size becomes available.

00:08:01.750 Info InputReader 134  Device added: id=9, name='bu21018mwv-ics', sources=0x00001103

00:08:01.750 Info InputReader 134  Device added: id=8, name='bu21018mwvkey', sources=0x00000101

00:08:01.750 Info InputReader 134  Device added: id=3, name='7k_handset', sources=0x80000101

00:08:01.750 Info InputReader 134  Reconfiguring input devices.  changes=0x00000004

00:08:01.750 Info InputReader 134  Device reconfigured: id=9, name='bu21018mwv-ics', surface size is now 480x800, mode is 1
And GREAAAT... My touchscreen is work as native touchscreen..

Click image for larger version Name: ss-driver-idc1.jpg Views: 780 Size: 17.3 KB ID: 769879Click image for larger version Name: ss-driver-idc2.jpg Views: 821 Size: 12.3 KB ID: 769880

I think this methode will can be implemented on all touchscreen driver, and maybe we not must to do that if we can modify the libinput source code.

or maybe other developers have another methode? please share in this thread..

G+: tjstyle Github: tjstyle Twitter: tj_style

Like my work? Please award it with some donation..
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7JHEY7QERQUWU
 
REPLY
The Following 7 Users Say Thank You to tj_style For This Useful Post: [ Click to Expand ]
 
swm5126 		Old
1st November 2011, 09:19 PM
#3  
Senior Member
Thanks Meter 195
Posts: 252
Join Date: Dec 2009

 
DONATE TO ME
Hi there,

I'm actually doing the same thing for my device (porting touchscreen driver). What device did you port the driver from?

Any info you have would be greatly appreciated!

Sent from my ADR6300 using xda premium
 
REPLY
 
tj_style 		Old
2nd November 2011, 09:06 AM
#4  
tj_style's Avatar
Recognized Developer - OP
Thanks Meter 1311
Posts: 808
Join Date: May 2010
Location: Gadog - Bogor
Quote:
Originally Posted by swm5126 View Post
Hi there,

I'm actually doing the same thing for my device (porting touchscreen driver). What device did you port the driver from?

Any info you have would be greatly appreciated!

Sent from my ADR6300 using xda premium
this night i will post the complete logs and modified source that can be adaptable to other driver, i'm on work now.

Sent from my FIH-FB0

G+: tjstyle Github: tjstyle Twitter: tj_style

Like my work? Please award it with some donation..
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7JHEY7QERQUWU
 
REPLY
 
swm5126 		Old
2nd November 2011, 12:08 PM
#5  
Senior Member
Thanks Meter 195
Posts: 252
Join Date: Dec 2009

 
DONATE TO ME
Cool thank you. I actually got the touchscreen driver I was porting from the Nexus S running and can now use the touchscreen in ICS, but I'm havubh trouble getting the softkeys to work.

Sent from my ADR6300 using xda premium
 
REPLY
 
zorlin 		Old
14th November 2011, 07:25 AM
#6  
zorlin's Avatar
Member
Thanks Meter 278
Posts: 94
Join Date: Aug 2009
Bumping this thread - any idea if/how this could be used on the HTC Sensation?
 
REPLY
 
oguzhan mobile 		Old
14th November 2011, 06:00 PM
#7  
oguzhan mobile's Avatar
Senior Member
Thanks Meter 199
Posts: 289
Join Date: Sep 2011
Location: Bursa
ı want to ideos x5
 
REPLY
 
twistedumbrella 		Old
14th November 2011, 06:05 PM
#8  
twistedumbrella's Avatar
Recognized Developer
Thanks Meter 5966
Posts: 5,656
Join Date: Sep 2007

 
DONATE TO ME
Quote:
Originally Posted by oguzhan mobile View Post
ı want to ideos x5
Is that a new exercise?
 
REPLY
 
oguzhan mobile 		Old
15th November 2011, 07:01 PM
#9  
oguzhan mobile's Avatar
Senior Member
Thanks Meter 199
Posts: 289
Join Date: Sep 2011
Location: Bursa
http://forum.xda-developers.com/show....php?t=1316080


touch screen not working. please mod. because ı make not


sory my bad english
 
REPLY
 
ziggy46 		Old
21st November 2011, 10:55 PM
#10  
ziggy46's Avatar
Recognized Contributor
Thanks Meter 1893
Posts: 2,119
Join Date: Aug 2011
Location: Chambersburg, Pa

 
DONATE TO ME
@tj... i own the motorola triumph, which is very similar to the magnum hd and your device. will this method work for my device?
 
REPLY

The Following User Says Thank You to ziggy46 For This Useful Post: [ Click to Expand ]
 
Post Reply+
Page 1 of 4    1 23 >>
Tags
android 4.0, driver, ics, sdk, touchscreen
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...

XDA PORTAL POSTS

Boot Animation Paradise for your Android Device

The default boot animations on any device, no matter whichmanufacturer, are generally pretty … more

Flash Custom ROM and Recovery to Samsung Galaxy S 4

After reading about Dan Rosenberg’s bootloader exploit for the Samsung Galaxy S 4,I … more

Windows-Based Multi-Tool for the Sony Xperia U

If you are a flashaholic and an owner of the Sony Xperia U, you may be interested in the … more

XDA University: Crafting Recovery-Flashable Packages

Those of us who use Linux on a day to day basis don’t think twice about sinking … more