---
title: S10e Navi Node
type: hardware
purpose: Remotely controlled Android node for Navi
owner: gmikcon
status: active
confidence: "100"
last_reviewed: 2026-09-29
review_interval: 90d
source_of_truth: adb-verified
---

# Samsung Galaxy S10e — Navi Android node

## Overview
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.

## Network / access
- Wi-Fi: 192.168.1.22 (home-lan), adb tcpip 5555 enabled — reachable over the network without USB
- adb: authorized from gprint keys (USB serial RF8MA0TYJMF + 192.168.1.22:5555)
- Control entrypoint: `gprint:~/pixel3a-work/s10e.sh`; from the Navi host: `~/pixel3a/s10e-remote.sh` (sshpass wrapper)
- PIN: stored in `gprint:~/pixel3a-work/.pin` (chmod 600); unlock automation verified (wake → swipe up → input PIN → enter)
- screencap returns 0 bytes on the secure lockscreen (Samsung FLAG_SECURE) — capture only when unlocked

## Applied settings (2026-09-29)
- stay_on_while_plugged_in=7, screen_off_timeout=600000 (raised from 60s during Termux work)
- protect_battery=1 (Samsung charge limit 85% for 24/7 USB power; verify after first day: level should settle ~85%)
- wifi_sleep_policy=2 (Wi-Fi never sleeps)
- Phantom process killer disabled (Termux-friendly)
- Night mode on, brightness 10 (manual), screensaver off

## Termux (v0.118.1, pre-installed 2024 by owner)
- Packages present: com.termux, com.termux.api, com.termux.widget, com.termux.tasker; installed via pkg: openssh, python 3.14.6, termux-api
- **SSH**: port 8022, key auth. Key on gprint: `~/.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.
- authorized_keys contains both the gprint key and the owner's old key (u0_a439@localhost) — do not overwrite
- Storage: READ/WRITE_EXTERNAL_STORAGE granted via `pm grant` (adb)
- **sshd is NOT autostarted**: after a phone reboot, open Termux and run `sshd` (via s10e.sh screen input, or set up Termux:Boot / RUN_COMMAND intent later)
- Gotcha: after `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 -A`
- termux-api verified: termux-battery-status (health GOOD, PLUGGED_USB), termux-tts-speak
- Owner's old Termux history (ssh to 192.168.68.x eserv/bserv/gprint, iperf3) — old network, left untouched

## Text input — ADBKeyboard (Cyrillic/Unicode)
- Installed `com.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.
- Activate: `adb shell ime enable com.android.adbkeyboard/.AdbIME && adb shell ime set com.android.adbkeyboard/.AdbIME`
- Type Unicode: `adb 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 strings
- Restore owner keyboard: `adb shell ime set com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME` (full class ID — short `...latin/.LatinIME` fails with "Unknown input method")
- Verified end-to-end 2026-09-29: Telegram search «Любимая» → opened chat «Любимая*» → typed and SENT a message from the phone (delivered, 20:30). Telegram search field tap: (849,197); message field tap: (520,2149); send button tap: (1049,2003) at 1080x2400.

## Notifications
- **Read**: `adb shell dumpsys notification --noredact` — all active notifications (pkg/title/text). `termux-notification-list` hangs (Termux:API IPC) — do not use.
- **Watcher**: systemd `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.state`
- **Post (test/control)**: `adb shell "cmd notification post -S bigtext -t 'Title' tag 'text'"` — posts as com.android.shell; watcher catches it within ~15s (verified end-to-end)
- Ideas: filter important (Telegram/SMS) → push to owner; dismiss by tag via `cmd notification dismiss`

## Planned
- SIM card (owner plan): mobile channel for the node — SMS read/send via adb (`content://sms`), mobile data as backup uplink, emergency reachability when LAN/WAN is down
- Candidate workloads: IP Webcam (camera), Telegram command channel, Syncthing, notification filter → push

## Recovery
- TWRP beyond0lte 3.7.0_9-2 at `gprint:/home/gprint/twrp-beyond0lte.img` (sha256 verified)
- Keepalive service auto-recovers adb after a phone reboot (re-enables tcpip via USB)
