So firstly, thanks for answer. Anyway you misunderstand me. I already have fully working application (https://market.android.com/details?id=menion.android.locus&feature=more_from_developer), anyway I now try to rotate map around X axis, and few problems occur (more info here http://stackoverflow.com/quest.....und-y-axis together with three images). Looks like some problem with drawing on Canvas, so I’ll probably have to start learn OpenGL ES.

And problem for me: all tutorials on OpenGL ES, use method that during initialize, they load bitmaps and then use them during rendering. In my case, I need to change map tiles (256×256 bitmaps) dynamically, because as you move with map, new tiles have to be loaded and displayed. And I’m still little bit confused how to do it.

So I asked for some tip on some sample application that should bring some light on this for me. Anyway ignore my posts if you don’t understand or not have time. Thanks anyway for your work on NeHe tutorials, if you’ll not point me on some way, I’ll probably start from begin with this!

I do not know if I got you correctly but if you need help with OpenGL in general you could start here (http://insanitydesign.com/wp/p.....oid-ports/) or jump over to NeHe directly.
If you need normal streetmaps you could use Googles own Android API to access Google Map.
If you just want to know in general how you could do a “map” app I would recommend to be “inspired” by the tile map loading every bigger map services does now. You cannot load big images at all as they would probably occupy or crash the memory of your phone, therefore you have to look for a “streaming” reloading of tiles of a map. These single tiles can then be loaded and drawn by OpenGL if you wish to. Basically something similar to classic tile maps with support of all the benefits OpenGL can offer.

I hope this is the direction you needed help. Otherwise let me know.

Regards.

Nice nice, thanks for that info. Haven’t ever thought once about that… ‘doh’…

Thx very much

Regarding the ‘hacked’ version where you don’t use GLUUtils, it has a big-endian/little-endian issue. It’ll work on little-endian phones, but not on big-endian phones. Wrapping the pixels as bytes manually solves that problem.

The below is also useful as a general way to load textures in OpenGL on Android if one desires to load bitmaps without premultiplied alpha (when using the GLUUtils alpha gets premultiplied (due to behaviour of Bitmap-class), meaning the colors loaded are a*r, a*g, a*b, a, instead of r,g,b,a).

int[] pixels = GraphicsUtil.extractPixels(bitmap);
byte[] pixelComponents = new byte[pixels.length*4];
int byteIndex = 0;
for (int i = 0; i > 16) & 0xFF); // red
pixelComponents[byteIndex++] = (byte) ((p >> & 0xFF); // green
pixelComponents[byteIndex++] = (byte) ((p) & 0xFF); // blue
pixelComponents[byteIndex++] = (byte) (p >> 24); // alpha
}
ByteBuffer pixelBuffer = ByteBuffer.wrap(pixelComponents);

gl.glTexImage2D(GL10.GL_TEXTURE_2D, level, GL10.GL_RGBA, bitmap.getWidth(), bitmap.getHeight(), 0, GL10.GL_RGBA, GL10.GL_UNSIGNED_BYTE, pixelBuffer);

The thing with the squares comes with MipMaps in general: If you have a look at http://en.wikipedia.org/wiki/Mipmapping a MipMap source has to be square. I do not know if there are any specifics how to “fake” something else, but this is how I learned and know it.

Regarding the GL11 problem: Good to know. Still hanging on my Magic ^^’ But I already noticed that there are far too many differences in between the different Android Phones as there should be.

Regards

Oddly enough, the reason I’m trying to do this is because the test for GL11 isn’t reliable. The HTC Eris and Hero, for example, will report a GL11 instance but will not generate mipmaps correctly. At this point I’m hoping to remove all reliance on the auto-generated mipmaps. :/