Now that I think of it my problems seemed to start after android 2.2 also. I also have noticed another symptom let me know if it happens to you. I biked 7 miles in one training session and it forced closed. I started it up again, biked another 10 miles and then closed the program normally, When I uploaded the training sessions The one that was forced closed showed up but the one I closed normally didn't!. Days later, I did a 6 mile bike and the Droid forced closed. I started it up again and did another 12 miles. When I uploaded the session. It showed the force close 6 mi bike and the 10 mile bike from the previous week! However it didn't show the 12mile bike I had just did and had closed normally. Extremely weird.
I have a log file from this weekends force close I wish I knew who to send it to.
I have latest Droid software FRG22D and RunGPS is up to date. I run with the phone in my pocket with the screen turned off. I still get force closes frequently and I then lose all my training data. I also use my phone camera to take pictures during hikes and Bikes. When I do that, it seems even more likely to force close.
I spent a lot of money for this application yet in looking at several of the Force close topics in the forum I don't see any
response from the developers.
So Developers, Any advice? Can I send you logs? Is there a debugging mode I can turn on in RunGPS?
Let me know.
Kevin
PS.
If you are having problems with your Droid be sure to add to this topic.