SoftApManager: Don't set mApInterfaceName to null when interface destroyed.
Issue happened steps: (No Concurrent support device only due to device will use same
interface between wifi and hotspot)
1. Turn on hotspot
2. Turn on WiFi
In current design, ApState will be updated to DISABLED state when exit StartedState,
Setting mApInterfaceName to null results in updateApState is called
with a null interface name on leaving StartedState.
This might cause Null Point Exception in WifiApStateChange broadcast receiver.
Solution:
Set mApInterfaceName to null after update to DISABLE State.
Add mIsInterfaceDestroyed flag to check if need to clean native interface
or not.
Bug: 126052725
Test: Manual test - Toggled wifi on/off multiple times (Cannot repro the crash now)
Test: unit test, atest frameworks/opt/net/wifi/tests/wifitests
Test: Will send for full regression tests.
Change-Id: Ifa3f7ee33438d918c4d871a2f73f9c3bc8e3d4c7
2 files changed