A couple of my tests for the experimental build were working on the Android emulator (Pixel_3a_API_31_arm64-v8a, chosen arbitrarily) but not on an actual device (Neffos x9 or so, v7 architecture I believe).

The eglConfigChooser() call was not requesting depth (or stencil) bits, although it seems some drivers are generous.

These modifications let you ask for a depth buffer and it will modify that request accordingly.

At the moment this is a simple "I want it", in which case it gives you a 16-bit depth buffer. (If you request a stencil buffer, which will be 8 bits, it will also throw the 16-bit depth buffer in, since these always seem to go hand-in-hand.)

Perhaps some refinement could follow later, e.g. for 24-bit depth, although it would probably have to query for capabilities or pixel formats.

The options are "wantsDepthBuffer" and "wantsStencilBuffer", which you can provide in build.settings like so:

	android =
	{
		applicationChildElements = {
			[[<meta-data android:name="wantsDepthBuffer" android:value="true" />]]
		}
	}

This gave me appropriate on-device results with that setting and without it.

I haven't run into the same need on Windows, Mac, iOS, or tvOS in my tests (these last two in their respective emulators), but they'd call for something similar if it should arise.

TODO?

I wasn't sure if I could trip those code paths that pass false, false when constructing fView and fCoronaRuntime.