Android Launcher3各启动场景源码分析


  团队博客: 汽车电子社区


一、概述

  Launcher3是Android系统提供的默认桌面应用(Launcher),它的源码路径在**“packages/apps/Launcher3/”**。Launcher3的启动场景主要包括:
    1、开机后启动:开机时,android ams服务拉起Launcher。
    2、按键启动:比如短压home键,android wms中的PhoneWindowManager拉起Launcher。
    3、异常崩溃后启动:Launcher异常崩溃后,android ams再次拉起Launcher。
  针对这三种情况,分析一下Aosp源码如何实现。

二、开机启动Launcher

2.1、开机启动Launcher流程图

在这里插入图片描述

2.2、开机启动流程源码分析

  Launcher的开机启动由Android的AMS服务完成。AMS在SystemReady阶段会调用startHomeOnAllDisplays函数。Android支持多Display(虚拟Display或者由硬件上报的实际Display),多Display情况下一般Launcher会针对不同Display做不同的效果。

// frameworks/base/services/core/java/com/android/server/am/ActivityManagerService.java
public void systemReady(final Runnable goingCallback, TimingsTraceLog traceLog) {
    traceLog.traceBegin("PhaseActivityManagerReady");
    synchronized(this) {
        if (mSystemReady) {
            // If we're done calling all the receivers, run the next "boot phase" passed in
            // by the SystemServer
            if (goingCallback != null) {
                goingCallback.run();
            }
            return;
        }

        mLocalDeviceIdleController
                = LocalServices.getService(DeviceIdleController.LocalService.class);
        mActivityTaskManager.onSystemReady();
        // Make sure we have the current profile info, since it is needed for security checks.
        mUserController.onSystemReady();
        mAppOpsService.systemReady();
        mSystemReady = true;
    }

    try {
        sTheRealBuildSerial = IDeviceIdentifiersPolicyService.Stub.asInterface(
                ServiceManager.getService(Context.DEVICE_IDENTIFIERS_SERVICE))
                .getSerial();
    } catch (RemoteException e) {}

    ArrayList<ProcessRecord> procsToKill = null;
    synchronized(mPidsSelfLocked) {
        for (int i=mPidsSelfLocked.size()-1; i>=0; i--) {
            ProcessRecord proc = mPidsSelfLocked.valueAt(i);
            if (!isAllowedWhileBooting(proc.info)){
                if (procsToKill == null) {
                    procsToKill = new ArrayList<ProcessRecord>();
                }
                procsToKill.add(proc);
            }
        }
    }

    synchronized(this) {
        if (procsToKill != null) {
            for (int i=procsToKill.size()-1; i>=0; i--) {
                ProcessRecord proc = procsToKill.get(i);
                Slog.i(TAG, "Removing system update proc: " + proc);
                mProcessList.removeProcessLocked(proc, true, false, "system update done");
            }
        }

        // Now that we have cleaned up any update processes, we
        // are ready to start launching real processes and know that
        // we won't trample on them any more.
        mProcessesReady = true;
    }

    Slog.i(TAG, "System now ready");
    EventLog.writeEvent(EventLogTags.BOOT_PROGRESS_AMS_READY, SystemClock.uptimeMillis());

    mAtmInternal.updateTopComponentForFactoryTest();
    mAtmInternal.getLaunchObserverRegistry().registerLaunchObserver(mActivityLaunchObserver);

    watchDeviceProvisioning(mContext);

    retrieveSettings();
    mUgmInternal.onSystemReady();

    final PowerManagerInternal pmi = LocalServices.getService(PowerManagerInternal.class);
    if (pmi != null) {
        pmi.registerLowPowerModeObserver(ServiceType.FORCE_BACKGROUND_CHECK,
                state -> updateForceBackgroundCheck(state.batterySaverEnabled));
        updateForceBackgroundCheck(
                pmi.getLowPowerState(ServiceType.FORCE_BACKGROUND_CHECK).batterySaverEnabled);
    } else {
        Slog.wtf(TAG, "PowerManagerInternal not found.");
    }

    if (goingCallback != null) goingCallback.run();
    // Check the current user here as a user can be started inside goingCallback.run() from
    // other system services.
    final int currentUserId = mUserController.getCurrentUserId();
    Slog.i(TAG, "Current user:" + currentUserId);
    if (currentUserId != UserHandle.USER_SYSTEM && !mUserController.isSystemUserStarted()) {
        // User other than system user has started. Make sure that system user is already
        // started before switching user.
        throw new RuntimeException("System user not started while current user is:"
                + currentUserId);
    }
    traceLog.traceBegin("ActivityManagerStartApps");
    mBatteryStatsService.noteEvent(BatteryStats.HistoryItem.EVENT_USER_RUNNING_START,
            Integer.toString(currentUserId), currentUserId);
    mBatteryStatsService.noteEvent(BatteryStats.HistoryItem.EVENT_USER_FOREGROUND_START,
            Integer.toString(currentUserId), currentUserId);

    // On Automotive, at this point the system user has already been started and unlocked,
    // and some of the tasks we do here have already been done. So skip those in that case.
    // TODO(b/132262830): this workdound shouldn't be necessary once we move the
    // headless-user start logic to UserManager-land
    final boolean bootingSystemUser = currentUserId == UserHandle.USER_SYSTEM;

    if (bootingSystemUser) {
        mSystemServiceManager.startUser(currentUserId);
    }

    synchronized (this) {
        // Only start up encryption-aware persistent apps; once user is
        // unlocked we'll come back around and start unaware apps
        startPersistentApps(PackageManager.MATCH_DIRECT_BOOT_AWARE);

        // Start up initial activity.
        mBooting = true;
        // Enable home activity for system user, so that the system can always boot. We don't
        // do this when the system user is not setup since the setup wizard should be the one
        // to handle home activity in this case.
        if (UserManager.isSplitSystemUser() &&
                Settings.Secure.getInt(mContext.getContentResolver(),
                     Settings.Secure.USER_SETUP_COMPLETE, 0) != 0) {
            ComponentName cName = new ComponentName(mContext, SystemUserHomeActivity.class);
            try {
                AppGlobals.getPackageManager().setComponentEnabledSetting(cName,
                        PackageManager.COMPONENT_ENABLED_STATE_ENABLED, 0,
                        UserHandle.USER_SYSTEM);
            } catch (RemoteException e) {
                throw e.rethrowAsRuntimeException();
            }
        }

        if (bootingSystemUser) {
            // 启动Home,也就是Launcher
            mAtmInternal.startHomeOnAllDisplays(currentUserId, "systemReady");
        }

        mAtmInternal.showSystemReadyErrorDialogsIfNeeded();

        if (bootingSystemUser) {
            final int callingUid = Binder.getCallingUid();
            final int callingPid = Binder.getCallingPid();
            long ident = Binder.clearCallingIdentity();
            try {
                Intent intent = new Intent(Intent.ACTION_USER_STARTED);
                intent.addFlags(Intent.FLAG_RECEIVER_REGISTERED_ONLY
                        | Intent.FLAG_RECEIVER_FOREGROUND);
                intent.putExtra(Intent.EXTRA_USER_HANDLE, currentUserId);
                broadcastIntentLocked(null, null, intent,
                        null, null, 0, null, null, null, OP_NONE,
                        null, false, false, MY_PID, SYSTEM_UID, callingUid, callingPid,
                        currentUserId);
                intent = new Intent(Intent.ACTION_USER_STARTING);
                intent.addFlags(Intent.FLAG_RECEIVER_REGISTERED_ONLY);
                intent.putExtra(Intent.EXTRA_USER_HANDLE, currentUserId);
                broadcastIntentLocked(null, null, intent,
                        null, new IIntentReceiver.Stub() {
                            @Override
                            public void performReceive(Intent intent, int resultCode, String data,
                                    Bundle extras, boolean ordered, boolean sticky, int sendingUser)
                                    throws RemoteException {
                            }
                        }, 0, null, null,
                        new String[] {INTERACT_ACROSS_USERS}, OP_NONE,
                        null, true, false, MY_PID, SYSTEM_UID, callingUid, callingPid,
                        UserHandle.USER_ALL);
            } catch (Throwable t) {
                Slog.wtf(TAG, "Failed sending first user broadcasts", t);
            } finally {
                Binder.restoreCallingIdentity(ident);
            }
        } else {
            Slog.i(TAG, "Not sending multi-user broadcasts for non-system user "
                    + currentUserId);
        }
        mAtmInternal.resumeTopActivities(false /* scheduleIdle */);
        if (bootingSystemUser) {
            mUserController.sendUserSwitchBroadcasts(-1, currentUserId);
        }

        BinderInternal.nSetBinderProxyCountWatermarks(BINDER_PROXY_HIGH_WATERMARK,
                BINDER_PROXY_LOW_WATERMARK);
        BinderInternal.nSetBinderProxyCountEnabled(true);
        BinderInternal.setBinderProxyCountCallback(
                new BinderInternal.BinderProxyLimitListener() {
                    @Override
                    public void onLimitReached(int uid) {
                        Slog.wtf(TAG, "Uid " + uid + " sent too many Binders to uid "
                                + Process.myUid());
                        BinderProxy.dumpProxyDebugInfo();
                        if (uid == Process.SYSTEM_UID) {
                            Slog.i(TAG, "Skipping kill (uid is SYSTEM)");
                        } else {
                            killUid(UserHandle.getAppId(uid), UserHandle.getUserId(uid),
                                    "Too many Binders sent to SYSTEM");
                        }
                    }
                }, mHandler);

        traceLog.traceEnd(); // ActivityManagerStartApps
        traceLog.traceEnd(); // PhaseActivityManagerReady
    }
}

  调用ActivityTaskManagerInternal类型的接口startHomeOnAllDisplays,这个接口ActivityTaskManagerService.java文件中实现。

// android/frameworks/base/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
final class LocalService extends ActivityTaskManagerInternal {
    @Override
    public boolean startHomeOnAllDisplays(int userId, String reason) {
        synchronized (mGlobalLock) {
            // 这个对象是RootActivityContainer类型
            return mRootActivityContainer.startHomeOnAllDisplays(userId, reason);
        }
    }
}

  接下来调用RootActivityContainer的接口startHomeOnAllDisplays,第二个参数reson的值为“systemReady”。

// frameworks/base/services/core/java/com/android/server/wm/RootActivityContainer.java
boolean startHomeOnAllDisplays(int userId, String reason) {
    boolean homeStarted = false;
    for (int i = mActivityDisplays.size() - 1; i >= 0; i--) {
        final int displayId = mActivityDisplays.get(i).mDisplayId;
        homeStarted |= startHomeOnDisplay(userId, reason, displayId);
    }
    return homeStarted;
}

  遍历mActivityDisplays对于所有处于Active状态的Display调用startHomeOnDisplay,在每个Display上都启动Home(Launcher)。

boolean startHomeOnDisplay(int userId, String reason, int displayId) {
    // allowInstrumenting :false
    // fromHomeKey : false
    return startHomeOnDisplay(userId, reason, displayId, false /* allowInstrumenting */,
            false /* fromHomeKey */);
}
    
boolean startHomeOnDisplay(int userId, String reason, int displayId, boolean allowInstrumenting,
        boolean fromHomeKey) {
    // 如果DisplayID是非法的,使用当前处于顶层焦点的 Display
    // Fallback to top focused display if the displayId is invalid.
    if (displayId == INVALID_DISPLAY) {
        displayId = getTopDisplayFocusedStack().mDisplayId;
    }
    
    // 构建一个Intent
    Intent homeIntent = null;
    ActivityInfo aInfo = null;
    if (displayId == DEFAULT_DISPLAY) {
        // 如果DisplayID是默认的Display(一般是主屏)
        // 调用ActivityTaskManagerService的getHomeIntent,拿到用来启动Home的Intent
        homeIntent = mService.getHomeIntent();
        // 查找当前系统里包含 android.intent.category.HOME的Activity。
        // 择优选择使用哪个Activity
        aInfo = resolveHomeActivity(userId, homeIntent);
    } else if (shouldPlaceSecondaryHomeOnDisplay(displayId)) {
        // 如果不是默认Display屏幕
        Pair<ActivityInfo, Intent> info = resolveSecondaryHomeActivity(userId, displayId);
        aInfo = info.first;
        homeIntent = info.second;
    }
    if (aInfo == null || homeIntent == null) {
        return false;
    }
    
    // 判断是否运行启动Home
    if (!canStartHomeOnDisplay(aInfo, displayId, allowInstrumenting)) {
        return false;
    }

    // 更新Home Intent
    // Updates the home component of the intent.
    homeIntent.setComponent(new ComponentName(aInfo.applicationInfo.packageName, aInfo.name));
    homeIntent.setFlags(homeIntent.getFlags() | FLAG_ACTIVITY_NEW_TASK);
    // 如果是从HomeKey启动的,添加额外参数、
    // Updates the extra information of the intent.
    if (fromHomeKey) {
        homeIntent.putExtra(WindowManagerPolicy.EXTRA_FROM_HOME_KEY, true);
    }
    // Update the reason for ANR debugging to verify if the user activity is the one that
    // actually launched.
    final String myReason = reason + ":" + userId + ":" + UserHandle.getUserId(
            aInfo.applicationInfo.uid) + ":" + displayId;
    // 启动Home
    mService.getActivityStartController().startHomeActivity(homeIntent, aInfo, myReason,
            displayId);
    return true;
}

  startHomeOnDisplay函数中查询当前系统中包含 android.intent.category.HOME信息的Activity(resolveHomeActivity),如果找到了多个Activity则选择高优先级的。根据查找的Activity信息构建Intent,使用ActivityTaskManagerService的ActivityStartController启动Home对应的Activity。
  getHomeIntent函数在ActivityTaskManagerService中实现。

// frameworks/base/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
Intent getHomeIntent() {
        // String mTopAction = Intent.ACTION_MAIN;
    Intent intent = new Intent(mTopAction, mTopData != null ? Uri.parse(mTopData) : null);
    intent.setComponent(mTopComponent);
    intent.addFlags(Intent.FLAG_DEBUG_TRIAGED_MISSING);
    if (mFactoryTest != FactoryTest.FACTORY_TEST_LOW_LEVEL) {
            // 非FactoryTest模式下走这里。
            // android.intent.category.HOME
        intent.addCategory(Intent.CATEGORY_HOME);
    }
    return intent;
}

  resolveHomeActivity函数用于查找包含android.intent.category.HOME信息的Activity。实现上是通过PMS完成的。

// frameworks/base/services/core/java/com/android/server/wm/RootActivityContainer.java
/**
 * This resolves the home activity info.
 * @return the home activity info if any.
 */
@VisibleForTesting
ActivityInfo resolveHomeActivity(int userId, Intent homeIntent) {
        final ComponentName comp = homeIntent.getComponent();
        try {
                if (comp != null) {
                        // Factory test.
                } else {
                        final String resolvedType =
                                        homeIntent.resolveTypeIfNeeded(mService.mContext.getContentResolver());
                        // 调用PMS查找信息
                        final ResolveInfo info = AppGlobals.getPackageManager()
                                        .resolveIntent(homeIntent, resolvedType, flags, userId);
                        if (info != null) {
                                aInfo = info.activityInfo;
                        }
                }
        } catch (RemoteException e) {
                // ignore
        }

        aInfo = new ActivityInfo(aInfo);
        aInfo.applicationInfo = mService.getAppInfoForUser(aInfo.applicationInfo, userId);
        return aInfo;
}

  当找到所需信息后,调用ActivityStartController的startHomeActivity启动Home。该接口与AMS的startActivity和startActivityAsUser实现上基本原理一样,都是通过Intent启动Activity(fork一个进程出来)。

// frameworks/base/services/core/java/com/android/server/wm/ActivityStartController.java
void startHomeActivity(Intent intent, ActivityInfo aInfo, String reason, int displayId) {
        final ActivityOptions options = ActivityOptions.makeBasic();
        options.setLaunchWindowingMode(WINDOWING_MODE_FULLSCREEN);
        if (!ActivityRecord.isResolverActivity(aInfo.name)) {
                // The resolver activity shouldn't be put in home stack because when the foreground is
                // standard type activity, the resolver activity should be put on the top of current
                // foreground instead of bring home stack to front.
                options.setLaunchActivityType(ACTIVITY_TYPE_HOME);
        }
        options.setLaunchDisplayId(displayId);
        // 启动Activity
        mLastHomeActivityStartResult = obtainStarter(intent, "startHomeActivity: " + reason)
                        .setOutActivity(tmpOutRecord)
                        .setCallingUid(0)
                        .setActivityInfo(aInfo)
                        .setActivityOptions(options.toBundle())
                        .execute();
        mLastHomeActivityStartRecord = tmpOutRecord[0];
        final ActivityDisplay display =
                        mService.mRootActivityContainer.getActivityDisplay(displayId);
        final ActivityStack homeStack = display != null ? display.getHomeStack() : null;
        if (homeStack != null && homeStack.mInResumeTopActivity) {
                // If we are in resume section already, home activity will be initialized, but not
                // resumed (to avoid recursive resume) and will stay that way until something pokes it
                // again. We need to schedule another resume.
                mSupervisor.scheduleResumeTopActivities();
        }
}

三、短压Home键启动Launcher

3.1、短压Home键启动Launcher流程图

在这里插入图片描述

3.2、短压Home键启动Launcher源码分析

  短压与长按区分,点一下Home键就属于短压。短压Home键后,Android会启动Home。

// frameworks/base/services/core/java/com/android/server/input/InputManagerService.java

// Native callback.
private long interceptKeyBeforeDispatching(IBinder focus, KeyEvent event, int policyFlags) {
        // native层的 inputservice,通过这个接口上报回调
    return mWindowManagerCallbacks.interceptKeyBeforeDispatching(focus, event, policyFlags);
}
// frameworks/base/services/core/java/com/android/server/wm/InputManagerCallback.java
/**
Provides an opportunity for the window manager policy to process a key before
ordinary dispatch.
*/
@Override
public long interceptKeyBeforeDispatching(IBinder focus, KeyEvent event, int policyFlags) {
         WindowState windowState = mService.windowForClientLocked(null, focus, false);
         return mService.mPolicy.interceptKeyBeforeDispatching(windowState, event, policyFlags);
}

  mService是WindowManagerService类型,WindowManagerService中的mPolicy是PhoneWindowManager。PhoneWindowManager作为WMS的Policy配置文件,专门用来处理与UI行为有关的事件。PhoneWindowManager会拦截HomeKey事件进行相应处理后选择不再派发Home(PhoneWindowManager处理完就不需要其他人处理了),或者继续派发HomeKey给当前焦点View。

// frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java
private long interceptKeyBeforeDispatchingInner(WindowState win, KeyEvent event,
            int policyFlags) {
    final boolean keyguardOn = keyguardOn();
    final int keyCode = event.getKeyCode();
    final int repeatCount = event.getRepeatCount();
    final int metaState = event.getMetaState();
    final int flags = event.getFlags();
    final boolean down = event.getAction() == KeyEvent.ACTION_DOWN;
    final boolean canceled = event.isCanceled();
    final int displayId = event.getDisplayId();

    // First we always handle the home key here, so applications
    // can never break it, although if keyguard is on, we do let
    // it handle it, because that gives us the correct 5 second
    // timeout.
    if (keyCode == KeyEvent.KEYCODE_HOME) {
            // 处理HomeKey
            DisplayHomeButtonHandler handler = mDisplayHomeButtonHandlers.get(displayId);
            if (handler == null) {
                    handler = new DisplayHomeButtonHandler(displayId);
                    mDisplayHomeButtonHandlers.put(displayId, handler);
            }
            return handler.handleHomeButton(win, event);
    } else if (keyCode == KeyEvent.KEYCODE_MENU) {
    // 省略
    }
}

/** A handler to handle home keys per display */
private class DisplayHomeButtonHandler {
    int handleHomeButton(WindowState win, KeyEvent event) {
        final boolean keyguardOn = keyguardOn();
        final int repeatCount = event.getRepeatCount();
        final boolean down = event.getAction() == KeyEvent.ACTION_DOWN;
        final boolean canceled = event.isCanceled();
        // If we have released the home key, and didn't do anything else
        // while it was pressed, then it is time to go home!
        if (!down) {
                // 省略
                // Post to main thread to avoid blocking input pipeline.
                // 处理短压Home
                mHandler.post(() -> handleShortPressOnHome(mDisplayId));
                return -1;
        }
        // 省略
        return -1;
    }
}

private void handleShortPressOnHome(int displayId) {
    // Turn on the connected TV and switch HDMI input if we're a HDMI playback device.
    final HdmiControl hdmiControl = getHdmiControl();
    if (hdmiControl != null) {
            hdmiControl.turnOnTv();
    }

    // If there's a dream running then use home to escape the dream
    // but don't actually go home.
    if (mDreamManagerInternal != null && mDreamManagerInternal.isDreaming()) {
            mDreamManagerInternal.stopDream(false /*immediate*/);
            return;
    }

    // 启动Home
    // Go home!
    launchHomeFromHotKey(displayId);
}

  PhoneWindowManager针对每个Display创建一个DisplayHomeButtonHandler ,通过它处理HomeKey。在启动Home期间如果开始了dream模式(类似于屏保),会先退出dream。最后调用launchHomeFromHotKey来启动Home,后续流程基本上与Home开机启动一致了。

四、Launcher异常崩溃后的自启动

4.1、Launcher异常崩溃后的自启动流程图

在这里插入图片描述

4.2、Launcher异常崩溃后的自启动源码分析

  Launcher意外退出(比如崩溃了)时,会触发AMS的forceStopPackage。AMS会再次将Home拉起。

//frameworks/base/services/core/java/com/android/server/am/ActivityManagerService.java
@Override
public void forceStopPackage(final String packageName, int userId) {
    try {
        IPackageManager pm = AppGlobals.getPackageManager();
        synchronized(this) {
            int[] users = userId == UserHandle.USER_ALL
                            ? mUserController.getUsers() : new int[] { userId };
            for (int user : users) {
                if (mUserController.isUserRunning(user, 0)) {
                    // 对每个运行的User,停掉 packageName对应的应用
                    forceStopPackageLocked(packageName, pkgUid, "from pid " + callingPid);
                    finishForceStopPackageLocked(packageName, pkgUid);
                }
            }
        }
    } finally {
        Binder.restoreCallingIdentity(callingId);
    }
}

  forceStopPackageLocked函数中,会先Kill掉应用对应的进程。然后 resume focused app,在resume的过程中会拉起Home。

//frameworks/base/services/core/java/com/android/server/am/ActivityManagerService.java
@GuardedBy("this")
final boolean forceStopPackageLocked(String packageName, int appId,
        boolean callerWillRestart, boolean purgeCache, boolean doit,
        boolean evenPersistent, boolean uninstalling, int userId, String reason) {
    // kill进程
    boolean didSomething = mProcessList.killPackageProcessesLocked(packageName, appId, userId,
    ProcessList.INVALID_ADJ, callerWillRestart, true /* allowRestart /, doit,
*                        evenPersistent, true /* setRemoved */,
    packageName == null ? ("stop user " + userId) : ("stop " + packageName));

    if (doit) {
        if (purgeCache && packageName != null) {
            AttributeCache ac = AttributeCache.instance();
            if (ac != null) {
                    ac.removePackage(packageName);
            }
        }
        if (mBooted) {
            // resume focused app
            // 通过这个函数重新拉起Home
            mAtmInternal.resumeTopActivities(true /* scheduleIdle */);
        }
    }

    return didSomething;
}

  调用ActivityTaskManagerServiced的resumeTopActivities函数。在 Home崩溃的情况下,调用这个函数,可以保证Home重新被拉起(这个函数最终会调用到RootActivityContainer 的resumeHomeActivity函数。感兴趣的可以继续顺着代码往下看)

//frameworks/base/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
@Override
public void resumeTopActivities(boolean scheduleIdle) {
    synchronized (mGlobalLock) {
        mRootActivityContainer.resumeFocusedStacksTopActivities();
        if (scheduleIdle) {
            mStackSupervisor.scheduleIdleLocked();
        }
    }
}
// frameworks/base/services/core/java/com/android/server/wm/RootActivityContainer.java
boolean resumeFocusedStacksTopActivities(
            ActivityStack targetStack, ActivityRecord target, ActivityOptions targetOptions) {
    for (int displayNdx = mActivityDisplays.size() - 1; displayNdx >= 0; --displayNdx) {
        // 省略
        if (!resumedOnDisplay) {
            // In cases when there are no valid activities (e.g. device just booted or launcher
            // crashed) it's possible that nothing was resumed on a display. Requesting resume
            // of top activity in focused stack explicitly will make sure that at least home
            // activity is started and resumed, and no recursion occurs.
            final ActivityStack focusedStack = display.getFocusedStack();
            if (focusedStack != null) {
                    focusedStack.resumeTopActivityUncheckedLocked(target, targetOptions);
            }
        }
    }

    return result;
}
  • 24
    点赞
  • 20
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: Android Launcher是Android系统中的一个应用程序,它是用户与设备交互的主要界面。它提供了桌面、应用程序列表、小部件等功能,用户可以通过它来启动应用程序、查看通知、管理设备等。 Android Launcher的源码分析主要包括以下几个方面: 1. 桌面布局:Android Launcher的桌面布局是通过GridView实现的,它可以显示应用程序图标和小部件。在源码中,可以看到GridView的相关代码,包括布局、适配器等。 2. 应用程序列表:Android Launcher的应用程序列表是通过ListView实现的,它可以显示所有安装的应用程序。在源码中,可以看到ListView的相关代码,包括布局、适配器等。 3. 搜索功能:Android Launcher提供了搜索功能,用户可以通过输入关键字来搜索应用程序、联系人等。在源码中,可以看到搜索框的相关代码,包括布局、事件处理等。 4. 桌面小部件:Android Launcher支持桌面小部件,用户可以在桌面上添加各种小部件,如天气、时钟、日历等。在源码中,可以看到小部件的相关代码,包括布局、事件处理等。 5. 动画效果:Android Launcher提供了各种动画效果,如应用程序图标的放大缩小、桌面的滑动等。在源码中,可以看到动画效果的相关代码,包括属性动画、插值器等。 总之,Android Launcher的源码分析涉及到很多方面,需要深入研究才能掌握。 ### 回答2: Android launcher是一个重要的应用程序,它是用户的桌面界面,负责管理应用程序、小部件、壁纸等的展示和操作。在Android开发中,我们可以使用默认的系统Launcher也可以自定义Launcher,下面就来分析一下Android Launcher的源码。 1. Launcher的结构分析 Launcher的展示分为三个层次:桌面、工作区和屏幕。在源码中,它们分别对应着Launcher、Workspace和CellLayout。Launcher类是整个应用程序的外壳,它管理了整个应用程序的生命周期。Workspace管理着桌面上的工作区,它可以管理多个屏幕。而CellLayout则是每个工作区上的单元格容器,用于展示应用程序和小部件的图标。 2. Launcher的主界面 Launcher的主界面一般包括一个搜索栏、一个Dock栏和一个应用程序列表。其中搜索栏和Dock栏是Launcher的核心部分,它们的实现都是需要注意的: 2.1 搜索栏 Launcher的搜索栏是通过SearchView实现的,需要处理SearchView的监听事件和搜索逻辑。其中监听事件可以根据具体需求进行定制,比如支持模糊搜索、联想搜索等。 2.2 Dock栏 Dock栏是一个固定在桌面底部的横向图标栏,它可以管理常用的应用程序和快捷方式。Dock栏的实现需要考虑如下几个问题: - 图标的布局 - 图标的拖动 - 图标的排序 - 图标的管理 3. Workspace实现分析 Workspace是Launcher的核心部分,它基本实现了所有的界面交互逻辑。在Workspace上,用户可以添加、移动、删除应用程序和小部件。Workspace的实现需要考虑如下几个问题: 3.1 桌面上的应用程序和小部件布局 Workspace上的每个屏幕都是通过CellLayout实现的,它负责管理应用程序和小部件的布局和显示。 3.2 图标的拖动和排序 用户可以通过拖动来移动和排序图标,需要考虑如下几个问题: - 拖动的实现逻辑 - 滑动过程的动画效果 - 拖动时的图标缩放效果 3.3 图标的删除和添加 用户可以通过长按图标来触发删除操作,也可以通过添加菜单来添加新的应用程序和小部件。 4. 总结 以上是针对Android Launcher源码分析,这些内容只是基础的使用方法和思路,具体的实现还需要根据自己的需求和场景进行定制和优化。在实现Launcher的时候,需要注意性能问题,尽量避免不必要的计算和操作;同时,还需要考虑到用户的交互体验,保证操作的流畅和直观。 ### 回答3: Android Launcher是Android手机主屏幕上最常见的应用,它提供了一个桌面环境和一些关键功能,如快速访问应用程序、设置壁纸、小部件和通知中心等。本文将对Android Launcher源码进行分析,重点关注Launcher的核心组件:Workspace、Folder、App Drawer和Widget。 首先,Workspace是Launcher中最核心的组件之一,它是桌面上的容器,用于展示应用程序图标和小部件。Workspace是一个基于GridView组件自定义的ViewGroup,用于支持滑动手势和快捷方式的编辑管理。Framework层通过Workspace类读取和更新数据,它通过扩展Adapter来创建UI元素,并通过GridLayoutManager装填与交换元素。 其次,Folder是Launcher用于存储和管理应用程序快捷方式的组件。Folder的UI元素扩展自ViewGroup,可以包含多个应用快捷方式,在Folder中用户可以自由地添加、删除和排序快捷方式。Folder同时提供一个搜索框,用于帮助用户快速搜索自己的应用程序。 其次,App Drawer是Launcher的另一个核心组件,它是一个垂直滚动的列表,用于展示所有的应用程序。App Drawer是按字母排序的,同时可以通过搜索框查找用户需要的特定应用程序。App Drawer实现类似于Workspace,只不过它只横向的有一个方向轴且没有操作修改排序功能。 最后,Widget是一个独特的组件,它是一些非小部件的快捷方式,用户可以将它们放置在桌面上。Widget允许用户在主屏幕上快速访问特定功能或信息,例如天气、电子邮件和日历等。Widget UI元素的设计与Folder和App Drawer不同,它们提供更多信息和控制,通常需要桌面空间大才能放下。 总体而言,Android Launcher的源码分析需要涉及多个关键组件,Workspace、Folder、App Drawer和Widget是其中最重要的几个。这些组件深度整合在Launcher中,可以帮助用户快速访问他们需要的应用程序和信息。因此,熟练掌握这些核心组件的基本实现和逻辑是Android开发者不可或缺的技能之一。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值