I did pull out the old pre component oriented refactor build from back in July and verified the available attribute configs returned by GL on the G-Slate and G2x. They are essentially the same with the G2x returning 56 and G-Slate 57. I don't think it's worth posting them as I am correctly grabbing the config that is specified in the decision tree.
My assumption from last message was incorrect regarding depth size as there is no 32 bit depth returned. The highest in all configs from the Tegra 2 is depth of 16. I tried many different config parameters including 8/8/8/16 and all sorts of variations with and without stencil, alpha, depth and also the config parameters which return EGL_NATIVE_RENDERABLE 1 / true. Of note the later configs with EGL_NATIVE_RENDERABLE set to true also have EGL_CONFIG_CAVEAT as EGL_SLOW_CONFIG (this was the case for the Droid too). I also printed out the eglGetError() state during context / surface init, during the intro screen, and during the main render loop and it always returns with EGL_SUCCESS (12888). With all context parameters tried EGL_SUCCESS was always returned and a valid surface and context were created. So while I see aberrant behavior / no rendering on the G-Slate with any combination of GL configuration parameters I'm still at a minor loss on why the same app / APK works fine on all phone devices (OS 1.5 to 2.3) and not the G-Slate (3.0) when no GL errors are returned and a context is properly created. The onus could be on my code of course, but I'll have to wait until I finish the rebuild of 3D support with the component architecture refactor ~1-2 weeks to continue. There are only diminishing returns on continuing to modify the old build as I'm in deep / almost done with the new rebuilt component based architecture and can try and solve it from there. I really want to try and have a private beta to give out to folks at I/O, so I'm against the wall to finish it up in time. I have verified that all the post context creation parameters are correct when setting the base projection too: GLActivityRuntime - setProjection - viewDim: [width=1280 height=768] GLActivityRuntime - setProjection - perspectiveAngle: 45.0 GLActivityRuntime - setProjection - gluPerspectiveAspect: 1.6666666 GLActivityRuntime - setProjection - nearClipPlane: 5.0 GLActivityRuntime - setProjection - farClipPlane: 2500.0 The only difference with the G2x is the viewDim of [width=800 height=480] If anyone has a Xoom or other Honeycomb tablet besides a G-Slate and would like to try and run the simple cube test I'd be glad to send it over via email as this could be a quick head check to verify if the G- Slate is the culprit as that is the next major head check to determine if the problem I'm seeing is specific to the G-Slate. Send an email to my founder address and I'll get in touch. Thanks for any tips / help. --Mike On Apr 25, 11:35 pm, MichaelEGR <[email protected]> wrote: > http://mobile-broadband.t-mobile.com/android-tablet/g-slate > > I believe it was previously called the LG Optimus Pad before release? > > It could be an issue from LG perhaps with a pseudo-incomplete GL > driver and not in the court of the Android team / Google. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
