465088ed2f4591d08738b2306f213c5149b3484b
When resetting legacy Always-On VPN, the intent is handled by main thread. And it will also initialize VPN shutdown process, which will cause networkInfo changed event on ConnectivityService internal thread. These two events need to hold their corresponding lock and ask for the other one, which causes the deadlock. This patch move the event handling to the same thread to prevent such deadlock, and cleanup some unused variables. Change-Id: I5b656c0d0381acb4e33409a11f502db9b180296c Fix: 139122208 Test: atest FrameworksNetTests, manual test
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%