Hi! I need Android device that can work with large touch screen displays (see picture). Does anyone know how to do it?
sounds alot like a moto device and webtop maybe you can borrow one and try it
http://www.motorola.com/Consumers/US-EN/Consumer-Product-and-Services/WEBTOP/Meet-WEBTOP
I believe Webtop is not using a touchscreen, instead it uses a touchpad with a cursor like a laptop.
The problem here would be drivers for the multitouch display. Single touch displays will usually work as a HID device, imitating the same hardware as a mouse and would probably work with any Android device that accepts HID devices via USB. I'm not sure how mulitouch monitors interface via USB.
Related
Hi, I'm a recent owner of the Archos Gen 8 and have also bought a bluetooth keyboard and mouse for the device.
The keyboard is working ok, but the mouse itself seems not native to the android os. For example, double-clicks equal to a touch in the screen, and I cannot select texts in documents-to-go, and so on. My question is whether it is possible that anyone can port the mouse-driver to the android so the mouse could work better?
Just my two-cent question since I know nothing about programming nor linux, but my work requires typing and editing documents on-the-go a lot. Anyone shares any opinions?
Thanks and best regs,
halfheartbreak said:
Hi, I'm a recent owner of the Archos Gen 8 and have also bought a bluetooth keyboard and mouse for the device.
The keyboard is working ok, but the mouse itself seems not native to the android os. For example, double-clicks equal to a touch in the screen, and I cannot select texts in documents-to-go, and so on. My question is whether it is possible that anyone can port the mouse-driver to the android so the mouse could work better?
Just my two-cent question since I know nothing about programming nor linux, but my work requires typing and editing documents on-the-go a lot. Anyone shares any opinions?
Thanks and best regs,
Click to expand...
Click to collapse
Moved to general as not android development
I have found this same problem on ARCHOS 101 Android 2.x.x. Bluetooth Mouse or USB Mouse could not use single click. Someone told me this problem relate to Android OS not ARCHOS device. But on my 7" Chiness Tablet Android 1.6 no problem with Mouse.
I don't know to to fix this bug on ARCHOS device.
Kind of like the HDMI webtop mod, especially the on screen keyboard/track pad when connected.
I wonder if it's possible to keep the on screen trackpad/keyboard when I connected my bluetooth mouse. Now the trackpad application will be disabled when the bluetooth HID is connected.
Somehow the android is not that responsive when I connected both my bluetooth keyboard and mouse, only one bluetooth device works properly at one time.
Ideally, the trackpad can be backup when either bluetooth device does not work.
If I'm not asking too much, is it possible to turn the trackpad screen back to the android window when the android mobile view is active in webtop mode, so that we can have better control of the android OS in webtop.
Any thoughts on how to implement these? Which application activates the onscreen keyboard/trackpad in webtop?
Hello all,
I recently bought an Android tv box and I want to put it in my car. I bought also a 7" digitiser and a "digitizer to usb interface from Adafruit named ar1100" that help me to connect via USB the digitiser and the Tv box.
My problem is that I have set up the interface and when I connect to my tv box using USB, it works as a touchpad , not like a touchscreen. This means that I see a cursor and I need to move that cursor like the touchpad from the laptop.. I want to activate the function where the digitiser works as it is designed.
I have read on some forums that is a "Touch mode" function that can be activated but from what I understand, it is made by developers which insert some lines in the source code...
Do you please have any suggestion for me in order to find a solution? Or an .apk that can solve this?
Thank you very much! :crying:
Did you ever resolve this? I've connected my Ar1100 to three Android devices and have exactly the same problem.
I'm trying to set up an Android-x86 instance, and I'm having trouble with the touchscreen controller. I've tried both an eGalax unit and an Adafruit AR1100. Here's how it goes:
For ROMs based on Android 4.4 and earlier, the USB touchscreen controller installs and works as expected. However, these older flavours don't support external sound cards (which I'm using).
For all ROMs on Android 5.0 and newer, the touchscreen works like a mouse. There's no absolute positioning, but if I swipe the screen a cursor moves. For eGalax controllers, this movement is also inverted on both the x and y axis, so it's completely unusable.
eGalax provide an Android driver but I don't know how to build it into Android. For the Adafruit AR1100, I found suggestions to include a custom .idc file, but it doesn't seem to work for me.
Any suggestions? Any ideas? I'm tearing my hair out over this.
Recently I got myself a Sculptor 16.1'' external portable monitor that has multi-touch and gravity sensors. The monitor claimed to support many smartphones including ours as well as some others like ROG Phone 1/2. While most other functionalities work (screen outputs at 1920x1080 @ 120Hz, USB-C Power Delivery works), touch and gravity sensors don't work as expected. Haven't tested about audio, but at present I'm not able to redirect audio to the monitor at the moment (the monitor seems to use HDMI for audio).
I'm currently on Havoc 3.5 GSI, with Trinity kernel and MR3 vendor. Can confirm that hid_multitouch is built into the kernel according to the kernel config. However, I couldn't find anything about how to configure the external touch panel and gravity sensor, despite both of them have been properly detected by the system:
1. A CH340 USB-Serial port (1A86:7523) which I believe is the gravity sensor. This device can be picked up by apps like Serial USB Terminal.
2. A Silicon Works SW4101C (29BD:4101) which is most likely the touch panel.
Some information online suggests me to create an IDC for the touch panel's device ID (at present it's identical to that of qwerty2.idc, except I now specified the device is an external device), and some even suggested to patch the kernel's hid-multitouch.c to add the device's ID and information into it, but hid-multitouch.c suggested otherwise, that a default method would be used for unspecified HID devices (that only devices known to have some quirks should be included along with the code for the quirks). I checked the stock ROM's /system/usr/idc and found nothing about external touch panels, either. (If anyone has experiences with such on stock ROM it'd be appreciated)
The gravity sensor is not really working at all (maybe this requires a specialized USB serial app). For the touchscreen part, I could at best get working touches from upper-left part of the screen (about 2/3 of total screen, I think), and only when the phone is in landscape mode (in portrait mode the touchscreen does not function at all). However, it seems sliding works on the entire screen as long as the touch is started from the area that has working touches. Touch is still unstable as some incorrect touches may occasionally occur (probably cable/power related). Also, my phone would generate a tremendous amount of heat when the monitor is attached, and doesn't seem to be able to boot properly if it's been overheated (like about 60-70 celsius).
Not sure if external touch panels are still new, or that such is not really practical for Android smartphones to use (compared to desktops and laptops), the information I could find about this is very limited (that it might require some vendor-specific system modes to function properly, which Huawei and Samsung phones seem to provide). I intend to use this panel as a substitute for my Pixel C which is now showing its age, as it could not handle certain recently released games very well anymore.
After some research it seems setting the phone's screen size to 1920x1080 will make the touchscreen work on the entire screen, although one may need to set the density as well to keep the size of items the same as before.
Code:
wm size 1080x1920
Please note that you'll need to manually revert the resolution later on. The resolution you changed here persists across reboots!
Code:
wm size reset
However, the touch panel is still erratic and can cause issues with games where touches may not work as intended (multi-touch does work). Not sure if using a different cable/adapter might help, as similar issues can happen on phone's own screens as well. The use of such monitors may be limited for now as I cannot find any way to enable things like desktop mode, or get the touch panel to work when the phone is in portrait mode.
EDIT: Not sure about the monitor itself, but even with some better cables and adapter the touch panel is still not in a good conditions (either it would stop responding, or it generates unexpected touch signals). A 65W power adapter connection is required to properly function (30W connections is not enough). Guess I'll just use it for other non-Android purposes and get a real tablet (like Galaxy Tab S6) instead...
I did try searching about similar topics regarding external touchscreens on Android. However, the ones I could find were mostly quite old, dated when Android was still at around KitKat or even earlier.
As for audio, I couldn't find anything about it anywhere in the settings. And I only just realized some Type-C cables are rated only at USB 2.0 speed (which is the case for most charging-oriented cables, despite them being rated 65W or even 100W).
I didn't know there is such a touch screen portable monitor. Is it convenient?