KitKat Hardware acceleration issues (particularly in browser)

682 views
Skip to first unread message

Weston Weems

unread,
Nov 4, 2013, 4:14:40 PM11/4/13
to android...@googlegroups.com
I've updated hardware/software we run to Kit Kat from the 4.4_r1 branch. It boots and I've been able to start plugging my drivers back in one by one.

What I've noticed is that (presumably because of the gles2 pixelflinger migration), I can no longer leave hardware acceleration in its default state because it basically breaks the browser.

If this is infact a problem with the powervr display driver, is there anyway to tell pixelflinger to fall back to 1.0? (How does kitkat support older devices, that may not support 2.0)

Any pointers would be greatly appreciated!


gpu is PowerVR SGX540... 

using latest binaries I could find... and I keep getting this:

E/IMGSRV  ( 1118): :0: gralloc_module_map: Mismatching lock usage bits 0xP...FHWR=0x00000033 vs requested usage bits 0xP...FHWR=0x00000100
E/IMGSRV  ( 1118): :0: MapBufferObtainParams: Mapping buffer failed
E/IMGSRV  ( 1118): :0: WSEGL_GetDrawableParameters: Failed to obtain buffer parameters
E/chromium( 1118): [ERROR:gl_image_egl.cc(36)] Error creating EGLImage: 12300
E/IMGSRV  ( 1118): :0: gralloc_module_map: Mismatching lock usage bits 0xP...FHWR=0x00000033 vs requested usage bits 0xP...FHWR=0x00000100
E/IMGSRV  ( 1118): :0: MapBufferObtainParams: Mapping buffer failed
E/IMGSRV  ( 1118): :0: WSEGL_GetDrawableParameters: Failed to obtain buffer parameters
E/chromium( 1118): [ERROR:gl_image_egl.cc(36)] Error creating EGLImage: 12300
E/IMGSRV  ( 1118): :0: gralloc_module_map: Mismatching lock usage bits 0xP...FHWR=0x00000033 vs requested usage bits 0xP...FHWR=0x00000100
E/IMGSRV  ( 1118): :0: MapBufferObtainParams: Mapping buffer failed
E/IMGSRV  ( 1118): :0: WSEGL_GetDrawableParameters: Failed to obtain buffer parameters
E/chromium( 1118): [ERROR:gl_image_egl.cc(36)] Error creating EGLImage: 12300
E/IMGSRV  ( 1118): :0: gralloc_module_map: Mismatching lock usage bits 0xP...FHWR=0x00000033 vs requested usage bits 0xP...FHWR=0x00000100
E/IMGSRV  ( 1118): :0: MapBufferObtainParams: Mapping buffer failed
E/IMGSRV  ( 1118): :0: WSEGL_GetDrawableParameters: Failed to obtain buffer parameters
E/chromium( 1118): [ERROR:gl_image_egl.cc(36)] Error creating EGLImage: 12300
E/IMGSRV  ( 1118): :0: gralloc_module_map: Mismatching lock usage bits 0xP...FHWR=0x00000033 vs requested usage bits 0xP...FHWR=0x00000100
E/IMGSRV  ( 1118): :0: MapBufferObtainParams: Mapping buffer failed
E/IMGSRV  ( 1118): :0: WSEGL_GetDrawableParameters: Failed to obtain buffer parameters
E/chromium( 1118): [ERROR:gl_image_egl.cc(36)] Error creating EGLImage: 12300
E/IMGSRV  ( 1118): :0: gralloc_module_map: Mismatching lock usage bits 0xP...FHWR=0x00000033 vs requested usage bits 0xP...FHWR=0x00000100
E/IMGSRV  ( 1118): :0: MapBufferObtainParams: Mapping buffer failed
E/IMGSRV  ( 1118): :0: WSEGL_GetDrawableParameters: Failed to obtain buffer parameters

Jay Wu

unread,
Nov 10, 2013, 8:31:00 AM11/10/13
to android...@googlegroups.com
Got the exactly same problem on Nexus S. The error was originally thrown out by eglCreateImageKHR() function in ui/gl/gl_image_egl.cc. 12300 means EGL_BAD_PARAMETER. As you said, Google forced it by hardware acceleration to create images. But I read somewhere this function is mandatory in implementation of either GLES 1.1 or 2.0. So things seem not that bad, I got the black screen randomly when entering webview contents. I and other devs tried to fall back to GLES 1.1 in SurfaceFlinger, but no effects as far as I know. I also tried to debug the EGL_BAD_PARAMETER error in Android OpenGL codes, the weird thing is I got nothing. Where this bad parameter error comes from? I hope some Android developers can help SGX540 users. Thanks.

matadeen mishra

unread,
Mar 28, 2014, 5:12:43 AM3/28/14
to android...@googlegroups.com
Hi Weston,

Have you got the reason behind why it is throwing error??
I am also getting the same issue.
Could you please let me know or share some solution.


Reply all
Reply to author
Forward
0 new messages