WifiServiceImpl: Reject startSoftAp when already tethering
Originally we did not want WifiServiceImpl to make any interface mode
related decisions. ActiveModeWarden handles all such device
capability checks. But, tethering seems to be an exception to that rule,
we don't need to ever support 2 tethering sessions even if the device
can support 2 AP interfaces. Hence, block tethering start if there is
already a session active to make the API more robust to misuse from
clients (Eg: invoking startSoftAp twice without stopSoftAp).
Bug: 110697252
Test: ./frameworks/opt/net/wifi/tests/wifitests/runtests.sh
Test: Manual verification by modifying ACTS test to trigger back to back
startSoftAp (Repro'ed the issue originally & then verified the fix).
Test: Will send for regression tests
Change-Id: If27f9062c14846e0541e9b849e18001f61d34084
2 files changed