Request Android touch screen support here.

[Outbound]

I've edited env.ini to add the vid and pid on Lineage as well as the trial test build suggested on your post to maximaljan:

Re: Request Android touch screen support here.
Post by codewalker » Tue Jan 18, 2022 3:24 pm

Try installing this trial test version.
https://dn.odroid.com/S922X/ODROID-N2/A ... dn2.img.xz

I'm still experiencing the same issues on both builds. HDMI functions but USB touchscreen fails and kills all my USB slots so no other USB devices function after the touchscreen USB has been plugged in.

Code: Select all

odroidn2:/odm # nano env.ini
odroidn2:/odm # lsusb
Bus 002 Device 002: ID 05e3:0620
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0610
Bus 002 Device 001: ID 1d6b:0003
Bus 001 Device 003: ID 1997:2433
odroidn2:/odm # lsusb
Bus 002 Device 002: ID 05e3:0620
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0610
Bus 002 Device 001: ID 1d6b:0003
Bus 001 Device 004: ID 0416:c168
Bus 001 Device 003: ID 1997:2433
odroidn2:/odm # reboot

c:\adb>adb shell
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003

The first lsusb I ran was before the USB touchscreen was plugged in, the second was after, then my input devices stopped functioning and the touchscreen would not work even when I would unplug and replug them in. After I reboot the USB devices continue to fail and no longer show as connected.

These are popular large touchscreens on Amazon that work with Raspberry Pi / Windows, and I'm really hoping to get this functioning on Odroid N2 / N2+.

Thank you for assisting! Please let me know if there's anything else I can try.

[codewalker]

When touch device does not working, Is not other usb device (ex, mouse or storage) working?

I've edited env.ini to add the vid and pid on Lineage as well as the trial test build suggested on your post to maximaljan:

Re: Request Android touch screen support here.
Post by codewalker » Tue Jan 18, 2022 3:24 pm

Try installing this trial test version.
https://dn.odroid.com/S922X/ODROID-N2/A ... dn2.img.xz

I'm still experiencing the same issues on both builds. HDMI functions but USB touchscreen fails and kills all my USB slots so no other USB devices function after the touchscreen USB has been plugged in.

Code: Select all

odroidn2:/odm # nano env.ini
odroidn2:/odm # lsusb
Bus 002 Device 002: ID 05e3:0620
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0610
Bus 002 Device 001: ID 1d6b:0003
Bus 001 Device 003: ID 1997:2433
odroidn2:/odm # lsusb
Bus 002 Device 002: ID 05e3:0620
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0610
Bus 002 Device 001: ID 1d6b:0003
Bus 001 Device 004: ID 0416:c168
Bus 001 Device 003: ID 1997:2433
odroidn2:/odm # reboot

c:\adb>adb shell
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
odroidn2:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003

The first lsusb I ran was before the USB touchscreen was plugged in, the second was after, then my input devices stopped functioning and the touchscreen would not work even when I would unplug and replug them in. After I reboot the USB devices continue to fail and no longer show as connected.

These are popular large touchscreens on Amazon that work with Raspberry Pi / Windows, and I'm really hoping to get this functioning on Odroid N2 / N2+.

Thank you for assisting! Please let me know if there's anything else I can try.

[Outbound]

No, once the USB touch device is connected all USB devices stop working. I can't use mouse or keyboard or touch device. When I restart all USB devices continue not to work. I must disconnect USB touch device and restart for other USB devices to work again. I have tried using different USB devices and tried all USB slots, but same result each time.

I connected with adb over network connection to run lsusb. You can see in my previous post vid/pid 0416:c168 appears and then all USB devices stop running in following attempts for running lsusb.

Any ideas?

Thank you

[Richard Schaefer]

It might be the display is taking to much power ... Try a power adapter with more power.
Does the display support external power ?

[Outbound]

Thank you for the suggestion Richard. The touchscreen has it's own power adapter, though I did try a 12V 3A adapter on the Odroid N2+ to see if the additional 1A would make difference but unfortunately it didn't help.

I've tried multiple builds of Android & Lineage on both my Odroid N2 and Odroid N2+ and find they both fail in the same way for my touchscreen (VID: 0416 PID: C168). I also noted that the same behavior of all the USB slots on the Odroid failing when the touchscreen's USB is connected, occurs even on Armbian 22.02.1 terminal when no Android / Lineage is installed. This makes me think it's a compatibility issue with the board rather than the OS, as karlosoliveira suggested:

Hello,
I have tested the touchscreen in a XU4 powered by Android Lineage 16 and it works fine.
Seems like Amlogic platform doesn`t have support for this.

With that being said, does anyone know if it's likely there will be a solution for this? Should I be looking at using a different device than Odroid N2+ for my project? I'd really like to use the Odroid N2+ if possible.

I appreciate the feedback!

[Outbound]

I still haven't been able to get my touchscreen VID: 0416 PID: C168 to work with Odroid N2 or N2+, but I was able to get it to work properly with Lineage on Raspberry Pi 3B+.

I tried using a powered USB hub with Odroid N2 to see if that would help, but it didn't make a difference.

The touchscreen manufacturer issued Android drivers (attached) but I'm having trouble following the instructions to get them installed. Could anyone please assist me on how to install these drivers for Android or Lineage on Odroid N2?

thank you

[odroid]

@Outbound,
If your touchscreen is not compatible with the standard multitouch HID protocol, your touchscreen will not work on ODROID until you port the custom device driver by yourself.
https://magazine.odroid.com/wp-content/ ... pdf#page=4

Here is an example of porting a custom touch driver.
viewtopic.php?f=101&t=26043

[elabjer]

Hi.

I received a Waveshare monitor almost perfect for my application, but touch doesn't work.
I tried adding the VID:PID, but no change.. idk, I might be missing something trivial.
I'm using voodik's latest Lineage 18.

1. VID of touch screen controller
0eef
2. PID of touch screen controller
0005
3. Brand/Manufacturer name of the touch screen panel
Waveshare
4. Product(model) name of the touch screen
WS170120/1.11/210719
5. Your board (XU4/C1/C2/C4/N2)
N2 and N2+

Can you please take a look at my logcat from connection of the monitor and tell me if driver porting will be necessary?
https://pastebin.com/wYwRuGzk

Thank you!

UPDATE: I flashed the latest Mate image [ubuntu-22.04-4.9-mate-odroid-n2-20220629.img.xz] and touch works.

UPDATE #2: I flashed your latest Android image and it works!
sorry about not checking everything first. I assumed voodik's LOS is derived from your base and hence these peripherals should work.
maybe it's good to leave this here, so that others might gain some insight out of this.
thank you.

[elabjer]

I'm using voodik's latest Lineage 18.

Could you find this section in env.ini file on voodik's LOS image? If yes, try changing the option to "true" or "false.

Code: Select all

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Disable VU7
disable_vu7="false"

[elabjer]

Could you find this section in env.ini file on voodik's LOS image? If yes, try changing the option to "true" or "false.

I did. Previously I did it only in boot.ini, but now I also did in env.ini, as you suggested.. it still doesn't work.
now, I don't know enough to conclude where the culprit is, but looking at logcat messages from both HK Pie and voodik's LOS, it seems to me that the device is initialized succesfully, but in the latter Surface Flinger doesn't log anything.

I also posted this in LOS18 thread, but please - maybe you can take a look at these and share your opinion..
Waveshare [0eef:005] ON2 HK Pie
Waveshare [0eef:005] ON2 LOS18

I also tried "transplanting" your kernel into LOS18 to no avail. Then I also tried LOS17, LOS16.. it doesn't work on any.

Thank you.

[StrikeLines]

Are you still doing these? I need help with this display.

vid: 0525
pid: a4ac
Hardware: Garmin /Netchip Technology
Product: Garmin 8616
Board: N2L and M1

Thank you.

[codewalker]

Do you try to edit test_mt_vid/pid in env.ini with N2L?
You can check for yourself whether it works.
If it works please let me know. We will release new version included your touchscreen v/pid.
If it doesn't work there is nothing more I can do for you here.

Code: Select all

$ adb shell 
# vi /odm/env.ini

test_mt_vid="0525"
test_mt_pid="a4ac"

If you want to test with M1 you must install this version.
https://dn.odroid.com/RK3568/ODROID-M1/Android/test/
Edit config.ini

Code: Select all

$ adb shell
# busybox vi /fat/config.ini
user_def_args="test_mt_vid="0525" test_mt_pid="a4ac""

Are you still doing these? I need help with this display.

vid: 0525
pid: a4ac
Hardware: Garmin /Netchip Technology
Product: Garmin 8616
Board: N2L and M1

Thank you.