Messages

gpx file attached

I made a canoe trip on a lake and used MyTracks to record the track. In the picture below this MyTracks recorded track is displayed with MyTracks (left) and with Locus (right). I understand there will be noise on the elevation because of inaccuracy of the computed GPS altitude, but MyTracks obviously use a stronger smoothing algorithm, making it more correct. MyTracks reports an accumulated "Elevation Gain" = 137 meters, while Locus reports 649 meters "Uphill Elevation"! This correlates to the way the two applications display the results, but the way Locus computes elevation gain it is not of any interest with results so completely off any meaningful level. I think elevation gain (uphill elevation) is a very interesting number, but Locus has to significantly improve the way it is calculated in order to make it useful and meaningful.

[attachment=0:p6rpi9r6]Both2.jpg[/attachment:p6rpi9r6]

I DO see the tracks now - see my previous post. (The other crash problem - see separate post. No, I haven't tried another SD card for that issue)

I understand most people do not experience these problems. But you forwarded to me an email from another user who had experienced exactly the same behavior and found that setting minimum frequency to 384MHz and tracking with myTracks at the same time solved his problem. That didn't make any difference for me.

1.8.8 didn't make any difference. I updated to 1.8.8 this morning before running to work and it crashed twice. I then also used min freq = 422MHz and tracked with both myTracks and Locus. Last time is crashed it was impossible to restart Locus, even after reboot. The "Recording" message kept popping up and I had to remove the cache/track_rec files to get Locus back into life.

Regarding your question if crash during recording only: I have also tried with Locus only showing the position and using myTracks for recording. Same issue. I have also experienced my phone going dead just by having Locus up and running with no recordings at all. So I now always exit Locus completely when finished. Then my phone is stable.

What about experience that both you and several other people had with the recording process that just died in version 1.7? That was something you fixed. I was wondering if a similar thing - i.e. a process that just dies - can be the case here too?

Do not worry about my problems Menion, if it is only me. But referring to the line above - if there is something similar here too, then that could point to some general issues with Locus. Just an idea, I don't know.

You are right - it was nonsence. I first did indeed not see any of my Locus tracks. But now I see them all. I don't know why I initially didn't see them. Anyway, good to know where they are stored and which file to backup. Thanks for answers!

The phone hang endless nightmare continues.

Now I have even tried this:
- different maps
- map centering on/off
- screen on/off
- minimum CPU speed stepped up one step (384MHz) and two steps (422MHz)
- recording using only Locus, only myTracks, and with both running at the same time
- different temperatures
- with/without other GPS apps at the same time
- 1s, 5s, 10s time interval between recorded points
- just having Locus showing current position without recording can cause phone hang
- screen can be on, position moving, I do not touch anything - then suddenly the error message "Application Locus not responding" and phone gets completely locked and dead

Very, very rarely I have experienced an (other) application crashing, but it always happens gracefully with no phone hang and app can be restarted. Locus is the only application that crashes brutally and causes the phone to lock up completely and I have to take out the battery.

Since I get this "Application Locus not responding" message if I have the screen on when it crashes, it seems that some of the processes that Locus started, has stopped or timed out. Since there was another thread here on the forum about arecording process that stopping for no reason. That issue was solved. But that fact that a process stopped for no reason, could it be another similar issue here?

I want to make a backup of my tracks. Looking through the directory tree under Locus, I can't find any "tracks" directory. I see directories like "poi" and "maps" etc, and expected to find something like "tracks"?
The only I find is "cache/track_rec". There I found two files with today's date. Since I had a problem with a crashed recording that prevented Locus to start (even after Locus reinstall and reboot if the phone), I deleted those two files in the "cache/track_rec" directory. That solved the start problem, but I lost ALL my recorded tracks too!

So where are the directory/files with the tracks such that I can make a backup?

I used MyTracks for some track recordings today. Then I selected those trakcs in Locus and hit "Merge tracks". Locus reported  "Action successful" and indeed created a new track - but with 0 points. A bug I guess?

Test version 1.8.4.1:

1) In the Tracks submenu there is now a new "+" button in the header line. The Satellite submenu has three such "+" buttons in the header line. They bring you to different setup menues. Usually Locus is using "+" to add something, e.g. a new point. Here it is to go to a setup menu. This is confusing. Specially it is messy to have three "+" in the Satellite submenu - impossible to remember which "+" goes to which setup menu. And I do not see the need for it.

2) I am excited to test if this new version that has focused on the track recording issues, also solves the phone hang incidents I have experienced when using Locus recording. My phone changed from crashing 5-8 times per day to 0 when I stopped using Locus recording four days ago.

I reported this in a thread some days ago, but case was marked as solved since the map centered again after restarting Locus.

However, today it happened again. Without custom screen the map was centering correctly. When I turned on custom screen, the map stopped centering.
--> I made the map centering again by simply selecting another skin and then back to the first again.
It haven't tested out the sequencing that causes the map to lock, but I can say that I started Locus this morning from scratch (I terminated with Exit yesterday) and enabled custom screen with the existing skin choice. At that point the map got locked.

I didn't need much time to find out that nothing helped, not even your new settings. But as we have talked about before, may be this is something with my phone and what I have installed.  It is a fact that I have had recording issues for a long time, but recently I have had an increasing number of cases where my phone goes completely locked and dead even when Locus is not running. I will now reformat my phone from scratch. There is something very unstable.

So, Menion, since nobody else seems to have recording issues with your latest versions (since 1.0 I think??), don't use any more effort on this. I'll reformat my phone, and then see.

Today there are 4 custom screens included and I can remember the difference between them. But as the number of custom screens grow, it can be hard to remember the differences. In the list of skins, a unique icon, like the one for MaleSmurf, can help a lot. The other skins are all using the standard Locus Free icon. Please make a unique icon for these as well Also. would it be an idea to double the height of each line in this list, making room for a 4x larger icon (which may be could be a screen shot)?

Forget this. Worked ok today.
Same setup as yesterday (and yes, I had the lower left button - Center Map - on also yesterday for sure). Only difference is that I restarted Locus.
Case closed.

Locus version 1.8.3: The new version of custom screen MaleSmurf does not keep map centered  when moving. Since map does not move, my position eventually moves out of the screen view. Otherwise it is a great screen. Map correctly keeps centered for the other custom screen that shows map (Simple Map).

Thank you for your feedback, Menion. From what you are saying, it is my understanding that you haven't heard about this issue from other users. So, yes, may be this is something with my phone.

There is one very interesting thing I read about on the Cyanogen forum (my new ROM without HTC Sense), that some users have problems with sending MMS with this ROM, but one user reported that setting the minimum CPU frequency one step up solved the problem. The CPU needs some time to step up the frequency upon a load change, and his theory was that a too low minimum frequency didn't allow the phone to respond quickly enough to initial network traffic when sending MMS.

I have been wondering if a too slow CPU (waking up from minimum frequency) could cause point writing and new position calculations to take so long time that requests are timing out, causing the hang situations. I am guessing that the work load for GPS positioning and recording is changing quickly all the time.

---> So to test out that theory, I have now stepped up the minimum CPU frequency setting from 245 MHz to the next higher step, 384 MHz. I am now testing this by using Locus'es own track recording with 1 second interval. Need more test experiences before drawing any conclusions, but so far, so good.

I will test this through this whole week to gather some experience, before trying the new features you have been so kind to implement. Thank you very much for your support and interesting in this, Menion. Let's first see if my new CPU setting makes any difference.