GLES 3.2 on Nexus 9 Marshmallow?

[BlazingSoul]

Is OpenGL ES 3.2 available on Android M?  I heard that the Nexus 9 got the update but the state of GLES is still unclear?  I tried Dolphin on my N9 but it says it is using 3.1 when booting a game.  


To put it simply, is 3.2 already implemented in Dolphin? Or, did Marshmallow never had it in the first place?

[Nintonito]

The drivers STILL haven't been updated since release so no.  Officially Google won't make it a priority unless android officially support it.

[BlazingSoul]

(11-13-2015, 12:46 PM)Nintonito Wrote: The drivers STILL haven't been updated since release so no.  Officially Google won't make it a priority unless android officially support it.

I see, I thought 3.2 was a feature of Marshmallow.  Let's hope that Google wakes up and add support, since the Snapdragon 820 will use 3.2 no doubt.

Do you know if there are any custom roms that use 3.2 on the Nexus 9.  Regardless, the nexus 9 is a beast.  I can run many games close to full speed, and it doesn't throttle as much as my Galaxy S6. It is too bad that the X1 didn't use those Denver cores.

[zxcvbad]

In order for S820/S810 to support GLES 3.2 they need a commercial driver, I'd say it'll happen around S820 release and a major Android update that will have GLES 3.2 as a core feature. On the Nexus 9 part Nvidia already have GLES 3.2 driver so it's all up to Google's standardization, like Nintonito just said

[Nintonito]

(11-13-2015, 11:28 PM)zxcvbad Wrote: In order for S820/S810 to support GLES 3.2 they need a commercial driver, I'd say it'll happen around S820 release and a major Android update that will have GLES 3.2 as a core feature. On the Nexus 9 part Nvidia already have GLES 3.2 driver so it's all up to Google's standardization, like Nintonito just said

Well funnily enough on the Qualcomm side Google is actually shipping ES 3.2 drivers, as they keep those devices much more up to date with drivers than the N9.  

[Sonicadvance1]

Wrong.
Android 6.0 doesn't "support" ES 3.2, as in it doesn't provide java bindings for it. This doesn't matter for Dolphin since we wouldn't use the java bindings anyway.
Also the Nexus 9 and /any/ Qualcomm device don't yet have OpenGL ES 3.2 support (I'm expecting the first QC device with ES 3.2 to be an S820).
The only device currently shipping with an ES 3.2 driver is the Nvidia SHIELD Android TV, which doesn't matter since it supports GL 4.5 anyway.

[aterraki]

(11-14-2015, 02:27 AM)Sonicadvance1 Wrote: Wrong.
Android 6.0 doesn't "support" ES 3.2, as in it doesn't provide java bindings for it. This doesn't matter for Dolphin since we wouldn't use the java bindings anyway.
Also the Nexus 9 and /any/ Qualcomm device don't yet have OpenGL ES 3.2 support (I'm expecting the first QC device with ES 3.2 to be an S820).
The only device currently shipping with an ES 3.2 driver is the Nvidia SHIELD Android TV, which doesn't matter since it supports GL 4.5 anyway.

I'm not sure to understand, It's working now ? or maybe soon, with a update for ES 3.2 ?

[Sonicadvance1]

This may be slightly difficult to explain.
So whenever Android advertises that it supports OpenGL ES X.Y in whatever version of Android. This means they provide Java bindings for that version of ES starting with that particular version of Android.
So, Android 4.3 added support for OpenGL ES 3.0
Android 5.0 added support for OpenGL ES 3.1 + Android Extension Pack.
Android 6.0 does NOT add support for OpenGL ES 3.2.

So since Dolphin mobile uses java purely for the UI, we don't need to use the Java function calls to the OpenGL ES library.
All of the OpenGL/ES code is in the C++(JNI) portion of the application. Since we are linking "directly" with the vendor's OpenGL system library, and due to how OpenGL and extensions are set up, we can use newer versions of OpenGL without Android "supporting" it.
This is how we get desktop OpenGL on Tegra devices. Android doesn't support OpenGL 4.5, nor has Nvidia changed the Android java bindings to support it.

Another example is that the Samsung Galaxy S4 was the first OpenGL ES 3.0 device and it initially shipped with Android 4.2. A version of Android that didn't support ES 3.0 yet Dolphin could still run on it.

So then, Android doesn't need to "support" it, but the video drivers still need to. The Nvidia graphics driver is still fairly recent with its OpenGL ES 3.2 support (358.xx minimum) and Google decided not to upgrade the video driver on the device.
So the Nexus 9 is running an older video driver that doesn't support OpenGL ES 3.2. While the Nvidia SHIELD Android TV is supporting OpenGL 4.5 and OpenGL ES 3.2 currently.

Of course all this nonsense doesn't really matter to the Dolphin application itself. We already properly support ES 3.2 and OpenGL 4.5 in the application with the latest development versions. Once the video drivers on the device receive an update and get ES 3.2 support, then it will automatically use it.

A good way for finding out what version of OpenGL ES your device supports is to download this application. https://play.google.com/store/apps/details?id=nl.svdree.glesinfo
Then move over to the GLES2.X tab and it will show which version of OpenGL ES your device supports.

Sadly this application doesn't support showing desktop GL features, so you can't see what version of desktop GL the device supports, and we've removed the device information in Dolphin Mobile. I don't think there is currently any application that shows this information, and I won't be adding it back to Dolphin.

[aterraki]

(12-02-2015, 11:39 PM)Sonicadvance1 Wrote: This may be slightly difficult to explain.
So whenever Android advertises that it supports OpenGL ES X.Y in whatever version of Android. This means they provide Java bindings for that version of ES starting with that particular version of Android.
So, Android 4.3 added support for OpenGL ES 3.0
Android 5.0 added support for OpenGL ES 3.1 + Android Extension Pack.
Android 6.0 does NOT add support for OpenGL ES 3.2.

So since Dolphin mobile uses java purely for the UI, we don't need to use the Java function calls to the OpenGL ES library.
All of the OpenGL/ES code is in the C++(JNI) portion of the application. Since we are linking "directly" with the vendor's OpenGL system library, and due to how OpenGL and extensions are set up, we can use newer versions of OpenGL without Android "supporting" it.
This is how we get desktop OpenGL on Tegra devices. Android doesn't support OpenGL 4.5, nor has Nvidia changed the Android java bindings to support it.

Another example is that the Samsung Galaxy S4 was the first OpenGL ES 3.0 device and it initially shipped with Android 4.2. A version of Android that didn't support ES 3.0 yet Dolphin could still run on it.

So then, Android doesn't need to "support" it, but the video drivers still need to. The Nvidia graphics driver is still fairly recent with its OpenGL ES 3.2 support (358.xx minimum) and Google decided not to upgrade the video driver on the device.
So the Nexus 9 is running an older video driver that doesn't support OpenGL ES 3.2. While the Nvidia SHIELD Android TV is supporting OpenGL 4.5 and OpenGL ES 3.2 currently.

Of course all this nonsense doesn't really matter to the Dolphin application itself. We already properly support ES 3.2 and OpenGL 4.5 in the application with the latest development versions. Once the video drivers on the device receive an update and get ES 3.2 support, then it will automatically use it.

A good way for finding out what version of OpenGL ES your device supports is to download this application. https://play.google.com/store/apps/details?id=nl.svdree.glesinfo
Then move over to the GLES2.X tab and it will show which version of OpenGL ES your device supports.

Sadly this application doesn't support showing desktop GL features, so you can't see what version of desktop GL the device supports, and we've removed the device information in Dolphin Mobile. I don't think there is currently any application that shows this information, and I won't be adding it back to Dolphin.

woah thanks a lot for this complete explication ! merci beaucoup !