diff --git a/androidApp/src/main/assets/firmware_releases.json b/androidApp/src/main/assets/firmware_releases.json
index 2c6ed92f7..ac6bdf3c3 100644
--- a/androidApp/src/main/assets/firmware_releases.json
+++ b/androidApp/src/main/assets/firmware_releases.json
@@ -188,6 +188,18 @@
     ]
   },
   "pullRequests": [
+    {
+      "id": "10850",
+      "title": "Update LovyanGFX to v1.2.24",
+      "page_url": "https://github.com/meshtastic/firmware/pull/10850",
+      "zip_url": "https://img.shields.io/badge/Flash_this_PR_in_the_Web_Flasher-2C2D3C?style=for-the-badge"
+    },
+    {
+      "id": "10849",
+      "title": "Update Quency-D_chsc6x digest to 3b2b6ce",
+      "page_url": "https://github.com/meshtastic/firmware/pull/10849",
+      "zip_url": "https://img.shields.io/badge/Flash_this_PR_in_the_Web_Flasher-2C2D3C?style=for-the-badge"
+    },
     {
       "id": "10846",
       "title": "InkHUD: GPS improvements",
@@ -218,6 +230,12 @@
       "page_url": "https://github.com/meshtastic/firmware/pull/10839",
       "zip_url": "https://img.shields.io/badge/Flash_this_PR_in_the_Web_Flasher-2C2D3C?style=for-the-badge"
     },
+    {
+      "id": "10829",
+      "title": "exclude the variant from LTO",
+      "page_url": "https://github.com/meshtastic/firmware/pull/10829",
+      "zip_url": "https://img.shields.io/badge/Flash_this_PR_in_the_Web_Flasher-2C2D3C?style=for-the-badge"
+    },
     {
       "id": "10807",
       "title": "Add DeltaPlusProto Edict board variant",
diff --git a/core/resources/src/commonMain/composeResources/values-bg/strings.xml b/core/resources/src/commonMain/composeResources/values-bg/strings.xml
index 1154e7acb..49f3d7bef 100644
--- a/core/resources/src/commonMain/composeResources/values-bg/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-bg/strings.xml
@@ -229,6 +229,7 @@
     <string name="debug_filter_included">Филтъра включва</string>
     <string name="debug_filter_preset_title">Предварително зададени филтри</string>
     <string name="debug_filters">Филтри</string>
+    <string name="debug_logcat_refresh">Опресняване</string>
     <string name="debug_logs_export">Експортиране на журнали</string>
     <string name="debug_panel">Панел за отстраняване на грешки</string>
     <string name="debug_search_clear">Изчистване на търсенето</string>
diff --git a/core/resources/src/commonMain/composeResources/values-de/strings.xml b/core/resources/src/commonMain/composeResources/values-de/strings.xml
index 3c2780cac..6d64ac3bd 100644
--- a/core/resources/src/commonMain/composeResources/values-de/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-de/strings.xml
@@ -307,6 +307,7 @@
     <string name="debug_filter_preset_title">Voreingestellte Filter</string>
     <string name="debug_filters">Filter</string>
     <string name="debug_log_api_enabled">Debug-Protokoll-API aktiviert</string>
+    <string name="debug_logcat_refresh">Aktualisieren</string>
     <string name="debug_logs_export">Protokolle exportieren</string>
     <string name="debug_panel">Debug-Ausgaben</string>
     <string name="debug_search_clear">Neue Suche</string>
@@ -429,6 +430,7 @@
     <string name="doc_section_developer">Entwicklerhandbuch</string>
     <string name="doc_section_user">Benutzerhandbuch</string>
     <string name="doc_title_connections">Verbindungen</string>
+    <string name="doc_title_debug_logs">Fehlersuchprotokolle</string>
     <string name="doc_title_desktop">Desktop App</string>
     <string name="doc_title_discovery">Entdecken</string>
     <string name="doc_title_firmware">Firmwareaktualisierungen</string>
diff --git a/core/resources/src/commonMain/composeResources/values-et/strings.xml b/core/resources/src/commonMain/composeResources/values-et/strings.xml
index bec6c686f..10fae8469 100644
--- a/core/resources/src/commonMain/composeResources/values-et/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-et/strings.xml
@@ -309,6 +309,7 @@
     <string name="debug_filter_preset_title">Eelseadistatud filtrid</string>
     <string name="debug_filters">Filtrid</string>
     <string name="debug_log_api_enabled">Silumislogi API lubatud</string>
+    <string name="debug_logcat_refresh">Värskenda</string>
     <string name="debug_logs_export">Salvesta logi</string>
     <string name="debug_panel">Arendaja paneel</string>
     <string name="debug_search_clear">Puhasta otsing</string>
diff --git a/core/resources/src/commonMain/composeResources/values-fi/strings.xml b/core/resources/src/commonMain/composeResources/values-fi/strings.xml
index 2db703406..ee02811c6 100644
--- a/core/resources/src/commonMain/composeResources/values-fi/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-fi/strings.xml
@@ -311,6 +311,7 @@
     <string name="debug_filter_preset_title">Oletussuodattimet</string>
     <string name="debug_filters">Suodattimet</string>
     <string name="debug_log_api_enabled">Vianetsintälokirajapinta käytössä</string>
+    <string name="debug_logcat_refresh">Päivitä</string>
     <string name="debug_logs_export">Vie lokitiedot</string>
     <string name="debug_panel">Vianetsintäpaneeli</string>
     <string name="debug_search_clear">Tyhjennä haku</string>
@@ -907,7 +908,17 @@
     <string name="match_any">Täsmää yhteen | kaikkiin</string>
     <string name="max">Kaikki</string>
     <!-- MESH -->
+    <string name="mesh_beacon_invitations_title">Mesh-verkon kutsut</string>
+    <string name="mesh_beacon_notification_body">Lähellä oleva mesh-verkko kutsuu sinut liittymään</string>
+    <string name="mesh_beacon_notification_title">Mesh-verkon kutsu</string>
+    <string name="mesh_beacon_offer_channel">Kanava: %1$s</string>
+    <string name="mesh_beacon_offer_discover">Haku</string>
     <string name="mesh_beacon_offer_dismiss">Hylkää</string>
+    <string name="mesh_beacon_offer_from_unknown">Tuntemattomasta radiosta</string>
+    <string name="mesh_beacon_offer_join">Liity</string>
+    <string name="mesh_beacon_offer_preset">Esiasetus: %1$s</string>
+    <string name="mesh_beacon_offer_region">Alue: %1$s</string>
+    <string name="mesh_beacon_offer_title">Mesh-verkon kutsu</string>
     <string name="mesh_map_location">Meshtastic kartan sijainti</string>
     <string name="mesh_map_location_description">Ottaa käyttöön puhelimen sijainnin sinisenä pisteenä meshtastic kartalla.</string>
     <!-- MESHTASTIC -->
@@ -917,6 +928,7 @@
     <string name="meshtastic_broadcast_notifications">Yleislähetysviestien ilmoitukset</string>
     <string name="meshtastic_low_battery_notifications">Akun vähäisen varauksen ilmoitukset</string>
     <string name="meshtastic_low_battery_temporary_remote_notifications">Akun vähäisen varauksen ilmoitukset (suosikkilaitteet)</string>
+    <string name="meshtastic_mesh_beacon_notifications">Mesh-verkon ilmoitukset</string>
     <string name="meshtastic_messages_notifications">Suorien viestien ilmoitukset</string>
     <string name="meshtastic_new_nodes_notifications">Uuden laitteen ilmoitukset</string>
     <string name="meshtastic_service_notifications">Palveluilmoitukset</string>
@@ -1425,6 +1437,7 @@
     <string name="status_message">Tilaviesti</string>
     <string name="status_message_config">Tilaviestin asetukset</string>
     <string name="stay_connected_anywhere">Pysy yhteydessä kaikkialla</string>
+    <string name="stop_connecting">Lopeta yhdistäminen</string>
     <string name="store_forward">Varastoi &amp; välitä</string>
     <string name="store_forward_config">Varastoi &amp; välitä asetukset</string>
     <string name="store_forward_enabled">Varastoi &amp; välitä käytössä</string>
diff --git a/core/resources/src/commonMain/composeResources/values-fr/strings.xml b/core/resources/src/commonMain/composeResources/values-fr/strings.xml
index ece9df7a9..cd1cb7f26 100644
--- a/core/resources/src/commonMain/composeResources/values-fr/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-fr/strings.xml
@@ -301,6 +301,7 @@
     <string name="debug_filter_preset_title">Filtres prédéfinis</string>
     <string name="debug_filters">Filtres</string>
     <string name="debug_log_api_enabled">API de journalisation de débogage activée</string>
+    <string name="debug_logcat_refresh">Actualiser</string>
     <string name="debug_logs_export">Exporter les logs</string>
     <string name="debug_panel">Panneau de débogage</string>
     <string name="debug_search_clear">Effacer la recherche</string>
diff --git a/core/resources/src/commonMain/composeResources/values-ja/strings.xml b/core/resources/src/commonMain/composeResources/values-ja/strings.xml
index 3fc8d6e15..3d6d41aec 100644
--- a/core/resources/src/commonMain/composeResources/values-ja/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ja/strings.xml
@@ -306,6 +306,7 @@
     <string name="debug_filter_preset_title">プリセットフィルタ</string>
     <string name="debug_filters">フィルタ</string>
     <string name="debug_log_api_enabled">デバッグログAPIを有効化</string>
+    <string name="debug_logcat_refresh">更新</string>
     <string name="debug_logs_export">ログのエクスポート</string>
     <string name="debug_panel">デバッグ</string>
     <string name="debug_search_clear">検索をクリア</string>
diff --git a/core/resources/src/commonMain/composeResources/values-ro/strings.xml b/core/resources/src/commonMain/composeResources/values-ro/strings.xml
index 1e5be4706..e1b6f1c28 100644
--- a/core/resources/src/commonMain/composeResources/values-ro/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ro/strings.xml
@@ -235,6 +235,7 @@
     <string name="debug_filter_preset_title">Presetări filtre</string>
     <string name="debug_filters">Filtre</string>
     <string name="debug_log_api_enabled">Debug log API activat</string>
+    <string name="debug_logcat_refresh">Reimprospatare</string>
     <string name="debug_logs_export">Export jurnale</string>
     <string name="debug_panel">Panou de depanare</string>
     <string name="debug_search_clear">Ștergeți căutarea</string>
diff --git a/core/resources/src/commonMain/composeResources/values-ru/strings.xml b/core/resources/src/commonMain/composeResources/values-ru/strings.xml
index 614c766d7..ab594171f 100644
--- a/core/resources/src/commonMain/composeResources/values-ru/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ru/strings.xml
@@ -87,7 +87,9 @@
     <!-- APP -->
     <string name="app_functions_get_node_list">Получить список нод</string>
     <string name="app_functions_get_recent_messages">Получать последние сообщения</string>
+    <string name="app_functions_read_section">Функции чтения</string>
     <string name="app_functions_send_message">Отправить сообщение</string>
+    <string name="app_functions_settings_summary">Контролируй, какие функции доступны помощникам ИИ</string>
     <string name="app_functions_write_section">Написание функций</string>
     <string name="app_notifications">Уведомления приложений</string>
     <string name="app_settings">Приложение</string>
@@ -113,19 +115,26 @@
     <string name="bluetooth">Bluetooth</string>
     <string name="bluetooth_available_devices">Доступные Bluetooth-устройства</string>
     <string name="bluetooth_config">Настройка Bluetooth</string>
+    <string name="bluetooth_disabled">Bluetooth выключен. Включи его, чтобы искать находящиеся рядом устройства.</string>
     <string name="bluetooth_enabled">Bluetooth включен</string>
     <string name="bluetooth_feature_config">Настройки</string>
     <string name="bluetooth_feature_config_description">Беспроводное управление настройками устройства и каналами.</string>
     <string name="bluetooth_feature_discovery">Обнаружение</string>
     <string name="bluetooth_feature_discovery_description">Найдите и определите устройства Meshtastic рядом с вами.</string>
     <string name="bluetooth_permission">Bluetooth</string>
+    <string name="bluetooth_scan_start_failed">Невозможно запустить сканирование Bluetooth. Попробуй снова или включи/выключи Bluetooth, если проблема не исчезнет.</string>
     <string name="bold_heading">Выделять заголовок жирным</string>
+    <string name="bonding_failed_permissions">Сопряжение не удалось. Дай соседнему устройству разрешения и попробуй снова.</string>
+    <string name="bonding_failed_retry">Сопряжение не завершилось. Попробуй снова.</string>
     <string name="bottom_nav_settings">Настройки</string>
     <string name="broadcast_interval">Период рассылки</string>
     <string name="button_gpio">Кнопка GPIO</string>
     <string name="buzzer_gpio">Зуммер GPIO</string>
     <string name="calculating">Вычисление…</string>
+    <string name="call_sign_summary">Твой позывной радиолюбителя, до 8 символов</string>
     <string name="camera_permission">Разрешение камеры</string>
+    <string name="camera_permission_rationale">Разреши доступ к камере, для сканирования QR-кодов.</string>
+    <string name="camera_unavailable">Камера не может запуститься. Попробуй снова или закрой сканер и открой заново.</string>
     <string name="cancel">Отмена</string>
     <string name="cancel_reply">Отменить ответ</string>
     <string name="canned_message">Шаблонные сообщения</string>
@@ -190,6 +199,7 @@
     <string name="codec2_sample_rate">Частота дискретизации CODEC2</string>
     <string name="coding_rate">Частота кодирования</string>
     <string name="collapse_chart">Свернуть диаграмму</string>
+    <string name="collapsed">Развален</string>
     <string name="communicate_off_the_grid">Общайтесь вне сети со своими друзьями и сообществом без использования сотовой связи.</string>
     <!-- COMPASS -->
     <string name="compass_bearing">Граница: %1$s</string>
@@ -223,6 +233,7 @@
     <string name="config_display_wake_on_tap_or_motion_summary">Необходимо наличие акселерометра на вашем устройстве.</string>
     <string name="config_lora_frequency_slot_summary">Рабочая частота вашей ноды рассчитывается на основе региона, настроек модема и этого поля. При значении 0 интервал автоматически рассчитывается на основе названия основного канала и изменяется с публичного интервала по умолчанию. Вернитесь к публичному интервалу по умолчанию, если настроены частный основной и общедоступный дополнительный каналы.</string>
     <string name="config_lora_hop_limit_summary">Задает максимальное количество прыжков, по умолчанию - 3. Увеличение количества также увеличивает перегрузку и должно использоваться с осторожностью. Сообщения с 0 прыжков не будут получать подтверждения.</string>
+    <string name="config_lora_modem_preset_licensed_summary">Пресеты этого региона предназначены только для лицензированных операторов (любительское радио). Включи «Лицензированный радиолюбитель (Ham)» в настройках пользователя, чтобы выбрать их.</string>
     <string name="config_lora_modem_preset_summary">Доступные пресеты модема, по умолчанию - Long Fast.</string>
     <string name="config_lora_region_summary">Регион, в котором вы будете использовать ваше радио.</string>
     <string name="config_network_eth_enabled_summary">Включение Ethernet отключит Bluetooth-соединение с приложением. TCP-соединения не доступны на устройствах Apple.</string>
@@ -285,6 +296,7 @@
     <string name="debug_filter_preset_title">Готовые фильтры</string>
     <string name="debug_filters">Фильтры</string>
     <string name="debug_log_api_enabled">API журнала отладки включен</string>
+    <string name="debug_logcat_refresh">Обновить</string>
     <string name="debug_logs_export">Выгрузить логи</string>
     <string name="debug_panel">Панель отладки</string>
     <string name="debug_search_clear">Очистить условия поиска</string>
@@ -328,6 +340,7 @@
     <string name="device_db_cache_limit_summary">Максимальное количество баз данных для этого устройства</string>
     <string name="device_gps">GPS устройства</string>
     <string name="device_links">Ссылки на устройства</string>
+    <string name="device_links_i_want_one">Я хочу один</string>
     <string name="device_links_open_in_browser">Открыть в браузере</string>
     <string name="device_metrics_label_value">%1$s: %2$s</string>
     <string name="device_metrics_log">Интервал передачи</string>
@@ -348,9 +361,15 @@
     <string name="disconnected">Отключено</string>
     <string name="discovered_network_devices">Найденные сетевые устройства</string>
     <!-- DISCOVERY -->
+    <string name="discovery_analysing_results">Анализирую результаты</string>
+    <string name="discovery_cancelling_scan">Отмена сканирования</string>
+    <string name="discovery_connection_warning">Нет подключения. Подключись к устройству Meshtastic, чтобы начать сканирование.</string>
     <string name="discovery_delete_session">Удалить сессию</string>
+    <string name="discovery_delete_session_confirm">Ты уверен что хочешь удалить эту сессию обнаружения? Это действие нельзя отменить.</string>
     <string name="discovery_dwell_minutes">%1$d минут</string>
     <string name="discovery_dwell_time">Время задержки</string>
+    <string name="discovery_dwell_time_description">Время послушки каждого пресета</string>
+    <string name="discovery_empty_history">Пока сессий обнаружения нет</string>
     <string name="discovery_export_report">Экспортировать отчет</string>
     <string name="discovery_history">История обнаружения</string>
     <string name="discovery_keep_screen_awake">Не гасить экран</string>
@@ -376,15 +395,25 @@
     <string name="discovery_session_detail">Детали сессии</string>
     <string name="discovery_shifting_to">Шифтинг to %1$s</string>
     <string name="discovery_start_scan">Начало сканирования</string>
+    <string name="discovery_start_scan_reason_no_presets">пресеты не выбраны</string>
+    <string name="discovery_start_scan_reason_not_connected">устройство не подключено</string>
     <string name="discovery_stat_channel_utilization">Использование канала</string>
     <string name="discovery_stat_date">Дата</string>
     <string name="discovery_stat_direct">Прямой</string>
+    <string name="discovery_stat_home_preset">Домашний пресет</string>
     <string name="discovery_stat_mesh">Меш</string>
     <string name="discovery_stat_messages">Сообщения</string>
     <string name="discovery_stat_online_total_nodes">Онлайн / всего нод</string>
     <string name="discovery_stat_packets_rx">Ракеты RX</string>
     <string name="discovery_stat_packets_tx">Пакеты TX</string>
+    <string name="discovery_stat_preset_results">Результаты пресета</string>
     <string name="discovery_stat_selected">Выбрано</string>
+    <string name="discovery_stat_status">Состояние</string>
+    <string name="discovery_stat_total_unique_nodes">Всего уникальных нод</string>
+    <string name="discovery_stat_unique_nodes">Уникальные ноды</string>
+    <string name="discovery_stop_scan">Остановить сканирование</string>
+    <string name="discovery_unique_nodes">%1$d уникальных нод</string>
+    <string name="discovery_view_map">Посмотреть карту</string>
     <string name="disk_free_indexed">Свободно на диске %1$d</string>
     <!-- DISPLAY -->
     <string name="display">Дисплей</string>
@@ -422,6 +451,8 @@
     <string name="doc_search_placeholder">Поиск по документации…</string>
     <string name="doc_section_developer">Руководство разработчика</string>
     <string name="doc_section_user">Руководство пользователя</string>
+    <string name="doc_title_android_auto">Android авто</string>
+    <string name="doc_title_app_functions">Функции прилож-я</string>
     <string name="doc_title_connections">Соединения</string>
     <string name="doc_title_desktop">Десктопное приложение</string>
     <string name="doc_title_discovery">Обнаружение</string>
@@ -598,6 +629,9 @@
     <string name="generate_input_event_on_press">Создать событие ввода при нажатии</string>
     <string name="generate_qr_code">Сгенерировать QR-код</string>
     <!-- GEOFENCE -->
+    <string name="geofence_box_use_view">Использовать текущий вид</string>
+    <string name="geofence_favorites_only">Только избранные</string>
+    <string name="geofence_off">Выкл</string>
     <string name="get_started">Начать работу</string>
     <string name="good">Хороший</string>
     <!-- GPIO -->
@@ -679,6 +713,8 @@
     <string name="label_short_fast">Малая дальность - Быстро</string>
     <string name="label_short_slow">Малая дальность - Медленно</string>
     <string name="label_short_turbo">Малая дальность - Турбо</string>
+    <string name="label_tiny_fast">Tiny - Fast</string>
+    <string name="label_tiny_slow">Tiny - Slow</string>
     <string name="label_very_long_slow">Очень большая дальность - Медленный</string>
     <string name="last_heard_filter_label">Фильтр по времени последнего сообщения: %1$s</string>
     <string name="last_position_update">Обновление последнего местоположения</string>
@@ -720,11 +756,20 @@
     <string name="location_disabled">Доступ к местоположению выключен, невозможно отправлять координаты в сеть.</string>
     <string name="location_sharing">Поделиться местоположением</string>
     <!-- LOCKDOWN -->
+    <string name="lockdown_backoff">Попробуй снова через %1$d секунд.</string>
     <string name="lockdown_confirm_passphrase">Подтвердить парольную фразу</string>
+    <string name="lockdown_disable">Отключить блокировку</string>
+    <string name="lockdown_disable_message">Введи пароль для отключения блокировки. Устройство расшифрует хранилище и перезагрузится.</string>
+    <string name="lockdown_enable">Включить блокировку</string>
     <string name="lockdown_enable_ack">Понимаю</string>
+    <string name="lockdown_enable_warning">Внимание: включение режима блокировки закрывает отладочный порт (SWD) на поддерживаемом оборудовании. Ты можешь отключить блокировку в любое время с помощью пароля, а полное стирание устройства восстанавливает всё при необходимости.</string>
     <string name="lockdown_enter_passphrase">Введи парольную фразу</string>
     <string name="lockdown_hide_passphrase">Скрыть</string>
+    <string name="lockdown_hours_until_expiry">Часов до истечения</string>
     <string name="lockdown_incorrect_passphrase">Неправильная парольная фраза.</string>
+    <string name="lockdown_lock_now">Заблокировать сейчас</string>
+    <string name="lockdown_lock_reason">Причина: %1$s</string>
+    <string name="lockdown_mode">Режим блокировки</string>
     <string name="lockdown_passphrase">Пароль</string>
     <string name="lockdown_passphrases_do_not_match">Пароли не совпадают</string>
     <string name="lockdown_session_no_time_limit">Без ограничения по времени</string>
@@ -798,7 +843,14 @@
     <string name="match_any">Совпадение любой | Все</string>
     <string name="max">Макс</string>
     <!-- MESH -->
+    <string name="mesh_beacon_invitations_title">Приглашения в сеть</string>
+    <string name="mesh_beacon_notification_body">Ближайшая сеть пригласила тебя присоединиться</string>
+    <string name="mesh_beacon_notification_title">Приглашение в сеть</string>
+    <string name="mesh_beacon_offer_channel">Канал: %1$s</string>
     <string name="mesh_beacon_offer_dismiss">Отменить</string>
+    <string name="mesh_beacon_offer_preset">Пресет: %1$s</string>
+    <string name="mesh_beacon_offer_region">Регион: %1$s</string>
+    <string name="mesh_beacon_offer_title">Приглашение в сеть</string>
     <string name="mesh_map_location">Карта расположения нод</string>
     <string name="mesh_map_location_description">Включает синюю точку местоположения для вашего телефона на карте нод.</string>
     <!-- MESHTASTIC -->
@@ -808,6 +860,7 @@
     <string name="meshtastic_broadcast_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>
     <string name="meshtastic_messages_notifications">Уведомления о личных сообщениях</string>
     <string name="meshtastic_new_nodes_notifications">Уведомления о новых нодах</string>
     <string name="meshtastic_service_notifications">Служебные уведомления</string>
@@ -848,6 +901,7 @@
     <string name="mqtt_probe_tcp_failure">Не удается подключиться к брокеру (TCP)</string>
     <string name="mqtt_probe_timeout">Тайм-аут после %1$d мс</string>
     <string name="mqtt_probe_tls_failure">Ошибка TLS-рукопожатия: %1$s</string>
+    <string name="mqtt_proxy_local">MQTT-прокси на этом телефоне</string>
     <string name="mqtt_status_connected">Подключено</string>
     <string name="mqtt_status_connecting">Подключение…</string>
     <string name="mqtt_status_disconnected">Отключено</string>
@@ -899,6 +953,8 @@
     <string name="no_network_devices_seen">Сетевые устройства не обнаружены</string>
     <string name="no_pax_metrics_logs">Метрики прохожих недоступны</string>
     <string name="no_usb_devices_found">Устройства USB не найдены</string>
+    <string name="no_usb_devices_hint">Подключи устройство с помощью USB-кабеля для передачи данных, чтобы использовать последовательное соединение.</string>
+    <string name="no_usb_devices_seen">USB-устройства не обнаружены</string>
     <!-- NODE -->
     <string name="node_count_template">(онлайн %1$d / показано %2$d / всего %3$d)</string>
     <string name="node_filter_exclude_infrastructure">Исключить инфраструктуру</string>
@@ -1217,6 +1273,8 @@
     <!-- SCAN -->
     <string name="scan">Сканирования</string>
     <string name="scan_bluetooth_devices">Сканировать Bluetooth-устройства</string>
+    <string name="scan_channels_nfc">Сканировать общие каналы NFC</string>
+    <string name="scan_channels_qr">Сканировать QR-код общих каналов</string>
     <string name="scan_network_devices">Сканировать сетевые устройства</string>
     <string name="scan_nfc">Сканировать NFC</string>
     <string name="scan_nfc_text">Поднесите ваше устройство ближе к метке NFC для сканирования.</string>
@@ -1248,7 +1306,10 @@
     <string name="security_icon_insecure_precise_only">Небезопасный канал, точное местоположение</string>
     <string name="security_icon_secure">Безопасный</string>
     <string name="security_icon_warning_precise_mqtt">Предупреждение: Небезопасно, точное местоположение; Uplink MQTT</string>
+    <string name="security_signed_message_info">Проверено с помощью ключа отправителя.</string>
     <string name="security_signed_node">Подписанная нода</string>
+    <string name="security_signed_node_desc">Автоматически проверено</string>
+    <string name="security_signed_node_help">Эта нода подписывает свои трансляции с помощью XEdDSA. Трансляции, которые ты видишь от неё, проверяются радио с использованием его ключа идентификации.</string>
     <string name="security_signed_verified">Подписано · проверено</string>
     <string name="select">Выбрать</string>
     <string name="select_all">Выбрать все</string>
@@ -1277,6 +1338,7 @@
     <!-- SHARE -->
     <string name="share">Поделиться</string>
     <string name="share_channels_qr">Поделиться QR-кодом каналов</string>
+    <string name="share_connected_node">Поделиться подключенной нодой</string>
     <string name="share_contact">Отправить контакт</string>
     <string name="share_location">Поделиться геопозицией</string>
     <string name="share_location_description">........</string>
@@ -1313,6 +1375,7 @@
     <string name="status_message">Состояние сообщения</string>
     <string name="status_message_config">Настройка состояния сообщений</string>
     <string name="stay_connected_anywhere">Оставайтесь на связи везде</string>
+    <string name="stop_connecting">Остановить подключение</string>
     <string name="store_forward">Store &amp; Forward</string>
     <string name="store_forward_config">Настройка Store &amp; Forward</string>
     <string name="store_forward_enabled">Store &amp; Forward включена</string>
@@ -1544,5 +1607,9 @@
     <string name="wind_gust">Порыв ветра</string>
     <string name="wind_lull">Штиль</string>
     <string name="wind_speed">Скорость ветра</string>
+    <string name="write_nfc">Записать в NFC-метку</string>
+    <string name="write_nfc_failed">Не удалось записать в метку. Используй пустую NFC-метку, которую можно записывать, и держи её неподвижно.</string>
+    <string name="write_nfc_success">Написано для метки</string>
+    <string name="write_nfc_text">Поднеси записываемую NFC-метку к задней части своего телефона.</string>
     <string name="you">Вы</string>
 </resources>
diff --git a/core/resources/src/commonMain/composeResources/values-sr/strings.xml b/core/resources/src/commonMain/composeResources/values-sr/strings.xml
index 72faa3555..9c6b06419 100644
--- a/core/resources/src/commonMain/composeResources/values-sr/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sr/strings.xml
@@ -151,6 +151,7 @@
     <!-- DISTANCE -->
     <string name="distance">Udaljenost</string>
     <!-- DOC -->
+    <string name="doc_title_debug_logs">Дебаг логови</string>
     <string name="doc_title_firmware">Ажурирања фирмвера</string>
     <string name="doc_title_nodes">Чворови</string>
     <string name="double_tap_as_button_press">Двоструки додир као дугме</string>
diff --git a/core/resources/src/commonMain/composeResources/values-srp/strings.xml b/core/resources/src/commonMain/composeResources/values-srp/strings.xml
index ad0aa54cc..9d74c7482 100644
--- a/core/resources/src/commonMain/composeResources/values-srp/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-srp/strings.xml
@@ -151,6 +151,7 @@
     <!-- DISTANCE -->
     <string name="distance">Раздаљина</string>
     <!-- DOC -->
+    <string name="doc_title_debug_logs">Дебаг логови</string>
     <string name="doc_title_firmware">Ажурирања фирмвера</string>
     <string name="doc_title_nodes">Чворови</string>
     <string name="double_tap_as_button_press">Двоструки додир као дугме</string>
diff --git a/core/resources/src/commonMain/composeResources/values-sv/strings.xml b/core/resources/src/commonMain/composeResources/values-sv/strings.xml
index d6f0dac10..98deda5f7 100644
--- a/core/resources/src/commonMain/composeResources/values-sv/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sv/strings.xml
@@ -255,6 +255,7 @@
     <string name="debug_filter_preset_title">Förinställda filter</string>
     <string name="debug_filters">Filter</string>
     <string name="debug_log_api_enabled">API för debugloggen igång</string>
+    <string name="debug_logcat_refresh">Uppdatera</string>
     <string name="debug_logs_export">Exportera loggar</string>
     <string name="debug_panel">Felsökningspanel</string>
     <string name="debug_search_clear">Rensa sökning</string>
diff --git a/core/resources/src/commonMain/composeResources/values-uk/strings.xml b/core/resources/src/commonMain/composeResources/values-uk/strings.xml
index 0ae00c179..1b7c172b4 100644
--- a/core/resources/src/commonMain/composeResources/values-uk/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-uk/strings.xml
@@ -244,6 +244,7 @@
     <string name="debug_filter_preset_title">Готові фільтри</string>
     <string name="debug_filters">Фільтри</string>
     <string name="debug_log_api_enabled">API журналу відладки увімкнено</string>
+    <string name="debug_logcat_refresh">Оновити</string>
     <string name="debug_logs_export">Експортувати журнали</string>
     <string name="debug_panel">Панель налагодження</string>
     <string name="debug_search_clear">Очистити пошук</string>
diff --git a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml
index 7f453b3b2..edac5d0c2 100644
--- a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml
@@ -308,6 +308,7 @@
     <string name="debug_filter_preset_title">重置筛选</string>
     <string name="debug_filters">筛选器</string>
     <string name="debug_log_api_enabled">启用调试日志 API </string>
+    <string name="debug_logcat_refresh">刷新</string>
     <string name="debug_logs_export">导出程序日志</string>
     <string name="debug_panel">调试面板</string>
     <string name="debug_search_clear">清除搜索</string>
diff --git a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml
index 342c42607..feafd338d 100644
--- a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml
@@ -282,6 +282,7 @@
     <string name="debug_filter_preset_title">預設篩選條件</string>
     <string name="debug_filters">篩選</string>
     <string name="debug_log_api_enabled">啟用除錯日誌 API</string>
+    <string name="debug_logcat_refresh">重新整理</string>
     <string name="debug_logs_export">匯出日誌</string>
     <string name="debug_panel">偵錯面板</string>
     <string name="debug_search_clear">清除搜尋結果</string>
diff --git a/docs/ar-rSA/user/debug-logs.md b/docs/ar-rSA/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ar-rSA/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/be-rBY/user/debug-logs.md b/docs/be-rBY/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/be-rBY/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/bg-rBG/user/debug-logs.md b/docs/bg-rBG/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/bg-rBG/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ca-rES/user/debug-logs.md b/docs/ca-rES/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ca-rES/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/cs-rCZ/user/debug-logs.md b/docs/cs-rCZ/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/cs-rCZ/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/de-rDE/user/debug-logs.md b/docs/de-rDE/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/de-rDE/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/el-rGR/user/debug-logs.md b/docs/el-rGR/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/el-rGR/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/es-rES/user/debug-logs.md b/docs/es-rES/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/es-rES/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/et-rEE/user/debug-logs.md b/docs/et-rEE/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/et-rEE/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/fi-rFI/user/debug-logs.md b/docs/fi-rFI/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/fi-rFI/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/fr-rFR/user/debug-logs.md b/docs/fr-rFR/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/fr-rFR/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ga-rIE/user/debug-logs.md b/docs/ga-rIE/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ga-rIE/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/gl-rES/user/debug-logs.md b/docs/gl-rES/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/gl-rES/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/hr-rHR/user/debug-logs.md b/docs/hr-rHR/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/hr-rHR/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ht-rHT/user/debug-logs.md b/docs/ht-rHT/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ht-rHT/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/hu-rHU/user/debug-logs.md b/docs/hu-rHU/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/hu-rHU/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/is-rIS/user/debug-logs.md b/docs/is-rIS/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/is-rIS/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/it-rIT/user/debug-logs.md b/docs/it-rIT/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/it-rIT/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/iw-rIL/user/debug-logs.md b/docs/iw-rIL/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/iw-rIL/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ja-rJP/user/debug-logs.md b/docs/ja-rJP/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ja-rJP/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ko-rKR/user/debug-logs.md b/docs/ko-rKR/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ko-rKR/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/lt-rLT/user/debug-logs.md b/docs/lt-rLT/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/lt-rLT/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/nl-rNL/user/debug-logs.md b/docs/nl-rNL/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/nl-rNL/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/no-rNO/user/debug-logs.md b/docs/no-rNO/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/no-rNO/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/pl-rPL/user/debug-logs.md b/docs/pl-rPL/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/pl-rPL/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/pt-rBR/user/debug-logs.md b/docs/pt-rBR/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/pt-rBR/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/pt-rPT/user/debug-logs.md b/docs/pt-rPT/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/pt-rPT/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ro-rRO/user/debug-logs.md b/docs/ro-rRO/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ro-rRO/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/ru-rRU/user/android-auto.md b/docs/ru-rRU/user/android-auto.md
index 4d310ba5e..f976b9a2c 100644
--- a/docs/ru-rRU/user/android-auto.md
+++ b/docs/ru-rRU/user/android-auto.md
@@ -3,7 +3,7 @@ title: Android Auto
 parent: Руководство пользователя
 nav_order: 18
 last_updated: 2026-06-11
-description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving.
+description: Используй Meshtastic без рук на головном устройстве Android Auto — читай сообщения вслух, отвечай голосом и проверяй ноды и состояние сети, пока ты за рулем.
 aliases:
   - android-auto
   - car
@@ -13,42 +13,42 @@ aliases:
 
 # Android Auto
 
-Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road.
+Meshtastic интегрируется с Android Auto, так что ты можешь оставаться на связи со своей сетью, пока едешь, не отрывая рук от руля и глаз от дороги.
 
-> ⚠️ **Note:** Android Auto support is available on **Google-flavor Android builds only**. It is not included in the F-Droid build, and it is not available on Desktop or iOS.
+> ⚠️ **Примечание:** поддержка Android Auto доступна только на **Android-сборках от Google**. Она не включена в сборку F-Droid и недоступна на ПК или iOS.
 
 ## Обзор
 
-When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents a tabbed Home screen optimized for driving-safe, glanceable use:
+Когда твой телефон подключен к головному устройству Android Auto (или к эмулятору Desktop Head Unit, используемому для разработки), Meshtastic появляется как приложение для обмена сообщениями, созданное с помощью библиотеки Android Car App. Интерфейс автомобиля представляет собой экран «Домой» с вкладками, оптимизированный для безопасного использования за рулем и быстрого просмотра:
 
-- **Messages** — recent conversations, with hands-free reading and replies.
-- **Nodes** — the mesh node list, with a node-detail view.
-- **Status** — current connection and mesh status.
+- **Сообщения** — недавние разговоры с возможностью чтения и ответов без рук.
+- **Узлы** — список нод сети с подробным просмотром каждой ноды.
+- **Статус** — текущий статус подключения и сети.
 
-The car app does not add a new connection of its own. It uses the Meshtastic app's existing connection, node, and message state, so it reflects whatever your phone is already connected to.
+Приложение для машины само по себе не добавляет новое соединение. Оно использует уже существующее соединение, ноду и состояние сообщений в приложении Meshtastic, так что отображает то, к чему твой телефон уже подключен.
 
-> ⚠️ **Note:** Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state.
+> ⚠️ **Примечание:** твой телефон должен быть подключен к радиостанции Meshtastic, чтобы автомобильное приложение показывало данные в реальном времени. Если приложение отключено, экран автомобиля показывает отключенное состояние.
 
 ## Сообщения
 
-The Messages tab lists your recent conversations. While driving, you can:
+Вкладка «Сообщения» показывает твои недавние разговоры. За рулём ты можешь:
 
-- **Have messages read aloud** so you don't need to look at the screen.
-- **Reply by voice or text** using your head unit's reply control, dictating your response hands-free.
+- **Прослушивать сообщения вслух**, чтобы не приходилось смотреть на экран.
+- **Отвечай голосом или текстом** с помощью кнопки ответа на своей головной панели, диктуя свой ответ без рук.
 
 ## Ноды
 
-The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See [Nodes](nodes) for the full meaning of the information shown.
+Вкладка «Ноды» показывает список нод вашей сетки в удобном для машины формате. Выбор ноды открывает представление с подробной информацией об этой ноде. Смотри [Ноды](nodes), чтобы полностью понять информацию, показанную здесь.
 
-## Status
+## Статус
 
-The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you're still connected to your radio without opening your phone.
+Вкладка «Статус» позволяет одним взглядом увидеть твоё текущее соединение и состояние сети — удобно, чтобы проверить, что ты всё ещё подключен к радиостанции, не открывая телефон.
 
 ## Связанные темы
 
-- [Messages & Channels](messages-and-channels) — full messaging features on your phone
-- [Nodes](nodes) — detailed node list and node-detail information
-- [Connections](connections) — how the app connects to your radio
+- [Сообщения и Каналы](messages-and-channels) — все функции обмена сообщениями на твоём телефоне
+- [Ноды](nodes) — подробный список нод и информация о каждой ноде
+- [Подключения](connections) — как приложение подключается к твоей радиостанции
 
 ---
 
diff --git a/docs/ru-rRU/user/debug-logs.md b/docs/ru-rRU/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/ru-rRU/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/sk-rSK/user/debug-logs.md b/docs/sk-rSK/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/sk-rSK/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/sl-rSI/user/debug-logs.md b/docs/sl-rSI/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/sl-rSI/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/sq-rAL/user/debug-logs.md b/docs/sq-rAL/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/sq-rAL/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/sr-rLatn/user/debug-logs.md b/docs/sr-rLatn/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/sr-rLatn/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/srp/user/debug-logs.md b/docs/srp/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/srp/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/sv-rSE/user/debug-logs.md b/docs/sv-rSE/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/sv-rSE/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/tr-rTR/user/debug-logs.md b/docs/tr-rTR/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/tr-rTR/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/uk-rUA/user/debug-logs.md b/docs/uk-rUA/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/uk-rUA/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/zh-rCN/user/debug-logs.md b/docs/zh-rCN/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/zh-rCN/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---
diff --git a/docs/zh-rTW/user/debug-logs.md b/docs/zh-rTW/user/debug-logs.md
new file mode 100644
index 000000000..2f003e74b
--- /dev/null
+++ b/docs/zh-rTW/user/debug-logs.md
@@ -0,0 +1,58 @@
+---
+title: Debug Logs
+parent: User Guide
+nav_order: 22
+last_updated: 2026-07-01
+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
+  - logcat
+  - app-logs
+  - bug-report
+---
+
+# Debug Logs
+
+When something misbehaves, the app's debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them **for you, from inside the app** — you no longer need `adb` or any desktop tooling to collect them.
+
+Open the **Debug Panel** from **Settings → Advanced → Debug Panel**.
+
+> 📎 **Filing an issue?** Export your logs (see below) and attach the `.txt` file to your report at [github.com/meshtastic/Meshtastic-Android/issues](https://github.com/meshtastic/Meshtastic-Android/issues). A log capture that covers the moment the problem happened turns "it doesn't work" into something a developer can actually track down.
+
+## The two tabs
+
+The Debug Panel has two tabs:
+
+- **Packets** — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
+- **App logs** — the app's own diagnostic log (Android _logcat_), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
+
+Each tab has its own **export** button and produces its own file, so you can grab whichever is relevant — or both.
+
+## Viewing app logs
+
+The **App logs** tab shows the most recent log lines from **this app only** — never other apps on your device.
+
+- **Search** — type in the search box to filter to matching lines.
+- **Level filter** — the **V / D / I / W / E** chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
+- **Refresh** — the refresh icon re-reads the latest logs.
+
+Error and warning lines are tinted so problems stand out.
+
+## Exporting
+
+Tap the **download** icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example `meshtastic_logcat_20260701_143312.txt`) so repeated exports never overwrite each other.
+
+Attach that file to your GitHub issue.
+
+> 🔒 **Privacy:** Exports automatically **redact** sensitive values such as channel keys and admin/session keys before writing the file. Even so, logs can contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt.
+
+## 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.
+
+## Related Topics
+
+- [Help & In-App Docs](help-and-docs) — reading this documentation offline inside the app
+- [Connections](connections) — if the problem is getting connected to your radio in the first place
+
+---