Request Android touch screen support here.
-
- Posts: 68
- Joined: Thu Apr 27, 2017 3:33 am
- languages_spoken: French, English
- ODROIDs: Odroid C2
USB GPS, Bluetooth, Wifi
Emmc 8g Android M
Rtc modue - Contact:
Re: Request Android touch screen support here.
Thank's I wait for your return =)
Edit 1.0:
Good news for me I see the commit for my screen
https://github.com/hardkernel/linux/tre ... -android-m
Edit 2.0:
On your next release can you activate mobprob module please
Now I wait for your release =)
Edit 1.0:
Good news for me I see the commit for my screen
https://github.com/hardkernel/linux/tre ... -android-m
Edit 2.0:
On your next release can you activate mobprob module please
Now I wait for your release =)
Last edited by InspecteurGadget on Tue May 01, 2018 7:41 am, edited 1 time in total.
-
- Posts: 8
- Joined: Sat Jan 13, 2018 4:07 am
- languages_spoken: english
- ODROIDs: XU4
- Contact:
Re: Request Android touch screen support here.
The terminal app on the odroid XU4?odroid wrote:@eiest1,
Check "dmesg" output on the terminal app.
-
- Posts: 68
- Joined: Thu Apr 27, 2017 3:33 am
- languages_spoken: French, English
- ODROIDs: Odroid C2
USB GPS, Bluetooth, Wifi
Emmc 8g Android M
Rtc modue - Contact:
Re: Request Android touch screen support here.
Yeseiest1 wrote:The terminal app on the odroid XU4?odroid wrote:@eiest1,
Check "dmesg" output on the terminal app.
-
- Posts: 8
- Joined: Sat Jan 13, 2018 4:07 am
- languages_spoken: english
- ODROIDs: XU4
- Contact:
Re: Request Android touch screen support here.
I checked the dmesg output is there anything I should be specifically looking for?InspecteurGadget wrote:Yeseiest1 wrote:The terminal app on the odroid XU4?odroid wrote:@eiest1,
Check "dmesg" output on the terminal app.
-
- Posts: 1
- Joined: Thu Jul 12, 2018 11:46 pm
- languages_spoken: english, german
- Contact:
Re: Request Android touch screen support here.
VID: 04e7
PID: 0020
Brand Name: ELO 2244L 22-inch Touchmonitor
Board: XU4
Thanks !
PID: 0020
Brand Name: ELO 2244L 22-inch Touchmonitor
Board: XU4
Thanks !
- codewalker
- Posts: 515
- Joined: Mon Feb 25, 2013 11:03 am
- languages_spoken: english
- ODROIDs: all
- Contact:
Re: Request Android touch screen support here.
It was already included.
#define USB_VENDOR_ID_ELO 0x04E7
#define USB_DEVICE_ID_ELO_TS2515 0x0022
#define USB_DEVICE_ID_ELO_TS2700 0x0020
#define USB_DEVICE_ID_ELO_1919L 0x0073
#define USB_DEVICE_ID_ELO_5010 0x0041
#define USB_DEVICE_ID_ELO_5020 0x0042
#define USB_DEVICE_ID_ELO_3243L0027 0x0027
#define USB_DEVICE_ID_ELO_3243L2400 0x2400
https://github.com/hardkernel/linux/blo ... /hid-ids.h
#define USB_VENDOR_ID_ELO 0x04E7
#define USB_DEVICE_ID_ELO_TS2515 0x0022
#define USB_DEVICE_ID_ELO_TS2700 0x0020
#define USB_DEVICE_ID_ELO_1919L 0x0073
#define USB_DEVICE_ID_ELO_5010 0x0041
#define USB_DEVICE_ID_ELO_5020 0x0042
#define USB_DEVICE_ID_ELO_3243L0027 0x0027
#define USB_DEVICE_ID_ELO_3243L2400 0x2400
https://github.com/hardkernel/linux/blo ... /hid-ids.h
-
- Posts: 11
- Joined: Tue Aug 21, 2018 4:11 pm
- languages_spoken: english
- Contact:
Re: Request Android touch screen support here.
Hello all,
Before posting a question or a request, I tried to review all posts that are talking about PQ Labs overlay frame because it's what I'd like to make it works at home. And I have to say that it's ot clear to me at all after this posts review.
I have a G4 PQLabs system and I understood from PQLabs support that there is a need to build an Android version with the driver they sent me to make this G4 product working with another hardware than their iStick.
So, is there already an android version available somewhere with these drivers and working on a Odroid UX4 ?
Shall I build my own version ? (which is a huge challenge for me as I never build any Android version before and I'm not a software guy)
Thanks in advance to provide some help or some guide lines
Before posting a question or a request, I tried to review all posts that are talking about PQ Labs overlay frame because it's what I'd like to make it works at home. And I have to say that it's ot clear to me at all after this posts review.
I have a G4 PQLabs system and I understood from PQLabs support that there is a need to build an Android version with the driver they sent me to make this G4 product working with another hardware than their iStick.
So, is there already an android version available somewhere with these drivers and working on a Odroid UX4 ?
Shall I build my own version ? (which is a huge challenge for me as I never build any Android version before and I'm not a software guy)
Thanks in advance to provide some help or some guide lines
justin_h wrote:Hello,
Can you tell me if this touchscreen will work with ODROID C2 or UX4 and Android:
1. VID : 1EF1
2. PID: 0057
3. PQLabs
4. C2 or UX4 (with Android)
- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
XU4 Android OS already included the VID:PID. But we have no idea whether it worked or not since we can't buy all the different touchscreen overlays.
https://github.com/hardkernel/linux/blo ... 1059-L1061
https://github.com/hardkernel/linux/blo ... 1059-L1061
-
- Posts: 11
- Joined: Tue Aug 21, 2018 4:11 pm
- languages_spoken: english
- Contact:
Re: Request Android touch screen support here.
Thank you for this quick answer.
And sorry for the dummy question but that means I can test with teh latest android version available on the hardkernel wiki ?
And sorry for the dummy question but that means I can test with teh latest android version available on the hardkernel wiki ?
odroid wrote:XU4 Android OS already included the VID:PID. But we have no idea whether it worked or not since we can't buy all the different touchscreen overlays.
https://github.com/hardkernel/linux/blo ... 1059-L1061
- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
Right. You don't need to build the Android OS from the source code. Just flash the pre-built OS image and run it.Sprint95 wrote:Thank you for this quick answer.
And sorry for the dummy question but that means I can test with teh latest android version available on the hardkernel wiki ?
-
- Posts: 9
- Joined: Wed Feb 27, 2013 9:20 pm
- languages_spoken: english
- ODROIDs: U2
- Contact:
Re: Request Android touch screen support here.
1. VID 0483
2. PID 5750
3. ByQDtech
4. 7 inch 1024x600 capacitive hid-multitouch USB HID v1.10 Device
5. C2
Thank you
2. PID 5750
3. ByQDtech
4. 7 inch 1024x600 capacitive hid-multitouch USB HID v1.10 Device
5. C2
Thank you
-
- Posts: 9
- Joined: Wed Feb 27, 2013 9:20 pm
- languages_spoken: english
- ODROIDs: U2
- Contact:
Re: Request Android touch screen support here.
Hello,
Is somone still following this forum? Can you help please?
7 days for response is gone and there is no reply yet
Is somone still following this forum? Can you help please?
7 days for response is gone and there is no reply yet

- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
@waldorf,
Sorry. We will check it soon.
Sorry. We will check it soon.
-
- Posts: 9
- Joined: Wed Feb 27, 2013 9:20 pm
- languages_spoken: english
- ODROIDs: U2
- Contact:
Re: Request Android touch screen support here.
@odroid
Please check indeed.
Do you need any info from me?
Please check indeed.
Do you need any info from me?
- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
@waldorf,
The VID/PID was added.
We will release a update package within a few days.
The VID/PID was added.
We will release a update package within a few days.
-
- Posts: 1
- Joined: Tue Sep 18, 2018 10:18 am
- languages_spoken: english
- ODROIDs: C1+
- Contact:
Re: Request Android touch screen support here.
1. VID : 0x04DD
2. PID : 0x991C
3. Brand : SHARP
4. Model Name : TSLV238
5. C1+, C2
2. PID : 0x991C
3. Brand : SHARP
4. Model Name : TSLV238
5. C1+, C2
- tobetter
- Posts: 2631
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: X, X2, U2, U3, XU3, C1
- Location: Paju, South Korea
- Contact:
Re: Request Android touch screen support here.
@hhleejh, could you try new release for ODROID-C2?hhleejh wrote:1. VID : 0x04DD
2. PID : 0x991C
3. Brand : SHARP
4. Model Name : TSLV238
5. C1+, C2
https://wiki.odroid.com/odroid-c2/os_im ... allow_v4.5
-
- Posts: 9
- Joined: Tue Oct 02, 2018 6:40 pm
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
1. VID : 04e7
2. PID : 0050
3. Brand : ELO
4. Model Name : ET1590L
5. C2
EDIT (Some extra information):
This is working fine on the odroid with Ubunutu, but not with the Android image.
Output of lsusb (run on Ubuntu):
2. PID : 0050
3. Brand : ELO
4. Model Name : ET1590L
5. C2
EDIT (Some extra information):
This is working fine on the odroid with Ubunutu, but not with the Android image.
Output of lsusb (run on Ubuntu):
Code: Select all
Bus 001 Device 006: ID 04e7:0050 Elo TouchSystems 2216 AccuTouch® Touchmonitor Interface
- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
The latest C2 Android update added a new feature that user can add a VID/PID for testing.JOSH wrote:1. VID : 04e7
2. PID : 0050
3. Brand : ELO
4. Model Name : ET1590L
5. C2
EDIT (Some extra information):
This is working fine on the odroid with Ubunutu, but not with the Android image.
Output of lsusb (run on Ubuntu):
Code: Select all
Bus 001 Device 006: ID 04e7:0050 Elo TouchSystems 2216 AccuTouch® Touchmonitor Interface
viewtopic.php?f=137&t=19203#p236080
-
- Posts: 9
- Joined: Tue Oct 02, 2018 6:40 pm
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
Thanks odroid. I have tried this but it doesn't seem to work.
I've contacted the ELO customer support about this, so far the response is that this screen won't work with android because the "accutouch" technology requires drivers.
The suggestion is to move to a PCAP display. Unfortunately I don't think that will work for me because the screen is being used with rubber gloves.
In theory if I can get them to provide drivers I should be able to make this work though, right? Do you have any suggestions about getting this working?
I've contacted the ELO customer support about this, so far the response is that this screen won't work with android because the "accutouch" technology requires drivers.
The suggestion is to move to a PCAP display. Unfortunately I don't think that will work for me because the screen is being used with rubber gloves.
In theory if I can get them to provide drivers I should be able to make this work though, right? Do you have any suggestions about getting this working?
- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
If your ELO touchscreen works in standard HID multitouch protocol, it should work with C2 Android.
Can you show us your modified /internal/boot.ini file for the latest Android 6.0 v4.7 release?
Can you show us your modified /internal/boot.ini file for the latest Android 6.0 v4.7 release?
-
- Posts: 9
- Joined: Tue Oct 02, 2018 6:40 pm
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
I'm not sure how to determine whether it uses that standard protocol, but my guess is that it doesn't. They call it "accutouch" which I guess is a different protocol.odroid wrote:If your ELO touchscreen works in standard HID multitouch protocol, it should work with C2 Android.
Here it is:odroid wrote:Can you show us your modified /internal/boot.ini file for the latest Android 6.0 v4.7 release?
Code: Select all
ODROIDC2-UBOOT-CONFIG
setenv dtbaddr 0x1000000
setenv loadaddr 0x20000000
# Resolution Configuration
# 'hdmimode' must be one of below to configure display resolution within
# supported by your TV or monitor.
# Symbol | Resolution
# ----------------------+-------------
# "480x320p60hz" | 480x320 Progressive 60Hz
# "480p60hz" | 720x480 Progressive 60Hz
# "576p50hz" | 720x576 Progressive 50Hz
# "720p60hz" | 1280x720 Progressive 60Hz
# "720p50hz" | 1280x720 Progressive 50Hz
# "1080p60hz" | 1920x1080 Progressive 60Hz
# "1080p50hz" | 1920x1080 Progressive 50Hz
# "1080p30hz" | 1920x1080 Progressive 30Hz
# "1080p24hz" | 1920x1080 Progressive 24Hz
# "1080i60hz" | 1920x1080 Interlaced 60Hz
# "1080i50hz" | 1920x1080 Interlaced 50Hz
# "2160p60hz" | 3840x2160 Progressive 60Hz
# "2160p50hz" | 3840x2160 Progressive 50Hz
# "2160p30hz" | 3840x2160 Progressive 30Hz
# "2160p25hz" | 3840x2160 Progressive 25Hz
# "2160p24hz" | 3840x2160 Progressive 24Hz
# "2160p60hz420" | 3840x2160 Progressive 60Hz YCbCr 4:2:0
# "2160p50hz420" | 3840x2160 Progressive 50Hz YCbCr 4:2:0
# "640x480p60hz" | 640x480 Progressive 60Hz
# "800x480p60hz" | 800x480 Progressive 60Hz
# "800x600p60hz" | 800x600 Progressive 60Hz
# "1024x600p60hz" | 1024x600 Progressive 60Hz
# "1024x768p60hz" | 1024x768 Progressive 60Hz
# "1280x800p60hz" | 1280x800 Progressive 60Hz
# "1280x1024p60hz" | 1280x1024 Progressive 60Hz
# "1360x768p60hz" | 1360x768 Progressive 60Hz
# "1440x900p60hz" | 1440x900 Progressive 60Hz
# "1600x900p60hz" | 1600x900 Progressive 60Hz
# "1600x1200p60hz" | 1600x1200 Progressive 60Hz
# "1680x1050p60hz" | 1680x1050 Progressive 60Hz
# "1920x1200p60hz" | 1920x1200 Progressive 60Hz
# "2560x1080p60hz" | 2560x1080 Progressive 60Hz
# "2560x1440p60hz" | 2560x1440 Progressive 60Hz
# "2560x1600p60hz" | 2560x1600 Progressive 60Hz
# "3440x1440p60hz" | 3440x1440 Progressive 60Hz
setenv hdmimode "1080p60hz"
setenv rootopt "root=/dev/mmcblk0p2 rw init=/init rootwait"
setenv consoleopt "console=ttyS0,115200"
setenv androidopt "androidboot.hardware=odroidc2 androidboot.serialno=${fbt_id#}"
setenv logoopt "osd1,loaded,${fb_addr},${hdmimode}"
setenv selinuxopt "androidboot.selinux=disabled"
# HDMI/DVI Mode Configuration
# This will enforce the signal type of display
# "hdmi" - For HDMI interface
# "dvi" - For DVI interface
setenv vout_mode "hdmi"
# Display Auto Detection
# "false" or "true"
setenv display_autodetect "true"
# HPD enable/disable option
setenv disablehpd "false"
# Overscan offset configuration
# All offsets are zero and can be tuned by manual or ODROID Utility
setenv overscan_top "0"
setenv overscan_left "0"
setenv overscan_bottom "0"
setenv overscan_right "0"
setenv led_onoff "on"
suspend_hdmiphy=0
# Force HDMI to use RGB colorspace regardless of TV request
setenv hdmi_forcergb "0" # Disabled
# setenv hdmi_forcergb "1" # Enabled
# max cpu frequency in dvfs table / in MHz unit
# setenv max_freq "2016" # 2.016GHz
# setenv max_freq "1944" # 1.944GHz
# setenv max_freq "1920" # 1.920GHz
# setenv max_freq "1896" # 1.896GHz
# setenv max_freq "1752" # 1.752GHz
# setenv max_freq "1680" # 1.680GHz
# setenv max_freq "1656" # 1.656GHz
# setenv max_freq "1536" # 1.536GHz
setenv max_freq "1536"
# max cpu-cores
# setenv maxcpus "1"
# setenv maxcpus "2"
# setenv maxcpus "3"
setenv maxcpus "4"
# disable vu7
setenv disable_vu7 "true"
# invert touch screen x,y
setenv touch_invert_x "false"
setenv touch_invert_y "false"
# gpio power key : J2 (2x20) Pin#35, GPIOY.BIT3
#setenv gpiopower "214"
# usb timing tweak
setenv usbmulticam "false"
setenv hdmitx "hdmitx=${cecconfig}"
if test "${hdmi_forcergb}" = "1"; then setenv hdmitx "hdmitx=forcergb"; fi
if test "${display_autodetect}" = "true"; then usb pwren; hdmitx edid; fi
if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi
# Enable backlight_pwm
# disable : backlight "no"
# ODROID-VU5/7 : backlight "yes"
# ODROID-VU8 : backlight "invert"
setenv backlight_pwm "no"
setenv test_mt_vid "04e7"
setenv test_mt_pid "0050"
showddrclk
setenv bootargs "${rootopt} ${consoleopt} hdmimode=${hdmimode} ${cmode} ${hdmitx} vout=${vout_mode} disablehpd=${disablehpd} logo=${logoopt} ${androidopt} ${selinuxopt} suspend_hdmiphy=${suspend_hdmiphy} led_onoff=${led_onoff} max_freq=${max_freq} maxcpus=${maxcpus} disable_vu7=${disable_vu7} touch_invert_x=${touch_invert_x} touch_invert_y=${touch_invert_y} usbmulticam=${usbmulticam} gpiopower=${gpiopower} backlight_pwm=${backlight_pwm} ddrclock=${ddrclock} test_mt_pid=${test_mt_pid} test_mt_vid=${test_mt_vid}"
save
showlogo ${hdmimode}
#usb pwren
movi read dtb 0 ${dtbaddr}
# load kernel from vat or boot partition.
movi read boot 0 ${loadaddr}
#fatload mmc 0:1 ${loadaddr} Image_android
booti ${loadaddr} - ${dtbaddr}
-
- Posts: 28
- Joined: Thu Jun 30, 2016 12:56 am
- languages_spoken: english
- ODROIDs: XU4
- Contact:
Re: Request Android touch screen support here.
VID : 0EEF
PID : 0001
BRAND : IIYAMA
Model : ProLite T1530S / PLT1500
MCU : C2
If at all possible. Regards
PID : 0001
BRAND : IIYAMA
Model : ProLite T1530S / PLT1500
MCU : C2
If at all possible. Regards
- tobetter
- Posts: 2631
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: X, X2, U2, U3, XU3, C1
- Location: Paju, South Korea
- Contact:
Re: Request Android touch screen support here.
Do you use Android Marshmallow (v4.6+)? If so, could you try new feature to set VID/PID from the boot.ini?Riiio wrote:VID : 0EEF
PID : 0001
BRAND : IIYAMA
Model : ProLite T1530S / PLT1500
MCU : C2
If at all possible. Regards
You can set like this for your touch screen, and the 'boot.ini' must be in /internal/boot.ini, after changing the file you must reboot your ODROID-C2.
Code: Select all
setenv test_mt_vid "0eef"
setenv test_mt_pid "0001"
- codewalker
- Posts: 515
- Joined: Mon Feb 25, 2013 11:03 am
- languages_spoken: english
- ODROIDs: all
- Contact:
Re: Request Android touch screen support here.
Do you try to set disable_vu7 "true" in boot.ini?
Riiio wrote:VID : 0EEF
PID : 0001
BRAND : IIYAMA
Model : ProLite T1530S / PLT1500
MCU : C2
If at all possible. Regards
-
- Posts: 1
- Joined: Thu Nov 22, 2018 9:03 pm
- languages_spoken: italian, english, grossetan
- Contact:
Re: Request Android touch screen support here.
Hallotobetter wrote: Do you use Android Marshmallow (v4.6+)? If so, could you try new feature to set VID/PID from the boot.ini?
You can set like this for your touch screen, and the 'boot.ini' must be in /internal/boot.ini, after changing the file you must reboot your ODROID-C2.Code: Select all
setenv test_mt_vid "0eef" setenv test_mt_pid "0001"
where i can find some informations\guides about this new "feature"?
easiliy adding this lines to boot.ini with my monitor's VID\PID will enable the multitouch screen support?!
if is true ill buy 6-10 odroids for museal purposes!
thanks for you work&support!
- tobetter
- Posts: 2631
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: X, X2, U2, U3, XU3, C1
- Location: Paju, South Korea
- Contact:
Re: Request Android touch screen support here.
The feature is available since Marshmallow v4.6.AltCtrlDroid wrote:Hallotobetter wrote: Do you use Android Marshmallow (v4.6+)? If so, could you try new feature to set VID/PID from the boot.ini?
You can set like this for your touch screen, and the 'boot.ini' must be in /internal/boot.ini, after changing the file you must reboot your ODROID-C2.Code: Select all
setenv test_mt_vid "0eef" setenv test_mt_pid "0001"
where i can find some informations\guides about this new "feature"?
easiliy adding this lines to boot.ini with my monitor's VID\PID will enable the multitouch screen support?!
if is true ill buy 6-10 odroids for museal purposes!
thanks for you work&support!
https://wiki.odroid.com/odroid-c2/os_im ... allow_v4.6
It would be nice if you test it with your touch device and let us know if it works or not before you place an order.
-
- Posts: 28
- Joined: Thu Jun 30, 2016 12:56 am
- languages_spoken: english
- ODROIDs: XU4
- Contact:
Re: Request Android touch screen support here.
Thanks ToBetter.
[yet another] c2 in the post. will update the forum when it arrives.
[yet another] c2 in the post. will update the forum when it arrives.
-
- Posts: 8
- Joined: Wed Dec 05, 2018 8:02 am
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
Hello
I run the code on “lsusb ” on my terminal I got this
Bus 001 device 008: ID 0483:5710 STMicroelectronics joystick in fs mode
I’m sure it is my touchscreen cause I unplug the usb from my odroid c2 run the code to identify if and plug it back I get the info cause I don’t see the name of manufacture
Waveshare 10.1 lcd capacity touchscreen 1024x600
I run the code on “lsusb ” on my terminal I got this
Bus 001 device 008: ID 0483:5710 STMicroelectronics joystick in fs mode
I’m sure it is my touchscreen cause I unplug the usb from my odroid c2 run the code to identify if and plug it back I get the info cause I don’t see the name of manufacture
Waveshare 10.1 lcd capacity touchscreen 1024x600
- tobetter
- Posts: 2631
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: X, X2, U2, U3, XU3, C1
- Location: Paju, South Korea
- Contact:
Re: Request Android touch screen support here.
Can you try to copy the file boot.ini into the directory /internal and change the value of disable_vu7 from false to true? After changing them, you must reboot the board. Please let us know how it works.edgaresn wrote:Hello
I run the code on “lsusb ” on my terminal I got this
Bus 001 device 008: ID 0483:5710 STMicroelectronics joystick in fs mode
I’m sure it is my touchscreen cause I unplug the usb from my odroid c2 run the code to identify if and plug it back I get the info cause I don’t see the name of manufacture
Waveshare 10.1 lcd capacity touchscreen 1024x600
-
- Posts: 8
- Joined: Wed Dec 05, 2018 8:02 am
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
edgaresn wrote:Hello
I run the code on “lsusb ” on my terminal I got this
Bus 001 device 008: ID 0483:5710 STMicroelectronics joystick in fs mode
I’m sure it is my touchscreen cause I unplug the usb from my odroid c2 run the code to identify if and plug it back I get the info cause I don’t see the name of manufacture
Waveshare 10.1 lcd capacity touchscreen 1024x600
I did copy the boot.ini on /internal and edit the line disable_vu7 from false to true but still nothing works no touchscreen
-
- Posts: 8
- Joined: Wed Dec 05, 2018 8:02 am
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
tobetter wrote:Can you try to copy the file boot.ini into the directory /internal and change the value of disable_vu7 from false to true? After changing them, you must reboot the board. Please let us know how it works.edgaresn wrote:Hello
I run the code on “lsusb ” on my terminal I got this
Bus 001 device 008: ID 0483:5710 STMicroelectronics joystick in fs mode
I’m sure it is my touchscreen cause I unplug the usb from my odroid c2 run the code to identify if and plug it back I get the info cause I don’t see the name of manufacture
Waveshare 10.1 lcd capacity touchscreen 1024x600
I did but nothing works anny help or tips
-
- Posts: 8
- Joined: Wed Dec 05, 2018 8:02 am
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
Thorsten wrote:Hi at all,
VID: 0eef
PID 0005
Brand Name: Waveshare 10.1inch HDMI LCD (B) Capacitive Touchscreen 40020
Board C2
I know it’s long time ago from this post but I’m looking for a solution to make the same touchscreen works for me anny tips or help
- odroid
- Site Admin
- Posts: 29651
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English
- ODROIDs: ODROID
- Contact:
Re: Request Android touch screen support here.
@edgaresn,
The VID/PID was already included in the driver a couple of years ago and some people reported it worked.
https://github.com/hardkernel/linux/blo ... #L273-L276
The VID/PID was already included in the driver a couple of years ago and some people reported it worked.
https://github.com/hardkernel/linux/blo ... #L273-L276
-
- Posts: 8
- Joined: Wed Dec 05, 2018 8:02 am
- languages_spoken: english
- ODROIDs: c2
- Contact:
Re: Request Android touch screen support here.
Yes it’s works on anny Linux dist none on Androidodroid wrote:@edgaresn,
The VID/PID was already included in the driver a couple of years ago and some people reported it worked.
https://github.com/hardkernel/linux/blo ... #L273-L276
Who is online
Users browsing this forum: No registered users and 1 guest