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. One would think the default Honeycomb implementation I assume from Google was heavily tested against the Tegra 2 SoC and may exhibit the problem say on the Xoom or other Honeycomb tablet. I have yet to test anything beside the G-Slate. My assumption is that without being able to test directly (IE print out all the config profiles the GL driver returns to verify) is that the likely optimum depth size could be 32 for the Tegra 2 devices and that the max my config chooser currently searches for is 24 (2nd gen devices) and this is not present on Tegra 2 devices (3rd gen). Therefore depth 24 does not match anything and the further default fall back searches for depth size 16 which is located as a "valid" GL config found by TyphonRT. So 5/6/5/16 works OK with the G2x, but fails with the G-Slate. No EGL / GL errors are raised and 5/6/5/16 comes back as a valid config arrangement on the G-Slate, but it's broken such that no rendering occurs with this non-optimum config setting. The expected behavior I believe is that some sort of rendering should occur if a valid GL config is matched and a context obtained even if it is not the optimum config. Of note though there are no perceived performance problems with the G2x at this config setting. It seems obvious that 5/6/5/16 is not the optimum configuration for a Tegra 2 device (was the optimum setting for gen 1 devices). Once I modify the default fall back settings and include 5/6/5/32 as the top config to search after verifying that indeed is a valid target in general I'm guessing things will match up with the optimum supported config on Tegra 2 devices and things will be fine. It just happens that things are not borked on the G2x at 5/6/5/16, but the G-Slate fails with this setting further misleading me. As things go I've yet to add external settings (extra XML file / external config by exception, etc.) to configure GL config parameters, so until I finish rebuilding my platform in ~1-2 weeks I won't get to update the defaults or finish the external XML config mechanism. In the future with my efforts an external XML file that can filter by device / family as necessary can provide the GL config decision tree and not rely on the hard coded default decision tree, so testing will be easy in the future without recompiling. Regards, --Mike On Apr 25, 10:54 pm, Romain Guy <romain...@android.com> wrote: > What is the "G-Slate" you keep referring to?? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
