Develop
Ticket #2034 (closed defect: fixed)
6.3.1 (No Horizon) catlog from uncommanded exit
| Reported by: | tangoeight@… | Owned by: | RobD |
|---|---|---|---|
| Priority: | normal | Milestone: | XCSoar 6.3 |
| Component: | Other | Version: | 6.3 |
| Keywords: | Cc: |
Description
I "provoked" the exit by doing some task switching, hope this is helpful.
Attachments
Change History
comment:1 Changed 13 months ago by max
- Owner set to RobD
- Status changed from new to assigned
Sorry, I can only support official XCSoar builds. I reassign your ticket to RobD, because this is his private (unofficial) XCSoar build.
comment:2 Changed 13 months ago by RobD
T8, I don't notice anything in the file that shows a cause of the error. If this is replicable, please include steps to replicate it. It may depend on your xcsoardata folder too. Is it replicable on the normal XCSoar? (You can install both on your streak concurrently.) XCSoar should be 100% identical to your version except the horizon code).
Also, the logcat file unfortunately does not save the XCSoar version. Were you running 6.3 or 6.3.1? (the version displays in the upper-left corner of the startup screen).
comment:3 Changed 13 months ago by tangoeight@…
Rob: 6.3.1 (no horizon). The uncommanded quit has only happened to me when using the Streak stand alone on internal GPS (testing in my car or in hand, not in the glider). It has only happened to me when I have switched apps or turned the display off. I have found no way to reproduce this on command.
comment:4 Changed 13 months ago by Turbo
this sounds more like the Android OS killing the process because it has moved to the background and needs to much memory...
comment:5 Changed 13 months ago by RobD
- Status changed from assigned to closed
- Resolution set to invalid
Switching apps may cause the Android OS to kill XCSoar. i.e. taking photos, then returning to xcsoar may not guarantee XCSoar has not been killed.
