Fort everyone interested in this thread: It seems there is a new version out (2.3.9.c ast 2.3.9b). Maybee the problems are less or gone in this version. I'm gonna give it a spin tomorrow.
19.05.2011 10:39:58 UTCgeändert am 19.05.2011 11:08:01 UTC
Motorola Atrix has same problem
I own a Motorola Atrix (MB860) for about 10 days now, so apps installed is not very high and handset is in pristine condition. It is dual core 1GHz with 1GB of RAM, so specs should be sufficient for RunGPS I hope :-).
However, I had a very bad first run with the phone rebooting after about 15 min and then showing bad run tracking after restart. See training data below
http://www.gps-sport.net/trainings/running_574039
After the crash I restarted the handset and forgot to enable the GPS for about another 15min, but once it was enabled the DOP and speed recorded were pretty bad.
FYI. Before this I used a HTC HD2 with Win Mob 6.5 running Android HTC Desire Sense build (FroyoSense V3.2) of the SD card and I had PERFECT workouts (apart from the known issue of the HD2 showing the track sometimes a bit zig-zagy). Compare the above run to this one below which is a run in the same location with the same conditions with regards to how the phone has been carried and what other accessories have been used, i.e. Bluetooth headset and Polar BT heartrate belt.
http://www.gps-sport.net/trainings/running_560220
What is even more annoying is that I started to use Android from the SD card as my HTC HD2 did crash midway during trainings when using RunGPS from WinMob 6.5. So imagine how gutted I am to have bought a brand new EXPENSIVE phone which now crashes as well. Thinking of selling the handset again, but have seen recently many posts that seeem to imply that higher Android version 2.3.3 or 2.3.4 also had issues with high DOP/GPS location problems when using RunGPS.
As far as I can judge from our user reports, the problem of rebooting only occurs on modified ROMs. We have not found out yet what is the reason for this. From my experience I can say that this *could* happen when too much main memory and/or CPU time is used by the app.