service-lifecycle

Android VPN and proxy service lifecycle coordination is handled by a ServiceController that manages end-to-end start and stop orchestration across runtime coordinators, ensuring reliable state transitions. It aligns runtimes, policy resolvers, and telemetry collectors for stable operation.

Handovers and restarts for Android VPN services are managed through handover-triggered restart logic and remembered-policy replay. This approach maintains a stable operational state by coordinating between VPN and proxy runtimes during network transitions without manual intervention.

Telemetry and diagnostics for a proxy service lifecycle are collected through a structured telemetry pipeline and ServiceStateStore logging. These mechanisms capture runtime events and manage consistent state, providing diagnostic visibility during service start, stop, and handover operations.

Yes, a single ServiceController can manage both VPN and proxy runtimes on Android. It coordinates across both runtimes alongside policy resolvers and telemetry collectors to apply consistent state management and orchestrate lifecycle events uniformly.

Android proxy services lose policy configuration after restarts when consistent state management is absent. This skill applies remembered-policy replay during handover-triggered restarts, restoring the previous policy configuration to maintain operational continuity.