chore: Scheduled updates (Firmware, Hardware, Translations) (#7442)

Co-authored-by: github-merge-queue[bot] <118344674+github-merge-queue[bot]@users.noreply.github.com>
2026-10-02 16:44:33 -04:00 · 2026-09-29 12:38:36 +00:00
1 parent 888ea3db8c
commit 2c33852f93
@@ -508,6 +508,7 @@
    <string name="doc_keywords_mqtt">mqtt,broker,internet,bridge,uplink,downlink</string>
    <string name="doc_keywords_node_metrics">metrics,telemetry,signal,snr,rssi,battery,traceroute</string>
    <string name="doc_keywords_nodes">node,mesh,list,role,status,favorite,filter</string>
+    <string name="doc_keywords_notifications">notification,alert,sound,mute,reply,watch,wear os</string>
    <string name="doc_keywords_onboarding">setup,welcome,permissions,first-launch</string>
    <string name="doc_keywords_settings_module">module,serial,telemetry,canned,store-forward,administration</string>
    <string name="doc_keywords_settings_radio">settings,radio,lora,region,modem,device,power,security</string>
@@ -630,6 +631,11 @@
    <string name="firmware_edition">Версия прошивки</string>
    <string name="firmware_event_ended_banner">%1$s завершен. Вернитесь к стандартной Meshtastic прошивке, чтобы восстановить нормальные функции.</string>
    <string name="firmware_event_ended_button">Обновление прошивки</string>
+    <string name="firmware_maintenance_bootloader_available">Последнее: %1$s</string>
+    <string name="firmware_maintenance_bootloader_installed">Установлено: %1$s</string>
+    <string name="firmware_maintenance_bootloader_latest_hint">Последняя версия: %1$s. Установленная версия отображается после перезагрузки устройства в режиме обновления.</string>
+    <string name="firmware_maintenance_bootloader_up_to_date">Загрузчик обновлён</string>
+    <string name="firmware_maintenance_bootloader_up_to_date_hint">Обновлять нечего. Далее переустанавливается прошивка, что приведёт к перезагрузке устройства.</string>
    <string name="firmware_maintenance_cdc_unblock_failed">Файл стирания был скопирован, но устройство не начало стирание. Пока ничего не изменилось. Отключи устройство, дважды нажми кнопку сброса и повтори попытку.</string>
    <string name="firmware_maintenance_copy_failed">Не удалось скопировать файл на диск устройства. Убедите, что диск всё ещё подключён, и повтори попытку.</string>
    <string name="firmware_maintenance_data_unavailable">Список образов для стирания сейчас недоступен. Проверь подключение и повтори попытку или используй веб-флешер на flasher.meshtastic.org.</string>
@@ -1074,8 +1080,11 @@
    <!-- MESHTASTIC -->
    <string name="meshtastic">Meshtastic</string>
    <string name="meshtastic_alerts_notifications">Служебные уведомления</string>
+    <string name="meshtastic_alerts_notifications_description">Критические оповещения, отправляемые нодами в сеть.</string>
    <string name="meshtastic_app_name">Meshtastic</string>
    <string name="meshtastic_broadcast_notifications">Уведомления о сообщениях в общем чате</string>
+    <string name="meshtastic_broadcast_notifications_description">Сообщения, отправляемые в ваши каналы.</string>
+    <string name="meshtastic_client_notifications">Уведомления по радио</string>
    <string name="meshtastic_low_battery_notifications">Уведомление о низком уровне заряда</string>
    <string name="meshtastic_low_battery_temporary_remote_notifications">Уведомления о низком заряде батареи (избранные ноды)</string>
    <string name="meshtastic_mesh_beacon_notifications">Уведомления о приглашениях в сеть</string>
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Начало работы
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Първи стъпки
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Fehlersuchprotokolle
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Erste Schritte
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Primeros Pasos
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Arendaja logid
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: Vaata ja ekspordi rakenduse arendajalogi rakenduse seest ning lisa GitHubi probleemile jäädvustus vigade diagnoosimiseks – adb-d pole vaja.
 aliases:
  - arendaja-logid
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Töölaud

-Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil **Rakenduse logid** rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi.
+Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil **Rakenduse logid** rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Seotud teemad

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: Esimese käivitamise seadistus — õigused, sissejuhatav voog ja järgmised sammud pärast raadio ühendamist.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic kasutab sinu asukohta ka järgmiseks:
 - Calculating distances to other nodes
 - GPS koordinaatide jagamine teiste kärgvõrgu liikmetega (kui lubatud)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Virheenjäljityslokitiedot
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: Tarkastele ja vie sovelluksen omat virheenjäljityslokitiedot suoraan sovelluksesta ja liitä lokitiedot GitHub-vikaraporttiin ongelmien selvittämisen helpottamiseksi — adb:tä ei tarvita.
 aliases:
  - debug-lokitiedot
@@ -47,7 +47,7 @@ Liitä tämä tiedosto GitHub-vikaraporttiisi.

 ## Työpöytä

-Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten **Sovelluslokit**-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla.
+Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten **Sovelluslokit**-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Aiheeseen liittyvät aiheet

@@ -1,7 +1,7 @@
 ---
 title: Aloittaminen
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: Ensimmäisen käynnistyksen määritys — käyttöoikeudet, käyttöönottoprosessi ja seuraavat vaiheet radion yhdistämisen jälkeen.
 aliases:
  - ensimmäinen käynnistys
@@ -54,6 +54,8 @@ Meshtastic käyttää sijaintiasi myös seuraaviin tarkoituksiin:
 - Etäisyyksien laskeminen muihin radioihin
 - GPS-koordinaattiesi jakaminen muiden verkon jäsenten kanssa (jos käytössä)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Myönnä **Sovelluksen käytön aikana**. Sovellus ei pyydä taustasijaintia — sen manifestissa ei ole ACCESS_BACKGROUND_LOCATION-oikeutta — joten Android ei tarjoa **Aina**-vaihtoehtoa, ja sijaintipäivitykset tapahtuvat sovelluksen ollessa etualalla tai sen suorittaessa taustapalvelua.

 Sijaintikäyttöoikeuden hylkääminen ei estä sovelluksen muuta toimintaa. Android 12:ssa ja uudemmissa versioissa Bluetooth toimii edelleen, ja vain kartta, sijainnin näyttäminen ja sijainnin jakaminen poistuvat käytöstä. Android 11:ssä ja uudemmissa versioissa myös Bluetooth-skannaus estyy, koska Android liittää sen tähän käyttöoikeuteen — lisäksi järjestelmän **Sijaintipalvelut** on oltava käytössä, jotta skannaus palauttaa tuloksia.
@@ -328,6 +328,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Come iniziare
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: デバッグログ
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: アプリのデバッグログをアプリ内で表示・エクスポートし、バグの診断に役立つよう GitHub の issue にキャプチャを添付できます。adb は不要です。
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ The **App logs** tab shows the most recent log lines from **this app only** —

 ## デスクトップ

-デスクトップアプリにはシステムの logcat がないため、「**アプリログ**」タブは代わりに、アプリ自身がキャプチャしたログ出力を表示します。検索、絞り込み、エクスポートは同じように機能します。
+デスクトップアプリにはシステムの logcat がないため、「**アプリログ**」タブは代わりに、アプリ自身がキャプチャしたログ出力を表示します。検索、絞り込み、エクスポートは同じように機能します。 Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## 関連トピック

@@ -1,7 +1,7 @@
 ---
 title: はじめに
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: 初回起動時のセットアップ：権限、オンボーディングの流れ、無線機を接続した後の次のステップ。
 aliases:
  - 初回起動
@@ -54,6 +54,8 @@ Meshtastic は、次の目的でも位置情報を使用します：
 - 他のノードまでの距離を計算する
 - 他のメッシュメンバーと GPS 座標を共有する（有効な場合）

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Отладочные журналы
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: Просматривайте и экспортируйте отладочные журналы приложения из самого приложения, а также прикрепляйте их к задаче на GitHub для помощи в диагностике ошибок — без необходимости в adb.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ The **App logs** tab shows the most recent log lines from **this app only** —

 ## Desktop

-У компьютерного приложения нет системного logcat, поэтому вкладка **Журналы приложения** вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же.
+У компьютерного приложения нет системного logcat, поэтому вкладка **Журналы приложения** вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Связанные темы

@@ -1,7 +1,7 @@
 ---
 title: Начало работы
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: Настройка при первом запуске — разрешения, процесс знакомства с приложением и следующие шаги после подключения твоей радиостанции.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic также использует местоположение для:
 - Вычисление расстояний до других нод
 - Обмен GPS-координатами с другими участниками сети (если включено)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Предоставьте **"При использовании приложения"**. Приложение не запрашивает фоновое определение местоположения — в его манифесте нет параметра `ACCESS_BACKGROUND_LOCATION` — поэтому Android не предлагает опцию "Всегда", и обновление местоположения происходит, когда приложение находится на переднем плане или выполняет функцию службы переднего плана.

 При отключении остальная часть приложения продолжает работать: на Android 12 и более новых версиях Bluetooth не затрагивается, отключаются только отображение местоположения на карте и обмен данными о местоположении. На Android 11 и более ранних версиях сканирование Bluetooth также прекращается, поскольку для этого требуется разрешение, которое Android блокирует. Кроме того, для получения каких-либо результатов сканирования необходимо включить системные **службы определения местоположения**.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**
@@ -1,7 +1,7 @@
 ---
 title: Debug Logs
 nav_order: 22
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: View and export the app's own debug logs from inside the app, and attach a capture to a GitHub issue to help diagnose bugs — no adb required.
 aliases:
  - debug-logs
@@ -47,7 +47,7 @@ Attach that file to your GitHub issue.

 ## Desktop

-The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way.
+The desktop app has no system logcat, so the **App logs** tab shows the app's own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.

 ## Related Topics

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 nav_order: 1
-last_updated: 2026-08-30
+last_updated: 2026-09-28
 description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
 aliases:
  - first-launch
@@ -54,6 +54,8 @@ Meshtastic also uses your location for:
 - Calculating distances to other nodes
 - Sharing your GPS coordinates with other mesh members (if enabled)

+On Android 12 and newer, choose **Precise** to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
+
 Grant **"While using the app"**. The app does not request background location — `ACCESS_BACKGROUND_LOCATION` is not in its manifest — so Android will not offer an "Always" option, and position updates happen while the app is in the foreground or running its foreground service.

 Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system **Location Services** must also be switched on for a scan to return anything.
@@ -331,6 +331,7 @@ appears only when your own node is selected. It is grouped rather than flat:

 - **Allow analytics and crash reporting** — opt in or out of diagnostics.
 - **Provide phone location to mesh** — share this phone's position when the node has no GPS fix.
+  It needs precise location: with approximate location allowed, turning it on asks for precise.
 - **Homoglyph encoding** — how look-alike characters in names are handled.

 **Appearance**