Tested and can confirm the problem.
UART 0 @4800b / LX160s,
UART 1 @19200 / LX FLARM (MB).
On the first attempt, 30+ minutes before comm failure
Set USB debug mode ON after the first attempt, restart XCSoar.
On the second, comm operated about 10 minutes before failure.

please attach the .prf file used and also the logcat files

Testing now. Need help updating IOIO firmware.

This ticket cannot be pursued by the dev team until you post the requested logs and .prf files. Without them, we don't even know what version of XCSoar you are running!
The logcat file from your droid can be downloaded from your droid by going to the market and installing the app called, "LogViewer? Lite(LogCat?)" by ukzzang.

Also, there is a known bug in the IOIO library that we use in compiling XCSoar 6.2.x. This bug is fixed in all versions of 6.3alphax and later. We're hoping that if you are using 6.2.5 (as it says in this ticket ; ) and that by upgrading to 6.3alpha3 these behaviors are corrected.

The XCSoar version I was using was the latest, 6.2.6 I think. When the power was cycled in the IOIO. Now I have upgrated to ioio 0311 and XCSoar 6.3, and it works without problems. I tested about 1.5 hours with this configuration. I am sorry, that I was not able to get more clear results - this IOIO firmware update really went out of my control.

All IOIO problems should be fixed in 6.3_alpha3b. If not, please reopen this ticket.

xcsoar-registry.prf as requested

Log file off problem with (almost) current stable version 6.2.5

Log file off problem with developement version 6.3

The problem exists with both versions 6.2.5 and 6.3a3. I managed to reproduce the problem and collect log files with both versions. I have attached the logs.

I had to upgrade the IOIO firmware to run the development version (then downgrade it afterwards to run the stable version for flying). I also ran these tests with the Flarm running at 57600 baud and the Borgelt running at 4800 baud as this seems to bring on the problem faster.

(Sorry my turn around time on this has been a bit slow but my logistics are a bit tricky. I did these tests with the glider in the trailer, late on Friday night and towed it out to the club on Saturday morning. I just got time to post the data now.)

Please check version 6.3_alpha3b - the latest fixes are not present in 6.3_alpha3!

Sorry, I just checked the development version loaded in my Dell. It is in fact "XCSoar v6.3_alpha3b-Android" not 6.3a3 as I reported above. (I downloaded it from the Market on Friday - 3 days ago)

Is this version stable enough for flying? If so I will stick with the 6.3 version and report back if the problem recurs.

An update on this issue. It has not been resolved completed. I am now running version 6.4 stable. I managed to get a 4h30 minute winter wave flight yesterday. XCsoar froze up 3 or 4 times, both on the ground before launch and then occasionally in the air.

However unplugging and reconnecting the USB cable restores the comms instantly. Not perfect but useable. Full Flam Radar + air data + external power make up for the inconvenience of a dodgy connection. But it would be nice to make the problem go away completely.

I am not sure is this is actually an XCSoar issue, or if it is something in the OS. I am use a Dell Streak with the last released 2.2.2 version of Android. Maybe the "semi official" Dell 2.3 version of Android as described in this link would help?

​http://techienetizen.blogspot.com/2011/12/install-gingerbread-233-on-dell-streak.html

Ian,
I think that it is problem of DELL Streak. When I updated to "Olleh" android version (2.3 I think) I have not had any problems. Also, with LG P970 phone no problems. And in China they sell Streak with modified operating system, that works without problems. With Bluetooth communication Streak seems to work without any problems ever.
I am quite disappointed with Dell. Streak seems to be a great device, but DELL failed to sell it - Possibly the reason was poor customer support?