Solution Screen Problem m4 Ss4040

24/3/2016
ODROIDForumViewtopicTouchscreenresolutionmismatch.Howtocalibrate.
ODROIDForum
HardkernelODROID
Skiptocontent
BoardindexEOLProductsODROIDX2ODROIDX2Android
Changefontsize
Printview
FAQ
Members
Register
Login
Touchscreenresolutionmismatch.Howtocalibrate.
Moderators:mdrjr,odroid
Postareply
Firstunreadpost26postsPage1of1
Touchscreenresolutionmismatch.Howtocalibrate.
bydilo83FriJun28,20136:31am
Hi,
ihaveanX2withOdroidBeta1.7.1andAndroid4.1.2
Kernelis:
#unamea
Linuxlocalhost3.0.51#1SMPFriMay2411:24:14KST2013armv7lGNU/Linux
Iinstalledanexternaltouchscreenwhichisrecognizedbyandroid.ThescreenisconnectedtotheHDMI
Port.Theproblemis:theresoultionofthetouchscreenandtheresoultionfromthemonitordoesn'tmatch.
I'vereadtheforumandinthisthread
viewtopic.php?f=14&t=1348
theproblemmightbethesamebutigotnohelpfulanswer!
Intheupperleftedgeofthescreenthecursormatchesnearlythetouchpoint.Themoreigotothelower
rightedge,themorethecursorisbehindthetouchpoint.Theresolutionofthedisplayis1920x1080,the
http://forum.odroid.com/viewtopic.php?f=14&t=1617
1/27
24/3/2016
resolutionofthescaledtouchseemstobesomethinglike1366x768.Soit'snotpossibletoreachthe
menubar.Itriedtoeditthefile"/system/usr/idc/odroidxts.idc"butnothingchanged.
WhenipluginthetouchscreeninUSBportigotthefollowingmessages:
[120.598655]init:nosuchservice'hciattach'
[122.580450]usb12.3:newfullspeedUSBdevicenumber7usings5pehci
[122.718264]input:HID1aad:000fas/devices/platform/s5pehci/usb1/12/12.3/12.3:1.0/input/input3
[122.726708]hidmultitouch0003:1AAD:000F.0002:input:USBHIDv1.10Mouse[HID1aad:000f]on
usbs5pehci2.3/input0
Bootingthesystemwithpluggedintouchscreenshowsthefollowing:
[2.468234]odroid_keypad_init
[2.468658]input:odroidkeypadas/devices/virtual/input/input0
[2.468670]odroid_keypad_open
[2.468839]
[2.468846]odroidkeypaddriverinitialized!!Ver1.0
[2.468850]
[2.468860]platform_driver_register0
[2.469008]usbcore:registerednewinterfacedriverxpad
[2.469265]input:odroidxtsas/devices/platform/s3c2440i2c.0/i2c0/0007f/input/input1
[2.469450]
[2.469457]TOUCHSCREENINFORMATION
[2.469461]
[2.469467]TOUCHINPUTName=odroidxts
[2.469472]TOUCHABSXMAX=1920,TOUCHABSXMIN=0
[2.469478]TOUCHABSYMAX=1080,TOUCHABSYMIN=0
[2.469482]DummyTouchscreendriver!
[2.469486]
[2.469596]i2ccore:driver[odroidts]usinglegacysuspendmethod
[2.469603]i2ccore:driver[odroidts]usinglegacyresumemethod
With"getenv"icouldseethatthetouchscreenhasanresolutionof4096x4096pointsandworksfine.
Wherethisresolutionismappedtothescreensize?Theremustbeatleastonefactorforxandybut
wherethisisconfigured?Isthereanypossibilitytocalibratethescreen?
Ihavealsoseenthatthereweremorethanoneframebufferavailable.Whythisisnecessary?Towhich
framebufferthetouchscreenisscaled?Couldichangetheresoultionofthisframebufferthatitmatches
theresolutionoftheHDMIPort?Orisitpossibletoselectthedefaultframebuffer?
Bestregards,
Dirk
dilo83
Posts:11
Joined:FriJun28,201312:32am
languages_spoken:english
2/27
24/3/2016
ODROIDs:X2+Rev0.520130228
Privatemessage
Top
Re:Touchscreenresolutionmismatch.Howtocalibrate.
bymdrjrFriJun28,20137:43am
Youhavetouseaboot.scrthatactuallymatchsyourneed.
Ifyourscreenneedsa1080p.Usea1080pboot.scrthatalsosetsthefake_fbto1080p.
boothdmi_1080pfb_1920x1080kernel_movi.scr
Istheboot.scrthatyouneed.Putiton/mnt/sdcardrenamedasboot.scrandletmeknow
Newsfor:C1XU3/XU3LiteU2/U3
ODROIDProject'sHosting
MyG+mostlyODROID
Howto'sandGuides
ODROIDUtility
(PMmeifyouwanttosuggestanewguide/howto)
mdrjr
SiteAdmin
Posts:11231
Joined:FriFeb22,201311:34pm
Location:Brazil
languages_spoken:english,portuguese
ODROIDs:
Privatemessage
Website
Top
bydilo83FriJun28,20135:47pm
Yes,thisiswhati'vedone.InUBootprintenvisee:
*******************************************
Exynos4412#printenv
baudrate=115200
bootargs=console=/dev/ttySAC1,115200n8androidboot.console=ttySAC1v_out=hdmifake_fb=true
fb_x_res=1920fb_y_res=1080hdmi_phy_res=1080led_blink=1
bootcmd=echo>>>RunDefaultBootcmd<<<movireadkernel040008000movireadrootfs0
41000000100000bootm4000800041000000
bootdelay=1
3/27
24/3/2016
bootscript=source40008000
default_bootcmd=echo>>>RunDefaultBootcmd<<<movireadkernel040008000movireadrootfs0
41000000100000bootm4000800041000000
ethaddr=00:40:5c:26:0a:5b
fake_fb=true
fb_x_res=1920
fb_y_res=1080
filesize=22D
gatewayip=192.168.0.1
hdmi_phy_res=1080
ipaddr=192.168.0.20
led_blink=1
loadbootscript_1=echo>>>LoadBootScriptfrommmc0:1<<<fatloadmmc0:140008000boot.scr
loadbootscript_2=echo>>>LoadBootScriptfrommmc0:2<<<fatloadmmc0:240008000boot.scr
netmask=255.255.255.0
serverip=192.168.0.10
v_out=hdmi
Environmentsize:877/16380bytes
*******************************************
Iuse"boothdmi_1080pfb_1920x1080kernel_movi.scr"andthentheresolutioniscorrectforthe
display.
BUTTHISDOESNOTAFFECTTHETOUCHSCREEN!!!
Wheniuseanotherfilee.g."boothdmi_1080pfb_1280x720kernel_movi.scr"thetochscreenmatches
withthedisplay.SoithinkthetouchscreenisALWAYSMAPPEDTO1280x720pxonanother
framebufferdevice.
MaybethetouchscreenismappedtotheframebufferoftheLCDDisplayPortandnottothe
framebufferoftheHDMIPort.
dilo83
Posts:11
Privatemessage
Top
byodroidFriJun28,20139:02pm
NormallywemadeatrickycodeinthedevicedriverwhenweusedeGalaxtouchdevicedriver.
ButyouareusingagenericHIDdriverandthereisnoplacetoimplementthetrickycode.
Inthatcase,youmayneedtomodifytheeventhubsourcecodeinAndroidplatformorsimilarapproach.
4/27
24/3/2016
IthinkyoumustfindthepathoftouchpointdatafromtheHIDdriverinKerneltotoucheventhandler
inAndroidplatform.
BecausewehavenoexperienceofHIDbasedtouchscreendriver,itisveryhardtohelpyou.
odroid
SiteAdmin
Posts:14219
Location:SeoulKorea
ODROIDs:ODROID
Privatemessage
Top
Ok,iwilltrytofixthedriver(whenifoundhim...)
Meanwhilehowcanichangetheresolutionsoftheotherframebuffersmaybethisisanworkaround
(theHIDdrivergetstheresolutionfromthewrongframebuffer,butifithasthesameresolutionlikemy
displayitshouldbeok)
dilo83
Posts:11
Privatemessage
Top
byodroidFriJun28,20139:33pm
LCDdriveris"kernel_4412/drivers/video/samsung/u133wa01.c"forODROIDX/X2.
Butyouneedtocheckwhetherthatdriverislinkedornotwhenyouusethefakefb.
5/27
24/3/2016
odroid
SiteAdmin
Posts:14219
Location:SeoulKorea
ODROIDs:ODROID
Privatemessage
Top
SotheLCDresolutionisfixinkernelandnotchangeablethroughcommandlineorUBoot?
dilo83
Posts:11
Privatemessage
Top
byodroidSatJun29,201311:27am
Yes..youshouldmodifytheLCDdriverandbuildit.
odroid
SiteAdmin
Posts:14219
6/27
24/3/2016
Location:SeoulKorea
ODROIDs:ODROID
Privatemessage
Top
bydilo83WedJul10,201312:23am
Irecompiledthekernelwithouttheodroidtsandthefake_fb.
Thetouchscreenisrecognizedbythesystem:
Code:Selectall
root@android:/#cat/proc/bus/usb/devices
T:Bus=01Lev=02Prnt=02Port=02Cnt=03Dev#=7Spd=12MxCh=0
D:Ver=1.10Cls=00(>ifc)Sub=00Prot=00MxPS=64#Cfgs=1
P:Vendor=1aadProdID=000fRev=0.00
C:*#Ifs=1Cfg#=1Atr=a0MxPwr=108mA
I:*If#=0Alt=0#EPs=1Cls=03(HID)Sub=00Prot=00Driver=usbhid
E:Ad=81(I)Atr=03(Int.)MxPS=14Ivl=10ms
with"geteventp"igetthefollowingoutput:
Code:Selectall
root@android:/#geteventp
adddevice1:/dev/input/event1
name:"HID1aad:000f"
events:
KEY(0001):014a
ABS(0003):0000:value941,min0,max4095,fuzz0,flat0,resolution0
0001:value3205,min0,max4095,fuzz0,flat0,resolution0
002f:value0,min0,max1,fuzz0,flat0,resolution0
inputprops:
INPUT_PROP_DIRECT
name:"odroidkeypad"
events:
7/27
24/3/2016
KEY(0001):0074
inputprops:
<none>
dumpsysgivesmethisinformationaboutthetouchscreeninputdevice:
Code:Selectall
Device1:e
Generation:8
IsExternal:true
Sources:0x00001002
KeyboardType:0
MotionRanges:
X:source=0x00001002,min=0.000,max=1279.688,flat=0.000,fuzz=0.312
Y:source=0x00001002,min=0.000,max=719.824,flat=0.000,fuzz=0.176
PRESSURE:source=0x00001002,min=0.000,max=1.000,flat=0.000,fuzz=0.000
TouchInputMapper:
Parameters:
GestureMode:spots
DeviceType:touchScreen
AssociatedDisplay:id=0,isExternal=true
OrientationAware:true
RawTouchAxes:
X:min=0,max=4095,flat=0,fuzz=0,resolution=0
Y:min=0,max=4095,flat=0,fuzz=0,resolution=0
Pressure:unknownrange
TouchMajor:unknownrange
TouchMinor:unknownrange
ToolMajor:unknownrange
ToolMinor:unknownrange
Orientation:unknownrange
Distance:unknownrange
TiltX:unknownrange
TiltY:unknownrange
TrackingId:min=0,max=65535,flat=0,fuzz=0,resolution=0
Slot:min=0,max=1,flat=0,fuzz=0,resolution=0
Calibration:
touch.size.calibration:none
touch.pressure.calibration:none
touch.orientation.calibration:none
touch.distance.calibration:none
SurfaceWidth:1280px
SurfaceHeight:720px
SurfaceOrientation:0
TranslationandScalingFactors:
XScale:0.312
YScale:0.176
XPrecision:3.200
8/27
24/3/2016
YPrecision:5.689
GeometricScale:0.244
PressureScale:0.000
SizeScale:0.000
OrientationCenter:0.000
OrientationScale:0.000
DistanceScale:0.000
HaveTilt:false
TiltXCenter:0.000
TiltXScale:0.000
TiltYCenter:0.000
TiltYScale:0.000
LastButtonState:0x00000000
LastRawTouch:pointerCount=0
LastCookedTouch:pointerCount=0
Configuration:
ExcludedDeviceNames:[]
VirtualKeyQuietTime:250.0ms
PointerVelocityControlParameters:scale=1.000,lowThreshold=500.000,
highThreshold=3000.000,acceleration=3.000
WheelVelocityControlParameters:scale=1.000,lowThreshold=15.000,
highThreshold=50.000,acceleration=4.000
PointerGesture:
Enabled:true
QuietInterval:100.0ms
DragMinSwitchSpeed:50.0px/s
TapInterval:150.0ms
TapDragInterval:300.0ms
TapSlop:20.0px
MultitouchSettleInterval:100.0ms
MultitouchMinDistance:15.0px
SwipeTransitionAngleCosine:0.3
SwipeMaxWidthRatio:0.2
MovementSpeedRatio:0.8
ZoomSpeedRatio:0.3
TheBUGis(seethedumpsysoutput):
SurfaceWidth:1280px
SurfaceHeight:720px
Theresolutionshouldbe1920x1080(whichissettedupwiththe"boot.scr"file)
Ihackedsomethingsin"hidmultitouch.c"butdidn'tgetthistowork.The.idcfilesarealsoignored.
I'vetriedthefollowingfilenames:
/system/usr/idc/hidmultitouch.c
and
9/27
24/3/2016
Vendor_1aad_Product_000f.idc
aftertheconventionof:http://source.android.com/devices/tech/...files.html
Maybeanworkingidcfilewouldbethesolution.
Hereissomestufffrommydebugoutputofthehidmultitouch.candhidinput.cifithelps:
Code:Selectall
HID_UP_DIGITIZER#FORhidinput_configure_usage(id=[1],type=[0]:field[0],physical=
[0]),logical=[852002],ph_max=[0],log_max=[1]
HID_UP_GENDESK#FORhidinput_configure_usage(id=[1],type=[0]:field[3],physical=
HID_UP_DIITIZER#FORhidinput_configure_usage(id=[1],type=[0]:field[5],physical=
HID_UP_BUTTON#FORhidinput_configure_usage(id=[4],type=[0]:field[0],physical=
HID_UP_BUTTON#FORhidinput_configure_usage(id=[4],type=[0]:field[0],physical=
Thanks,
Dirk
dilo83
Posts:11
10/27
24/3/2016
Privatemessage
Top
bydilo83ThuJul11,20131:30am
Hi
todayicouldsolvetheproblem.
Firstthefilepermissionsoftheidcfilewerenotsettorootand644,thusthe.idcfilesareignoredby
android.
Forsecondihavetowrite"device.internal=1"intotheidcfiles.Somebodysaid,thattheresolutionfor
externaldevicesislimited(maybe?)butwithoutthisorwith"device.internal=0"itdoesnotwork.
Nowitworks.Manythanksforyourhelp.
P.S.inhttp://dev.odroid.com/projects/howtobuild4isantypobytheX2:
editdevice/hardkernel/odroidx/BoardConfig.mk
mustbe:
editdevice/hardkernel/odroidx2/BoardConfig.mk
inthisconfiganresolutionisdeclaredichangeditbutnothinghaschanged.Don'tknowforwhatthis
is.TheFixwiththeIDCFileworks.
dilo83
Posts:11
Privatemessage
Top
byodroidThuJul11,201311:37am
11/27
24/3/2016
Thankyouforthesharing.
IalsofixedthetypebytheX2.
odroid
SiteAdmin
Posts:14219
Location:SeoulKorea
ODROIDs:ODROID
Privatemessage
Top
byLeparti83TueJul16,201310:22pm
Hello
Ihavesimilarproblem,butthistricksdidn'tsolvetheproblem.ihaveEgalaxtouchscreencontrollerand
itis:0eef0001type.Touchscreenworksperfectlynormalotherwise,butithinkthereisproblemeither
calibrationorresolution.
ihave"Showtouches"and"Pointerlocation"checkedin"Setup"and"Developeroptions"andwheni
clickindisplayigetfollowingcoordinates:
Topleftcornerx=35,y=63
Toprightcornerx=1241,y=70
Bottomleftcornerx=35,y=655
Bottomrightcornerx=1241,y=655
SoitseemslikethereissmallersquareinsideactualscreenwherethePointermoves.Isthereany
possibilitiestochangecalibrationvaluessomewhere?oristhereanyothersolutiontofixthis?
Leparti83
Posts:9
Joined:TueMar05,201311:10pm
Privatemessage
Top
12/27
24/3/2016
byLeparti83FriJul19,20134:00am
Leparti83wrote:Hello
Ihavesimilarproblem,butthistricksdidn'tsolvetheproblem.ihaveEgalaxtouchscreen
controlleranditis:0eef0001type.Touchscreenworksperfectlynormalotherwise,buti
thinkthereisproblemeithercalibrationorresolution.
ihave"Showtouches"and"Pointerlocation"checkedin"Setup"and"Developeroptions"
andwheniclickindisplayigetfollowingcoordinates:
Topleftcornerx=35,y=63
Toprightcornerx=1241,y=70
Bottomleftcornerx=35,y=655
Bottomrightcornerx=1241,y=655
SoitseemslikethereissmallersquareinsideactualscreenwherethePointermoves.Isthere
anypossibilitiestochangecalibrationvaluessomewhere?oristhereanyothersolutiontofix
this?
Igotittoworkandifoundawayhowto"calibrate"touchscreen.igotRAWcalibrationdatathrough
"adbshell:Getevent"andtouchedallthescreencornersandsavedthecoordinatesigotthenichanged
thosevaluestoUsbtouchscreen.h
InmycaseichangedthevalueinEgalaxdisplayafter"{DEVTYPE_EGALAX]={"to"min_xc",
"max_xc"etc...andnowihaveworkingtouchscreen.
IalsoaddedinkernelmenuconfignewdisplaytypeEGALAX2withswappedandreversedaxis
Leparti83
Posts:9
Privatemessage
Top
bysonicxtacy02FriJul19,20135:43am
wouldyoumindsharingyour.hfiles?Wouldbeanawesomeservicetofuturebuildersusingthesame
hardware.
sonicxtacy02
Posts:31
Joined:ThuMay30,20135:08am
13/27
24/3/2016
ODROIDs:X2
Privatemessage
Top
byLeparti83FriJul19,201310:54pm
sonicxtacy02wrote:wouldyoumindsharingyour.hfiles?Wouldbeanawesomeserviceto
futurebuildersusingthesamehardware.
HereistheKconfigandUsbtouchreen.hpacked.
Attachments
touchscreen.tar.gz
(20KiB)Downloaded248times
Leparti83
Posts:9
Privatemessage
Top
bysonicxtacy02MonJul22,20133:09am
Leparti83wrote:
sonicxtacy02wrote:wouldyoumindsharingyour.hfiles?Wouldbean
awesomeservicetofuturebuildersusingthesamehardware.
Thankyouverymuch.I'veaddedthesefilesotthekernelandrebuiltbutitdoesntappeartofixmy
problemwiththeEgalaxtouchscreen.Thetouchscreenworks,butthetopportionofthescreencannotbe
pressedviathetouchscreen,asiftheresolutionoftheTSisincorrect.Thebottomofthescreenresponds
asitshould.Isthistheproblemyouhaveencountered?
14/27
24/3/2016
sonicxtacy02
Posts:31
ODROIDs:X2
Privatemessage
Top
byLeparti83TueJul23,20133:34am
sonicxtacy02wrote:
Leparti83wrote:
sonicxtacy02wrote:wouldyoumindsharingyour.hfiles?Would
beanawesomeservicetofuturebuildersusingthesamehardware.
Thankyouverymuch.I'veaddedthesefilesotthekernelandrebuiltbutitdoesntappearto
fixmyproblemwiththeEgalaxtouchscreen.Thetouchscreenworks,butthetopportionof
thescreencannotbepressedviathetouchscreen,asiftheresolutionoftheTSisincorrect.
Thebottomofthescreenrespondsasitshould.Isthistheproblemyouhaveencountered?
yeskindofsameproblem,butformeitwasaround50pixelsaroundscreenthatdidn'twork.Maybeyou
havetodosamecalibrationasidid.InAndroidrootuse(Geteventtl/dev/input/"whateverisyour
toucscreen")andtouchscreencornersandwritedownrawcoordinates.thenyoucanedittouchscreen.h
andwritethosevaluesinthatEgalax2.Hopefullythisisanyhelp
Leparti83
Posts:9
Privatemessage
Top
15/27
24/3/2016
bysonicxtacy02WedJul24,20139:47am
Leparti83wrote:
sonicxtacy02wrote:
Leparti83wrote:
sonicxtacy02wrote:wouldyoumindsharingyour.h
files?Wouldbeanawesomeservicetofuturebuilders
usingthesamehardware.
Thankyouverymuch.I'veaddedthesefilesotthekernelandrebuiltbutit
doesntappeartofixmyproblemwiththeEgalaxtouchscreen.Thetouchscreen
works,butthetopportionofthescreencannotbepressedviathetouchscreen,
asiftheresolutionoftheTSisincorrect.Thebottomofthescreenrespondsasit
should.Isthistheproblemyouhaveencountered?
yeskindofsameproblem,butformeitwasaround50pixelsaroundscreenthatdidn'twork.
Maybeyouhavetodosamecalibrationasidid.InAndroidrootuse(Geteventtl
/dev/input/"whateverisyourtoucscreen")andtouchscreencornersandwritedownraw
coordinates.thenyoucanedittouchscreen.handwritethosevaluesinthatEgalax2.
Hopefullythisisanyhelp
I'vetriedthis,makingchangesthe"Egalax"and"Egalax2"min_yinusbtouchscreen.cdoesntappearto
makeanychangestothecalibration.I'mcuriousastowhatinstructsthesystemtousetheEgalax2
descriptoroveranyotherone.Theonlyfilethatappearstomodifythetouchscreenbehaviorformeis
hidinput.c,thefileihadtomodifytocorrectthereversedaxisproblem.
Ifithelps,thenameofmydeviceingeteventiseGalaxIncUSBTouchcontroller
sonicxtacy02
Posts:31
ODROIDs:X2
Privatemessage
16/27
24/3/2016
Top
byLeparti83MonJul29,20134:26am
sonicxtacy02wrote:
Leparti83wrote:
sonicxtacy02wrote:
Leparti83wrote:
sonicxtacy02wrote:wouldyoumind
sharingyour.hfiles?Wouldbean
awesomeservicetofuturebuildersusing
thesamehardware.
Thankyouverymuch.I'veaddedthesefilesotthekerneland
rebuiltbutitdoesntappeartofixmyproblemwiththeEgalax
touchscreen.Thetouchscreenworks,butthetopportionofthe
screencannotbepressedviathetouchscreen,asiftheresolutionof
theTSisincorrect.Thebottomofthescreenrespondsasitshould.
Isthistheproblemyouhaveencountered?
yeskindofsameproblem,butformeitwasaround50pixelsaroundscreenthat
didn'twork.Maybeyouhavetodosamecalibrationasidid.InAndroidrootuse
(Geteventtl/dev/input/"whateverisyourtoucscreen")andtouchscreencorners
andwritedownrawcoordinates.thenyoucanedittouchscreen.handwrite
thosevaluesinthatEgalax2.Hopefullythisisanyhelp
I'vetriedthis,makingchangesthe"Egalax"and"Egalax2"min_yinusbtouchscreen.c
doesntappeartomakeanychangestothecalibration.I'mcuriousastowhatinstructsthe
systemtousetheEgalax2descriptoroveranyotherone.Theonlyfilethatappearstomodify
thetouchscreenbehaviorformeishidinput.c,thefileihadtomodifytocorrectthereversed
axisproblem.
Ifithelps,thenameofmydeviceingeteventiseGalaxIncUSBTouchcontroller
17/27
24/3/2016
Okithinkthatexplainedwhyitdon'tworkforyou.Formeandroiddidn'tevenregocnizethewhole
touchscreenatfirst.Iforcedthedrivertoworkwithmenuconfigandiset"egalax/egalax2"as"builtin"
(star)notasamodule"M"thatwayitsomehowforcesthatmydriverinsteadofhidinput.cwhichdidn't
workforme.Youcouldtrythesametrick.
Leparti83
Posts:9
Privatemessage
Top
bymikecwelSatAug03,20131:38am
Hello,
I'mredingthisthreadverycarfullybutIhavesomeproblems.
Imanagedtogetmytouchscreentowork(alilliput669resistivetouchscreenaneGalax?)
Itisaresistivetouchscreen
ButIhavesomepixelsAROUNDthescreenthandoesn'tseemtorespondtotouch.
withthiscommandiget
root@android:/dev#cat/proc/bus/usb/devices
P:Vendor=0eefProdID=0001Rev=1.00
S:Manufacturer=eGalaxInc.
S:Product=USBTouchController
withthiscommandiget
name:"eGalaxInc.USBTouchController"
events:
KEY(0001):0140*014a
MSC(0004):0004
inputprops:
<none>
18/27
24/3/2016
events:
KEY(0001):01100111
MSC(0004):0004
inputprops:
<none>
WiththiscommandIget
root@android:/#dumpsysinput
INPUTMANAGER(dumpsysinput)
EventHubState:
BuiltInKeyboardId:6
Devices:
4:eGalaxInc.USBTouchController
Classes:0x80000004
Path:/dev/input/event3
Descriptor:cddc04d4892194263bfe7aec89b063fd65abb0ca
Location:usbs5pehci2.3/input0
UniqueId:
Identifier:bus=0x0003,vendor=0x0eef,product=0x0001,version=0x0210
KeyLayoutFile:
KeyCharacterMapFile:
ConfigurationFile:
HaveKeyboardLayoutOverlay:false
InputReaderState:
Device4:eGalaxInc.USBTouchController
Generation:18
IsExternal:true
Sources:0x00006002
KeyboardType:0
MotionRanges:
TouchInputMapper:
Parameters:
GestureMode:spots
DeviceType:pointer
AssociatedDisplay:id=0,isExternal=false
OrientationAware:false
RawTouchAxes:
19/27
24/3/2016
TiltX:unknownrange
TiltY:unknownrange
TrackingId:unknownrange
Slot:unknownrange
Calibration:
SurfaceWidth:1280px
SurfaceHeight:720px
XScale:0.319
YScale:0.181
XPrecision:3.134
YPrecision:5.522
PressureScale:0.000
SizeScale:0.000
DistanceScale:0.000
HaveTilt:false
TiltXCenter:0.000
TiltXScale:0.000
TiltYCenter:0.000
TiltYScale:0.000
[0]:id=0,x=2728,y=1671,pressure=0,touchMajor=0,touchMinor=0,toolMajor=0,toolMinor=0,
orientation=0,tiltX=0,tiltY=0,distance=0,toolType=2,isHovering=true
[0]:id=0,x=860.992,y=291.730,pressure=0.000,touchMajor=0.000,touchMinor=0.000,
toolMajor=0.000,toolMinor=0.000,orientation=0.000,tilt=0.000,distance=0.000,toolType=2,
isHovering=true
PointerGestureDetector:
XMovementScale:0.208
YMovementScale:0.208
XZoomScale:0.078
YZoomScale:0.078
MaxSwipeWidth:1411.928955
Ihavethissettingindevtools:
screenlayout:0x10000023
density:1.0
densitydpi:160
20/27
24/3/2016
densitydpi:160
hightpixels:672
scaledensity:1.0
widthpixels:1280
xdpi:160.15764
ydpi:160.42105
CouldsomeonehelpmeanssaywhatIshoulddonexttogetmyfullscreenrespondingtotouch?
Thankyou
EDIT:
inmy/system/usr/idcfolderIdon'thavethehidmultitouch.candVendor_1aad_Product_000f.idcfiles
mikecwel
Posts:61
Joined:TueJul09,20133:51pm
languages_spoken:english,french,polish
ODROIDs:OdroidX2
Privatemessage
Top
byLeparti83WedAug07,20134:37am
mikecwelwrote:Hello,
I'mredingthisthreadverycarfullybutIhavesomeproblems.
Imanagedtogetmytouchscreentowork(alilliput669resistivetouchscreenaneGalax?)
Itisaresistivetouchscreen
ButIhavesomepixelsAROUNDthescreenthandoesn'tseemtorespondtotouch.
withthiscommandiget
root@android:/dev#cat/proc/bus/usb/devices
P:Vendor=0eefProdID=0001Rev=1.00
S:Manufacturer=eGalaxInc.
S:Product=USBTouchController
withthiscommandiget
21/27
24/3/2016
events:
KEY(0001):0140*014a
MSC(0004):0004
inputprops:
<none>
events:
KEY(0001):01100111
MSC(0004):0004
inputprops:
<none>
WiththiscommandIget
root@android:/#dumpsysinput
INPUTMANAGER(dumpsysinput)
EventHubState:
BuiltInKeyboardId:6
Devices:
4:eGalaxInc.USBTouchController
Classes:0x80000004
Path:/dev/input/event3
Descriptor:cddc04d4892194263bfe7aec89b063fd65abb0ca
Location:usbs5pehci2.3/input0
UniqueId:
Identifier:bus=0x0003,vendor=0x0eef,product=0x0001,version=0x0210
KeyLayoutFile:
KeyCharacterMapFile:
ConfigurationFile:
HaveKeyboardLayoutOverlay:false
InputReaderState:
Device4:eGalaxInc.USBTouchController
Generation:18
IsExternal:true
Sources:0x00006002
KeyboardType:0
MotionRanges:
TouchInputMapper:
Parameters:
GestureMode:spots
DeviceType:pointer
22/27
24/3/2016
DeviceType:pointer
AssociatedDisplay:id=0,isExternal=false
OrientationAware:false
RawTouchAxes:
TiltX:unknownrange
TiltY:unknownrange
TrackingId:unknownrange
Slot:unknownrange
Calibration:
SurfaceWidth:1280px
SurfaceHeight:720px
XScale:0.319
YScale:0.181
XPrecision:3.134
YPrecision:5.522
PressureScale:0.000
SizeScale:0.000
DistanceScale:0.000
HaveTilt:false
TiltXCenter:0.000
TiltXScale:0.000
TiltYCenter:0.000
TiltYScale:0.000
[0]:id=0,x=2728,y=1671,pressure=0,touchMajor=0,touchMinor=0,toolMajor=0,
toolMinor=0,orientation=0,tiltX=0,tiltY=0,distance=0,toolType=2,isHovering=true
[0]:id=0,x=860.992,y=291.730,pressure=0.000,touchMajor=0.000,touchMinor=0.000,
toolMajor=0.000,toolMinor=0.000,orientation=0.000,tilt=0.000,distance=0.000,
toolType=2,isHovering=true
PointerGestureDetector:
23/27
24/3/2016
YMovementScale:0.208
XZoomScale:0.078
YZoomScale:0.078
MaxSwipeWidth:1411.928955
Ihavethissettingindevtools:
screenlayout:0x10000023
density:1.0
densitydpi:160
hightpixels:672
scaledensity:1.0
widthpixels:1280
xdpi:160.15764
ydpi:160.42105
CouldsomeonehelpmeanssaywhatIshoulddonexttogetmyfullscreenrespondingto
touch?
Thankyou
EDIT:
inmy/system/usr/idcfolderIdon'thavethehidmultitouch.cand
Vendor_1aad_Product_000f.idcfiles
Wellyouwillnothavethat"Vendor_1aad_Product_000f.idc"sinceyourtouchcontrolleridshouldbe
"Vendor_0eef_Product_0001.idc"(youhaveexactlysamecontrollerasihave )
Thenyoucouldtry"geteventlt"commandtotrackyourkeypressesintouchscreen.Andtrypresscorner
andafterBTN_TOUCHDOWNyouseeABS_XandABS_Ywritedownthosevaluesandinwhat
corneryougetthosethendothesametorestofthecornersthoseareRAWrealcoordinates.Thenedit
"usbtouchscreen.c"andfindpartof#ifdefCONFIG_TOUCSCREEN_USB_EGALAXandinthere
.min_xcetc...youwillputthoserawcoordinatevaluestomin_xc,max_xcetcthensaveandrecomile
kerneletc...Tryyourtoucscreenifitwillstartworkthen
iforgotthatrawcoordinatesbythegeteventltshowsas"00000076b"orsimilarsoin
"usbtouchscreen.c"youneedtowritejust"0x076b"
Leparti83
Posts:9
Privatemessage
Top
24/27
24/3/2016
bycarlosgnetoWedAug14,20139:25pm
Dilo83.
Whichmonitoryouareusing,IneedtomonitorwithtouchforX2and
getnothing!
carlosgneto
Posts:8
Joined:MonFeb25,201312:22am
ODROIDs:odroidq
Privatemessage
Top
byinfographxSatOct05,20136:05pm
Hi,
I'mnewwithodroidx2andgotproblemconfiguringlinuxforkernelrecompilation,cansomeonecan
createanimagethatintegrateegalaxtouchandpostit?
SomeoneknowwhereicanfindapreconfiguredlinuxvmthatintegrateandroiddevToolsforodroid?
Also,IgotinstructionsandfilesfromeGalaxtomodifykerneltofullysupporttouchscreenwith
calibrationapp.Ifsomeonecanintegrateitinthekernelitcanbeusefulforall.
askmecodeifyouareinterrested.
infographx
Posts:1
Joined:TueOct01,20138:43pm
ODROIDs:odroidx2
Privatemessage
Top
bymikecwelThuMay15,20141:26am
25/27
24/3/2016
hello,
I'mcommingbackwiththisthredandIhopethatsomeone'gonnareaditandcouldhelpme.
SoIfollowedLEPARTI83toldmetodoandIgottherawcoordinatesofallcorners.
ButfromthesenumbershowIknowwhichoneistheminandtheotherthemaxasIhave4"X
coordinates"and4"Ycoordinates"?
AndasIcansee,mytouchscreenisnotrespondingallaroundthetheedgesofthescreen:icannot
accessthebottomdown,thefarleftsideandfarrightsideanndtheupperside
Anyhelp?
Thanks
mikecwel
Posts:61
Joined:TueJul09,20133:51pm
languages_spoken:english,french,polish
ODROIDs:OdroidX2
Privatemessage
Top
byLeparti83FriMay16,20145:54pm
mikecwelwrote:hello,
I'mcommingbackwiththisthredandIhopethatsomeone'gonnareaditandcouldhelpme.
SoIfollowedLEPARTI83toldmetodoandIgottherawcoordinatesofallcorners.
ButfromthesenumbershowIknowwhichoneistheminandtheotherthemaxasIhave4
"Xcoordinates"and4"Ycoordinates"?
AndasIcansee,mytouchscreenisnotrespondingallaroundthetheedgesofthescreen:i
cannotaccessthebottomdown,thefarleftsideandfarrightsideandtheupperside
Anyhelp?
Thanks
Youhavenow2Xcoordinatesforeachsideofthescreen.Itdoesn'tmatterthatmuchwhichoneyou
chooseofthosetwovalues.Example:youhavetwoleftsidexcoordinates(fromupperandlowercorner)
justpickoneofthoseandputinmin_xcvalue(ifirememberrightthatisforleftsidecoordinate)then
nextdothesameforrightside:chooseoneofthoserightsidexcoordinatesandputitinmax_xc...do
thissameprocedurealsoforbothycoordinates(min_ycandmax_yciquess?)
Leparti83
Posts:9
Privatemessage
26/27
24/3/2016
Top
byjesusangelThuJul23,20158:32pm
dilo83wrote:Ihackedsomethingsin"hidmultitouch.c"butdidn'tgetthistowork.The.idc
filesarealsoignored.I'vetriedthefollowingfilenames:
/system/usr/idc/hidmultitouch.c
and
Vendor_1aad_Product_000f.idc
Hi,Iknowthisanoldpost,but,haveyouVendor_1aad_Product_000f.idcfileandmodificationsyou
madetohidmultitouch.c??I'mfacingproblemswiththistouchscreen.
Thankyouinadvance.
jesusangel
Posts:1
Joined:ThuJul23,20158:20pm
languages_spoken:englishspanish
Privatemessage
Top
Displaypostsfromprevious: Allposts
Sortby Posttime
Ascending
Go
Postareply
26postsPage1of1
ReturntoAndroid
Jumpto: Android
Go
Whoisonline
Usersbrowsingthisforum:Noregisteredusersand1guest
Boardindex
TheteamDeleteallboardcookiesAlltimesareUTC+9hours
PoweredbyphpBBForumSoftwarephpBBGroup
27/27

Solution Screen Problem m4 Ss4040

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Solution Screen Problem m4 Ss4040

Încărcat de

Drepturi de autor:

Formate disponibile

24/3/2016

S-ar putea să vă placă și