Hi all,

This post contains several questions that are related and some may
have been answered in other posts but after about 15 minutes of
searching through this group I've determined that it is easier to ask
in a new post.  I'd also like to make sure that this thread does not
veer-off in some direction so please post a new thread with a link
back to this one if you would like to submit a related question to
what I am asking.  OK, here goes:

I have a game that relies on OpenGL ES 1.0 and I (finally) have it to
the point that the amount of bugs and ANR's being reported through the
Market is nearing zero.  So, what better time to make a major revision
that ruins all that, correct?  What I would like to do is the
following:

 - Update to OpenGL ES 2.0 using android.opengl.GLES20 class:  At the
moment, my app actually imports a JSR-239 jar stub so I am compatible
with non-Android devices.  Since non-Android devices cannot match the
pace of Android adoption, I think it is work the effort to make a
branch that imports GLES20 and utilizes more features, specifically:
     - FBOs/VBOs
     - Floating-point calls (everything is still in fixed-point)
     - Shaders, etc.
 - Upgrade the application (2.x branch) without creating a new
application in the market but still have users on older devices still
see the 1.x branch.

Questions:

1. a) What version of Android guarantees a hardware accelerated OpenGL
ES 2.0 context?  Since I cannot filter the application to specific
hardware, can I filter to SDK 8 (Froyo) and glEsVersion to
"0x00020000" and assume that any devices that match have a hardware
accelerated context?

   b) Many early devices (MyTouch 3G for example) have been updated to
Froyo but have pretty awful OpenGL performance when measured against
the latest Android devices.  I would like to limit limit these devices
to the 1.x branch version of the app. and if the answer to 1(a) is
'you cannot', then is there a better method to restrict users with old
hardware and latest OS from seeing the 2.x branch app?

2. How can I have 2 apps in the Android Market that have the same
name?  I'd rather not have to append some word like 'Pro', 'Extreme',
etc. on a new application since my current users that have sufficient
hardware to run the 2.x branch would not be automatically updated.  Is
the solution to add code to the 1.x branch that checks the hardware on
startup and posts some message that they should download the new 2.x
branch app instead?

Thank you for reading and any help is greatly appreciated!

-- 
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

Reply via email to