Backup options disabled even when not recording

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Not really sure what the first step is.
2. Settings->Back up is disabled but the app is not actively recording.
3. A work around can be to start and stop recording.

What is the expected output?
The Backup options should be available when not recording.

Please use labels and text to provide additional information.
I think the issue occurs when the preference does not match the service state.

Original issue reported on code.google.com by sandordo...@google.com on 30 Sep 2010 at 4:10

[GoogleCodeExporter]

Indeed, they're disabled based on the preference. Perhaps I should query the 
service after that to update it again?

Original comment by rdama...@google.com on 30 Sep 2010 at 5:26

[GoogleCodeExporter]

At the end of a long ride (30 MI bicycle), I found out that tracking had 
stopped at a point where I paused to take some pictures (and either tried to 
email or mms one). I used alogcat and saved the kml file. I figured it was some 
out-of-memory or similar issue and forgot about it until I saw the postings on 
GoogleGroups discussion that described the "can't upload file while recording" 
(sic) message which I recalled seeing when I initially tried to save the 1/2 
map of my ride. I can also tell you that when I used the menu key to access 
what should have been a "stop recording" option, it read "start recording"  I 
honestly can't recall how I cleared the condition (my tracks not allowing map 
saving/upload due to some flag saying it was recording). Hopefully, the 
attached files will be of some use?

Original comment by JeffAKna...@gmail.com on 30 Sep 2010 at 8:53

Attachments:

• [Track 72.kml](https://storage.googleapis.com/google-code-attachments/mytracks/issue-169/comment-2/Track 72.kml)
• alogcat.2010-09-19-18-53-19-0400.txt

[GoogleCodeExporter]

Taking a quick look at log -- I see a SIG: 9 getting sent to "TrackRecord..." 
if preferences / state mismatched at that point,.... I'm guessing that the 
subsequent restart might have been a problem. Good luck folks... love this app.

Original comment by JeffAKna...@gmail.com on 30 Sep 2010 at 9:00

[GoogleCodeExporter]

Can you confirm if this still happens with the latest version?

Original comment by rdama...@google.com on 30 Apr 2011 at 10:01

[GoogleCodeExporter]

Original comment by rdama...@google.com on 30 Apr 2011 at 6:12

• Added labels: Component-Logic, Component-Persistence

[GoogleCodeExporter]

No response for many months, closing.

Original comment by rdama...@google.com on 6 Jan 2012 at 5:10

• Changed state: NotReproducible