More info...
My DEXT is the LATAM version, has the firmware version Blur_Version.0.11.8.MB200.AmericaMovil.en.MX (no updates available), and at least in Speed Forge 3D I still can't see nothing rendered. I tried to contact the developers to find out if they were using VBO, but seems very likely, since the logcat shows a very similar output (many non implemented OpenGL calls).
Motorola, any idea on future firmware updates for this region??? :-)
I'm trying to get something together, but, even if I'm a skilled Java programmer on the backend side, my GL is still in "Hello Rectangle", so it may take me a few days to have something that fully tests if my frmware has the fix in the US version. (we are on different 3G frequencies, so, I expect you guys to get fixes first)
I found a reference to the Samsung Galaxy having a simmilar issue, that was solved by changing the settings to eglChooseConfig, like so:
m_glView.setEGLConfigChooser(
new GLSurfaceView.EGLConfigChooser() {
public EGLConfig chooseConfig(EGL10 egl,EGLDisplay display) {
int[] attributes=new int[]{
//EGL10.EGL_RED_SIZE,
//5,
//EGL10.EGL_BLUE_SIZE,
//5,
//EGL10.EGL_GREEN_SIZE,
//6,
EGL10.EGL_DEPTH_SIZE,
16,
EGL10.EGL_NONE
};
EGLConfig[] configs=new EGLConfig[1];
int[] result=new int[1];
egl.eglChooseConfig(display,attributes,configs,1,result);
return configs[0];
}
}
);
Taken from: http://www.anddev.org/samsung_galaxy_odd_ogl_es_hardware_acceleration_resolved-t8511.html
This could work, as Hexage posted a similar issue on the android lists about getting different bit depths, related to VBO working or not. I might try this, but again, I'm just beginning to grok GL.
But, if you have a small sample apk I can test, I could tell you what the real status is (log cat and all).
Gerardo
