580 crash on HTC Hero about unflobtactical HOT 8 CLOSED

I'd love to understand why Xenowar crashes on some systems; I don't have access 
to a good test device. (Although I'm looking for one.) Marking accepted but not 
assigning. Also hoping someone else with a device can debug. 

I can try, but I need some kind of step by step HowTo.

Can the reason be in target=android-8 string in build.properties. HTC Hero 
seems to be 2.1 type device.

I test on:
- HTC incredible (2.2)
- Galaxy S (2.1)
- Nexus One (2.2)

The 2.1 thing is okay. It does a static link to some android libraries, but 
never actually hits the 2.2 dynamically linked part. It's a little fishy, but 
tests fine in the emulator and on device.

Also the crash seems to be limited to Gen1 devices. (Generally all the 500MHz 
devices). I don't think it's the clock speed, but could be a chip feature? 
(Although that should be detected by the install filter.)

Ideas on the bug:
- driver reporting vbo supported, but not. (test: turn off the vbo detection in 
gpu manager code)
- driver reporting particles supported, but not. (same test)
- running out of texture memory
- using unsupported opengl call (*should* be caught by emulator - another 
driver bug?)

I'll try to add a wiki this weekend on building it, but if you are set up for 
Android NDK building:

On windows VS 2010:
- build everything "debug"
- run 'makeres.bat'. You may need to create missing directories. This creates 
the game database.
- in the android/ufoattack_1/jni directior, ndk-build
- open the anroid project in eclipse
- run

Regrettably, I have no better idea than to splatter the Java code with logs, 
the c++ code with GLOUTPUTS, and hope to find where it goes down on the device.

Is it possible to provide Windows binaries so that I won't have to mess with 
Visual Studio in addition to Eclipse Android SDK and NDK? Maybe it is possible 
to contain all development activities to Eclipse only?

Actually, on the trunk, you can use the release database. And, apparently, I 
have checked said database into source control. This is certainly a mistake, 
but a rather happy one. You don't need the windows compile at all!

i have a hero and xenowar has never run for me, i just get a white screen.

it doesn't force close though so i have no idea what the problem would be.
i've been usung custom roms of the latest versions of android (custom cyanogen 
built for hero) to the same effect which makes me think the hero can't run it.

Ongoing bug; no dev system to reproduce. Marking utr until more info.