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?
Related
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 softwinners A20 7" tablet with. Initially it worked great with no issues. Now, however, when I plug in a mouse or 3G broadband dongle via OTG, the touch screen functionality on my tablet freaks out (i.e. touching on location causes one or two other locations to be touched as well). Is there an app that can fix this, is there a setting I need to adjust?
Has anyone found a Bluetooth remote (preferably with keyboard) but most importantly with a programmable IR blaster to control the other home theater equipment and a mic for voice control on Nexus Player?
I personally haven't tried with the nexus player yet but if anyone is willing to give it a shot, might i suggest this:
http://www.amazon.com/Rii-mini-i13-...TF8&qid=1447105809&sr=8-6&keywords=rii+remote
Had it for PC for awhile before I gave up on wireless air mouse (air mouse kinda sucks on a PC to me) and gave it to a friend, but I did try on my nexus 5 via usb OTG adapter and worked pretty well for what it was worth on the little screen. Heres what I remember about it:
the IR function allows you to program up to 8 devices via IR. to program you point the IR lights at eachother and hold down the corresponding button on the rii13 until the blue light flashes, then press the button you want the rii13 to learn on the other remote. This was nice and essentially allowed full customization of the IR side of the remote, but made programming take a little more time than finding a code and pressing it to match the device you want to program. Only real downsides i found to the IR side of the remote was the IR emitter was kind of weak. Depending on the device, you had to sometimes point either real close or aim just right to get the remote to work. Devices with good IR receivers werent much of an issue. For example, my Samsung tv was easy to aim and control, but my remote control tower fan was always tricky to point at, even directly aiming. the other downside was rapid Ir blasting was lacking. for example, my samsung tv i could press the volume down button rapidly or hold it down to make volume turn down quickly. on the rii13, input works, but was rather slow. there would always feel like a short pause between presses.
keyboard and mice work well on the rii13. keyboard side was pretty responsive, and mouse featured 3 different speed settings. downside was that whenever the mouse/keyboard function would be turned off, the speed setting reset back to default when turned on. The device also has microphone/speaker output. speaker wasnt that great, but worked. microphone wasnt awful but left a bit to be desired. it was as though there was feedback preventing the voice software on my pc to properly detect what i said. interestingly i dont recall this issue on my nexus 5, but then again i only played around with it on there, so dont have much experience. the mic does not have a push to talk button. I think its always on, as i recall simply saying "okay google" on my nexus 5 to activate it.
Now I know this all sounds awful, but i dont have much to compare it to other rii branded devices. for all i know, the other rii devices could have the same IR issues, etc. maybe i had a faulty unit. But I think it might be worth a shot to try and play with on the nexus player if anyone is curious or interested. Perhaps you dont care about the mic/speaker functions, in which case maybe the IR "issues" i had might not bother you that much.
Hi,
I have a BQ Aquaris E6 with a broken screen (only a black screen is shown).
I need to access the device to save some data and, if possible, to control it from a pc in the future.
The mobile seems to react to the digitiser based on the sounds. It looks like that only the display is broken and I could still control the device.
The device still receive notifications from different apps.
WiFi is enabled and it automatically connects to my home WiFi network.
Unfortunately, no developer options were enabled, no USB debug enabled and impossible to use adb solution will work. (If someone told me how to remotely enabled...it would be amazing!)
The only solution I thought was to use the MHL connection to enable the USB debugging options by duplicating the screen and controlling it with a TV when I touch the display.
I bought a MHL-HDMI cable but TV does not react at all after connection. I thought immediate screen duplication would happen but it is not the case...
Could anyone give a feasible solution to access the device?
Thank you very much in advance.
http://www.devicespecifications.com/en/model/c71730e7
According to the spec sheet, it does not appear to support any video out format. With out USB Debugging enabled, there's really nothing else that you could do beyond getting the LCD fixed.
es0tericcha0s said:
According to the spec sheet, it does not appear to support any video out format. With out USB Debugging enabled, there's really nothing else that you could do beyond getting the LCD fixed.
Click to expand...
Click to collapse
First of all, thank you very much for your reply.
I had a look to the link and it is true there is no mention to any video output format. But I know it has MHL connection since other people were able to connect it through the MHL connection to a TV.
There are some websites where the MHL is also mentioned (no way to paste links because I am new...shame...)
Any idea about how could I enable the USB debugging with a working touchscreen but blinded?
Any way to send a piece of code to do it?
Looks like you are right about the MHL. I should have researched further. Not sure if there's a setting on the phone that you might need to do before it outputs the stream. Either way, I do not know of a solution that would work in this situation.
Other than getting a new screen connected to it...
http://www.ebay.com/itm/New-BQ-Aqua...izer-Assembly-IPS5K0750FPC-A1-E-/291693340931
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.