On Sep 30, 2:29*am, Max Kellermann wrote:
akiley wrote:
I still occasionally get kicked out of the app and have to restart
it, but it happens less with each upgrade. *That said, this type of
thing happens with SeeYou and iPaq too.

We expect that this does not happen at all, and we take every bug
report very serious. *On Windows CE, the unstable operating system and
ancient flaky hardware is responsible for most crashes. *But on
Android, once we get a good bug report, it's usually fairly easy to
fix.

What we need in a bug report is a "logcat" (Android's system log).
Install an app such as "CatLog" from the market. *WhenXCSoarcrashes,
use CatLog to save the log to a file. *Upload that file to a bug
report on our bug tracker (http://www.xcsoar.org/trac/newticket).

Bugs don't get fixed magically, they only get fixed if users report
them to us.

(And thanks for praisingXCSoar, all on the team are putting a lot of
sweat into it ...)

Max

Thanks Max, I attempted to do a bug report a few months ago as per
your instructions on your forum. I downloaded catlog, but I couldn't
figure out what triggered it my crash. My luck, every time I ran
CatLog it wouldn't crash. For that reason I didn't do an "official"
bug report. But you fixed something because I've been using the 6.2.1
with no problems so far. Ran it for several hours today and a few
yesterday. Noticed you did several Android bug fixes with 6.2.1 and
that may have done the trick. Great App. ... Aaron