[...] the way back on November 2nd, we reported on a problem with the OpenGL ES implementation on the CLIQ. That story caught the attention of Motorola and and gave us a chance to [...]

This is exactly the same problem my application has!
Come join us on anddev in solving this issue: http://www.anddev.org/samsung_galaxy_odd_opengl_es_hardware_acceleration-t8511.html

Only problem there is that the GPU reports support for this particular extension. Note also that the CLIQ uses the EXACT same processor as is present in the G1.

The OpenGL ES API in Android 1.6 and below is only guaranteed to be at level 1.0. The VBO extension is not in OpenGL ES 1.0. It is only available if the GPU on the phone adds it in. The HTC G1′s GPU includes VBO support. It is unfortunate for developers to have to deal with anything less than OpenGL ES 1.1, because of the performance enhancing features it brings like VBO. However, I understand Android 2.0 and above will guarantee OpenGL ES 1.1 support.

I tested a game i develop using OpenGl on the Galaxy of a friend of mine and it’s about 2fps compared to >60fps on the G1 or the Magic. I’ll ask him next time we meet about trying a game from Hexage.

What problems are you having on the Galaxy? I’m sure Hexage would like to hear about it.

ups should have a cliq at my door within 5 hours so ill try it out, hopefully its only some devices (sorry nex) because i want my buka lol

i wish i could say for sure if buka was on a demo unit, i just dont remember entirely

Is this the same problem as on the Samsung Galaxy?

Justin,

If you can send me those logcat logs that show the API problems, I’ll get them forwarded on to the CLIQ team.

Thanks

-E

I can confirm this issue on my CLIQ.