Messages

Is it possible to set alarms for the distance cycled.  for example I would like locus maps to allow me to specify a sequence of distances travelled and to have alarms pop up at 0.5km, 0.2km 0.1km before the distance and then at the distance itself.

My Gold subscription ( Paid annually in October) reverted to the community/standard version after an update.  This was noticed at the start of a long (100km) bicycle ride that I wanted to capture data for.

To allow data capture I used the offer for a one month free trial but of course forgot to cancel the temporary second subscription.   This led to me having two subscriptions to Locus maps (one of which I have now cancelled). 

Apologies.  I should have said I'm using a smartphone with Android 11.  The loss of connection occurs if an autopause is sufficiently long, or if I manually pause the recording.

I do long distance cycling and use Locus maps for navigating my routes.  When I'm riding I have bluetooth sensors for heartrate, speed and cadence.  If I stop for a short while, e.g. to mend I puncture, or stop at a cafe and pause the recording, the connection with sensors is lost and I must manually restart them.

This has been a long term problem which was evident in the previous incarnation of Locus maps.

Am I doing something wrong or is this an issue that cannot be resolved?

Audax is the sport of long distance cycling.   Consequently, I frequently follow gpx routes using my phone over distances of 2/300 km.  The experience of using Locus Maps (Full version) for navigating by gpx is marred by a number of minor issues.  I'd either like to raise these issues as problems or receive pointers as to where the respective setting options are located.

1.  Compass display is obscured

I have a 3x4 item display at the top of the screen.  This covers the compass.  Is there an option to relocate where the compass displays on the screen.

2. Route Alignment - 2 issues

I have the map set to auto rotate.  My expectation is that the blue line of the route should intersect the top of the screen.

Problem 1.  Frequently the gpx line is just left to right on the screen or even aligned so that the route intersects the bottom of the screen.

Problem 2.  The arrow icon points back along the part of the route I have ridden and not in the direction I have yet to ride.

3. Bluetooth devices do not reconnect after a pause

I use BT 4 LTE HR and Speed/Cadence devices.  These devices connect as expected when I start route recording.  However, if I postpone route recording at the start due to a short delay, or if I pause recording due to a scheduled stop, the bluetooth devices never reconnect when I restart route recording (at least the display of the values generated by those devices is not actively displayed).  If I go to setting the devices are generally disconnected.  I connect the devices then the displays come back.

4. The calculation of moving average speed does not acknowledge pauses in recording

Due to the distance ridden, there are stops for eating and refilling water bottles etc.  I pause the recording at such stops to make sure that the gps also stops recording.  I know there is a setting to stop the gps recording when I stop but that doesn't seem to work, hence the manual pause.  The main issue is that the time for which the recording is stopped is not included in the calculation of the moving average speed.  Audax has a minimum speed so this value is useful to know.  It would be helpful to have a moving average speed which did not exclude pause time from its calculation.

Last Wednesday/Thursday I did a 300km bike ride.   I ran into two problems.

• Sometimes the autorotate maps feature had the route going down or across the screen  rather than up the screen.

• Tracking did not resume after breaks (these would have been 30 minutes +)  Sensors were redetected on restarting but I lost sections of the route recording.  This happened after just leaving locus maps running whilst at a break stop or if I paused the recording.  Once I'd been caught out by this I stopped the ride at each break and saved that portion of the ride.  The annoyance here was that I lost the overall average  and moving average speeds which are quite useful for monitoring progress when Audaxing.

I was doing a mandatory gpx route which meant that to get the ride validated I had to provide a full record of the ride which matched the gpx I had previously submitted so gaps in the recording were an issue.