FORUMS

Analysis & Opinion

Top Forum Discussions

[DEV]CM9/ICS Work-In-Progress

114 posts
Thanks Meter: 611
 
Post Reply Subscribe to Thread Email Thread
16th December 2011, 04:51 PM |#491  
CallMeVentus's Avatar
Recognized Contributor
Flag Singapore
Thanks Meter: 2,874
 
Donate to Me
More
Quote:
Originally Posted by djsky2011

ok but what i'm thinking is it return this value in logcat upon first touch, not an error but should that be the right value?

D/InputReader( 173): Fake event sent, touch=0 !

I think the fake events were reversed

Oh yes , one more question .
Why does the ROM installation in CWM generate a random offset ?

Sent from my GT-S5830 using XDA App
Last edited by CallMeVentus; 16th December 2011 at 04:56 PM.
 
 
16th December 2011, 05:03 PM |#492  
djsky2011's Avatar
Recognized Contributor
Flag London
Thanks Meter: 1,238
 
More
Quote:
Originally Posted by EmoBoiix3

I think the fake events were reversed

Oh yes , one more question .
Why does the ROM installation in CWM generate a random offset ?

Sent from my GT-S5830 using XDA App

I get that too, but it seems to flash properly each time. Could be bug with CWM5 which is what i'm using
16th December 2011, 05:06 PM |#493  
Senior Member
127.0.0.1
Thanks Meter: 417
 
More
Wink
Quote:
Originally Posted by EmoBoiix3

Why does the ROM installation in CWM generate a random offset ?

Sent from my GT-S5830 using XDA App

Google gave this answer http://forum.xda-developers.com/show....php?t=1362200
16th December 2011, 05:13 PM |#494  
djsky2011's Avatar
Recognized Contributor
Flag London
Thanks Meter: 1,238
 
More
right now we need to focus on the touch screen, i have noticed that 1 tap= holding down on left mouse button, while a second tap executes the task, equivalent to releasing the left mouse button after holding it down or a double tap
16th December 2011, 05:14 PM |#495  
terrymcnuggets's Avatar
Member
Flag Singapore
Thanks Meter: 16
 
More
It's just a safety reminder xD

Sent from my GT-S5830 using xda premium
16th December 2011, 05:17 PM |#496  
Wayland_ACE's Avatar
Recognized Developer
Flag Riga
Thanks Meter: 5,891
 
More
Quote:
Originally Posted by EmoBoiix3

I think the fake events were reversed

But I think this log message inform us, if is touched BEFORE current event.
16th December 2011, 05:20 PM |#497  
Member
Thanks Meter: 5
 
More
May be i don't understand something but when i touch screen in cm7 there are no Fake event sent, touch=0 ! or Fake event sent, touch=1 ! (in logcat)/
16th December 2011, 05:22 PM |#498  
djsky2011's Avatar
Recognized Contributor
Flag London
Thanks Meter: 1,238
 
More
Quote:
Originally Posted by den191097

May be i don't understand something but when i touch screen in cm7 there are no Fake event sent, touch=0 ! or Fake event sent, touch=1 ! (in logcat)/

waylander patched the libs so it could work with ICS
The Following User Says Thank You to djsky2011 For This Useful Post: [ View ]
16th December 2011, 05:28 PM |#499  
Wayland_ACE's Avatar
Recognized Developer
Flag Riga
Thanks Meter: 5,891
 
More
Here is a libinput library with some debug information output: http://cs.fill.ee/ics/libinput.so
1short tap generated:

Quote:

I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0035 keycode=0x0000 value=0x000000e2 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0036 keycode=0x0000 value=0x0000004b flags=0x00000000
D/InputReader( 162): Fake event sent, touch=0 !
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0030 keycode=0x0000 value=0x00000001 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0032 keycode=0x0000 value=0x0000003f flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0000 scancode=0x0002 keycode=0x0000 value=0x00000000 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0000 scancode=0x0000 keycode=0x0000 value=0x00000000 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0035 keycode=0x0000 value=0x000000e2 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0036 keycode=0x0000 value=0x0000004b flags=0x00000000
D/InputReader( 162): Fake event sent, touch=1 !
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0030 keycode=0x0000 value=0x00000000 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0003 scancode=0x0032 keycode=0x0000 value=0x0000003f flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0000 scancode=0x0002 keycode=0x0000 value=0x00000000 flags=0x00000000
I/InputReader( 162): Input event: device=4 type=0x0000 scancode=0x0000 keycode=0x0000 value=0x00000000 flags=0x00000000



---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

Quote:
Originally Posted by den191097

May be i don't understand something but when i touch screen in cm7 there are no Fake event sent, touch=0 ! or Fake event sent, touch=1 ! (in logcat)/

InputReader was changed after gingerbread, in ICS. And our touchscreens become to LEGACY. So, now we use legacy ts hack.
16th December 2011, 05:38 PM |#500  
djsky2011's Avatar
Recognized Contributor
Flag London
Thanks Meter: 1,238
 
More
Quote:
Originally Posted by Wayland_ACE

Here is a libinput library with some debug information output: http://cs.fill.ee/ics/libinput.so
1short tap generated:



---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------



InputReader was changed after gingerbread, in ICS. And our touchscreens become to LEGACY. So, now we use legacy ts hack.

our touch is being registered as a long press, 1 touch produces this twice in my log

D/InputReader( 173): Fake event sent, touch=0 !
D/InputReader( 173): Fake event sent, touch=1 !
D/InputReader( 173): Fake event sent, touch=1 !


notice inputreader being called twice from just one touch
16th December 2011, 05:42 PM |#501  
Wayland_ACE's Avatar
Recognized Developer
Flag Riga
Thanks Meter: 5,891
 
More
Quote:
Originally Posted by djsky2011

our touch is being registered as a long press, 1 touch produces this twice in my log

D/InputReader( 173): Fake event sent, touch=0 !
D/InputReader( 173): Fake event sent, touch=1 !
D/InputReader( 173): Fake event sent, touch=1 !


notice inputreader being called twice from just one touch

Check again, all ok, only once touch 1
The Following 2 Users Say Thank You to Wayland_ACE For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread

Tags
android, cm9, cooper, ice cream sandwich, sga, teamhackace, teamhacksung
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes