title: S10e Navi Node type: hardware purpose: Remotely controlled Android node for Navi owner: gmikcon status: active confidence: "100" last_reviewed: 2026-10-07 review_interval: 90d
Samsung Galaxy S10e (SM-G970F, codename beyond0lte, serial RF8MA0TYJMF, Android 12 / SDK 31, One UI) repurposed as a permanently connected Android execution node for Navi. Physically connected via USB to gprint (192.168.1.131, port 1-3), powered from USB. Screen turns off after 10 min; control does not require the screen.
2026-10-07: телефон временно передан владельцу как замена разбитому личному смартфону (до покупки нового). SIM расклад изменён: в S10e теперь личная SIM владельца (+380632912932, lifecell, слот 1, LOADED), узловая SIM Navi (+380939126548) переехала в Motorola — см. moto-g54-navi-node.md. Telegram владельца активен на S10e — узловые скрипты не трогать. Узел продолжает работать: adb по Wi-Fi (192.168.1.22:5555) и Termux SSH доступны, пока телефон в домашней Wi-Fi-сети. Изменения под повседневное использование (см. ниже) откатываются при возврате в режим узла.
gprint:~/pixel3a-work/s10e.sh; from the Navi host: ~/pixel3a/s10e-remote.sh (sshpass wrapper)gprint:~/pixel3a-work/.pin (chmod 600); unlock automation verified (wake → swipe up → input PIN → enter). PIN: 7485cmd uimode night no)settings put global mode_ringer и cmd audio set-ringer-mode НЕ работают — AudioService держит состояние, менять только через UI)~/.ssh/s10e_key (ed25519, comment gprint-navi). Connect: ssh -i ~/.ssh/s10e_key -p 8022 navi@192.168.1.22 (user navi = u0_a439). Works even with the phone screen locked.pm grant (adb)sshd (via s10e.sh screen input, or set up Termux:Boot / RUN_COMMAND intent later)pkg install openssh, the OLD sshd process keeps listening and resets connections (kex_exchange_identification: Connection reset) — kill the sshd PID and run sshd again; host keys via ssh-keygen -Acom.android.adbkeyboard (ADBKeyboard.apk, 17 KB, from github.com/senzhk/ADBKeyBoard; copy on gprint ~/pixel3a-work/apks/ADBKeyboard.apk). adb input text cannot type Cyrillic — this IME is the workaround.adb shell ime enable com.android.adbkeyboard/.AdbIME && adb shell ime set com.android.adbkeyboard/.AdbIMEadb shell am broadcast -a ADB_INPUT_B64 --es msg "$(printf '%s' 'текст' | base64 -w0)" — base64 variant is REQUIRED: plain ADB_INPUT_TEXT silently drops long/emoji/unicode stringsadb shell ime set com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME (full class ID — short ...latin/.LatinIME fails with "Unknown input method")adb shell dumpsys notification --noredact — all active notifications (pkg/title/text). termux-notification-list hangs (Termux:API IPC) — do not use.notif-watcher.service on gprint (active, enabled) — 10s poll, new notifications appended to ~/pixel3a-work/notif.log (format ts|pkg|title|text), dedup state in notif.stateadb shell "cmd notification post -S bigtext -t 'Title' tag 'text'" — posts as com.android.shell; watcher catches it within ~15s (verified end-to-end)cmd notification dismisscontent://sms), mobile data as backup uplinkgprint:/home/gprint/twrp-beyond0lte.img (sha256 verified)