UPDATE : ive tested the first debug version. others will follow to solve the problem. ill tell ya if we find out the problem.
UPDATE : now, after one week ive tested about 20 debug builds. the milestone / droid has some heavy problems rendering the ingame screen. actually vladimir and me has got ingame. but we just can see the background, ingame objects and the hud. besides that we hear the ingame music. and are able to move. but the level graphics itself arenīt there. lot work to do. but will keep you inform.
I'm mote interested in know if it was poor/bad coding or the Droid OS and/or hardware having issues with the coding (i.e. are their inherent flaws in the system).
You are right to be wary. There is much bullcrap. Be wary of me too, because I may be wrong. Make up your own mind after you evaluate all the evidence and the logic. - Mark Rippetoe
nothing much new actually, but vladimir said he wont give up until the game runs on our droid . now i use the log collector app to send him the log messages from the game. and he told me the logs are promissing for the next step of debugging.
This is Vladimir from GarageApps, I am the developer of Spacetracks. As we all know Spacetracks doesn't work on Motorola Droid / Milestone devices. During the development, the game has been tested on almost every popular Android device (Samsung Galaxy, HTC Tattoo, HTC Hero, the G1), except on the Motorola - I couldn't find any Moto user in my neighborhood willing to borrow me the device for testing purposes. So I've tried Spacetracks on a simulator configured like the Motorola, and running the same OS version like Motorola, and it worked very well!
Unfortunately, after releasing Spacetracks I've soon found out that the game crashes on real Motorola devices. Now, after almost three weeks from the release date, I'm working very hard with MustangGT500 to find out where is the problem. Yes, he tested so far about 20 debug builds (thank you very much for that Mustang). The main problem is that the game crashes without any exception messages shown on the screen. So, it is not a regular crash, and therefore it's very hard to find out what's the cause.
Currently we are working with a LogCollector app, which gives me the opportunity to log debug messages from Spacetracks, and Mustang sends me these log files after crash. I don't know for sure, but I think there must be an hardware incompatibility problem with OpenGL ES, or with the sound output.
Please be patient, I'm sure that next versions of Spacetracks will be full compatible with Motorola devices. It's hard to debug such a problem without having a real device beside me. It takes much more time as we test only one or two debug versions per day.
Vladimir - GarageApps