---
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 60s
(AMOLED burn-in protection); 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=0, screen_off_timeout=60000
- 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

## 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: Termux (SSH/cron/bots), IP Webcam (camera), Telegram command channel, Syncthing

## 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)
