Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - auric

Ok indeed.
I searched for that question and I stumbled upon that thread, but I didn't read it fully since it wasn't what I was reporting.

You're right, reloading every second can be power intensive.

manual refresh will do the trick as well :-)
Version: 1.8.3ME
System: Android 2.3.3, HTC build 2.36.405.8
Device: DHD

When recording using the MyTracks method and you hit the homebutton or "back" button, Locus will disable the GPS as though it was in non-recording mode. This is a virtual disable of course, since MyTracks keeps the GPS physically active. This behaviour however has consequences for the NMEA recording: although it is set to "track recording", it stops when Locus isn't active.

Current behaviour: When MyTracks recording is started and NMEA recording is set to "track record", NMEA recording will stop when Locus isn't active because of the GPS disabling.

Expected behaviour: When MyTracks recording is started and NMEA recording is set to "track record", keep GPS enabled and keep recording NMEA data, just like it is the case with Locus recording. GPS should only be disabled when Locus isn't recording, in the background (and the option "Keep GPS On when paused" is disabled, of course  ;) )
Version: 1.8.3ME
System: Android 2.3.3, HTC build 2.36.405.8
Device: DHD

Today, I did some testing with the MyTracks recording method.
It appears to me that the trail isn't shown in this case. It is however available in the Tracks list.
What works is this:
  • Select the track that is currently recorded
  • Go back to the map screen
  • The track is shown up to that point.
Of course, you keep on moving, so you can repeat this later on to update the track.

It is a nice-to-have when Locus would be able to do this automatically: retrieve the data and draw it while it's still recording, to have the same behaviour as when Locus tracking is used.
Quote from: "menion"aren't these two killing running services? check it because when they kill recording, notification will remain but record stops ...
As for me, I don't have any process killer installed.
Version: 1.8.3ME
Android version: 2.3.3, HTC build 2.36.405.8
Device: DHD

Hi Menion,

This was reported previously, then considered solved. However, I'm experiencing the same issues as a while ago: track recording stops by itself.
A little while ago, I updated my DHD to Gingerbread. Since then, I started stress-testing Locus again and I stumbled upon the same issue as in the early days of Locus.

Concrete situation: This morning at 8:09 local time I started a recording. Then, I hit the home button to return to my home screen with Locus running on the background. It's a 20 minute drive from home to work and I kept Locus recording on arrival. During the morning, I did little to nothing with my phone before I checked on Locus around 13:30. The GPS indicator told me that GPS was active and in good reception.

When I started Locus, it started from scratch (noticed because the screen was rebuild) as though it wasn't started yet, then the notification "unfinished track detected" popped up and the "recording state" was set to "paused".

Since I noticed this in the days after the upgrade, I cleaned all error logging yesterday (there were a bunch of  them) and I checked those log files: there was one created at 12:31.
Then I checked the recording itself and it seems that it didn't record a lot since my arrival at work, which could be due to my settings (not recording when new point is no 3m from previous recorded point, no recording when accuracy is lower then 15m).
Then I checked the NMEA file, which is recorded on track record, the last entry was saved at 9:20

During the recording, I was inside the building all the time, mostly next to a large window which means that I did have full GPS reception, I did however move some times so that GPS reception was sometimes lost.
At 9:20 I was still at my desk next to the window and what's more: yesterday I had a 150km car trip on which recording was stopped as well after about two hours of recording and while having a constant reception.

Included there's the error log from today - which is quiet unreadable due to obfuscation :-)  - which I hope can clarify things to you. It is created the moment that I opened Locus again to check for the current recording state.

After I noticed recording was stopped, I restarted recording (around 13:31) and checked again at 14:30. The same happened: Locus had to re-open and rebuild all over again and a new error log was created (included as well). No extra points were recorded, which could be because of my settings of course but I'm not sure because in the NMEA file there was no new entry either: the last entry was still the one of 9:20 and there was no new entry created for the recording (re-)started at 13:30

So, I'm detecting a couple of problems here:
  • Track recording stops after a while, probably when Locus is in the background
  • Restart recording doesn't seem to go very well after this kind of error
  • Restarting NMEA recording doesn't work either in this case

Please note: when starting a recording, stop recording after a little pause, restart recording after a little pause... both normal tracking as well as NMEA tracking work as expected!
Both 1.5.1 versions here (free and pro), are they expiring on a specific date or are they the market versions?
Works since version 0.9.28!
I did notice a problem while recording, returning to Locus and recording was paused by doing that, don't know how to reproduce and I didn't have that problem afterwards.
So until further notice, this problem is solved :)
You're right. It does. Hmm...
It did however disappear :-) I'll investigate it further.
Version: 0.9.28 ME
I need a little more testing on the restart unfinished track recording, but so far it looks great. I'll keep you posted on that.
There's a problem when recording is restarted: the positioning icon disappears. You can see the track advancing, but there's no arrow/dot that shows the current location.

How to reproduce
  • Start a recording
  • Pause the recording
  • Kill Locus manually
  • Restart Locus
At this point, you don't see the arrow anymore.
About question b:
Go to Settings > Map, then check Scale
Version: 0.9.27 ME

In the Tracks screen, tracks are automatically sorted by name. Of course, this will cause Mar 10 appear before Mar 2. You provided a nice way to order these tracks by date, which is great.

However, this ordering isn't remembered.
How to reproduce:
  • Go to the tracks screen
  • Order tracks by date
  • Return to the main screen
  • Go back to the tracks screen
Tracks are ordered by name again
Version: 0.9.27 ME

Yesterday, the track record (continually during the day) went just fine: the entire recording was successful.
When I came home, I paused recording and left it that way till this morning. Locus was moved out of the memory, so it had to be started again. When hitting record, it didn't remember that the track was paused, while the notification icon was still there. I restarted recording, got the message "unfinished track detected" and clicked OK to continue. When I arrived at my destination, I hit stop recording and got a Toast message that said something like "Process unsuccessful, Please restart downloading [...]" (it was a little to fast gone to remember the entire message)
I guess "downloading" should be "recording" in this case.

I restarted recording, the "unfinished track" message appeared again so I clicked "ok" and continued recording. When stopped, the track was saved. However, the track data between my first "continue recording" and my arrival at my destination is lost. The track does contain:
- The entire recording of yesterday
- The couple of seconds at my destination of today

Thus, I lost the data from home to my destination of today.

How to reproduce:
  • Start track recording
  • Pause track recording
  • Kill Locus (manually, using a task manager)
  • Start Locus
  • Start track recording, answer "ok" for the "unfinished track detected" dialog
  • Stop recording. Toast message appears
  • Restart recording, answer OK for  the "unfinished track detected" dialog
  • Stop recording. Recording is saved.
The data recorded between step 5 and 6 is lost.

Also keep the recording state in the service. When Locus is killed and restarted, read the recording state when the user hits the Recording functionality, thus presenting him/her a recording state there where he/she left it. I think implementing this will cause the "unfinished track detected" dialog disappear since you know the last recording state (probably "paused", but I guess it can be "recording" as well when Locus the app is killed while the service is still running - didn't try that one yet) and you know that the user wants to resume it when he/she hits "record" or he/she wants to finish it when he/she hits "stop", which will deprecate the dialog.
Cool! I was actually thinking only yesterday about how it would behave if recording was done as a service. It should be more stable. Indeed, I see the TrackRecordingService running. Ha!
Well, it's still recording, so that's great.

If it's still recording this evening, be sure I will kill Locus (app, not the services) manually just to see what happens  :P

Just tried MyTracks (long time) just to find out that they as well are using a Track Recording Service. You found it out by yourself, they needed 4 developers for it ;)

You're more than welcome. You're the one that deserves all credit for the magnificent app  :D
Yesterday, using version, I started a recording at 6:47:58 GMT. I wanted to try continual recording during the day (it helps that I'm next to a window all day and I have good reception). I hit the Home button to hide Locus and went off.
At 7:16:54 GMT I downloaded the NMEA track to my computer using Eclipse, so that the SD card remained mounted.

During the day, I didn't open Locus even once, I did use other applications. The GPS signal in the status bar was there all day at full reception.

At the end of the day, when I came home, I opened Locus to stop the recording. Then, things went very fast. What I saw was Locus starting entirely again (white screen, then map loading, ...) in stead of just coming back to the front and the GPS status gave me a "Searching for signal" icon (you know, the flickering icon). The recording seemed to be stopped in the morning, there was no record of my way back home.
The NMEA record goes up to 7:32:29 GMT then stops.
No error logs are created.

It confuses me, I can't find a way to reproduce this consistently :)
I was wondering... Are you logging anything and preferably everything with the tag Locus? I could try to run aLogCat continually, logging only the lines  Locus produces and trying to figure out what's going on... I however can't find any Locus-specific logging...

Today, I'm recording again the entire day, using 0.9.27 Market Edition. So far so good, Locus is still recording (NMEA file is still being updated) and I opened Locus a couple of times this morning. From now on, I'm not going to open it again though and see what happens.
Troubles & Questions / Unfinished tracks
March 07, 2011, 19:40:30
About that "continue unfinished track record"... When you stop a continued record, it won't get named automatically:
- Start a new track recording
- Kill Locus using a task manager or the default Android one
- Restart Locus, start recording
- The question "do you want to continue recording" appears. Click "yes"
- Then, stop the recording. It'll be saved as an unnamed track