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 - novus

Hi Menion.

Now I tried version 1.9.4 and the result is o.k., I think.

Whereas version saved 22 Points (first screenshot), version 1.9.2 saved 33 points (second screenshot) now version 1.9.4 saves 42 points on the same way.

I added a screenshot to show the difference.

So in my opinion this problem is solved for the moment.

Thank you very much!

Well, that's the way it looks like with version 1.9.2.

I did the way twice (with exatly the same starts and stops as I described above) and with both trials the result was like this:
Hi Menion.

What did you do?  :shock:

With version 1.9.2 track recording seems to work better. Did you solve the problem accidentally...?  ;)

I'll test it more intensivly the next days but at the moment my impression is that there are less points lost. There are still some points lost, but not as much as before.  :D
o.k.  :)

By the way: I tested again with version 1.9.1 - no difference to  :|
Hi Menion.

Do you have a debug-version for me...?  :)
Debug version is no problem. But be aware: my phone is not rooted and I don't plan to do so for warranty-issues... ;)

On which android did you do your tests? I'm using 2.2.1 and svartbjorn has 2.2 as well, as I see. Perhaps it is an android-issue.

To test if there are influences of the memory, you could make it configurable, where to save tracks. So I could try to save it to internal memory, external sd-card and so on.

If nothing helps, you should think about a workaround like for example an option "rebuild track". This could be done with the NMEA-File, if it has been saved.

The next possibility to answer here in the forum for me is this evening, because I'm goin out with my family now.
o.k., I'll do it.

EDIT: done.
Hmmm... Where is the attached NMEA-file...?

Next Trial.

EDIT: How can I attach the NMEA-file? It isn't shown here, although I uploaded it... Probably too big

EDIT 2: It's even too big for PM... :x (abaout 161.000 characters)

So how can you get it, menion?  :oops:
Hi menion.

Here is an NMEA-File of a track, which had half the error. :)

That means, that the track did not completely stop but lost a lot of points with available positions.

I added a screenshot of the track with manually added hints.

Short description:

1.) This is where I switched on GPS and got the fix with accuracy of 5 m. Then I switched the screen off and started biking.

2.) Here I made a short stop to have a look. So I switched on the screen, looked (track looked o.k.), and switched the screen off again. This in the recorded track is point no. 14. I went on biking.

You can see that from then on one more point is recorded, before a lot of points is missing although the position probably was available (from my experience with my track in the car, I described above). I followed the street "Am Kesselberg".

3.) Here locus wrote a position again. This happens if you are lucky. When I went by car, it often didn't. Instead no more point was written for an long time (more than a minute), so I had to force locus to write by pressing pause and record again. Maybe that locus would have started writing again after a few minutes, but that of course is not satisfying...

The points are numbered correctly within the track, that means the stop (2) was at point 14, then number 15 was recorded and the first recorded point after the missing positions has the number 16. By the way: within the part of the track, where the points are missing, my velocity was the highest, for it's going down a hill...

The parameters were the following:

Track recording: Intervall 1m, 3s

GPS: refresh 2s

So, although this is only half the error, I hope this will help you to find the problem.

Thank you for your help!

Hi skids.

The original OSM-vector-maps have to be prepared for Locus with another tool, called mapsforge.

As I understand it, this tool also creates the style and the content of the map in locus.

The style at the moment is close to Osmarender.

Here you can see a view to Whitehall in London with official Osmarender style of OpenStreetMap: ... 8&layers=O

Compare it to what Locus shows to you. I think the difference should be caused by the configuration while creating *.map-files with mapsforge out of the original files, you can find here:

I personally would also like to see housenumbers, but this probably only can be done by menion and his team or by anyone who is able to install and use mapsforge, osmosis, and so on...

Is this correct so far, menion? ;)
Me again...

One question: is there an algorithm implemented in track recording to minimize the number of recorded points?

Sometimes it looks as if the number of points is reduced on straight parts of tracks and increased in case of changing direction.

If so, I would try to search the error there. When I look at my tracks, the error occurs on straight parts of the track...
O.K., I'll try my best. But I can't promise to reproduce it soon, because as svartbjorn wrote, this error does not occur during every track-recording.

For example today (one hour ago during my lunch-break) I did a recording by foot - without any problems.

Tomorrow I'll try the same track by bike (higher velocity). The way I am going / biking is the same, on which the error occured the first time - also while using my bike...

When I have the file then, I'll attach it to a post here in this thread.
Hi menion.

Yes I saved the track. I also displayed the track again after reboot the phone. The missing points were still missing.

So how can I help you?

I understand you this way:

1.) record another track while having enabled saving NMEA messages in GPS settings and then send you the recorded data, right?

2.) Do you need the recorded track of yesterday also?

Question: Which data can I send to you in what way...?

I start a new thread on this subject, although it's probably the same error I had when I posted in "Auto switch to " pause " mode during track recording"...

It has nothing to do with "pause"-mode. Also there is no dependence on screen's switch off.

It is just a stop of recording available (!) positions.

So, what happened?

I went by car (as a passenger) for more than 1 hour. So I had some time to start experimenting.

The track-recording started and I saw the red line.

But just after a few points the line stopped although the position (by the arrow) was shown correctly. That means, locus knew the correct position but did not write it into the track.

By pressing the "pause"-button, locus was obviously forced to write the last position into the track, so the red line was drawn from the last recorded point to the position where I pressed "pause". A lot of points between (although they had been registered and shown by the arrow) missed.

Pressing "record"-button again (the big red dot on button) made locus in average writing the next two or three points (sometimes more, sometimes even not a single one) again until the error occured again.

Remark: the correct position was availible the whole time (arrow was correct, exactly on the street, also following curves).

One time I had the following phenomenon: When screen was on, I saw that the red line stopped. I did nothing and waited for auto-screenoff. When I switched screen on again, the track had continued and the red line was correct even at the points that before had not been shown. But this was only one time and not (!) reproducable.  :?


The parameters: GPS-refresh every 2 seconds, intervall of track recording 3 seconds.

I use android 2.2.1 on a Samsung Galaxy S I9000.

Remark: I'm not sure, but it seems to me that it may depend on velocity. I had this error only, when I went by bike or by car, never, when I went by foot...  :!:  :?:
Well, I repeated yesterday's test today and it worked fine.

Another track recording yesterday (a different tour) also worked fine. So it is 2:1 for "working fine" against "error"... ;)

I'll try the same track the next days every morning, for it's my way to office.

If there are news, I'll let you know.  :)