From bf82f769a3af98307b5e6f0dff3326d0d0ba902f Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Tue, 5 May 2026 15:23:42 +0100 Subject: [PATCH] moved - online edit of handbook/computing/myphone.html --- handbook/computing/myphone.html | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/handbook/computing/myphone.html b/handbook/computing/myphone.html index 0c1f2a084..05fbacb8a 100644 --- a/handbook/computing/myphone.html +++ b/handbook/computing/myphone.html @@ -28,14 +28,15 @@ For the latest updates on why "battery saver" kills accurate location for the mo

The reason why

-

Phones assume that you are walking along streets, or running along tracks or cycling. They are very, very bad at making the right guesses on the Totes Gebirge plateau. - -

Location, location, location

-
GPS position controls
Android GPS setting
+

Phones assume that you are walking along streets, or running along tracks or cycling. They are very, very bad at making the right guesses on the Totes Gebirge plateau. + +

Location, location, location

+ +

Do not select the "high accuracy" location setting on your phone. Mostly this will snap your position to the nearest cafe or bierstube: by default it will use the nearest WiFi it can find and assume that you are there, and will ignore the perfectly reasonable GPS position it has recorded directly.

This is all explained by Google here.