Pfffft...ooooook....i guess i'll leave it like that then. This is really strange...it's the same code that desktop jPCT uses.... I was just setting the fourth component (i.e. alpha) for some light source and overall lighting materials to 1...which is f***cking default according to the specs and i never ever had a problem with that. I really don't know if i'm wrong here and it never surfaced before or if the N1 is wrong!? Anyway, as long as it doesn't break anything on other phones, i'm fine with that change. I've updated the "official" AE-jar as well...

Just download it, rename the file and report back if this helps with your problem. In which way isn't opaque blitting not working? The changes that i made to the new version deal with transparency of objects. The blitting code is totally unrelated and hasn't changed. That's even more true for the resolution...jPCT-AE contains no code at all that deals with resolution. It works with whatever resolution you initialize your Activity with. It's up to you to set the resolution, the engine doesn't do anything in this regard. What you are seeing when you are getting 320*520 on a current phone, is a kind of compatibility mode that is triggered by your AndroidManifest.xml not specifying anything else. Have look here on how to deal with that: http://developer.android.com/guide/practices/screens_support.html

Oh sorry, I made mistake, I compiled my older project without it... I tested the newest version and on galaxy s working without any problem... And thanks for your advice with manifest, resolution is ok now.