Dear All,
I am working on a i.MX6S based custom board which is actually a "toned-down" version of i.MX6DL SABRE-SD board. This hardware is using 24-bit 800x480, parallel LCD display Panel. Since The Android 13.4.1 BSP has LVDS as default display for SABRE-SDP and also the BSP seems to have only LVDS and HDMI enabled in the kernel... !!
so I have done some configurations by going through the user guides and help and info available over the community. Now the display is active and screen is available but it seems to be not working properly.
The Android Virtual Keypad behaves differetently and appears to be shifted .... On touching any key on the screen, 1 or 2 places before key appears on the screen .. ( touching "p" , "i"appears and toucing "o" , "u" appears..) ... Also seems this display is not getting recognized by the Android for its correct size or resolution. Below is the respective section of "logcat".
Our Custom Hardware:
-------------------------------
I/imx6.gralloc( 2167): primary display name lcd
I/ ( 2167): XmlTool()
E/ ( 2167): open data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml failed
E/ ( 2167): invalidate parameter in loadAndParseFile
I/imx6.gralloc( 2167): colordepth is 0
I/imx6.gralloc( 2167): disp_mode is
W/imx6.gralloc( 2167): 32bpp setting of Framebuffer catched!
W/imx6.gralloc( 2167): using (fd=12)
W/imx6.gralloc( 2167): id = DISP3 BG
W/imx6.gralloc( 2167): xres = 800 px
W/imx6.gralloc( 2167): yres = 480 px
W/imx6.gralloc( 2167): xres_virtual = 800 px
W/imx6.gralloc( 2167): yres_virtual = 1536 px
W/imx6.gralloc( 2167): bpp = 32
W/imx6.gralloc( 2167): r = 16:8
W/imx6.gralloc( 2167): g = 8:8
W/imx6.gralloc( 2167): b = 0:8
W/imx6.gralloc( 2167): width = 127 mm (160.000000 dpi)
W/imx6.gralloc( 2167): height = 76 mm (160.421051 dpi)
W/imx6.gralloc( 2167): refresh rate = 60.26 Hz
i.MX6 SABRE-SDP Logcat:
-----------------------------------
I/imx6.gralloc( 2232): primary display name ldb
I/ ( 2232): XmlTool()
I/imx6.gralloc( 2232): colordepth is 0
I/imx6.gralloc( 2232): disp_mode is D:1024x768p-60
I/ ( 2235): ServiceManager: 0x1cbac0
W/imx6.gralloc( 2232): using (fd=12)
W/imx6.gralloc( 2232): id = DISP3 BG - DI1
W/imx6.gralloc( 2232): xres = 1024 px
W/imx6.gralloc( 2232): yres = 768 px
W/imx6.gralloc( 2232): xres_virtual = 1024 px
W/imx6.gralloc( 2232): yres_virtual = 2304 px
W/imx6.gralloc( 2232): bpp = 16
W/imx6.gralloc( 2232): r = 11:5
W/imx6.gralloc( 2232): g = 5:6
W/imx6.gralloc( 2232): b = 0:5
W/imx6.gralloc( 2232): width = 163 mm (159.568100 dpi)
W/imx6.gralloc( 2232): height = 122 mm (159.895081 dpi)
W/imx6.gralloc( 2232): refresh rate = 60.00 Hz
The problem appears to be in the highligted "Red" section of log or in any other sections of code / config not known to me. I am unable to trace the above code section / reason of the highlighted error. Would like to request sincerely for help in this regard from Freescale team and community member as I am a novice in this area and have very limited knowledge on patching or code tracing. My appologies for overlooking anything obvious or silly ...
Attached pl. find the complete logcat of our custom hardware for reference and analysis, Any help , suggestion, guidance or patch is heartily appreciated and is eagerly awaited...,
warm regards
Ujala Kumar
Original Attachment has been moved to: Logcat_11052013.log.zip
Hello,ujala,
the issue should be generated by origin of coordinates on Touch module , that is to say, origin of coordinates on touch module is not in accrod with that of LCD.
So check touch module driver , please!
Regards,
Weidong