Android 4.2 Wifi Display 之 Settings 源码分析
2015-10-13 20:16 指针空间 阅读(2482) 评论(0) 编辑 收藏 举报相关Service的启动
图中主要有以下几个模块,DisplayManagerService、MediaRouterService、WifiDisplayAdapter和WifiDisplayController。其中:
DisplayManagerService用于管理系统显示设备的生命周期,包含物理屏幕、虚拟屏幕、wifi display等,它用一组DiaplayAdapter来管理这些显示设备。
MediaRouterService用于管理各个应用程序的多媒体播放的行为。
MediaRouter用于和MediaRouterService交互一起管理多媒体的播放行为,并维护当前已经配对上的remote display设备,包括Wifi diplay、蓝牙A2DP设备、chromecast设备。
WifiDisplayAdapter是用于DisplayManagerService管理Wifi display显示的adapter。
WifiDisplayController用于控制扫描wifi display设备、连接、断开等操作。
先来顺着上面的架构图看各个Service的启动。首先来看DisplayManagerService,在SystemServer中先创建一个DisplayManagerService对象,然后调用systemReady方法:
- public DisplayManagerService(Context context, Handler mainHandler) {
- mContext = context;
- mHeadless = SystemProperties.get(SYSTEM_HEADLESS).equals("1");
- mHandler = new DisplayManagerHandler(mainHandler.getLooper());
- mUiHandler = UiThread.getHandler();
- mDisplayAdapterListener = new DisplayAdapterListener();
- mSingleDisplayDemoMode = SystemProperties.getBoolean("persist.demo.singledisplay", false);
- mHandler.sendEmptyMessage(MSG_REGISTER_DEFAULT_DISPLAY_ADAPTER);
- }
- public void systemReady(boolean safeMode, boolean onlyCore) {
- synchronized (mSyncRoot) {
- mSafeMode = safeMode;
- mOnlyCore = onlyCore;
- }
- mHandler.sendEmptyMessage(MSG_REGISTER_ADDITIONAL_DISPLAY_ADAPTERS);
- }
在DisplayManagerService的构造函数中,首先获取SYSTEM_HEADLESS属性,用于表明系统是否支持headless模式,默认为0。然后创建一个DisplayManagerHandler用于处理DisplayManagerService中的消息,mSigleDisplayDemoMode用于开发模式中。然后给自己发送MSG_REGISTER_DEFAULT_DISPLAY_ADAPTER,我们到DisplayManagerHandler看如何处理这个消息:
- private final class DisplayManagerHandler extends Handler {
- public DisplayManagerHandler(Looper looper) {
- super(looper, null, true /*async*/);
- }
- @Override
- public void handleMessage(Message msg) {
- switch (msg.what) {
- case MSG_REGISTER_DEFAULT_DISPLAY_ADAPTER:
- registerDefaultDisplayAdapter();
- break;
- case MSG_REGISTER_ADDITIONAL_DISPLAY_ADAPTERS:
- registerAdditionalDisplayAdapters();
- break;
处理MSG_REGISTER_DEFAULT_DISPLAY_ADAPTER消息就是调用registerDefaultDisplayAdapter来注册一个默认的DiaplayAdapter,DisplayManagerService维护一组DiaplayAdapter,用于管理这些显示设备。默认的DiaplayAdapter就是系统的物理屏幕,通过Surface flinger来控制输出。
- private void registerDefaultDisplayAdapter() {
- // Register default display adapter.
- synchronized (mSyncRoot) {
- if (mHeadless) {
- registerDisplayAdapterLocked(new HeadlessDisplayAdapter(
- mSyncRoot, mContext, mHandler, mDisplayAdapterListener));
- } else {
- registerDisplayAdapterLocked(new LocalDisplayAdapter(
- mSyncRoot, mContext, mHandler, mDisplayAdapterListener));
- }
- }
- }
- private void registerDisplayAdapterLocked(DisplayAdapter adapter) {
- mDisplayAdapters.add(adapter);
- adapter.registerLocked();
- }
管理surface finger的知识就不讲解了。接着来看systemReady函数中会发送MSG_REGISTER_ADDITIONAL_DISPLAY_ADAPTERS,这里就会调用registerAdditionalDisplayAdapters来注册其它的显示设备:
- private void registerAdditionalDisplayAdapters() {
- synchronized (mSyncRoot) {
- if (shouldRegisterNonEssentialDisplayAdaptersLocked()) {
- registerOverlayDisplayAdapterLocked();
- registerWifiDisplayAdapterLocked();
- registerVirtualDisplayAdapterLocked();
- }
- }
- }
这里主要注册三种DisplayAdapter,一种是OverlayDiaplayAdapter用于开发模式用;一种是WifiDisplayAdapter用于wifi display,也是我们接下来要讲的;还有一种是虚拟显示。接下来只看registerWifiDisplayAdapterLocked:
- private void registerWifiDisplayAdapterLocked() {
- if (mContext.getResources().getBoolean(
- com.android.internal.R.bool.config_enableWifiDisplay)
- || SystemProperties.getInt(FORCE_WIFI_DISPLAY_ENABLE, -1) == 1) {
- mWifiDisplayAdapter = new WifiDisplayAdapter(
- mSyncRoot, mContext, mHandler, mDisplayAdapterListener,
- mPersistentDataStore);
- registerDisplayAdapterLocked(mWifiDisplayAdapter);
- }
- }
这里会创建WifiDisplayAdapter对象,我们到它的构造函数中去分析,并调用registerDisplayAdapterLocked添加到mDisplayAdapter中,这里会回调WifiDisplayAdapter的registerLocked方法:
- public WifiDisplayAdapter(DisplayManagerService.SyncRoot syncRoot,
- Context context, Handler handler, Listener listener,
- PersistentDataStore persistentDataStore) {
- super(syncRoot, context, handler, listener, TAG);
- mHandler = new WifiDisplayHandler(handler.getLooper());
- mPersistentDataStore = persistentDataStore;
- mSupportsProtectedBuffers = context.getResources().getBoolean(
- com.android.internal.R.bool.config_wifiDisplaySupportsProtectedBuffers);
- mNotificationManager = (NotificationManager)context.getSystemService(
- Context.NOTIFICATION_SERVICE);
- }
- public void registerLocked() {
- super.registerLocked();
- updateRememberedDisplaysLocked();
- getHandler().post(new Runnable() {
- @Override
- public void run() {
- mDisplayController = new WifiDisplayController(
- getContext(), getHandler(), mWifiDisplayListener);
- getContext().registerReceiverAsUser(mBroadcastReceiver, UserHandle.ALL,
- new IntentFilter(ACTION_DISCONNECT), null, mHandler);
- }
- });
- }
PersistentDateStore用于持久性存储连过的wifi display设备,用于在WifiDisplaySettings中显示前面已经连接过的设备列表。SupportsProtectedBuffer与gralloc显示相关。在registerLocked通过updateRememberedDisplaysLocked去加载/data/system/display-manager-state.xml中保存过的列表,并记录在mRememberedDisplays中。接着实例化一个WifiDisplayController对象,同时注册对ACTION_DISCONNECT的receiver。接着到WifiDisplayController去分析,注意WifiDisplayController最后一个参数用于回调通知WifiDisplayAdapter相关状态的改变,比如wifi display打开/关闭、wifi display连接/断开等。
- public WifiDisplayController(Context context, Handler handler, Listener listener) {
- mContext = context;
- mHandler = handler;
- mListener = listener;
- mWifiP2pManager = (WifiP2pManager)context.getSystemService(Context.WIFI_P2P_SERVICE);
- mWifiP2pChannel = mWifiP2pManager.initialize(context, handler.getLooper(), null);
- IntentFilter intentFilter = new IntentFilter();
- intentFilter.addAction(WifiP2pManager.WIFI_P2P_STATE_CHANGED_ACTION);
- intentFilter.addAction(WifiP2pManager.WIFI_P2P_PEERS_CHANGED_ACTION);
- intentFilter.addAction(WifiP2pManager.WIFI_P2P_CONNECTION_CHANGED_ACTION);
- intentFilter.addAction(WifiP2pManager.WIFI_P2P_THIS_DEVICE_CHANGED_ACTION);
- context.registerReceiver(mWifiP2pReceiver, intentFilter, null, mHandler);
- ContentObserver settingsObserver = new ContentObserver(mHandler) {
- @Override
- public void onChange(boolean selfChange, Uri uri) {
- updateSettings();
- }
- };
- final ContentResolver resolver = mContext.getContentResolver();
- resolver.registerContentObserver(Settings.Global.getUriFor(
- Settings.Global.WIFI_DISPLAY_ON), false, settingsObserver);
- resolver.registerContentObserver(Settings.Global.getUriFor(
- Settings.Global.WIFI_DISPLAY_CERTIFICATION_ON), false, settingsObserver);
- resolver.registerContentObserver(Settings.Global.getUriFor(
- Settings.Global.WIFI_DISPLAY_WPS_CONFIG), false, settingsObserver);
- updateSettings();
- }
这里主要注册WifiP2pReceiver用于接收处理WIFI_P2P_STATE_CHANGED_ACTION、WIFI_P2P_PEERS_CHANGED_ACTION、WIFI_P2P_CONNECTION_CHANGED_ACTION、WIFI_P2P_THIS_DEVICE_CHANGED_ACTION消息,然后注册ContentObserver来监控Settings.Global这个数据库里面的WIFI_DISPLAY_ON、WIFI_DISPLAY_CERTIFICATION_ON和WIFI_DISPLAY_WPS_CONFIG,这里比较重要,我们后面会看到在WifiDisplaySettings里面enable wifi display的时候,就会走到这个地方来。接着调用updateSettings来处理默认是否打开Wifi display,这里默认是关闭的,我们后面再来分析这一块。
接着来看MediaRouterService和MediaRouter,MediaRouter通过AIDL调用MediaRouterService的实现来完成一些工作。在SystemServer启动MediaRouterService的时候,主要创建一个MediaRouterService,然后调用它的systemRunning方法,代码如下:
- public MediaRouterService(Context context) {
- mContext = context;
- Watchdog.getInstance().addMonitor(this);
- }
- public void systemRunning() {
- IntentFilter filter = new IntentFilter(Intent.ACTION_USER_SWITCHED);
- mContext.registerReceiver(new BroadcastReceiver() {
- @Override
- public void onReceive(Context context, Intent intent) {
- if (intent.getAction().equals(Intent.ACTION_USER_SWITCHED)) {
- switchUser();
- }
- }
- }, filter);
- switchUser();
- }
上面的方法比较简单,主要就是接收ACTION_USER_SWITCHED,这是关于多用户切换的操作。MediaRouterService的工作比较少,主要都是MediaRouter通过AIDL调用完成,接下来去看MediaRouter的部分,在Android官方文档中有说明MediaRouter的调用方法:
A MediaRouter is retrieved through Context.getSystemService()
of a Context.MEDIA_ROUTER_SERVICE
. 这样系统是实例化一个MediaRouter对象并返回,下面来看它的构造函数:
- public MediaRouter(Context context) {
- synchronized (Static.class) {
- if (sStatic == null) {
- final Context appContext = context.getApplicationContext();
- sStatic = new Static(appContext);
- sStatic.startMonitoringRoutes(appContext);
- }
- }
- }
- Static(Context appContext) {
- mAppContext = appContext;
- mResources = Resources.getSystem();
- mHandler = new Handler(appContext.getMainLooper());
- IBinder b = ServiceManager.getService(Context.AUDIO_SERVICE);
- mAudioService = IAudioService.Stub.asInterface(b);
- mDisplayService = (DisplayManager) appContext.getSystemService(Context.DISPLAY_SERVICE);
- mMediaRouterService = IMediaRouterService.Stub.asInterface(
- ServiceManager.getService(Context.MEDIA_ROUTER_SERVICE));
- mSystemCategory = new RouteCategory(
- com.android.internal.R.string.default_audio_route_category_name,
- ROUTE_TYPE_LIVE_AUDIO | ROUTE_TYPE_LIVE_VIDEO, false);
- mSystemCategory.mIsSystem = true;
- mCanConfigureWifiDisplays = appContext.checkPermission(
- Manifest.permission.CONFIGURE_WIFI_DISPLAY,
- Process.myPid(), Process.myUid()) == PackageManager.PERMISSION_GRANTED;
- }
MediaRouter中主要通过Static对象来实现其大多数的方法,Static就是一个单例模式,先看Static的构造函数,也可以通过上面的图看到,MediaRouter包含DisplayManager对象和MediaRouterService的BpBinder引用,MediaRouter还持有AudioService的BpBind,用于控制audio数据的输出设备,例如可以用于蓝牙A2DP中使用。接着看Static的startMonitoringRoutes方法:
- void startMonitoringRoutes(Context appContext) {
- mDefaultAudioVideo = new RouteInfo(mSystemCategory);
- mDefaultAudioVideo.mNameResId = com.android.internal.R.string.default_audio_route_name;
- mDefaultAudioVideo.mSupportedTypes = ROUTE_TYPE_LIVE_AUDIO | ROUTE_TYPE_LIVE_VIDEO;
- mDefaultAudioVideo.updatePresentationDisplay();
- addRouteStatic(mDefaultAudioVideo);
- // This will select the active wifi display route if there is one.
- updateWifiDisplayStatus(mDisplayService.getWifiDisplayStatus());
- appContext.registerReceiver(new WifiDisplayStatusChangedReceiver(),
- new IntentFilter(DisplayManager.ACTION_WIFI_DISPLAY_STATUS_CHANGED));
- appContext.registerReceiver(new VolumeChangeReceiver(),
- new IntentFilter(AudioManager.VOLUME_CHANGED_ACTION));
- mDisplayService.registerDisplayListener(this, mHandler);
- // Bind to the media router service.
- rebindAsUser(UserHandle.myUserId());
- // Select the default route if the above didn't sync us up
- // appropriately with relevant system state.
- if (mSelectedRoute == null) {
- selectDefaultRouteStatic();
- }
- }
首先注册系统中默认的AudioVideo输出设备,如果有处于活动状态的wifi display连接,就记录下当前处于活动连接的设备,默认为空。上面会注册两个broadcastReceiver,一个用于接收ACTION_WIFI_DISPLAY_STATUS_CHANGED,另一个接收VOLUME_CHANGED_ACTION,我们主要看前面接收ACTION_WIFI_DISPLAY_STATUS_CHANGED的receiver,如下:
- static class WifiDisplayStatusChangedReceiver extends BroadcastReceiver {
- @Override
- public void onReceive(Context context, Intent intent) {
- if (intent.getAction().equals(DisplayManager.ACTION_WIFI_DISPLAY_STATUS_CHANGED)) {
- updateWifiDisplayStatus((WifiDisplayStatus) intent.getParcelableExtra(
- DisplayManager.EXTRA_WIFI_DISPLAY_STATUS));
- }
- }
mFeatureState | 表明现在wifi display是关闭还是打开状态 |
mScanState | 表现现在wifi display是否在scanning状态 |
mActiveDisplayState | 表明现在wifi display是在连接还是无连接状态 |
mActiveDisplay | 处于正在连接或者连接中的WifiDisplay对象 |
mDisplays | 扫描到的WifiDisplay对象数组 |
mSessionInfo | 用于过Miracast认证时用 |
然后向DisplayManager注册一个回调函数,当有显示设备增加、删除或者改变的时候,就会有相应的回调函数来通知Static对象。接着绑定MediaRouterService:
- void rebindAsUser(int userId) {
- if (mCurrentUserId != userId || userId < 0 || mClient == null) {
- mCurrentUserId = userId;
- try {
- Client client = new Client();
- mMediaRouterService.registerClientAsUser(client,
- mAppContext.getPackageName(), userId);
- mClient = client;
- } catch (RemoteException ex) {
- Log.e(TAG, "Unable to register media router client.", ex);
- }
- publishClientDiscoveryRequest();
- publishClientSelectedRoute(false);
- updateClientState();
- }
- }
Enable WifiDisplay
- public void onCreate(Bundle icicle) {
- super.onCreate(icicle);
- final Context context = getActivity();
- mRouter = (MediaRouter)context.getSystemService(Context.MEDIA_ROUTER_SERVICE);
- mDisplayManager = (DisplayManager)context.getSystemService(Context.DISPLAY_SERVICE);
- mWifiP2pManager = (WifiP2pManager)context.getSystemService(Context.WIFI_P2P_SERVICE);
- mWifiP2pChannel = mWifiP2pManager.initialize(context, Looper.getMainLooper(), null);
- addPreferencesFromResource(R.xml.wifi_display_settings);
- setHasOptionsMenu(true);
- }
- public void onStart() {
- super.onStart();
- mStarted = true;
- final Context context = getActivity();
- IntentFilter filter = new IntentFilter();
- filter.addAction(DisplayManager.ACTION_WIFI_DISPLAY_STATUS_CHANGED);
- context.registerReceiver(mReceiver, filter);
- getContentResolver().registerContentObserver(Settings.Global.getUriFor(
- Settings.Global.WIFI_DISPLAY_ON), false, mSettingsObserver);
- getContentResolver().registerContentObserver(Settings.Global.getUriFor(
- Settings.Global.WIFI_DISPLAY_CERTIFICATION_ON), false, mSettingsObserver);
- getContentResolver().registerContentObserver(Settings.Global.getUriFor(
- Settings.Global.WIFI_DISPLAY_WPS_CONFIG), false, mSettingsObserver);
- mRouter.addCallback(MediaRouter.ROUTE_TYPE_REMOTE_DISPLAY, mRouterCallback,
- MediaRouter.CALLBACK_FLAG_PERFORM_ACTIVE_SCAN);
- update(CHANGE_ALL);
- }
首先注册对ACTION_WIFI_DISPLAY_STATUS_CHANGED的receiver,这个broadcast会在WifiDisplayAdapter里面当wifi display的状态发送改变时发送,包括扫描到新的设备、开始连接、连接成功、断开等消息都会被这个receiver接收到,后面我们会来分析这个receiver干了什么,然后在onStart中想MediaRouter对象注册一个callback函数,用于获取系统中remote display的相关回调信息。然后类似WifiDisplayController一样,注册一些对数据库改变的ContentObserver。接着来看MediaRouter.addCallback的实现:
- public void addCallback(int types, Callback cb, int flags) {
- CallbackInfo info;
- int index = findCallbackInfo(cb);
- if (index >= 0) {
- info = sStatic.mCallbacks.get(index);
- info.type |= types;
- info.flags |= flags;
- } else {
- info = new CallbackInfo(cb, types, flags, this);
- sStatic.mCallbacks.add(info);
- }
- sStatic.updateDiscoveryRequest();
- }
Static的mCallbacks是一个CopyOnWriteArrayList数组,记录所有注册到MediaRouter中的回调函数。如果已经向MediaRouter注册过这个callback,则更新相关的type和flag;如果没有注册,则新建一个CallbackInfo对象并添加到mCallbacks数组中。然后调用Static的updateDiscoveryRequest去更新是否需要发送Discovery request请求:
- void updateDiscoveryRequest() {
- final int count = mCallbacks.size();
- for (int i = 0; i < count; i++) {
- CallbackInfo cbi = mCallbacks.get(i);
- if ((cbi.flags & (CALLBACK_FLAG_PERFORM_ACTIVE_SCAN
- | CALLBACK_FLAG_REQUEST_DISCOVERY)) != 0) {
- // Discovery explicitly requested.
- routeTypes |= cbi.type;
- } else if ((cbi.flags & CALLBACK_FLAG_PASSIVE_DISCOVERY) != 0) {
- // Discovery only passively requested.
- passiveRouteTypes |= cbi.type;
- } else {
- // Legacy case since applications don't specify the discovery flag.
- // Unfortunately we just have to assume they always need discovery
- // whenever they have a callback registered.
- routeTypes |= cbi.type;
- }
- if ((cbi.flags & CALLBACK_FLAG_PERFORM_ACTIVE_SCAN) != 0) {
- activeScan = true;
- if ((cbi.type & ROUTE_TYPE_REMOTE_DISPLAY) != 0) {
- activeScanWifiDisplay = true;
- }
- }
- }
- if (routeTypes != 0 || activeScan) {
- // If someone else requests discovery then enable the passive listeners.
- // This is used by the MediaRouteButton and MediaRouteActionProvider since
- // they don't receive lifecycle callbacks from the Activity.
- routeTypes |= passiveRouteTypes;
- }
- // Update wifi display scanning.
- // TODO: All of this should be managed by the media router service.
- if (mCanConfigureWifiDisplays) {
- if (mSelectedRoute != null
- && mSelectedRoute.matchesTypes(ROUTE_TYPE_REMOTE_DISPLAY)) {
- // Don't scan while already connected to a remote display since
- // it may interfere with the ongoing transmission.
- activeScanWifiDisplay = false;
- }
- if (activeScanWifiDisplay) {
- if (!mActivelyScanningWifiDisplays) {
- mActivelyScanningWifiDisplays = true;
- mDisplayService.startWifiDisplayScan();
- }
- } else {
- if (mActivelyScanningWifiDisplays) {
- mActivelyScanningWifiDisplays = false;
- mDisplayService.stopWifiDisplayScan();
- }
- }
- }
- }
这个函数体比较长,主要通过注册的一系列的callback类型来决定是否要进行wifiDisplay scan的动作,根据在WifiDisplaySettings里面注册callback的方法: mRouter.addCallback(MediaRouter.ROUTE_TYPE_REMOTE_DISPLAY, mRouterCallback,
MediaRouter.CALLBACK_FLAG_PERFORM_ACTIVE_SCAN),上面函数中的activeScanWifiDisplay会为true,接着会调用DisplayManagerService中的startWifiDisplayScan,如下图。
- private void updateScanState() {
- if (mScanRequested && mWfdEnabled && mDesiredDevice == null) {
- if (!mDiscoverPeersInProgress) {
- Slog.i(TAG, "Starting Wifi display scan.");
- mDiscoverPeersInProgress = true;
- handleScanStarted();
- tryDiscoverPeers();
- }
- } else {
- if (mDiscoverPeersInProgress) {
- // Cancel automatic retry right away.
- mHandler.removeCallbacks(mDiscoverPeers);
- if (mDesiredDevice == null || mDesiredDevice == mConnectedDevice) {
- Slog.i(TAG, "Stopping Wifi display scan.");
- mDiscoverPeersInProgress = false;
- stopPeerDiscovery();
- handleScanFinished();
- }
- }
- }
- }
当初次进入到WifiDisplaySettings中,并没有去optionMenu中enable wifi display时,上面code中的mWfdEnabled为false,所以会跳出前面的if语句;后面的else语句中mDiscoverPeersInProgress也为false,因为这个变量只有在scan时才会被置为true。
接着来分析当用户点击了optionMenu中enable wifi display后的流程,先看WifiDisplaySettings的代码:
- public boolean onOptionsItemSelected(MenuItem item) {
- switch (item.getItemId()) {
- case MENU_ID_ENABLE_WIFI_DISPLAY:
- mWifiDisplayOnSetting = !item.isChecked();
- item.setChecked(mWifiDisplayOnSetting);
- Settings.Global.putInt(getContentResolver(),
- Settings.Global.WIFI_DISPLAY_ON, mWifiDisplayOnSetting ? 1 : 0);
这里首先改变OptionMenu的状态,并置mWifiDisplayOnSetting为上次MenuItem相反的状态,然后改变Settings.Global数据库中WIFI_DISPLAY_ON的指为1。前面我们介绍过,在WifiDisplaySettings和WifiDisplayController都有注册ContentObserver来监控这个值的变化。其中WifiDisplaySettings在监控到这个值的变化后,主要是调用MediaRouter和DisplayManager的方法去获取系统中已经扫描到的remote display设备,并更新到listview列表上,显然这时候还没有开始scan,所以listview列表为空。接着看WifiDisplayController处理ContentOberver的代码:
- private void updateSettings() {
- final ContentResolver resolver = mContext.getContentResolver();
- mWifiDisplayOnSetting = Settings.Global.getInt(resolver,
- Settings.Global.WIFI_DISPLAY_ON, 0) != 0;
- mWifiDisplayCertMode = Settings.Global.getInt(resolver,
- Settings.Global.WIFI_DISPLAY_CERTIFICATION_ON, 0) != 0;
- mWifiDisplayWpsConfig = WpsInfo.INVALID;
- if (mWifiDisplayCertMode) {
- mWifiDisplayWpsConfig = Settings.Global.getInt(resolver,
- Settings.Global.WIFI_DISPLAY_WPS_CONFIG, WpsInfo.INVALID);
- }
- updateWfdEnableState();
- }
这里主要置mWifiDisplayOnSetting为true,然后就调用updateWfdEnableState去更新wfd的状态:
- private void updateWfdEnableState() {
- if (mWifiDisplayOnSetting && mWifiP2pEnabled) {
- // WFD should be enabled.
- if (!mWfdEnabled && !mWfdEnabling) {
- mWfdEnabling = true;
- WifiP2pWfdInfo wfdInfo = new WifiP2pWfdInfo();
- wfdInfo.setWfdEnabled(true);
- wfdInfo.setDeviceType(WifiP2pWfdInfo.WFD_SOURCE);
- wfdInfo.setSessionAvailable(true);
- wfdInfo.setControlPort(DEFAULT_CONTROL_PORT);
- wfdInfo.setMaxThroughput(MAX_THROUGHPUT);
- mWifiP2pManager.setWFDInfo(mWifiP2pChannel, wfdInfo, new ActionListener() {
- @Override
- public void onSuccess() {
- if (DEBUG) {
- Slog.d(TAG, "Successfully set WFD info.");
- }
- if (mWfdEnabling) {
- mWfdEnabling = false;
- mWfdEnabled = true;
- reportFeatureState();
- updateScanState();
- }
- }
- @Override
- public void onFailure(int reason) {
- if (DEBUG) {
- Slog.d(TAG, "Failed to set WFD info with reason " + reason + ".");
- }
- mWfdEnabling = false;
- }
- });
- }
首先调用WifiP2pMananger的setWFDInfo把与wifi display相关的信息设置到wpa_supplicant,这些信息包括enable状态、device type(指为source还是sink)、session available(当前可否连接)、control port(用于rtsp连接)、maxThroughput(吞吐量),这些信息最终会随着P2P的IE信息在扫描阶段被对方知道。接着会调用reportFeatureState来通知WifiDisplayAdapter相应状态的变化,这里我们先看一下下面的流程图来了解一下WifiDisplaySettings、MediaRouter、DisplayMananger、WifiDisplayAdapter、WifiDisplayController是如何相互通知信息的,这其中有简单的callback,也有发送/接收broadcast,如下图:
- private void reportFeatureState() {
- final int featureState = computeFeatureState();
- mHandler.post(new Runnable() {
- @Override
- public void run() {
- mListener.onFeatureStateChanged(featureState);
- }
- });
- }
- private int computeFeatureState() {
- if (!mWifiP2pEnabled) {
- return WifiDisplayStatus.FEATURE_STATE_DISABLED;
- }
- return mWifiDisplayOnSetting ? WifiDisplayStatus.FEATURE_STATE_ON :
- WifiDisplayStatus.FEATURE_STATE_OFF;
- }
- public void onFeatureStateChanged(int featureState) {
- synchronized (getSyncRoot()) {
- if (mFeatureState != featureState) {
- mFeatureState = featureState;
- scheduleStatusChangedBroadcastLocked();
- }
- }
- }
- private void scheduleStatusChangedBroadcastLocked() {
- mCurrentStatus = null;
- if (!mPendingStatusChangeBroadcast) {
- mPendingStatusChangeBroadcast = true;
- mHandler.sendEmptyMessage(MSG_SEND_STATUS_CHANGE_BROADCAST);
- }
- }
- public void handleMessage(Message msg) {
- switch (msg.what) {
- case MSG_SEND_STATUS_CHANGE_BROADCAST:
- handleSendStatusChangeBroadcast();
- break;
- case MSG_UPDATE_NOTIFICATION:
- handleUpdateNotification();
- break;
- }
- ate void handleSendStatusChangeBroadcast() {
- final Intent intent;
- synchronized (getSyncRoot()) {
- if (!mPendingStatusChangeBroadcast) {
- return;
- }
- mPendingStatusChangeBroadcast = false;
- intent = new Intent(DisplayManager.ACTION_WIFI_DISPLAY_STATUS_CHANGED);
- intent.addFlags(Intent.FLAG_RECEIVER_REGISTERED_ONLY);
- intent.putExtra(DisplayManager.EXTRA_WIFI_DISPLAY_STATUS,
- getWifiDisplayStatusLocked());
- }
- // Send protected broadcast about wifi display status to registered receivers.
- getContext().sendBroadcastAsUser(intent, UserHandle.ALL);
上面的代码都比较简单,在getWifiDisplayStatusLocked中会根据WifiDisplayAdapter中的变量mFeatureState、mScanState、mActiveDisplayState、mActiveDisplay、mDisplays、mSessionInfo去构造一个WifiDisplayStatus对象,在前面我们介绍过这几个变量的含义了,当然这几个变量会从WifiDisplayListener的各个callback分别去改变自己的值。接着我们到MediaRouter中去看如何处理这个broadcastReceiver,前面我们已经讲过了,WifiDisplayStatusChangedReceiver会接收这个broadcast,然后调用updateWifiDisplayStatus来更新状态,我们稍后来看这部分的实现。回到WifiDisplayController的updateWfdEnableState方法中,接着会调用updateScanState方法开始扫描WifiDisplay设备:
- private void updateScanState() {
- if (mScanRequested && mWfdEnabled && mDesiredDevice == null) {
- if (!mDiscoverPeersInProgress) {
- Slog.i(TAG, "Starting Wifi display scan.");
- mDiscoverPeersInProgress = true;
- handleScanStarted();
- tryDiscoverPeers();
- }
- }
handleScanStarted用于通知WifiDisplayAdapter扫描开始了,当然WifiDisplayAdapter也会发broadcast给MediaRouter。接着会调用tryDiscoverPeers:
- private void tryDiscoverPeers() {
- mWifiP2pManager.discoverPeers(mWifiP2pChannel, new ActionListener() {
- @Override
- public void onSuccess() {
- if (DEBUG) {
- Slog.d(TAG, "Discover peers succeeded. Requesting peers now.");
- }
- if (mDiscoverPeersInProgress) {
- requestPeers();
- }
- }
- mHandler.postDelayed(mDiscoverPeers, DISCOVER_PEERS_INTERVAL_MILLIS);
- }
这里调用WifiP2pManager的discoverPeers去扫描所有的p2p设备,比较重要是后面有发一个delay message,表示每间隔10秒就去发一下P2P_FIND。当然下了P2P_FIND命令后,并不能马上获取到对方设备,但因为我们前面有讲过在/data/system/display-manager-state.xml有保存过前面连接过的设备列表,所以这里会马上调用requestPeers去获取设备列表。当然在WifiDisplayController也会注册对WIFI_P2P_PEERS_CHANGED_ACTION的receiver,最终还是会调用reqeustPeers去获取所有扫描到的设备列表,下面来看这个函数的实现:
- private void requestPeers() {
- mWifiP2pManager.requestPeers(mWifiP2pChannel, new PeerListListener() {
- @Override
- public void onPeersAvailable(WifiP2pDeviceList peers) {
- if (DEBUG) {
- Slog.d(TAG, "Received list of peers.");
- }
- mAvailableWifiDisplayPeers.clear();
- for (WifiP2pDevice device : peers.getDeviceList()) {
- if (DEBUG) {
- Slog.d(TAG, " " + describeWifiP2pDevice(device));
- }
- if (isWifiDisplay(device)) {
- mAvailableWifiDisplayPeers.add(device);
- }
- }
- if (mDiscoverPeersInProgress) {
- handleScanResults();
- }
- }
- });
- }
首先从扫描的设备列表中过滤掉不能做wifi display的设备,主要从三个方面过滤,一是纯粹的P2P设备,不会待用WfdInfo;第二是带有WfdInfo,但是暂时没有被enable;三是只能是PrimarySinkDevice,看起来Android还不支持SecondSink。并将过滤掉剩下的设备加入到mAvailableWifiDisplayPeers列表中,接着调用handleScanResults来组装WifiDisplay列表数组并notify给WifiDisplayAdapter:
- private void handleScanResults() {
- final int count = mAvailableWifiDisplayPeers.size();
- final WifiDisplay[] displays = WifiDisplay.CREATOR.newArray(count);
- for (int i = 0; i < count; i++) {
- WifiP2pDevice device = mAvailableWifiDisplayPeers.get(i);
- displays[i] = createWifiDisplay(device);
- updateDesiredDevice(device);
- }
- mHandler.post(new Runnable() {
- @Override
- public void run() {
- mListener.onScanResults(displays);
- }
- });
- }
这里首先根据mAvailableWifiDisplayPeers的数目创建一个WifiDisplay数组,然后一个个构造WifiDisplay对象,WifiDiplay对象包含以下几个变量:
mDeviceAddress | 设备的Mac地址 |
mDeviceName | 设备的名字 |
mDeviceAlias | 设备的别名,一般为NULL |
mIsAvailable | 是否可用状态 |
mCanConnect | WfdInfo中的SessionAvailable是否为1 |
mIsRemembered | 是否被记录的 |
- public void onScanResults(WifiDisplay[] availableDisplays) {
- synchronized (getSyncRoot()) {
- availableDisplays = mPersistentDataStore.applyWifiDisplayAliases(
- availableDisplays);
- boolean changed = !Arrays.equals(mAvailableDisplays, availableDisplays);
- // Check whether any of the available displays changed canConnect status.
- for (int i = 0; !changed && i<availableDisplays.length; i++) {
- changed = availableDisplays[i].canConnect()
- != mAvailableDisplays[i].canConnect();
- }
- if (changed) {
- mAvailableDisplays = availableDisplays;
- fixRememberedDisplayNamesFromAvailableDisplaysLocked();
- updateDisplaysLocked();
- scheduleStatusChangedBroadcastLocked();
- }
- }
- }
这里首先调用PersistentDateStore的applyWifiDisplayAliases方法去判断扫描到的设备中有没有以前连接过并记录下来的wifi display设备,比较方法是比较两者的MAC地址,如果在PersistentDateStore中找到,再比较两者的别名(Alias),如果不相同则更新results列表,细节的代码可以看applyWifiDisplayAlias中的实现。
- public WifiDisplay[] applyWifiDisplayAliases(WifiDisplay[] displays) {
- WifiDisplay[] results = displays;
- if (results != null) {
- int count = displays.length;
- for (int i = 0; i < count; i++) {
- WifiDisplay result = applyWifiDisplayAlias(displays[i]);
- if (result != displays[i]) {
- if (results == displays) {
- results = new WifiDisplay[count];
- System.arraycopy(displays, 0, results, 0, count);
- }
- results[i] = result;
- }
- }
- }
- return results;
- }
回到上面的onScanResults中,接着判断刚扫描到的设备列表(availableDisplays)和之前存储的设备列表(mAvailableDisplays)之间有没有变化,可以数组内容以及是否可连两个方面检查。如果有变化,则把刚扫描到的设备列表(availableDisplays)赋值给存储的设备列表(mAvailableDisplays)。接下来调用fixRememberedDisplayNamesFromAvailableDisplaysLocked来更新PersistentDateStore中存储的已经连接过的wifi display设备,更新的条件是设备的MAC地址一样,但设备的DeviceName和DeviceAlias有变化,这是就要更新到PersistentDateStore中,代码如下:
- private void fixRememberedDisplayNamesFromAvailableDisplaysLocked() {
- boolean changed = false;
- for (int i = 0; i < mRememberedDisplays.length; i++) {
- WifiDisplay rememberedDisplay = mRememberedDisplays[i];
- WifiDisplay availableDisplay = findAvailableDisplayLocked(
- rememberedDisplay.getDeviceAddress());
- if (availableDisplay != null && !rememberedDisplay.equals(availableDisplay)) {
- mRememberedDisplays[i] = availableDisplay;
- changed |= mPersistentDataStore.rememberWifiDisplay(availableDisplay);
- }
- }
- if (changed) {
- mPersistentDataStore.saveIfNeeded();
- }
- }
- private void updateDisplaysLocked() {
- List<WifiDisplay> displays = new ArrayList<WifiDisplay>(
- mAvailableDisplays.length + mRememberedDisplays.length);
- boolean[] remembered = new boolean[mAvailableDisplays.length];
- for (WifiDisplay d : mRememberedDisplays) {
- boolean available = false;
- for (int i = 0; i < mAvailableDisplays.length; i++) {
- if (d.equals(mAvailableDisplays[i])) {
- remembered[i] = available = true;
- break;
- }
- }
- if (!available) {
- displays.add(new WifiDisplay(d.getDeviceAddress(), d.getDeviceName(),
- d.getDeviceAlias(), false, false, true));
- }
- }
- for (int i = 0; i < mAvailableDisplays.length; i++) {
- WifiDisplay d = mAvailableDisplays[i];
- displays.add(new WifiDisplay(d.getDeviceAddress(), d.getDeviceName(),
- d.getDeviceAlias(), true, d.canConnect(), remembered[i]));
- }
- mDisplays = displays.toArray(WifiDisplay.EMPTY_ARRAY);
- }
上面的实现中先从mRememberedDisplays逐个添加wifi display设备到displays数组中,如果在mAvailableDisplays有相同的设备,则不添加到displays数组;后面再把mAvailableDisplays所有元素添加到displays数组,并全部赋值给mDisplays数组。
- static void updateWifiDisplayStatus(WifiDisplayStatus status) {
- WifiDisplay[] displays;
- WifiDisplay activeDisplay;
- if (status.getFeatureState() == WifiDisplayStatus.FEATURE_STATE_ON) {
- displays = status.getDisplays();
- activeDisplay = status.getActiveDisplay();
- } else {
- displays = WifiDisplay.EMPTY_ARRAY;
- activeDisplay = null;
- }
- String activeDisplayAddress = activeDisplay != null ?
- activeDisplay.getDeviceAddress() : null;
- // Add or update routes.
- for (int i = 0; i < displays.length; i++) {
- final WifiDisplay d = displays[i];
- if (shouldShowWifiDisplay(d, activeDisplay)) {
- RouteInfo route = findWifiDisplayRoute(d);
- if (route == null) {
- route = makeWifiDisplayRoute(d, status);
- addRouteStatic(route);
- } else {
- String address = d.getDeviceAddress();
- boolean disconnected = !address.equals(activeDisplayAddress)
- && address.equals(sStatic.mPreviousActiveWifiDisplayAddress);
- updateWifiDisplayRoute(route, d, status, disconnected);
- }
- if (d.equals(activeDisplay)) {
- selectRouteStatic(route.getSupportedTypes(), route, false);
- }
- }
- }
- // Remove stale routes.
- for (int i = sStatic.mRoutes.size(); i-- > 0; ) {
- RouteInfo route = sStatic.mRoutes.get(i);
- if (route.mDeviceAddress != null) {
- WifiDisplay d = findWifiDisplay(displays, route.mDeviceAddress);
- if (d == null || !shouldShowWifiDisplay(d, activeDisplay)) {
- removeRouteStatic(route);
- }
- }
- }
- sStatic.mPreviousActiveWifiDisplayAddress = activeDisplayAddress;
- }
- private final BroadcastReceiver mReceiver = new BroadcastReceiver() {
- @Override
- public void onReceive(Context context, Intent intent) {
- String action = intent.getAction();
- if (action.equals(DisplayManager.ACTION_WIFI_DISPLAY_STATUS_CHANGED)) {
- scheduleUpdate(CHANGE_WIFI_DISPLAY_STATUS);
- }
- }
- };
从MediaRouter中的callback消息也会进入到scheduleUpdate中,只是后面的参数不一样,通过callback进来的参数是CHANGE_ROUTES,而broadcast进来的参数是CHANGE_WIFI_DISPLAY_STATUS,来看scheduleUpdate,最终实现是mUpdateRunnable中:
- private void update(int changes) {
- boolean invalidateOptions = false;
- // Update wifi display state.
- if ((changes & CHANGE_WIFI_DISPLAY_STATUS) != 0) {
- mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
- // The wifi display feature state may have changed.
- invalidateOptions = true;
- }
- // Rebuild the routes.
- final PreferenceScreen preferenceScreen = getPreferenceScreen();
- preferenceScreen.removeAll();
- // Add all known remote display routes.
- final int routeCount = mRouter.getRouteCount();
- for (int i = 0; i < routeCount; i++) {
- MediaRouter.RouteInfo route = mRouter.getRouteAt(i);
- if (route.matchesTypes(MediaRouter.ROUTE_TYPE_REMOTE_DISPLAY)) {
- preferenceScreen.addPreference(createRoutePreference(route));
- }
- }
- // Additional features for wifi display routes.
- if (mWifiDisplayStatus != null
- && mWifiDisplayStatus.getFeatureState() == WifiDisplayStatus.FEATURE_STATE_ON) {
- // Add all unpaired wifi displays.
- for (WifiDisplay display : mWifiDisplayStatus.getDisplays()) {
- if (!display.isRemembered() && display.isAvailable()
- && !display.equals(mWifiDisplayStatus.getActiveDisplay())) {
- preferenceScreen.addPreference(new UnpairedWifiDisplayPreference(
- getActivity(), display));
- }
- }
- }
- }
上面的代码比较简单,一个是从MediaRouter中获取mRoutes数组中存着的remote display设备;一个是从broadcast中的WifiDisplayStatus对象中获取mDisplay数组,两者相互合并构建整个listview展现给用户。至此,wifi display的扫描流程就介绍完了,下面是整体的流程图: