AlpineQuest & OfflineMaps

I am a relatively long time & happy user of the software, but there are three problems I would like to point out:

1. the current track and the track loaded from the card should by default to have different colours; the blue & blue is terribly irritating.
2. the changes to ui are ok, but certain ...

Thank you for the effort!

It seems that the new version of AlpineQuest solved the problem. I did not look into the logs, but the tracker behaves as expected, that is it is recording from the start until it is turned off within the application. It looks that even if there are some crashes (I did not check it), the tracker ...

01-08 15:53:46.658 I/ActivityManager( 105): No longer want psyberia.alpinequest.full (pid 21087): hidden #16
01-08 15:53:46.705 I/WindowManager( 105): WIN DEATH: Window{4053cf40 psyberia.alpinequest.full/psyberia.alpinequest.full.AlpineQuestActivity paused=false}
01-08 15:53:46.721 I/System.out ...

The Tracker has still a hard time to get running again:

01-07 23:41:22.015 W/ActivityManager( 105): Scheduling restart of crashed service psyberia.alpinequest.full/com.psyberia.alpinequest.services.tracker.AlpineQuestTrackerService in 5367084ms

5367084ms = approxim. 1.5 h )

It seems at the first glance that the tracker works fine. I registered some logs, but I will be able to analyze it after the weekend.

One more remark: this crashes never happened to me when the main app is running and from what I understand you always start tracker as a separate process. So, if I am not mistaken, the process becomes crash prone only when it runs on its own. It may be actually a reason why users are not reporting ...

By the way, the typical pattern is that Tracker works for up to 30 minutes and then dies. This 20 second is probably a record.

Thanks for the effort! I have a full version of the app. Does it mean that I can upgrade to 1.2.11 (full version) only via the market?

If you have any additional ideas regarding testing/debugging I can do on my phone, I would be glad to give it a try. In particular, if you want some additional logs ...

My impression is that after every crash the Tracker, when it is restored by the system, is not capable of reading gps signal. Could you confirm or reject it?

From what I understand when a process is restored only onCreate method is called. Maybe something from onStart is missing? Sorry for this ...

This is the alpinequest.log for the relevant period of time

Current date is 2012-01-03
[11:24:02.751] aqControler: entering function 'AlpineQuestControler'
[11:24:03.049] aqSettingsModel: shared preferences are not empty
[11:24:03.050] aqSettingsManager: retrieving application folders...
[11:24:03 ...

This is .tracker.log.back

Current date is 2012-01-03
[10:33:07.737] AlpineQuestTrackerService: callback to 'onCreate'
[10:33:07.741] AlpineQuestTrackerService: callback to 'onStartCommand'
[10:33:07.742] AlpineQuestTrackerService: entering function '_handleCommand'
[10:33:07.974] PsyLogsInstance ...

Let ma add the following additional crash report

01-03 14:06:32.105 I/ActivityManager( 105): Start proc com.google.android.apps.maps:LocationFriendService for service com.google.android.apps.maps/com.google.googlenav.friend.reporting.LocationReceiverService: pid=19884 uid=10026 gids={3003, 1015 ...

Let me provide some more logs.

01-02 18:10:05.644 I/ActivityManager( 105): Start proc com.google.android.apps.listen for content provider com.google.android.apps.listen/.ListenProvider: pid=13361 uid=10057 gids={1015, 3003}
01-02 18:14:40.738 W/InputManagerService( 105): Window already focused ...

This was a misunderstanding. By "uninstalling application" I meant uninstalling one of the applications running in the background. I am aware that any piece of software has to go through a number of improvements.