Hello,
Currently i'm working on a personal project to integrate my GS3 into my car display and audio. Well this was easy with the help of a MHL or Allshare Cast Dongle.
My next goal was to install a 4 wire resistive touchscreen on my car display and use it as an external touchscreen control. I bought a 7" 4 wire resistive touchscreen with a USB module build around the CYPRESS CY7C63723C chip. I hooked up the touchscreen with OTG to test if there any initial reactions from my GS3, needless to say there wasn't any (no surprise there).
After a little digging around I came up with the conclusion that I need to create a custom "Input Device Configuration Files" for my touchscreen based on the following links
http://source.android.com/tech/input/touch-devices.html
http://source.android.com/tech/input/input-device-configuration-files.html
My initial question before I start plugging away with some codes is how would I name the files, the documents states "Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name." How would I find the product ID or the input device name for the touchscreen? I'm sure this can be done thru terminal or something but I am new to android development so cut me a little slack here
Also if you know of any Input device configuration files dealing with touchscreen please post it.
After digging thru dmesg I found this:
<6>[ 626.370303] hub 1-0:1.0: USB hub found
<6>[ 626.370334] hub 1-0:1.0: 1 port detected
<6>[ 626.684205] usb 1-1: new low speed USB device number 2 using msm_hsusb_host
<6>[ 626.844071] usb 1-1: New USB device found, idVendor=0eef, idProduct=0001
<6>[ 626.844132] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 626.844254] usb 1-1: Product: USB TouchController
<6>[ 626.844284] usb 1-1: Manufacturer: eGalax Inc.
Thus meaning my Input device configuration files should be named
USB_TouchController.idc or 0eef_XXXX_0001_XXXX.idc right? Anyone?
Either I have the name of the file wrong or my code is wrong I can not get any reaction from my Galaxy S3
Code:
device.internal = 0
touch.deviceType = touchScreen
touch.orientationAware = 1
cursor.mode = navigation
cursor.orientationAware = 1
touch.size.calibration = area
touch.size.scale = 28
touch.size.bias = 0
touch.size.isSummed = 0
touch.toolSize.calibration = area
touch.toolSize.areaScale = 22
touch.toolSize.areaBias = 0
touch.toolSize.linearScale = 6
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.0125
touch.orientation.calibration = vector
Can anyone help me
hi,
i want to do the same (sort off)
i want to make a padphone only for gs3.
:laugh:
keep up the work:good:
Thanks, still no progress on this can anyone help?
hechen said:
Thanks, still no progress on this can anyone help?
Click to expand...
Click to collapse
Hey mate, did you ever make any headway on this? I'm desperately trying to integrate ANY android device with GPS into my V36 skylines touch screen :'(
Im working on the same thing I got a 7inch touch kit with hdmi and 12v av trigger for reversing camera
The touch screen driver bord is cy7c63723c /e galaxy
Trying to run with android pc mk809iii
Should be a good carputer if I can get it to work
Any help would be good
Related
would it be possible for someone to build this driver for the SGSII
http://android.serverbox.ch/?p=285
ftdi_sio.ko
and
usbserial.ko
can someone compile these for me plese
i want to use the sgsII as my dashboad for my car but it connects via serial port to the ECU, i have chroot ubuntu 10.10 running on the sgsII so now all i need is the FTDI.ko file.
thanks in advance
You do run Ubuntu on SGS 2?
Emblema
Correct I have a working ch root I modified from a dell sterak one. Ill host it at some point with instructions.
The driver you asked
I got to compile those, for lite'ning 6.1 (android 2.3.4, kernel 2.6.36-11 ninphetamine 2.0.5+)
The modules loads with insmod:
{{{
# lsmod
ftdi_sio 25196 0 - Live 0xbf176000
usbserial 20872 1 ftdi_sio, Live 0xbf147000
dhd 245100 0 - Live 0xbf029000
j4fs 66440 1 - Live 0xbf013000 (P)
Si4709_driver 14444 0 - Live 0xbf00a000
bthid 2832 0 - Live 0xbf004000
vibrator 5408 2 - Live 0xbf000000
}}}
However from a console (I did not install ubuntoo), I plugged the device and still got in dmesg:
{{{
<6>[ 4367.754254] usb 2-1: new full speed USB device using s3c_otghcd and address 2
<3>[ 4367.771009] usb 2-1: device v0403 p6001 is not supported
<3>[ 4367.776871] hub 2-0:1.0: unable to enumerate USB device on port 1
}}}
I compiled the modules from https://github.com/Ninpo/ninphetamine/commit/2d1ffbcb9521299fdb53f681f65e7fe1230e0b32
If you still need those ko files, I attach them. I don't trust 100% my compilation (I had to cheat the versionmagic "+" in ninphetamine 2.0.5+), but they load OK according to lsmod and dmesg.
Please come back to me if you get some FTDI device to show in lsusb, or even better appear as ttyUSB device, I need that myself.
See http://forum.xda-developers.com/showthread.php?p=18081882#post18081882
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A
working usbserial.ko and ftdi_sio.ko
Thanks to siniy and many others, I have now been able to plug a FTDI USB device and get corresponding ttyUSB0, on a kernel based on ninphetamine. You will need a kernel and can't just do with a driver (the kernel must be compiled to accept that familly of devices).
Hi Folks!
I'm a happy owner of a Galaxy Tab 10.1, and an EE engineer who frequently uses a small USB microscope while assembling boards.
I would be really happy to be able to use my Galaxy Tab as a lightweight portable screen for this microscope. This would be much more handy than having a bulky laptop stand in there.
So I've seen that the Galaxy Tab 10.1 has USB host capabilities. And after a quick verification, I've noted that the stock kernel has the uvcvideo driver builtin (the microscope is UVC compatible, actually it's a Logitech C310 hardware with added optics).
Seems like everything is in place to make it work. However when I plug the device in, I get an unrecognized USB device message popping up.
Here's the output from dmesg:
Code:
<6>[11734.027241] Board P4 : tegra_otg_en = 1<6>[11734.037361] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[11734.037391] tegra-otg tegra-otg: tegra_start_host+
<4>[11734.038884] tegra_usb_phy_open() called instance :0
<6>[11734.038966] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[11734.039001] utmi_phy_power_on() called. instance : 0
<6>[11734.040244] tegra-otg tegra-otg: Acc power on detect
<6>[11734.057205] Board P4 : tegra_acc_power token : (1,1) on
<4>[11734.057234] utmi_phy_clk_enable() called. instance : 0
<6>[11734.058757] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[11734.059016] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[11734.067158] [ CONNECTOR_DRIVER (acc_notified,387) ] ACCESSORY=OTG : STATE=online
<6>[11734.087920] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[11734.107159] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[11734.107282] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[11734.107306] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[11734.107326] usb usb1: Product: Tegra EHCI Host Controller
<6>[11734.107343] usb usb1: Manufacturer: Linux 2.6.36.3 ehci_hcd
<6>[11734.107359] usb usb1: SerialNumber: tegra-ehci.0
<6>[11734.111805] hub 1-0:1.0: 1 port detected
<6>[11734.113078] tegra-otg tegra-otg: tegra_start_host-
<6>[11734.113101] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[11734.327059] usb 1-1: new high speed USB device using tegra-ehci and address 2
<3>[11734.592745] usb 1-1: device v046d p081b is not supported
<6>[11734.618692] host_notify: ndev name=tegra-ehci.0: from state=0 -> to state=5
<3>[11734.620877] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11734.787068] usb 1-1: new high speed USB device using tegra-ehci and address 3
<3>[11735.040504] usb 1-1: device v046d p081b is not supported
<6>[11735.076960] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.077029] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.237112] usb 1-1: new high speed USB device using tegra-ehci and address 4
<3>[11735.505766] usb 1-1: device v046d p081b is not supported
<6>[11735.528455] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.528541] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.687712] usb 1-1: new high speed USB device using tegra-ehci and address 5
<3>[11735.950203] usb 1-1: device v046d p081b is not supported
<6>[11735.978040] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.978125] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.137097] usb 1-1: new high speed USB device using tegra-ehci and address 6
<3>[11736.393178] usb 1-1: device v046d p081b is not supported
<6>[11736.417207] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.419203] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.580821] usb 1-1: new high speed USB device using tegra-ehci and address 7
<3>[11736.840702] usb 1-1: device v046d p081b is not supported
<6>[11736.866992] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.867057] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.027074] usb 1-1: new high speed USB device using tegra-ehci and address 8
<3>[11737.279441] usb 1-1: device v046d p081b is not supported
<6>[11737.306990] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.307086] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.467126] usb 1-1: new high speed USB device using tegra-ehci and address 9
<3>[11737.736913] usb 1-1: device v046d p081b is not supported
<6>[11737.758513] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.758578] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.916947] usb 1-1: new high speed USB device using tegra-ehci and address 10
[email protected]:/ $ dmesg
Then it goes on and on with the 'new device [...] unable to enumerate' messages until I unplug it.
The device is found, and early init seems to go through (VID/PID are correct) but it doesn't seem to make it to the uvcvideo driver (or the driver is rejecting it, I don't know).
I am not very savvy as regards to linux's USB stack (though I know my way around linux, having cross compiled it, and tweaked it several times for boards I design), so I'm a bit lost as to what I could further investigate to pinpoint the issue.
I am certain that uvcvideo is present (dmesg shows 'usbcore: registered new interface driver uvcvideo' after boot).
Things works fine when I plug in a USB flash drive.
Things works fine too when I plug the microscope to my linux desktop (through uvcvideo).
Any idea or advices would be greatly appreciated!
Thanks,
Theo
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi tbeauchant,
I am also looking for same , till now i didn't get any success but after going through with the code , i have seen that samsung have disable the feature of detecting a few device , in my case it says , unkown usb device and
dmesg says :: device ######(product id) ######(vendor id) not supported ,
did you get any success or any approch which you will follow.
Hi,
I am trying to use a Columbus V800+ usb gps (mtk3329) with my Alwinner A10 tablet. Current rom is Cyanogenmod 10 - 20130327. kernel 3.0.36+. After connecting gps, lsusb show up: Bus 01 Device 008: ID 0e8d:3329. Using USB info apk I got: /dev/bus/usb/001/008 assigned to mtk gps. Seems that device was detected, but I can not use it. I tried to find the CDC-ACM.ko module in lib/modules, but there is no such file.
dmesg after inserting gps:
insmod_host_driver
[sw_hcd0]: sw_usb_host0_enable start
-----------------sw_hcd0_soft_disconnect----------
[sw_hcd0]: open_usb_clock
[sw_hcd0_host0]:set USB power ON
[sw_hcd0]:sw_usb_host0-enable end
-----------------IRQ CONNECT-----------------------
[sw_hcd0]: reset port
[sw_hcd0]:reset port stopped
spurious?
usb 1-1 new full speed USB device number 2 using sw_hcd_host0
[sw_hcd0]: reset port
[sw_hcd0]:reset port stopped
[sw_hcd0]:sw_hcd_h_disable, epnum = 0
[sw_hcd0]:sw_hcd_h_disable, epnum = 0
Does anyone knows how to get the gps working ? I am new to android, but reads a lot.
Thank you in advance.
Hello,
I tested with three different REDMI 3 devices and three different rom versions and have the following problem:
initially everything with connecting an external usb camera was ok. My usb camera app received events asking for permissions for using usb camera. But after 3 or 4 full charges the app stopped receiving permissions. I checked with couple other apps but again no permission. If my battery drops under 60% suddenly everything is ok again and the app detects the camera. It is stranger, that before full detect of the camera the app starts some kind of permission loop. I click allow and after 2 seconds the permission dialog shows again and so on... I checked the source code and appears my USBManager returns empty device list. For me it looks like some kind of battery optimizer or usb state optimizer doing it. I will be more than happy if someone can help me with this issue. Additionally I checked with all other stock rom version. It is all the same.
Here is some log from dmsg.
Code:
<6>[12449.627983] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12449.647323] psy->name:usb
<6>[12449.652992] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12449.653558] healthd: battery l=94 v=4240 t=22.3 h=2 st=4 c=382 chg=
<6>[12449.744320] msm_hsusb_host msm_hsusb_host: EHCI Host Controller
<6>[12449.744844] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[12449.751356] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0x078d9000
<6>[12449.769480] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[12449.769624] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[12449.769636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[12449.769646] usb usb1: Product: EHCI Host Controller
<6>[12449.769656] usb usb1: Manufacturer: Linux 3.10.49-perf-g48b885e ehci_hcd
<6>[12449.769665] usb usb1: SerialNumber: msm_hsusb_host
<6>[12449.772688] hub 1-0:1.0: USB hub found
<6>[12449.772729] hub 1-0:1.0: 1 port detected
<6>[12449.876761] msm_otg 78d9000.usb: USB in low power mode
<6>[12450.296922] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12450.519306] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<6>[12450.949089] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<6>[12451.619450] usb 1-1: new high-speed USB device number 5 using msm_hsusb_host
<11>[12452.316729] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<11>[12453.339456] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12453.759449] usb 1-1: new high-speed USB device number 13 using msm_hsusb_host
<6>[12455.879543] usb 1-1: new high-speed USB device number 21 using msm_hsusb_host
<6>[12456.212015] XXX::smb358_get_prop_batt_status:reg=0x0
<6>[12456.216663] psy->name:rk-bat
<6>[12456.216678] status=3, percent=94
<6>[12456.216684] status=3, percent=94
<6>[12456.222182] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12456.222723] healthd: battery l=94 v=4248 t=22.4 h=2 st=4 c=401 chg=
<6>[12456.319281] usb 1-1: new high-speed USB device number 22 using msm_hsusb_host
<11>[12457.382047] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<6>[12457.499222] usb 1-1: new high-speed USB device number 26 using msm_hsusb_host
<11>[12458.407239] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12458.899381] usb 1-1: new high-speed USB device number 31 using msm_hsusb_host
<6>[12459.339269] usb 1-1: new high-speed USB device number 32 using msm_hsusb_host
Im now at tampered rom (the rom says miui global 7.1 | 7.1.1.0.0 stable) it not real global rom! gold colour. but i dont have any problem with otg or battery drops. All working fine. Except a few settings turns back to default if i reset the device. But its doesnt bothered me much.
Hey guys,
Currently i`m digging into this matter. So here's the concept:
[HU] - one of the back USB's
|
[USB Hub] - powered form an external power supply (external 5V)
| |
U1 U2 - (32GB USB Drives)
A.) Current behaviour
- only the first inserted USB drive get's mounted under /mnt/usb_storage2
- the second usb drive is recognised by the kernel and does not get mounted by the system (not assigned to any "drive letter" so to speak(i think)).
B.) Current investigations:
B.1 ) by unpacking the boot.img - fstab.rk30board.bootmode.*
Code:
/devices/platform/usb20_otg/usb /mnt/usb_storage vfat defaults voldmanaged=usb_storage:auto
/devices/platform/usb20_host/usb /mnt/usb_storage2 vfat defaults voldmanaged=usb_storage2:auto
B.2) by unpacking the boot.img - init.rk30board.rc
Code:
[13] export THIRD_VOLUME_STORAGE /mnt/usb_storage
[14] mkdir /mnt/usb_storage 0000 system system
[15] export THIRD_VOLUME_STORAGE2 /mnt/usb_storage2
[16] mkdir /mnt/usb_storage2 0000 system system
On the Application Side, for example MTCAPKInstall_source/com/hct/apkinstall/DevListAdapter.java
Code:
} else if (path.equals("/mnt/usb_storage")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb1));
} else if (path.equals("/mnt/usb_storage2")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb2));
This can be solved easily by creating a for, or by duplication each else if (the copy/paste way )
I need to do some more tests... i`m also interested for your opinions/experience with this (What have you tested, What worked, What did not work, Why is not working, etc..)
So cheers to everyone and keep you posted
So far i rulled out the usb driver, internal hub.. It has something to do with the block creation and vold...
Will dig more tomorrow(i hope)
okey, so baseline the issue is related to VOLD
VOLD does not generate the block device for the new devices... i`m not 100% sure that VOLD handles the block device generation
for the time being i managed to mount 3 separate partitions from the same USB storage -> by doing this i ruled out the kernel itself, the irq assignment, etc..
I need to dig deeper into VOLD and to see exactly what is the process for generating the block device eg (/dev/block/vold/8:X)
from this point it would be nice to exchange some experience with someone that really know how things work on Android, i`m an iOS user, and the HU is my first Android System
I can't help as haven't gone down the road of digging to deep into kernels and Roms due to other commitments..
But just want to offer words of encouragement as you are working towards a good course..
I don't use a mobile modem and so at the moment that spare usbport is doing nothing. Would be nice to load it up with a spare USB drive I have around here .
That then brings up the powering up thread which the boys have already sorted..
So once you crack this and get a kernel mode going we are good to go..
Sent from my SM-G900I using Tapatalk
I tried to have a look in the binary code of vold shipped with the firmware, but friday was short... I'll continue my work next week
Keep you guys posted
In the past i did some test with a 4 Port USB hub. I connected several USB sticks and a 350 gb harddisk. They were not recognised by rootexplorer or android itself, but ESF file Explorer did recognised all of the devices.
Another strange thing is that when i connect a USB RTL dab+ dongle on the First USB Port on my hui and the harddisk on the other usb port my GPS is not working propperly.
well i`m 100% sure that the hub is not the issue, because:
<<1'st usb drive>>
<6>[ 1757.992589] usb 2-1.3: new high speed USB device number 30 using usb20_host
<6>[ 1758.093203] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5204
<6>[ 1758.093230] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1758.093282] usb 2-1.3: Product: Cruzer Crossfire
<6>[ 1758.093303] usb 2-1.3: Manufacturer: SanDisk Corporation
<6>[ 1758.093322] usb 2-1.3: SerialNumber: 000016A29874531B
<4>[ 1758.094142] --mtc usb storage 2-1.3 0781 5204
<6>[ 1758.094989] scsi11 : usb-storage 2-1.3:1.0
<5>[ 1759.092957] scsi 11:0:0:0: Direct-Access SanDisk Cruzer 4.05 PQ: 0 ANSI: 2
<5>[ 1759.094087] sd 11:0:0:0: [sda] 16055949 512-byte logical blocks: (8.22 GB/7.65 GiB)
<5>[ 1759.094577] sd 11:0:0:0: [sda] Write Protect is off
<7>[ 1759.094601] sd 11:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1759.095072] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.095095] sd 11:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1759.098162] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.098183] sd 11:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1759.100316] sda: sda1
<3>[ 1759.104583] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.104621] sd 11:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1759.104663] sd 11:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1759.846560] SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
<<2'nd usb drive>>
<6>[ 1956.392593] usb 2-1.2: new high speed USB device number 31 using usb20_host
<6>[ 1956.493577] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1666
<6>[ 1956.493616] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1956.493647] usb 2-1.2: Product: DataTraveler 3.0
<6>[ 1956.493666] usb 2-1.2: Manufacturer: Kingston
<6>[ 1956.493683] usb 2-1.2: SerialNumber: 60A44C425294BE10A9820D20
<4>[ 1956.494632] --mtc usb storage 2-1.2 0951 1666
<4>[ 1960.190620] ~ arm_rev_16bits err0 0
the GUI applications are dependent of Device Block Assignment, as you can clearly see, kernel recognises both USB Storage devices, but only the first is assigned with a block device.
okey, so i had a chance to check with IDA the vold binary from our units... seems that vold binary is custom than from other rom's
i will do some tests on the unit itself with a modified version of vold to see what happens
Later Edit,
vold has nothing to do with the block assignment ... on the front USB port also known by the unit : usb20_otg works like a charm... i added 4 USB Drivers each one named accordingly -> sda, sdb, etc.. i managed to mount them manually -> success
On the rear USB also known by the unit usb20_hub it still does not work, VOLD was stopped and removed during tests
clearly things do not add up.. and VOLD so far seems to be ok..
i ran out of ideas
i'm not a developer, but if you find a solution for that problem, you'll be a hero. hope you have finally the idea that will be the right one