How wenadb/flux works
FLUX is presented as a rootless Android performance optimizer, with dashboard telemetry, optimization commands, ART compilation, app management, game tuning, execution history, and Shizuku connection controls. The sampled web engine seeds demo telemetry and simulates command execution; it persists selected state in browser localStorage. The tree also contains a native Android implementation, but its source was not sampled, so its runtime wiring is not mapped here.
Main entry points: App.tsx App orchestrator · fluxEngine.ts Flux engine · index.ts Domain types · DashboardScreen.tsx Dashboard
Components 17
Web interface
- App orchestrator
src/App.tsx - Shizuku controls
src/components/ShizukuModal.tsx - Command results
src/components/ExecutionModal.tsx - Top bar
src/components/TopBar.tsx
Optimization features
- Dashboard
src/screens/DashboardScreen.tsx - Optimizer
src/screens/OptimizerScreen.tsx - ART tools
src/screens/ArtScreen.tsx - App manager
src/screens/AppsScreen.tsx - Game Space
src/screens/GameSpaceScreen.tsx - Execution history
src/screens/HistoryScreen.tsx - Settings
src/screens/SettingsScreen.tsx - About
src/screens/AboutScreen.tsx
Engine and state
- Flux engine
src/services/fluxEngine.ts - Domain types
src/types/index.ts
System integration
- Browser storage
- Shizuku / ADB
Other components
- User
Connections 23
- User → App orchestrator: uses
- App orchestrator → Dashboard: renders
- App orchestrator → Optimizer: renders
- App orchestrator → ART tools: renders
- App orchestrator → App manager: renders
- App orchestrator → Game Space: renders
- App orchestrator → Execution history: renders
- App orchestrator → Settings: renders
- App orchestrator → About: renders
- App orchestrator → Top bar: renders
- App orchestrator → Shizuku controls: renders
- App orchestrator → Command results: renders
- App orchestrator → Flux engine: subscribes; reads telemetry
- App orchestrator → Flux engine: runs optimization; executes commands
- App orchestrator → Flux engine: freezes apps
- App orchestrator → Flux engine: rolls back; clears logs
- App orchestrator → Flux engine: sets Shizuku status
- Flux engine → Browser storage: loads and saves state
- Flux engine → Shizuku / ADB: simulates command execution
- App orchestrator → Domain types: uses data contracts
- Dashboard → Domain types: displays telemetry
- ART tools → Domain types: uses package data
- Game Space → Domain types: uses packages and tweaks