I am doing a little experiment with OpenGL ES on Nexus One. Got a problem about the full screen resolution. It seems like I can never get the real full resolution of Nexus One, which is 480*800. I am using an orthogonal projection and just want to draw a simple triangle with identity model view matrix:



The coordinates for the triangle are:



And I get the result in the second attachment. The result is same on emulator and Nexus 1. Obviously I didn’t get the full resolution (because the top vertex of the triangle is already close to the right edge, if width is real 480, this should be on the left of the half width). Another strangeness is that in sizeChanged (I am using GLSurfaceView, this is the override method in the renderer required by GLSurfaceView), I always get width = 480 and height = 800 no matter whether I start the app in full screen mode. I was expecting that with app title bar and status bar, the size passed to sizeChanged should be smaller right? I mean if the size passed to this method isn’t the real size I am getting, then how can I setup a correct viewport?

I also did a quick implementation using GLUT with the same setup and draw the exact same triangle. I get the result in the first attachment, which is the expected result. Anyone can help me figure out how to get this same result on the phone?

just a head check here, but you do have this in your AndroidManifest.xml to turn off automatic compatibility mode right?

<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true"/>

Yes, I have already put that tag in AndroidManifest.xml. In particular, I found that it seems like only android:anyDensity="true"|”false” matters, as this does change the rendered result. Others don’t change the result at all. Also my project is on SDK 1.6, which is recommended for developing apps that support larger phone screen.

...another head check... Can you print out the width & height parameters in sizeChanged method and verify that they are what you think they are.

Also there is the classic GL mistake of not having the right matrix mode selected when doing the projection setup (in your case ortho projection) or forgetting to switch the matrix mode after the ortho call to GL_MODELVIEW can subtely mess things up even though you seemingly get "reasonable" results.

So try dropping in this after the GLU ortho method. You can likely omit the glPushMatrix I do that cause I push / pop into and out of ortho mode from a 3D projection state:




If that doesn't work try this method instead of the GLU ortho method:



Also here is the sequence I use to enter ortho mode (again pushing the projection/modelview matrix so that I can pop back off to whatever 3D projection was set before):



------------------------------

This should give a few things to check/verify before continuing.

Thanks MichaelEGR for the answers, they helped me a lot!

I found myself extremely embarrassing to tell you the real cause of this problem, which I solved just now. The triangle class that I copied from one of the samples actually scale on the coordinates that you define in the position array by the factor of two! I just modified the coordinates in the array and I didn’t notice when they are loaded into the vertex buffer, they get scaled!

I am guilty… But let’s just be careful with something copied over as you trust it does something in the way you expected, but it doesn’t, this is the triangle class I copied the code from http://code.google.com/p/apps-for-andro ... derer.java, and notice that on line number 215, the positions get scaled by 2! Really evil as a sample…

Also, when using GLSurfaceView, use android.opengl.GLSurfaceView instead of the GLSurfaceView.java in your sample folder sdk_root\platforms\android-1.1\samples\ApiDemos\src\com\example\android\apis\graphics. As the latter one is an early version and has some strange behaviors.