Hi,
I encountered an issue while recording a hicking track .
All seemd to go as well as usual until I paused the recording while stopping for a lunch break; when trying to resum the recording the track was pratically gone, I tried several times to pause and re run but there was now way to resume the track recording that wasn't even visible on the map.
I then decided to stop the recoding and suddently the track reappeard on the map.
Then I begin recording a new track but it was almost impossible to see the track line on the map, had the recoding icon was on (green flashing icon) but nothing was recorded, so I lost all my way back to the beginning of the trail.
At the end would have been a pretty long trak of over 25km , luckly I had recorded the track with a garmin but this was my first bad esperience with IOS ver
I always keep y old android phone in the backpack for double recording in case of failure but his time I didn't, unfortunately :)
In the attached screen shot you can see the first recorded part of the track and short folLocueIOSissue_July25.jpglowing trakcs that led to the error.
Just another quick question, why the short track (that was impossible to keep running) shows a green and red dot ?
Thank you for any advice
Piero
Hi, thanks for valuable feedback. This fail to properly record your activity was indeed unfortunate.
So when you restarted track recording, the app records portion of the activity but then stop completely? Could you please share that activity via link? We will discuss this with responsible developer once he will be available.
Green dot indicates start of the track, while red one is finish.
However please note, that BETA versions can be sometimes unstable. Also latest BETA is already older than public version available via App Store.
Hi, thanks again for your report. I'll try to replicate your issue. Could you please check your recording settings in the meantime? There are options to store location samples during track recording in the recording profile. Make sure the required location accuracy is set to maximum so all location samples can be stored. Also, ensure that the time and distance intervals between stored location samples are configured correctly.
Hello Petr and thank you for your support.
I confirm that the settings are exactely as shown on your screenshot for the related activity type (Hiking) I created and are as follow:
-Interval 5 mt
-Interval time 2 sec
-Recording condition: Distance OR Time
-Precision : No limit (300 mt)
Just Cycling has a different interval of 10 mt between recorded points.
Hello Jan,
when I restarded / unpaused the initial track nothing was visibile, even the track, so I couldn't tell if something was recorded, there was no colored line as well .
So I stopped the recording and began a new one but as shown in the screenshot, it kept stopping as well.
My question on the green and red dot was just becouse they appeard only on the second track but have never seen then in the past, was that due to a particular recording mode?
Btw, today I recoded a cycling track and all went prefect as usual ;)
Piero
Quote from: Jan Čapek on August 13, 2025, 15:38:00Hi, thanks for valuable feedback. This fail to properly record your activity was indeed unfortunate.
So when you restarted track recording, the app records portion of the activity but then stop completely? Could you please share that activity via link? We will discuss this with responsible developer once he will be available.
Green dot indicates start of the track, while red one is finish.
However please note, that BETA versions can be sometimes unstable. Also latest BETA is already older than public version available via App Store.
Hi, I attempted to simulate the described behavior by pausing track recording, but I was unsuccessful. Nevertheless, I'll describe how the recording is done under the hood, and maybe we can find the mystery. (Sorry for the longer text):
- The location of the device is obtained from the iOS via the so-called location manager. A separate location manager manages the device's position on the map, while another location manager is used for track recording. Both managers are configured slightly differently. If you switch off the display or switch to another app, the location manager, which indicates the device's position on the map, is automatically switched off to save energy. The location manager for track recording works in the background. It is also configured for faster response. Therefore, you can sometimes see a difference between the current position for track recording and the user's position on the map. It is normal behaviour, and after a particular time, both locations should almost match (the difference should be in meters).
- At the beginning of the track recording, the app waits till the first valid location is received from the location manager. This can take even half a minute if you stay in the rugged terrain and the GPS signals are weak. The app ignores all invalid locations. No track line is drawn on the map. When track recording is paused, the location manager is switched off to save energy, and the current location has to be established again when track recording is resumed. It can again take some time.
- If you start a new track recording or resume one, start moving. The valid location will come after a few seconds.
- The simplified version of the recorded track is displayed on the map. It means that every 5th location is displayed to conserve energy.
- The green points on the recorded track indicate the start point, and the red ones indicate the end of the track section.
- All received location samples are stored in a separate database and processed after the track recording is finished. If you stay in the same place during track recording, only a few samples are kept, and the rest of them are not copied to the final track (stop detection).
Summary: If you don't see the recorded track on the map immediately after starting or resuming the track recording, don't panic, keep moving, and wait till valid locations are received. To investigate the problem, would it be possible to export this track as GPX? I can see more details with location accuracy.
Hi Petr,
thank you for the very interesting explanation of what happens "bEhind the hood".
I can confirm you that i kept moving and that's when I found the issue, the track was not even displayed on the map even after several hundreds meters of walk and with several satellites visibile/connected.
Anyway attached the link to the gpx of the main track that was paused and then unable to resume (can't attached to the msg due to its size over 2mb):
https://link.locusmap.app/t/p9n2yn
and the two tracks that I recorded trying to record the second half of the trail.
Thank you very much
Piero
Hi Piero,
Thank you for sharing the track. I have imported and analyzed it, so you can disable sharing now. The location accuracy aligns well with the terrain. I noticed some of the worst samples had a horizontal accuracy of 15 meters, which is typical in wooded areas. I don't believe this is the source of the problem.
During my weekend test, I stayed in an area with a very poor GSM signal. I found that updates for Points of Interest (POIs) and maps can sometimes be delayed when the network connection is weak and the map source is set to online or automatic. It can also affect the drawing of the currently recorded track, and it should not happen. I am currently working on resolving this issue.
As a workaround to prevent any glitches in map updates, I recommend switching the map source to offline mode if you are in an area with poor GSM coverage. I hope to address the network connection issues in the next app release.
Best regards,
Petr
That's might be the reason,
When I first installed LocusMap on mIphone 16Pro, I have immediately downloaded the offline LoMap but I did not switch the settings to USE the offline, I just figure out now that it's not a default setting to utilize the offline map insteasd the online if the first is installed.
Will test soon.
Thank you very much for your help!
Oh, just a note for a possible new feature to add to the IOS versione that I missed a lot: Distance circles while recording and live elevation while moving the cursor on the map;)
Thak you
Piero
Hi Piero,
Maps are switched to the automatic data source after installation. It means that the map itself and POIs are read from the offline source. Highs (hill shades) and POI details, such as photos, are downloaded from the server. The target is to provide users with fresh information. A poor internet connection can cause some timeouts and lag. So in such areas, it is better to switch to an offline data source. The hill shades will not be used (it will be added to the offline maps later), but the map should be more responsive, and energy consumption will be lower.
Regarding distance marks during recording, you are another user requesting this feature, so I'll increase the priority of this topic.
Best regards,
Petr