Open GoogleCodeExporter opened 8 years ago
Ok..
Scratch that. It appears to work correctly if I force it as a ThinkPad Tablet.
Original comment by peter.r....@gmail.com
on 14 Apr 2013 at 10:17
I see, they must be using an N-trig digitizer. Interesting!
Do you happen to know the android.os.Build.MODEL string? Then I'll make it
default to the ThinkPad Tablet pen method.
Original comment by vbraun.n...@gmail.com
on 15 Apr 2013 at 4:25
Hi vBraun,
It's not an N-trig. The pen requires a AAAA battery, but it is Chinese made
hardware, ostensibly from a company called Morgan Touch Technologies:
http://www.morgan-touch.com/
The tablet manufacturer's page is here:
http://www.ibnote.com/
I've attached the entire build.prop file. I believe the MODEL is
"crane-iNote_v4".
I've also attached a picture of the pen/touchscreen controller board.
I have root on the device and a rudimentary knowledge of java, so if you need
me to run or do anything on the device, just let me know.
Thanks,
pb
Original comment by peter.r....@gmail.com
on 16 Apr 2013 at 2:47
Attachments:
The N-trig pen on the thinkpad tablet also needs a battery (AAA I think).
Though I agree that there is no sign that the manufacturer is affiliated with
N-trig.
Original comment by vbraun.n...@gmail.com
on 16 Apr 2013 at 3:54
Ah.. I think I get it now.
In [PenEventThinkPadTablet], my pen driver must be returning "0" for
getTouchMajor(), so isPenEvent() is returning true.
isPenButtonPressed() then calls on ViewHackThinkpad.onTouchEvent(), where my
pen driver is responding with "MotionEvent.ACTION_DOWN" (ie. linux "BTN_TOUCH")
to the getActionMasked() function.
So it's not an N-trig specific thing at all. It's:
1] Does the pen driver return a single coordinate, or a touch area.
2] Does the pen driver provide a "BTN_TOUCH" event in linux.
3] Optionally, does the pen provide a "ABS_PRESSURE" report in linux.
It appears that if those conditions are met, then the [ThinkPadTablet]
methodology will work correctly.
Original comment by peter.r....@gmail.com
on 16 Apr 2013 at 11:04
Original issue reported on code.google.com by
peter.r....@gmail.com
on 13 Apr 2013 at 10:47Attachments: