Topics

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?

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.

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)?

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).

This issue - phone hangs while recording a track - has been discussed here at the forum before. Several weeks ago Menion rewrote the recording code and it go silent on the forum after that. Is it really true that nobody else is experiencing hang issues? I can't believe it is only me having serious trouble? This issue drives me crazy. About one out of 3 recordings causes the phone to go completely dead and I have to take out the battery to restart the phone. I once saw this message on the screen as the last message from a dying device: "Application Lotus does not respond".

I have tested track recording during 4 weeks now.
Here ere are my observations:

- not temperature dependent: one person on the forum claimed Desire has a main board overheat problem. That is definitely *not* the problem here. With Locus not running, the phone has never hang even though it has been so hot (inside the car windshield on a sunny day) that I have got a warning message. With Locus recording, it has hang even with free air cooling and 0 degrees C.

- doesn't matter if Locus is installed in internal memory or on the SD card: I have rooted my Desire, so I have moved most apps to the SD card. I later moved Locus back into internal memory to see if it made a difference. 50MB free memory space. Same hang issue.

- doesn't matter if other GPS apps are running: I have tried all kind of combinations. Hang happens just as often even if no other GPS apps are running.

- it ONLY happens when Locus is recording a track.

This is most likely an OS problem, either an Android problem or HTC Sense problem.

I know Menion said some weeks ago that the recording code is not water proof and recommended to use MyTracks or other apps to do track recording. However, I do not find it interesting to use Settings/Track Recording/"Use MyTracks" since it doesn't leave a real time track line on the map, and I do not get the same great features as from Locus recording.

Locus track recording is such a rich, useful and key feature, and everything else is so perfect with Locus now, so it is really sad that this problem is still there. When I go flying, I use Locus for recording, navigation and guiding. It is then really serious that the phone hangs during the flight, and I have to struggle with taking the battery out and restart the phone. Last Saturday I flew 5 legs, and the phone went dead on two out of those 5 recordings.

Any hope for a better world here, Menion?

There is a funny error in Settings/Track Recording/Interval (seconds):
- if I go into the menu, set a new value, and press OK, the settings displays (in yellow) "xx m", i.e. METERS. Now, if I return to the map view and then go back into the menu settings, the field correctly displays "xx s" (seconds). If I just go into the Interval menu again and press Ok for the existing value, the settings menu again shows "xx m".

- The chart grid lines are so dimmed that they are really hard to see, even indoors. Outdoors no chance.

- Also, would it be possible to step up the font size of the text along the axis? Indoors not too hard - outdoors in sunshine hard to see.

How to recreate the problem:
- turn off all internet connections (both GPRS and WiFi).
- select an offline map
- create a track. Two points is sufficient. Tap the "Compute route" button (3rd button from left on the track creation menu)
- Locus then complains: "Problem with internet connection"

If I enable internet connection, the "Compute route" completes.
Requirering internet connection when using offline maps can't be correct?

Points are organized in categories, which is very convenient. It would be just as convenient to have tracks organized in categories.

I understand Menion was forced by the map source providers to remove certain map sources from Locus, and that this is the reason behind the new release 1.5.2.
==>  But this is a disaster for Locus! What is left of map sources? Nothing - only OSM!

Is this going to be the future too? Aren't there any solutions to this? This is really, bad, bad news.

Some versions back the satellite screen had two command buttons at the bottom: "GPS on/off" and "Compass". Why did Compass disappear? That was a quick way to turn on/off map rotation by compass. Now I have to tap myself though Menu/Settings/Sensors/"Use hardware compass" and check/uncheck that box and back to map view. That is 5 steps.

Suggestion: The Rotate button at the bottom menu today has two sub menu commands: "Rotate map" and "Show view".
Could this be changed to the following 4 commands:

   - "North up"
   - "Bearing up"
   - "Rotate by compass"
   - "Show view"

In the menu Settings/Localization there are 4 entries for units (length, altitude, speed, angle). Would it be possible to display the selected unit below each entry head line, i.e. replacing the small text line "Choose default display units", "Distance units for height", etc. by the currently chosen unit? Now I have to go into each one just to see what is selected. I have seen this solution in other apps.

Locus Pro, version 1.4.0

The new guiding command "Nearest" incorrectly forces Guiding On Reverse back to Guiding On.

How to recreate the problem:
  - Create a track (straigt lines) with some few points.
  - Select Guide On Reverse.
  - Move map center closer to another point on the track but with a distance > Guiding/"Set next point".
  - Tap the new command "Nearest". Guiding correctly selects the new track point.
  - Next step goes wrong: move map center closer than Guiding/"Set next point". Guiding incorrectly jumps FORWARD to the next point as if Guiding On were active. It should jump BACK since Guiding On Reverse is active.

If you do not use the "Nearest" command, the Guide On Reverse jumps correctly backward on the track as you get within the Guiding/"Set next point" distance. So it is clear that it is the "Nearest" command that forces the guiding to normal (Guide On).

I discovered today a Waypoint guiding feature I was not aware of: Selecting "Guiding" in the Title field displays distance, bearing and estimated TIME to the waypoint. Track guiding doesn't display the time. Would that be possible? I imagine you have all required info and features there already, it is just a question of displayng it for Track guiding too.

I have been testing test release 1.3.0.3 with track guiding on two run exercises today  and realized the following issue (should be an easy fix):

If I am following a created track with guiding turned on, the guiding automatically jumps nicely to the next point when I am within Guiding/"Set next point" of the current point being guided to. Works really great in release 1.3.0.3.

But the issue is when I find it appropriate to pass the current guide point at a distance > "Set next point" value. Then the guiding will never give up the current point. Only way to make it jump to the next point is either to enter a higher "Set next point" value to trigger the jump, and then change back again, or to turn guiding off/on when the next point becomes the closer of the two points. Neither works very well.

So what would be really useful is this:
- if you tap the track (a point on the track), you get a pop-up menu with 3 commands today: "i", "Chart", "Guide Off". Add a new command here - "Next point", which will force the guiding to jump to the next point. I would think that should be very easy to implement, since all functionality is there today. The only thing needed is to let this command force a trigger of the "Set next point" condition.

Today tracks are sorted either from a ->z, from shortest-> longest (distance or time), from oldest -> newest, from fewest points -> most points.
You have the button with three squares and a DOWN arrow to select this sorting menu.

---> Would it be possible to add a similar menu button with an UP arrow to sort in the opposite direction?

That would be particularly useful for looking at the latest tracks. Today, you have to scroll down the whole list of tracks to get to the latest track, since that one is always at the bottom when sorted by date.

Case 1) I select one specific point and enable guiding to it. If I now tap the point and select "Hide" from the pop up menu, the guiding line is correctly turned off.
Case 2) I create a track and enable guiding to it. If I now deselect the track in the Tracks list, the guiding line remains on and the only way to turn it off, is to select guiding to a new point and then hide that point again. I assume the guiding line should turn off if the track is deselected.
Case 3) I create a track and enable guiding to it. I have GPS off. If I now have map center (red cross) close to one of the points, the guiding not necessarily selects guiding to that closest point. It rather seems arbitrary which point it picks. I thought guiding from map center should work even with GPS off, or will guiding only pick track points correctly from an active GPS position?

- If I create a track with guiding on, the guiding sound AND the guiding jump to next point are BOTH triggered by the distance value set in Guiding/"Set next point". The value set in Guiding/"Distance for sound" is ignored. I tried with Guiding/"Set next point" = 100 and Guiding/"Distance for sound" = 150. I tested this on three different tracks I created, each with 5-6 points and followed the guiding distance closely. The above happened consistantly for each point. ALSO - there is no sound for the last point (kind of makes sense in this picture, since there is no next point to jump to and sound is (incorrectly) triggered by the "set next point"). I assume the sound is supposed to be triggered by the Guiding/"Distance for sound", even when guiding on a created track (ref below).

- If I enable guiding to one specifically selected point, THEN Guiding/"Distance for sound" is used to trigger the sound.

The guiding info displayed above the guiding line is a great feature. However it seems to always being displayed at the leftmost end of the line as shown on the screen. So if target is to the left of current position, you have to pan the map until you get the target within the screen to see the guiding info (I know I can select the same guiding info in the Title field, but that is a separate selection). Guiding info should be displayed at the starting end of the line, i.e. your current position, since that is what you normally have centered on the map, and you want to see the updated info as you move.