You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AR1100 chip is used in a wide number of touchscreen displays, and is billed as a "Universal" controller as it appears as an HID Mouse. However, Android itself has an issue where it won't recognize any USB Mouse that's an "Absolute" mouse, which is what a touchscreen really should have.
There is a workaround, and it is extremely simple. Setting the AR1100 into Digitizer mode allows Android to notice it. Its functions, however, are not at all like what you would want with a standard touchscreen. This is only half of the solution - The other half involves a custom IDC file. Installation is simple: placing the file into /system/usr/idc and rebooting the device.
If this IDC file was already included in H3Droid, it would support AR1100 devices out of the box. The only thing the user would have to do is change it to digitizer mode.
Full disclosure: This solution is not mine. It's one I found when researching the issue. The original can be found here.
The text was updated successfully, but these errors were encountered:
The AR1100 chip is used in a wide number of touchscreen displays, and is billed as a "Universal" controller as it appears as an HID Mouse. However, Android itself has an issue where it won't recognize any USB Mouse that's an "Absolute" mouse, which is what a touchscreen really should have.
There is a workaround, and it is extremely simple. Setting the AR1100 into Digitizer mode allows Android to notice it. Its functions, however, are not at all like what you would want with a standard touchscreen. This is only half of the solution - The other half involves a custom IDC file. Installation is simple: placing the file into /system/usr/idc and rebooting the device.
If this IDC file was already included in H3Droid, it would support AR1100 devices out of the box. The only thing the user would have to do is change it to digitizer mode.
Full disclosure: This solution is not mine. It's one I found when researching the issue. The original can be found here.
The text was updated successfully, but these errors were encountered: