| collectors | ||
| commands | ||
| docs | ||
| static | ||
| templates | ||
| .gitignore | ||
| cache.py | ||
| config.py | ||
| export_state.py | ||
| history.py | ||
| README.md | ||
| scheduler.py | ||
| server.py | ||
| start.sh | ||
| state.py | ||
| sync_state.py | ||
NetDash
NetDash is a lightweight mobile network monitoring dashboard designed to run on a rooted Android device using Termux.
It exposes a local web dashboard accessible from devices on the same LAN, providing real-time and historical monitoring of cellular network metrics, device status, and command plugins.
The project is designed to be simple, efficient, and low resource, making it suitable for continuous execution on mobile hardware.
Features
-
📡 Cellular Signal Monitoring
- RSRP / RSRQ / SINR / RSSI
-
📶 Cell Information
- PCI / EARFCN / LTE Band / eNodeB / TAC
-
📊 Realtime Charts
- Signal graph (dual-axis)
- Traffic RX/TX graph
- 5 minute live preview
-
📜 Historical Data
- Up to 12 hours of time-series history
- Interactive modal charts
-
🔁 Cell Change Detection
- CELL_CHANGE / PCI_CHANGE / EARFCN_CHANGE
-
🔋 Device Monitoring
- Battery level & charging state
- CPU usage & temperature
- RAM usage
-
📡 Hotspot Monitoring
- Connected devices (IP / MAC)
-
⚡ Commands / Plugin System
- Dynamic dashboard panels for commands
- Each plugin supports
get_html()andset_state() - Optional
get_state()for state export - Supports assets (images, scripts) inside plugin folders
-
🌐 State Synchronization
- Local
state.jsonfor commands & selected collectors sync_state.pyto synchronize with remote JSONexport_state.pyto POST state to remote server with authentication
- Local
Architecture
ARCHITECTURE.md
NetDash follows a lightweight monitoring architecture optimized for mobile hardware:
Android system commands
↓
Python collectors (signal, cell, battery, hardware, hotspot, etc.)
↓
Scheduler / RAM cache / CSV history
↓
Flask API
↓
Web dashboard (Chart.js + Vanilla JS)
↓
Commands / Plugin panels (dynamic state)
Key design goals:
- minimal CPU usage
- minimal dependencies
- modular collectors
- simple frontend
Technology Stack
Backend
- Python
- Flask
Frontend
- HTML
- CSS
- Vanilla JavaScript
- Chart.js
Runtime environment
- Android (LineageOS)
- Termux
- root access
Installation (Termux)
Clone the repository:
git clone https://github.com/youruser/netdash.git
cd netdash
Install dependencies:
pip install flask
Run the server:
python server.py
The dashboard will be available at:
http://DEVICE_IP:8080
Project Structure
NetDash
├── cache.py
├── collectors
│ ├── battery.py
│ ├── cell_events.py
│ ├── cell.py
│ ├── hardware.py
│ ├── hotspot.py
│ ├── network.py
│ ├── signal.py
│ └── traffic.py
├── commands
│ ├── loader.py
│ └── test_button
│ └── main.py
├── config.py
├── docs
│ ├── ARCHITECTURE.md
│ └── BOOTSTRAP.md
├── export_state.py
├── history.py
├── logs
├── README.md
├── scheduler.py
├── server.py
├── start.sh
├── state
├── state.py
├── static
│ ├── chartjs/
│ ├── dashboard.js
│ └── style.css
├── sync_state.py
└── templates
└── dashboard.html
Roadmap
Planned future features:
- Better logs
- RF debugging tools
- event markers on signal graphs
- service mode (Termux background service)
License
MIT License
Copyright (c) 2026
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.