SoftApCallback using executor vs handler

Updating classes to support making SoftApCallback methods available to @SystemAPI including
the API for registration of a SoftApCallback which includes a change to
now use executor vs handler.

Bug: 143564153
Test: make RunSettingsRoboTests ROBOTEST_FILTER=WifiTetherPreferenceControllerTest
Also tested manually on a Hawk.

Change-Id: I952ad10dd88b7d97b3cd86b269b8f67b00b1fa15
This commit is contained in:
James Mattis
2019-11-04 16:57:32 -08:00
parent b499cc5643
commit 4a18957c2d

View File

@@ -3,6 +3,7 @@ package com.android.settings.wifi.tether;
import android.net.wifi.WifiClient;
import android.net.wifi.WifiManager;
import android.os.Handler;
import android.os.HandlerExecutor;
import java.util.List;
@@ -35,7 +36,7 @@ public class WifiTetherSoftApManager {
}
public void registerSoftApCallback() {
mWifiManager.registerSoftApCallback(mSoftApCallback, mHandler);
mWifiManager.registerSoftApCallback(mSoftApCallback, new HandlerExecutor(mHandler));
}
public void unRegisterSoftApCallback() {