Hello I am running the db410c with the Linksprite 7" Touchscreen.
With the touchscreen I received a sd card that has the android 5.1 release on it.
It is noted in the documentation that the android boot.img is a specific release for using with the display.
The boot image is modified for the 800 x 480 resolution.
I would assume that the kernel is modified or is there startup script that runs the command {adb shell wm size 800x480
} ?
The display works to some level with android but i do experience some issues. This is running the android release that comes on the sd card.
It is noted that to get the screen working to HOT-PLUG the usb after device startup. I was able to overcome the HOTPLUG by adding a powered usb hub and connecting the display usb to the hub. This way the display will not power on until the USB is initialized.
With the setup running like this you can reboot the dragonboard and when android comes up the touchscreen will be working just fine.
NOTE: To boot into fastboot you need to disconnect the usb hub and the display.
NOTE2: When connected to adb the display will not work. It freezes and displays the screen you were on when connecting adb.
My thought as a workaround for this is to run adb over wifi.
I DO A LOT in ADB.
I know you can access the terminal via serial and i do have that set up. But i have serial connected to a separate computer dedicated to the serial only. So it would be nice to use adb over wifi from my main system.
This leads to the other problem i have.
WIFI is not working with the android release provided on my sdcard.
I have to try a different android release. Which i did load the current android 5.1 release but cant test wifi because the display resolution.
So i guess in a nutshell here are the questions.
#1) Does the kernel require modification for the support of the display. Is it using a module or specific driver in the kernel?
If I build a custom kernel from the provided sources I would need to make these modifications.
If this is the case is there a DIFF that shows the kernel mods?
Is there source code available to build the display driver / module?
#2 Is it only necessary to run (adb shell wm size 800x480) to use the standard releases with this display.
The other issue i experience is that when i touch the screen to select anything…the display slowly fades out and comes back. Basically it takes about 3 to 5 seconds to select and get the display back. So multi clicking like to turn on developer options is not possible. This occurs with or without the usb hub added.
If we can fix this issue that would be great. Im guessing it is due to the fact that it is controlled through USB. But it appears that some online videos show the dragonboard and this screen not having this problem.
I am fairly good at working with android and the shell. I can get you logs if you need them. I have the serial console hooked up.
This error comes across my serial when i open the android lockscreen.
mdss_dsi_cmdsbuf_tx: failed to call cmd_dma_tx for cmd = 0X11
mdss_dsi_cmds_tx: failed to call
hdmi_get_video_id_code: timing is not supported h=800 v=480
It just seems like were missing a driver or something.
Thanks for any help.