I'm building Android 5.1 with kernel version 3.10.52. Everything goes fine before I attached a hdmi touch screen (http://www.waveshare.net/wiki/7inch_HDMI_LCD_(B)). HDMI output was fine and it's landscape, and touch function was working. But the direction of touch function is different from HDMI output. Touch screen is functioned via USB port by hid-usb driver.
In Linux dist, we usually use Xorg and the libinput config to calibrate. But now it's on Android, and I really don't know how to rotate touch screen.
Could anyone help?
Related
I am working with i.MX 6Quad SABRE-AI board and I tried to flash android image and boot from SD card.
I have followed "android_M6.0.1_2.1.0_docs/Android_Quick_Start_Guide" section 4.3.
I have successfully flashed and booted from SD card , while booting i can see splash screen from u-boot and kernel logo (tux) on the LVDS screen , but suddenly the backlight of LVDS goes off (once the kernel starts).
Also, We have found out that enable pin to LVDS is HIGH during the bootup (backlight ON) and it becomes LOW (backlight OFF) once the kernel starts.
Note : We can see the contents on the LVDS screen (if we look from an angle ) , so we believe if backlight is enabled LVDS would work proper for us.
Suspicious parts in bootup logs:
pwm-backlight supply power not found, using dummy regulator
MIPI DSI driver module loaded
MIPI DSI driver module loaded
mxc_sdc_fb fb#0: registered mxc display driver ldb
imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Console: switching to colour frame buffer device 128x48
How to make logic high on **BACKLITE_ON pin of "Port Expander A" from android M6 kernel?**
You might configure the GPIO of the backlight control properly in boot loader .
Possibility is that either
(1) the GPIO is being used by other driver in kernel space which is overwrite your boot loader configuration, check the GPIOs which is used in kernel driver by using GPIO sysfs command on terminal
Or
(2) If the backlight pins controlled from backlight driver, check logic state of on and off handled in driver
I am working on an nvidia jetson tk1 development board with android 4.4 system. I have connected the board with a screen through hdmi interface. The problem is that whenever I switch the screen to landscape mode the screen will be blurred, I mean have some jetter irregular lines when screen refreshing. I rotate the screen with the builtin app.
As I am not familar with the dsi architecture, could anyone help to indicate which module I should check, edid, hdmi or android?
Thanks.
If you've used an Android device, you're aware that there are some apps that force the display to portrait and ignore the device's orientation sensor. On a real device, this is not a problem, as you can physically rotate the device in your hands to use the app.
However, I am trying to use such an app on android-x86 in Oracle's VirtualBox on a Linux Mint PC, and cannot physically rotate my monitor. I have tried the f9-f12 keys that send a rotation event to the app, but since the orientation is fixed, this has no effect.
Short of keeping my neck cricked at a 90° angle, how might I configure android-x86, VirtualBox, and/or Linux to display the app right side up? To be clear, I don't have access to the source code of the app.
For sure now is too late to reply, anyway I discovered that I can rotate back my vd resetting resolution of screen on the fly. If my device is 1200x800 (landscape) and it is rotated left by an app I can get it vertical by shell comamnd: (adb shell) wm size 800x1200
I found that Rotation Locker (com.devasque.rotationlocker) solved the problem for me. Via this mailing list post.
I'm currently compiling for Android for a device and have recently upped the ICS build. I'm facing an issue with the touch. The touch controller is on but the screen is treated like a track pad for mouse input with a cursor appearing over the screen. How do I make the touchscreen input be used as a touch screen and not as a mouse input.
Thanks
Th issue here was with the IDC file. IDC = Input Device Configuration file. I had borrowed the touch driver from a different device with the same hardware, but I hadn't taken the idc file for this change.
Adding this to the product config file fixed it for me.
I have had a very unfortunate accident with my Samsung Galaxy S2 and the screen has suffered a complete shatter (top to bottom! - was closed in a car door)
I have downloaded and am running Droid#Screen to make sure the phone itself isn't damaged and can see that the screen is sat on the pattern lock screen. Is there a way I can simulate a touchscreen input from the PC?
I just need to unlock the screen then can use Kies Air to remove all of my pics and videos and important files.
Is there a way I can simulate a touchscreen input from the PC?
You can attempt to use monkeyrunner, though I have no idea if that can automate the lockscreen.