[android] Always use newest position available in every mode

Signed-off-by: Harry Bond <me@hbond.xyz>

Signed-off-by: Harry Bond <me@hbond.xyz>

android/app/src/fdroid/play/version.yaml

@@ -1 +1 @@
-version: 2025.07.23-2-FDroid+25072302
+version: 2025.03.02-7-FDroid+25030207

android/app/src/main/java/app/organicmaps/location/LocationHelper.java

@@ -34,10 +34,7 @@ import app.organicmaps.util.log.Logger;
 
 public class LocationHelper implements BaseLocationProvider.Listener
 {
-  private static final long INTERVAL_FOLLOW_MS = 0;
-  private static final long INTERVAL_NOT_FOLLOW_MS = 3000;
-  private static final long INTERVAL_NAVIGATION_MS = 1000;
-  private static final long INTERVAL_TRACK_RECORDING = 0;
+  private static final long INTERVAL_MS = 0;
 
   private static final long AGPS_EXPIRATION_TIME_MS = 16 * 60 * 60 * 1000; // 16 hours
   private static final long LOCATION_UPDATE_TIMEOUT_MS = 30 * 1000; // 30 seconds
@@ -318,18 +315,14 @@ public class LocationHelper implements BaseLocationProvider.Listener
 
   private long calcLocationUpdatesInterval()
   {
-    if (RoutingController.get().isNavigating())
-      return INTERVAL_NAVIGATION_MS;
-
-    if (TrackRecorder.nativeIsTrackRecordingEnabled())
-      return INTERVAL_TRACK_RECORDING;
-
     final int mode = Map.isEngineCreated() ? LocationState.getMode() : LocationState.NOT_FOLLOW_NO_POSITION;
     return switch (mode)
     {
-      case LocationState.PENDING_POSITION, LocationState.FOLLOW, LocationState.FOLLOW_AND_ROTATE ->
-          INTERVAL_FOLLOW_MS;
-      case LocationState.NOT_FOLLOW, LocationState.NOT_FOLLOW_NO_POSITION -> INTERVAL_NOT_FOLLOW_MS;
+      case LocationState.PENDING_POSITION,
+           LocationState.FOLLOW,
+           LocationState.FOLLOW_AND_ROTATE,
+           LocationState.NOT_FOLLOW,
+           LocationState.NOT_FOLLOW_NO_POSITION -> INTERVAL_MS;
       default -> throw new IllegalArgumentException("Unsupported location mode: " + mode);
     };
   }

docs/CONTRIBUTING.md

@@ -25,7 +25,8 @@ When reporting a bug please provide as much information as possible: OS and appl
 list of actions leading to a bug, a log file produced by the app.
 
 When using CoMaps app on a device, use the built-in "Report a bug" option:
-on Android it creates a new e-mail with a log file attached. Enabling logs in CoMaps settings on Android
+on Android it creates a new e-mail with a log file attached. Your issue will be processed much
+faster if you send it to <bugs@comaps.app>. Enabling logs in CoMaps settings on Android
 before sending the bug report also helps us a lot with debugging.
 
 ### Translations

tools/unix/update_gplay_relnotes.sh

@@ -1,11 +1,9 @@
 #!/usr/bin/env bash
 
 # Concatenates Android release notes in all languages into a single output format
-# suitable to upload to Google Play to add or update existing notes.
+# suitable to upload to Google Play to update existing notes.
 
-# Original relnotes files:
-GPLAY_NOTES=android/app/src/fdroid/play/listings/*/release-notes.txt
-# also symlinked for Triple-T automation to android/app/src/google/play/release-notes/*/default.txt
+GPLAY_NOTES=android/app/src/google/play/release-notes/*/default.txt
 
 for x in $(ls $GPLAY_NOTES); do
   l=$(basename $(dirname $x));