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.
Related
Greetings everyone,
I have been able to hook up a Bluetooth Keyboard and Mouse to my EVO 3D.
The keyboard works great. I have been able to type perfectly in my applications as well as configure the keyboard to work in my emulators.
The mouse I am having an issue with the "right" mouse button not working as the "go back" function in Android. Has anyone else had this issue? According to all the research I have done this is supposed to work.
I have also noticed in the CyanogenMod 6.X ROM videos on Youtube, that the people using a mouse also get a mouse cursor on their screens as well as being able to right click to "go back" and then using their middle mouse button as a "home" function in android. I did a search through 16 pages of posts on this and could not find an answer. Maybe someone reading this who is smarter than I am can shed some light on the issue.
This is what I am currently using.
Mouse: Microsoft Bluetooth Notebook Mouse 5000
Keyboard: Logitech MX5500 Keyboard.
If anyone else is using a mouse and is not having issues could you tell me the brand/model please? Maybe it is just an issue with this Microsoft Mouse.
Well it looks like the fancy mouse support with a cursor and button functionality was something that was included in CyanogenMod 6.X then removed on CyanogenMod 7.
They then added a patch for version 7. But now apparently it is being included in his latest CyanogenMod.
Regardless, it appears you need root access
**taps desk until HTC removed encryption from bootloader**
Yeah, but on the bright side, this is the first time I've seen HTC add in HID support for BT keyboards!!!!!!
HUGE gain!
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.
I have a Lenovo IdeaTab S6000 and I recently purchased the Red Samurai/GameStop V2 branded Bluetooth controller and I'm finding that when I connect the controller, a mouse cursor appears on screen that can be semi-controlled via the analog sticks. This essentially causes none of the compatible games for the controller to improperly function. Within my tablets setting menu is an option to change a mouse's cursor speed (something not present on my HTC One, which the controller works perfectly on) and I was wondering if this option could be a factor in the overall problem and if disabling this option is possible. I have spent the past two days trying to remedie this problem and have had no luck so any kind of support would be greatly appreciated.
Also, this being my first post, I apologize in advance if this was posted in the wrong area.
widower said:
I have a Lenovo IdeaTab S6000 and I recently purchased the Red Samurai/GameStop V2 branded Bluetooth controller and I'm finding that when I connect the controller, a mouse cursor appears on screen that can be semi-controlled via the analog sticks. This essentially causes none of the compatible games for the controller to improperly function. Within my tablets setting menu is an option to change a mouse's cursor speed (something not present on my HTC One, which the controller works perfectly on) and I was wondering if this option could be a factor in the overall problem and if disabling this option is possible. I have spent the past two days trying to remedie this problem and have had no luck so any kind of support would be greatly appreciated.
Also, this being my first post, I apologize in advance if this was posted in the wrong area.
Click to expand...
Click to collapse
I too would like some help with this. Exact same scenario.
ixiduffixi said:
I too would like some help with this. Exact same scenario.
Click to expand...
Click to collapse
Necroposting, but I figured I'd add to the conversation:
The only gamepad that I've gotten to work with this device (as a gamepad) is the Moga Hero. Connecting was always finicky at best and would require a full reboot, and immediately connect when it powers up. Otherwise it wouldn't pair at all.
I've tried the Red Samurai v2, the Nyko Playpad, and most recently the Mad Catz C.T.R.L.R. Invariably, the mouse mode works and works very well, but the gamepad mode always does what was written above.
In trying the xbox 360 gamepad, it blinks but doesn't connect.
As a lark, I purchased a Asus MeMo 7" HD tablet which has the same MediaTek chipset (8125) and the same exact problem exists with that device too (mouse mode works, no gamepad). Both the Memo and the Lenovo tabs are on the same version of Android (4.2.2) and the same kernel (3.4.5) on the stock rom. I assume it's Mediatek's fault, in which case HID gamepads are a no go on these devices.
Unless someone has other information, which would be much appreciated.
Oh, wanted to add something: when the C.T.R.L.R. connects in gamepad mode, you get only a cursor. When I connect my bluetooth keyboard, the multimedia controls start working. Not sure why that is.
I am working on a native library that creates 2 virtual input devices with /dev/uinput. 1 is a keyboard and the other is mouse. I have the keyboard working perfectly, but I am having a hard time with the mouse.
The library is a part of a remote control application I am working on that has a firewall punch through (for devices like android sticks or Google TV's that sit behind a firewall so you don't have to do any port forwarding).
I have the mouse clicking working just fine, but I am struggling setting the mouse pointers position. I can't get the mouse to go to where I want it.
My mouse creation and control code can be found here:
pastebin.com/ifNYF5BC
I am not sure what I am doing wrong. I have read some people saying it's not possible while other similar apps I have seen are doing what I want (in appearance at least).
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?