How ranvirrox/gce-wifi-autologin works
GCE Wi-Fi AutoLogin automates captive-portal sign-in through the app, a Quick Settings tile, or a home-screen widget. The documented workflow submits stored credentials, reports successful connectivity to Android, probes Google connectivity, and checks for mandatory updates. The README supports these capabilities and stages, but source excerpts were not provided, so implementation-level call wiring beyond that documented flow is uncertain.
Main entry points: AuthClient.kt Portal authentication · MainActivity.kt App interface · MyTileServices.kt Quick Settings tile · LoginWidgetProvider.kt Home widget
Components 11
Login entry points
- App interface
app/src/main/java/com/example/AutoLogin/MainActivity.kt - Quick Settings tile
app/src/main/java/com/example/AutoLogin/MyTileServices.kt - Home widget
app/src/main/java/com/example/AutoLogin/LoginWidgetProvider.kt
Authentication
- Credential session
app/src/main/java/com/example/AutoLogin/SessionManager.kt - Portal authentication
app/src/main/java/com/example/AutoLogin/AuthClient.kt
Connectivity and updates
- Android connectivity
- Google connectivity probe
- Update check
app/src/main/java/com/example/AutoLogin/MainActivity.kt
Other components
- User
- 24online portal
- Update host
Connections 12
- User → App interface: opens app
- User → Quick Settings tile: taps tile
- User → Home widget: taps widget
- App interface → Portal authentication: requests login
- Quick Settings tile → Portal authentication: triggers login
- Home widget → Portal authentication: triggers login
- Credential session → Portal authentication: provides credentials
- Portal authentication → 24online portal: POST credentials
- Portal authentication → Android connectivity: reports success
- Portal authentication → Google connectivity probe: verifies connectivity
- App interface → Update check: checks version
- Update check → Update host: compares versions