EDIT:Regarding the theora crash: Uswin or David_OSU, does anyone of you have a rooted device? If so, can you post the output of the command "cat /proc/cpuinfo" in a terminal emulator? I guess you can also open the file in a text editor/viewer. Somehow I suspect that the Tegra 2 lies about its available features.

EDIT 2:Maybe this new daily fixes the theora problem on Tegra CPUs: http://jjs.at/daily/AGS_2012-01-24_19-04-16.apkBut it is a stab in the dark. I will post the source later because my local repository got out of sync with the online one and I have to fiddle around with it some more to make it usable again :.

JJS, Unfortunately I don't have an access to rooted device yet,

but Good news, I confirmed that using the latest AGS_2012-01-24_19-04-16.apk, the theora crash DOESN'T OCCUR on LGP990 Optimus 2X ANYMORE. Kudoooos. Where is the LIKE button mate !!

Ok, so you mean the current development version in the SVN. All changes were only to the editor as far as I can tell, so no problem there. Also all ports are built from the same engine source, so they should be identical in compatibility.

EDIT:Regarding the theora crash: Uswin or David_OSU, does anyone of you have a rooted device? If so, can you post the output of the command "cat /proc/cpuinfo" in a terminal emulator? I guess you can also open the file in a text editor/viewer. Somehow I suspect that the Tegra 2 lies about its available features.

Here is the Features list from the cpuinfo command:

Features: swp half thumb fastmult vfp edsp vfpv3 vfpv3d16

Also, I know that the Tegra 2 does not have the NEON instructions, which is surprising.

David_OSU, thanks for the info! The problem is that the compiler generated code for neon, but to target the Tegra CPU it has to be set to vfpv3-d16. Fortunately this was easy to fix, a problem in the optimized assembler code would have been very hard to resolve for me.

The PlayBook is a Blackberry device, right? I have no clue how the development environment for that looks, but it is certainly not a simple recompile. This would be an entirely different port and I don't think it will happen tbh (at least not from me).

David_OSU, thanks for the info! The problem is that the compiler generated code for neon, but to target the Tegra CPU it has to be set to vfpv3-d16. Fortunately this was easy to fix, a problem in the optimized assembler code would have been very hard to resolve for me.

JJS, yes, the PlayBook is the BlackBerry tablet. With the new PlayBook OS (OS 2.0) Android developers will be able to release their Android apps in Blackberry App World. The only thing that is required is that the APK be converted to a BAR file. I'm sure there is more tweaking that might need to be done, but, generally apps seem to work well after the conversion.

I actually converted "AGS_2012-01-24_19-04-16.apk" to a BAR last night, but am unable to install it on my PlayBook without first getting a signing key from the RIM servers.

Here's a little video tut:

I might be able to tinker with it later tonight or tomorrow and let you know how it works out.

JJS, I can't even describe how awesome this project has come along in such short time. From not functioning to almost perfect compatibility in this amount of time is impressive my friend, and I applaud you for taking the time to make it possible. You can't beat playing 6 Days a Sacrifice in bed when I'm too lazy to get up and play on the computer. Especially considering my phone is very limited in terms of games.

JJS, I can't even describe how awesome this project has come along in such short time. From not functioning to almost perfect compatibility in this amount of time is impressive my friend, and I applaud you for taking the time to make it possible. You can't beat playing 6 Days a Sacrifice in bed when I'm too lazy to get up and play on the computer. Especially considering my phone is very limited in terms of games.

Seriously man, bravo.

Couldn't agree more mate. This is absolutely a brilliant effort to make the AGS step up to the next level.Kudos.

Looks like the PlayBook can only run the Java code, but not native ARM instructions. Because the whole AGS engine is in native code, this is of course bad news. I guess nothing except for reimplementing the whole engine in Java could fix this .

At the moment you will not be able to do the fighting and box pushing minigames I think. You could use the Windows binary from my daily build site and play through those sections on your PC because it should be savegame compatible though.

I dunno if it's exclusive to my device (Nexus) but the backspace key doesn't do anything. Which is really annyoing.... jus started playing Ghost's Hubris on my phone and the prefilled text of "player" can only be extended with further characters, but not deleted.