Align the Android application process with the native VPN service as the authoritative runtime owner.
The app process should not recreate unscoped VPN control actions or duplicate runtime state that belongs to the native service.
Changes
Remove the obsolete exact-alarm permission
Remove UI-process session-expiry forwarding
Remove duplicate VPN runtime-alive probing
Reuse the native service-owned Disconnect action
Keep Disconnect scoped to the active runtime generation
Align the notification channel with the VPN service
Retry notification text updates when a native update fails
This reduces duplicate runtime ownership between the Flutter app process and the native VPN service.
## Summary
Align the Android application process with the native VPN service as the authoritative runtime owner.
The app process should not recreate unscoped VPN control actions or duplicate runtime state that belongs to the native service.
## Changes
- Remove the obsolete exact-alarm permission
- Remove UI-process session-expiry forwarding
- Remove duplicate VPN runtime-alive probing
- Reuse the native service-owned Disconnect action
- Keep Disconnect scoped to the active runtime generation
- Align the notification channel with the VPN service
- Retry notification text updates when a native update fails
This reduces duplicate runtime ownership between the Flutter app process and the native VPN service.
Pull request closed
This pull request cannot be reopened because the branch was deleted.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Align the Android application process with the native VPN service as the authoritative runtime owner.
The app process should not recreate unscoped VPN control actions or duplicate runtime state that belongs to the native service.
Changes
This reduces duplicate runtime ownership between the Flutter app process and the native VPN service.
Pull request closed