Android的应用管理主要是通过PackageManagerService来完成的。PackageManagerService服务负责各种APK包的安装、卸载、优化和查询。
PackageManagerService在启动时会扫描所有的APK文件和Jar包,然后把他们的信息读取出来,保存在内存中,这样系统在运行时就能迅速找到各种应用和组件的信息。扫描过程中如果遇到没有优化的文件,还要执行转换工作,将app文件从dex格式转换为oat格式(Android5.0之前是转换为odex格式)。
启动后,PackageManagerService将提供安装包的信息查询服务以及应用的安装和卸载服务。Android5.x,/data/app目录或者/system/app目录下存放的是以应用名称命名的目录,在这个目录下存放的是apk文件和一个lib目录,lib目录存放的是应用的so文件。
Android中的应用可以简单的分为两大类:系统应用和普通应用。
系统应用是指位于/system/app或者/system/priv-app目录下的应用。priv-app目录中存放的是一些系统底层应用,如setting,systemui等。/system/app存放的则是系统级的应用,如Phone、Contacts等。在PackageManagerService中,所有的system应用包括这两个目录下的应用,而所谓的private应用特指priv-app目录下的应用。
普通应用:用户安装的应用,位于目录/data/app下。普通应用还可以按照在SD卡上,系统应用不可以。
通常情况下,系统应用是不能删除的,但是可以升级。升级的方法是安装一个包名相同,但是具有更高版本号的应用在/data/app目录下。对于系统中的这种升级情况,Android会在/data/system/packages.xml文件中用标签<update-package>记录被覆盖的系统应用的信息。如果在升级过程中,如果出现与原始包名不同的应用,最后会改成原始包名,Android会在packages.xml文件中用标签<rename-package>记录这种改名的情况。
系统目录/data/dalvik-cache下保存的是大部分的apk文件和jar包的odex版本。odex是一种优化过的格式,执行速度比apk文件的dex格式更快。
每个应用都有保存数据的目录,位于/data/data/<包名>/目录下。其中数据目录下常见的两个子目录:shared_prefs目录中保存的是应用的设置文件,database保存的是应用的数据库文件。
一、了解PackageManagerService
在应用中如果使用PackageManagerService服务,通常调用的是Context的getPackageManager()方法,这个方法返回的是PackageManager对象,注意Context是一个抽象类,ContextImpl类继承了Context,方法如下:
[java]
view plain
copy
- @Override
- public PackageManager getPackageManager() {
- if (mPackageManager != null) {
- return mPackageManager;
- }
- IPackageManager pm = ActivityThread.getPackageManager();
- if (pm != null) {
- // Doesn’t matter if we make more than one instance.
- return (mPackageManager = new ApplicationPackageManager(this, pm));
- }
- return null;
- }
从getPackageManager()方法的代码中可以看到它返回的PackageManager对象实际上是一个ApplicationPackageManager对象,这个对象创建时使用了IPackageManager对象作为参数。IPackageManager对象是一个PackageManagerService的引用对象。因此,ApplicationPackageManager对象就是PackageManagerService的代理对象。ApplicationPackageManager类继承自PackageManager类。PackageManager类中定义了应用可以操作PackageManagerService的接口。
PackageManagerService的两个重要成员变量mInstallerService和mInstller与应用安装有密切关系。mInstallerService是类PackageInstallerService的实例对象,一个应用的安装过程比较长,Android5.0中新增加了PackageInstallerService来管理应用的安装过程。另一个成员变量mInstaller是类Installer的实例对象,它也有一个名为mInstaller的成员变量,其类型是InstallerConnection,而InstallerConnection中存在着和Deamon进程Installd通信的Socket命令通道。实际上系统中进行apk文件格式转换、建立数据目录等工作最后都是由installd进程来完成的。这些对象之间的关系如下图所示。
1、理解Packages.xml和Settings类
这里先看一下Settings这个类,这个类用来保存和PackageManagerService相关的一些设置,它所保存的内容在解析应用时会用到。那么Settings中保存的值是从哪里来的?作用又是什么呢?我们先看一下Settings的构造方法,代码如下:
[java]
view plain
copy
- Settings(Context context) {
- this(context, Environment.getDataDirectory());//获取用户数据目录:/data
- }
[java]
view plain
copy
- Settings(Context context, File dataDir) {
- mSystemDir = new File(dataDir, “system”);
- mSystemDir.mkdirs();//在data目录下创建system目录:/data/system
- FileUtils.setPermissions(mSystemDir.toString(),
- FileUtils.S_IRWXU|FileUtils.S_IRWXG
- |FileUtils.S_IROTH|FileUtils.S_IXOTH,
- –1, –1);//设置目录的属性为0775
- mSettingsFilename = new File(mSystemDir, “packages.xml”);//data/system/packages.xml
- mBackupSettingsFilename = new File(mSystemDir, “packages-backup.xml”);
- mPackageListFilename = new File(mSystemDir, “packages.list”);
- FileUtils.setPermissions(mPackageListFilename, 0640, SYSTEM_UID, PACKAGE_INFO_GID);
- // Deprecated: Needed for migration
- mStoppedPackagesFilename = new File(mSystemDir, “packages-stopped.xml”);
- mBackupStoppedPackagesFilename = new File(mSystemDir, “packages-stopped-backup.xml”);
- }
Settings的构造方法会创建data目录下的system目录,这个目录用来保存很多系统文件。主要的工作是创建了5个位于目录/data/system下的File对象,分别是:
- packages.xml:记录系统中所有安装的应用信息,包括基本信息、签名和权限。
- packages-backup.xml:packages.xml文件的备份。
- packages.list:保存普通应用的数据目录和uid等信息。
- packages-stopped.xml:记录系统中被强制停止运行的应用信息。系统在强制停止某个应用时,会讲应用的信息记录到该文件中。
- packages-stopped-backup.xml:pacakges-stopped.xml文件的备份。
这5个文件中packages-backup.xml和packages-stopped-backup.xml是备份文件。当Android对文件packages.xml和packages-stopped.xml写之前,会先把他们备份,如果写文件成功了,再把备份文件删除。如果写的时候出问题了,重启后再需要读取这两个文件时,如果发现备份文件存在,会使用备份文件的内容,因为原文件可能损坏了。
packages.xml是PackageManagerService启动时需要用的文件,先看下文件的内容:
[java]
view plain
copy
- <package name=“com.dianping.v1”
- codePath=“/system/presetapp/BY_3RD_Dianping.apk”
- nativeLibraryPath=“/data/app-lib/BY_3RD_Dianping”
- primaryCpuAbi=“armeabi-v7a”
- flags=“1621572” ft=“14de3458a58” it=“14de3458a58” ut=“14de3458a58”
- version=“711” userId=“10091”>
- <sigs count=“1”>
- <cert index=“5” key=“3082025f308201c8a00……” />
- </sigs>
- <perms>
- <item name=“android.permission.WRITE_SETTINGS” />
- <item name=“android.permission.READ_SMS” />
- <item name=“android.permission.ACCESS_FINE_LOCATION” />
- ……
- </perms>
- <proper-signing-keyset identifier=“9” />
- <signing-keyset identifier=“9” />
- </package>
上面是文件的一个片段,通过标签<package>记录了一个应用的基本信息,签名和申明的权限。
标签<package>中的属性name表示应用的包名,codePath表示apk文件的位置,nativeLibraryPath表示应用的native库的存储路径;flags表示应用的属性,如FLAG_SYSTEM等;it表示应用安装的时间;ut表示应用最后一次修改的时间;version表示应用的版本号;userId表示应用所属的用户ID。
便签<sigs>表示应用的签名,属性count表示标签中包含有多少个证书。cert表示具体的证书的值。
标签<perms>表示应用声明使用的权限,每个子标签<item>代表一项权限。
<package>标签解析后将保存在PackageSetting对象中。系统中实际运行的应用信息会通过标签<package>记录,被升级包覆盖的系统应用不通过<package>标签记录,而是通过<update-packages>标签记录。这两个标签的记录基本一致。这两个标签的应用信息都将保存在PackageSetting对象中。类PackageSetting的继承关系如图。
PackageSetting类继承了PackageSettingBase类,PackageSettingBase类又继承了GrantedPermissions类,应用的基本信息保存在PackageSettingBase类的成员变量中,申明的权限保存在GrantedPremissions类,签名则保持在SharedUserSetting类的成员变量signatures中。
类SharedUserSetting用来描述具有相同sharedUserId的应用信息,它的成员变量packages保存了所有具有相同sharedUserId的应用信息的引用。这些应用的签名是相同的,所以只需在成员变量signatures中保存一份。通过这个对象,Android运行时很容易检索到和某个应用拥有相同sharedUserId的其他应用。
标签<package>所标识的应用的PackageSetting对象都保存在Settings的成员变量mPackages中,标签<update-packages>所标识的系统应用的PackageSetting对象都保存在Settings的成员变量mDisabledSysPackages中,定义如下:
[java]
view plain
copy
- private final ArrayMap<String, PackageSetting> mPackages = new ArrayMap<String, PackageSetting>();
[java]
view plain
copy
- private final ArrayMap<String, PackageSetting> mDisabledSysPackages = new ArrayMap<String, PackageSetting>();
package.xml文件中出了标签<package>、<updated-package>,还有两个标签<cleaning-package>和<renamed-package>。Settings中解析这些标签的代码如下:
[java]
view plain
copy
- if (tagName.equals(“package”)) {
- readPackageLPw(parser);
- } else if (tagName.equals(“permissions”)) {
- readPermissionsLPw(mPermissions, parser);
- } else if (tagName.equals(“updated-package”)) {
- readDisabledSysPackageLPw(parser);
- } else if (tagName.equals(“cleaning-package”)) {
- ……
- addPackageToCleanLPw(new PackageCleanItem(userId, name, andCode));
- }
- } else if (tagName.equals(“renamed-package”)) {
- ……
- mRenamedPackages.put(nname, oname);
标签<cleaning-package>用来记录哪些已经删除,但是数据目录还暂时保留的应用的信息。扫描后生成的对象是PackageCleanItem,放入mSettings的mPackagesToBeCleaned数组中管理。
[java]
view plain
copy
- // Packages that have been uninstalled and still need their external
- // storage data deleted.
- final ArrayList<PackageCleanItem> mPackagesToBeCleaned = new ArrayList<PackageCleanItem>();
标签<renamed-package>记录了系统中改名应用的新旧包名,它记录的信息都保存到mSettings的mRenamedPackaged对象中,定义如下:
[java]
view plain
copy
- final ArrayMap<String, String> mRenamedPackages = new ArrayMap<String, String>();
2、服务的初始化过程
PackageManagerService也是在SystemServer中开始初始化的,代码如下:
[java]
view plain
copy
- mPackageManagerService = PackageManagerService.main(mSystemContext, installer,
- mFactoryTestMode != FactoryTest.FACTORY_TEST_OFF, mOnlyCore);
- ……
- try {
- mPackageManagerService.performBootDexOpt();
- } catch (Throwable e) {
- reportWtf(“performing boot dexopt”, e);
- }
- ……
- try {
- mPackageManagerService.systemReady();
- } catch (Throwable e) {
- reportWtf(“making Package Manager Service ready”, e);
- }
SystemServer对PMS的初始化主要是通过上面代码完成的。首先看下PMS对象的创建,main()函数的代码如下:
[java]
view plain
copy
- public static final PackageManagerService main(Context context, Installer installer,
- boolean factoryTest, boolean onlyCore) {
- PackageManagerService m = new PackageManagerService(context, installer,
- factoryTest, onlyCore);
- ServiceManager.addService(“package”, m);
- return m;
- }
main函数比较简单,只是创建PMS对象并在ServiceManager中注册。
PMS的构造方法主要完成两件事,第一是把系统中的apk文件和jar包从dex格式转换成ART的oat格式;第二是扫描系统中所有安装的应用,把他们的信息提取出来。
[java]
view plain
copy
- public PackageManagerService(Context context, Installer installer,
- boolean factoryTest, boolean onlyCore) {
- EventLog.writeEvent(EventLogTags.BOOT_PROGRESS_PMS_START,
- SystemClock.uptimeMillis());
- if (mSdkVersion <= 0) {//检查SDK版本
- Slog.w(TAG, “**** ro.build.version.sdk not set!”);
- }
- Object bridgeObject;
- try {
- /*
- * load and create the security bridge:com.android.services.SecurityBridge.core.PackageManagerSB
- */
- bridgeObject = getClass().getClassLoader().loadClass(SECURITY_BRIDGE_NAME).newInstance();
- mSecurityBridge = (PackageManagerMonitor)bridgeObject;
- } catch (Exception e){
- Slog.w(TAG, “No security bridge jar found, using default”);
- mSecurityBridge = new PackageManagerMonitor();
- }
- mContext = context;
- mFactoryTest = factoryTest;//设置运行模式。工厂模式是一种测试模式
- mOnlyCore = onlyCore;//onlyCore为true表示只处理系统的应用,通常为false
- mLazyDexOpt = “eng”.equals(SystemProperties.get(“ro.build.type”));
- mMetrics = new DisplayMetrics();//DisplayMetrics对象存储屏幕的显示信息
- mSettings = new Settings(context);//新创建一个settings对象
- mSettings.addSharedUserLPw(“android.uid.system”, Process.SYSTEM_UID,
- ApplicationInfo.FLAG_SYSTEM|ApplicationInfo.FLAG_PRIVILEGED);
- mSettings.addSharedUserLPw(“android.uid.phone”, RADIO_UID,
- ApplicationInfo.FLAG_SYSTEM|ApplicationInfo.FLAG_PRIVILEGED);
- mSettings.addSharedUserLPw(“android.uid.log”, LOG_UID,
- ApplicationInfo.FLAG_SYSTEM|ApplicationInfo.FLAG_PRIVILEGED);
- mSettings.addSharedUserLPw(“android.uid.nfc”, NFC_UID,
- ApplicationInfo.FLAG_SYSTEM|ApplicationInfo.FLAG_PRIVILEGED);
- mSettings.addSharedUserLPw(“android.uid.bluetooth”, BLUETOOTH_UID,
- ApplicationInfo.FLAG_SYSTEM|ApplicationInfo.FLAG_PRIVILEGED);
- mSettings.addSharedUserLPw(“android.uid.shell”, SHELL_UID,
- ApplicationInfo.FLAG_SYSTEM|ApplicationInfo.FLAG_PRIVILEGED);
- //上面添加SharedUserSetting对象到mSettings中,sharedUserId属性相同的包可以运行在同一个进程中,或者相互读取资源。这里添加了6中系统的uid:system、phone、log、nfc、Bluetooth、shell。
- // TODO: add a property to control this?
- long dexOptLRUThresholdInMinutes;
- if (mLazyDexOpt) {
- dexOptLRUThresholdInMinutes = 30; // only last 30 minutes of apps for eng builds.
- } else {
- dexOptLRUThresholdInMinutes = 7 * 24 * 60; // apps used in the 7 days for users.
- }
- mDexOptLRUThresholdInMills = dexOptLRUThresholdInMinutes * 60 * 1000;
- String separateProcesses = SystemProperties.get(“debug.separate_processes”);
- if (separateProcesses != null && separateProcesses.length() > 0) {
- if (“*”.equals(separateProcesses)) {
- mDefParseFlags = PackageParser.PARSE_IGNORE_PROCESSES;
- mSeparateProcesses = null;
- Slog.w(TAG, “Running with debug.separate_processes: * (ALL)”);
- } else {
- mDefParseFlags = 0;
- mSeparateProcesses = separateProcesses.split(“,”);
- Slog.w(TAG, “Running with debug.separate_processes: “
- + separateProcesses);
- }
- } else {
- mDefParseFlags = 0;
- mSeparateProcesses = null;
- }
- mInstaller = installer;//应用安装器
- getDefaultDisplayMetrics(context, mMetrics);//设置DisplayMetrics对象
- //读取系统配置来初始化mGlobalGids、mSystemPermissions、mAvailableFeatures
- SystemConfig systemConfig = SystemConfig.getInstance();
- mGlobalGids = systemConfig.getGlobalGids();
- mSystemPermissions = systemConfig.getSystemPermissions();//保存在对象内部的变量列表
- mAvailableFeatures = systemConfig.getAvailableFeatures();
- synchronized (mInstallLock) {
- // writer
- synchronized (mPackages) {
- mHandlerThread = new ServiceThread(TAG,//创建用来处理消息的线程,并加入到Watchdog的监控中
- Process.THREAD_PRIORITY_BACKGROUND, true /*allowIo*/);
- mHandlerThread.start();
- mHandler = new PackageHandler(mHandlerThread.getLooper());
- Watchdog.getInstance().addThread(mHandler, WATCHDOG_TIMEOUT);
- //为/data目录下的子目录生成文件对象
- File dataDir = Environment.getDataDirectory();
- mAppDataDir = new File(dataDir, “data”);///data/data存放应用数据的目录
- mAppInstallDir = new File(dataDir, “app”);///data/app存放安装的应用
- mAppLib32InstallDir = new File(dataDir, “app-lib”);//存放应用自带的native库
- mAsecInternalPath = new File(dataDir, “app-asec”).getPath();
- mUserAppDataDir = new File(dataDir, “user”);//存放用户的数据文件
- mDrmAppPrivateInstallDir = new File(dataDir, “app-private”);//存放drm保护的应用
- sUserManager = new UserManagerService(context, this,
- mInstallLock, mPackages);//创建用户管理服务
- // Propagate permission configuration in to package manager.通过systemConfig得到系统中定义的permission。这些permission保存在/etc/permissions目录下的文件中。
- ArrayMap<String, SystemConfig.PermissionEntry> permConfig
- = systemConfig.getPermissions();
- for (int i=0; i<permConfig.size(); i++) {
- SystemConfig.PermissionEntry perm = permConfig.valueAt(i);
- BasePermission bp = mSettings.mPermissions.get(perm.name);
- if (bp == null) {
- bp = new BasePermission(perm.name, “android”, BasePermission.TYPE_BUILTIN);
- mSettings.mPermissions.put(perm.name, bp);
- }
- if (perm.gids != null) {
- bp.gids = appendInts(bp.gids, perm.gids);
- }
- }
- //通过systemConfig得到系统中的共享库列表
- ArrayMap<String, String> libConfig = systemConfig.getSharedLibraries();
- for (int i=0; i<libConfig.size(); i++) {
- mSharedLibraries.put(libConfig.keyAt(i),
- new SharedLibraryEntry(libConfig.valueAt(i), null));
- }
- //打开SELinux的policy文件
- mFoundPolicyFile = SELinuxMMAC.readInstallPolicy();
- //读取packages.xml文件的内容,解析后插到mSettings的mPackages等变量中
- mRestoredSettings = mSettings.readLPw(this, sUserManager.getUsers(false),
- mSdkVersion, mOnlyCore);
- //设置模块来代替framework-res.apk中的缺省ResolverActivity
- String customResolverActivity = Resources.getSystem().getString(
- R.string.config_customResolverActivity);
- if (TextUtils.isEmpty(customResolverActivity)) {
- customResolverActivity = null;
- } else {
- mCustomResolverComponentName = ComponentName.unflattenFromString(
- customResolverActivity);
- }
- long startTime = SystemClock.uptimeMillis();//记录开始扫描的时间
- EventLog.writeEvent(EventLogTags.BOOT_PROGRESS_PMS_SYSTEM_SCAN_START,
- startTime);
- // Set flag to monitor and not change apk file paths when
- // scanning install directories.设置扫描模式,以监测和扫描安装目录时不会改变apk文件路径
- final int scanFlags = SCAN_NO_PATHS | SCAN_DEFER_DEX | SCAN_BOOTING;
- //定义已经优化的文件集合,已经优化过的文件或不需要优化的文件将加到这个集合中
- final ArraySet<String> alreadyDexOpted = new ArraySet<String>();
- /**
- * Add everything in the in the boot class path to the
- * list of process files because dexopt will have been run
- * if necessary during zygote startup.
- */
- final String bootClassPath = System.getenv(“BOOTCLASSPATH”);
- final String systemServerClassPath = System.getenv(“SYSTEMSERVERCLASSPATH”);
- //把环境变量BOOTCALSSPATH中定义的包加入到已优化的集合alreadyDexOpted
- if (bootClassPath != null) {
- String[] bootClassPathElements = splitString(bootClassPath, ‘:’);
- for (String element : bootClassPathElements) {
- alreadyDexOpted.add(element);
- }
- } else {
- Slog.w(TAG, “No BOOTCLASSPATH found!”);
- }
[java]
view plain
copy
- if (systemServerClassPath != null) {
- String[] systemServerClassPathElements = splitString(systemServerClassPath, ‘:’);
- for (String element : systemServerClassPathElements) {
- alreadyDexOpted.add(element);
- }
- } else {
- Slog.w(TAG, “No SYSTEMSERVERCLASSPATH found!”);
- }
- final List<String> allInstructionSets = getAllInstructionSets();
- final String[] dexCodeInstructionSets =
- getDexCodeInstructionSets(allInstructionSets.toArray(new String[allInstructionSets.size()]));
- /**
- * Ensure all external libraries have had dexopt run on them.
- */
- if (mSharedLibraries.size() > 0) {
- // NOTE: For now, we’re compiling these system “shared libraries”
- // (and framework jars) into all available architectures. It’s possible
- // to compile them only when we come across an app that uses them (there’s
- // already logic for that in scanPackageLI) but that adds some complexity.
- for (String dexCodeInstructionSet : dexCodeInstructionSets) {
- for (SharedLibraryEntry libEntry : mSharedLibraries.values()) {
- final String lib = libEntry.path;
- if (lib == null) {
- continue;
- }
- try {
- byte dexoptRequired = DexFile.isDexOptNeededInternal(lib, null,
- dexCodeInstructionSet,
- false);
- if (dexoptRequired != DexFile.UP_TO_DATE) {
- alreadyDexOpted.add(lib);
- // The list of “shared libraries” we have at this point is
- if (dexoptRequired == DexFile.DEXOPT_NEEDED) {
- mInstaller.dexopt(lib, Process.SYSTEM_UID, true, dexCodeInstructionSet);
- } else {
- mInstaller.patchoat(lib, Process.SYSTEM_UID, true, dexCodeInstructionSet);
- }
- }
- } catch (FileNotFoundException e) {
- Slog.w(TAG, “Library not found: “ + lib);
- } catch (IOException e) {
- Slog.w(TAG, “Cannot dexopt “ + lib + “; is it an APK or JAR? “
- + e.getMessage());
- }
- }
- }
- }
- File frameworkDir = new File(Environment.getRootDirectory(), “framework”);
- // Gross hack for now: we know this file doesn’t contain any
- // code, so don’t dexopt it to avoid the resulting log spew.
- alreadyDexOpted.add(frameworkDir.getPath() + “/framework-res.apk”);
- // Gross hack for now: we know this file is only part of
- // the boot class path for art, so don’t dexopt it to
- // avoid the resulting log spew.
- alreadyDexOpted.add(frameworkDir.getPath() + “/core-libart.jar”);
- /**
- * And there are a number of commands implemented in Java, which
- * we currently need to do the dexopt on so that they can be
- * run from a non-root shell.
- */
- String[] frameworkFiles = frameworkDir.list();
- if (frameworkFiles != null) {
- // TODO: We could compile these only for the most preferred ABI. We should
- // first double check that the dex files for these commands are not referenced
- // by other system apps.
- for (String dexCodeInstructionSet : dexCodeInstructionSets) {
- for (int i=0; i<frameworkFiles.length; i++) {
- File libPath = new File(frameworkDir, frameworkFiles[i]);
- String path = libPath.getPath();
- // Skip the file if we already did it.
- if (alreadyDexOpted.contains(path)) {
- continue;
- }
- // Skip the file if it is not a type we want to dexopt.
- if (!path.endsWith(“.apk”) && !path.endsWith(“.jar”)) {
- continue;
- }
- try {
- byte dexoptRequired = DexFile.isDexOptNeededInternal(path, null,
- dexCodeInstructionSet,
- false);
- if (dexoptRequired == DexFile.DEXOPT_NEEDED) {
- mInstaller.dexopt(path, Process.SYSTEM_UID, true, dexCodeInstructionSet);
- } else if (dexoptRequired == DexFile.PATCHOAT_NEEDED) {
- mInstaller.patchoat(path, Process.SYSTEM_UID, true, dexCodeInstructionSet);
- }
- } catch (FileNotFoundException e) {
- Slog.w(TAG, “Jar not found: “ + path);
- } catch (IOException e) {
- Slog.w(TAG, “Exception reading jar: “ + path, e);
- }
- }
- }
- }
[java]
view plain
copy
- // Collect vendor overlay packages.
- // (Do this before scanning any apps.)
- // For security and version matching reason, only consider
- // overlay packages if they reside in VENDOR_OVERLAY_DIR.
- File vendorOverlayDir = new File(VENDOR_OVERLAY_DIR);
- scanDirLI(vendorOverlayDir, PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR, scanFlags | SCAN_TRUSTED_OVERLAY, 0);
- // Find base frameworks (resource packages without code).
- scanDirLI(frameworkDir, PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR
- | PackageParser.PARSE_IS_PRIVILEGED,
- scanFlags | SCAN_NO_DEX, 0);
- // Collected privileged system packages./system/priv-app
- final File privilegedAppDir = new File(Environment.getRootDirectory(), “priv-app”);
- scanDirLI(privilegedAppDir, PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR
- | PackageParser.PARSE_IS_PRIVILEGED, scanFlags, 0);
- // Collect ordinary system packages./system/app
- final File systemAppDir = new File(Environment.getRootDirectory(), “app”);
- scanDirLI(systemAppDir, PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR, scanFlags, 0);
- // Collect all vendor packages.
- File vendorAppDir = new File(“/vendor/app”);
- try {
- vendorAppDir = vendorAppDir.getCanonicalFile();
- } catch (IOException e) {
- // failed to look up canonical path, continue with original one
- }
- scanDirLI(vendorAppDir, PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR, scanFlags, 0);
- // Collect all OEM packages.
- final File oemAppDir = new File(Environment.getOemDirectory(), “app”);
- scanDirLI(oemAppDir, PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR, scanFlags, 0);
- if (DEBUG_UPGRADE) Log.v(TAG, “Running installd update commands”);
- mInstaller.moveFiles();
- // Prune any system packages that no longer exist.
- final List<String> possiblyDeletedUpdatedSystemApps = new ArrayList<String>();
- final ArrayMap<String, File> expectingBetter = new ArrayMap<>();
- if (!mOnlyCore) {
- Iterator<PackageSetting> psit = mSettings.mPackages.values().iterator();
- while (psit.hasNext()) {
- PackageSetting ps = psit.next();
- /*
- * If this is not a system app, it can’t be a
- * disable system app.
- */
- if ((ps.pkgFlags & ApplicationInfo.FLAG_SYSTEM) == 0) {
- continue;
- }
- /*
- * If the package is scanned, it’s not erased.
- */
- final PackageParser.Package scannedPkg = mPackages.get(ps.name);
- if (scannedPkg != null) {
- /*
- * If the system app is both scanned and in the
- * disabled packages list, then it must have been
- * added via OTA. Remove it from the currently
- * scanned package so the previously user-installed
- * application can be scanned.
- */
- if (mSettings.isDisabledSystemPackageLPr(ps.name)) {
- logCriticalInfo(Log.WARN, “Expecting better updated system app for “
- + ps.name + “; removing system app. Last known codePath=”
- + ps.codePathString + “, installStatus=” + ps.installStatus
- + “, versionCode=” + ps.versionCode + “; scanned versionCode=”
- + scannedPkg.mVersionCode);
- removePackageLI(ps, true);
- expectingBetter.put(ps.name, ps.codePath);
- }
- continue;
- }
- if (!mSettings.isDisabledSystemPackageLPr(ps.name)) {
- psit.remove();
- logCriticalInfo(Log.WARN, “System package “ + ps.name
- + ” no longer exists; wiping its data”);
- removeDataDirsLI(ps.name);
- } else {
- final PackageSetting disabledPs = mSettings.getDisabledSystemPkgLPr(ps.name);
- if (disabledPs.codePath == null || !disabledPs.codePath.exists()) {
- possiblyDeletedUpdatedSystemApps.add(ps.name);
- }
- }
- }
- }
- //look for any incomplete package installations
- ArrayList<PackageSetting> deletePkgsList = mSettings.getListOfIncompleteInstallPackagesLPr();
- //clean up list
- for(int i = 0; i < deletePkgsList.size(); i++) {
- //clean up here
- cleanupInstallFailedPackage(deletePkgsList.get(i));
- }
- //delete tmp files
- deleteTempPackageFiles();
- // Remove any shared userIDs that have no associated packages
- mSettings.pruneSharedUsersLPw();
- if (!mOnlyCore) {
- EventLog.writeEvent(EventLogTags.BOOT_PROGRESS_PMS_DATA_SCAN_START,
- SystemClock.uptimeMillis());
- scanDirLI(mAppInstallDir, 0, scanFlags | SCAN_REQUIRE_KNOWN, 0);
- scanDirLI(mDrmAppPrivateInstallDir, PackageParser.PARSE_FORWARD_LOCK,
- scanFlags | SCAN_REQUIRE_KNOWN, 0);
- /**
- * Remove disable package settings for any updated system
- * apps that were removed via an OTA. If they’re not a
- * previously-updated app, remove them completely.
- * Otherwise, just revoke their system-level permissions.
- */
- for (String deletedAppName : possiblyDeletedUpdatedSystemApps) {
- PackageParser.Package deletedPkg = mPackages.get(deletedAppName);
- mSettings.removeDisabledSystemPackageLPw(deletedAppName);
- String msg;
- if (deletedPkg == null) {
- msg = “Updated system package “ + deletedAppName
- + ” no longer exists; wiping its data”;
- removeDataDirsLI(deletedAppName);
- } else {
- msg = “Updated system app + “ + deletedAppName
- + ” no longer present; removing system privileges for “
- + deletedAppName;
- deletedPkg.applicationInfo.flags &= ~ApplicationInfo.FLAG_SYSTEM;
- PackageSetting deletedPs = mSettings.mPackages.get(deletedAppName);
- deletedPs.pkgFlags &= ~ApplicationInfo.FLAG_SYSTEM;
- }
- logCriticalInfo(Log.WARN, msg);
- }
- /**
- * Make sure all system apps that we expected to appear on
- * the userdata partition actually showed up. If they never
- * appeared, crawl back and revive the system version.
- */
- for (int i = 0; i < expectingBetter.size(); i++) {
- final String packageName = expectingBetter.keyAt(i);
- if (!mPackages.containsKey(packageName)) {
- final File scanFile = expectingBetter.valueAt(i);
- logCriticalInfo(Log.WARN, “Expected better “ + packageName
- + ” but never showed up; reverting to system”);
- final int reparseFlags;
- if (FileUtils.contains(privilegedAppDir, scanFile)) {
- reparseFlags = PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR
- | PackageParser.PARSE_IS_PRIVILEGED;
- } else if (FileUtils.contains(systemAppDir, scanFile)) {
- reparseFlags = PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR;
- } else if (FileUtils.contains(vendorAppDir, scanFile)) {
- reparseFlags = PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR;
- } else if (FileUtils.contains(oemAppDir, scanFile)) {
- reparseFlags = PackageParser.PARSE_IS_SYSTEM
- | PackageParser.PARSE_IS_SYSTEM_DIR;
- } else {
- Slog.e(TAG, “Ignoring unexpected fallback path “ + scanFile);
- continue;
- }
- mSettings.enableSystemPackageLPw(packageName);
- try {
- scanPackageLI(scanFile, reparseFlags, scanFlags, 0, null);
- } catch (PackageManagerException e) {
- Slog.e(TAG, “Failed to parse original system package: “
- + e.getMessage());
- }
- }
- }
- }
- // Now that we know all of the shared libraries, update all clients to have
- // the correct library paths.更新所有应用的动态库路径
- updateAllSharedLibrariesLPw();
- for (SharedUserSetting setting : mSettings.getAllSharedUsersLPw()) {
- // NOTE: We ignore potential failures here during a system scan (like
- // the rest of the commands above) because there’s precious little we
- // can do about it. A settings error is reported, though.
- adjustCpuAbisForSharedUserLPw(setting.packages, null /* scanned package */,
- false /* force dexopt */, false /* defer dexopt */);
- }
- // Now that we know all the packages we are keeping,
- // read and update their last usage times.
- mPackageUsage.readLP();
- EventLog.writeEvent(EventLogTags.BOOT_PROGRESS_PMS_SCAN_END,
- SystemClock.uptimeMillis());
- Slog.i(TAG, “Time to scan packages: “
- + ((SystemClock.uptimeMillis()-startTime)/1000f)
- + ” seconds”);
- // If the platform SDK has changed since the last time we booted,
- // we need to re-grant app permission to catch any new ones that
- // appear. This is really a hack, and means that apps can in some
- // cases get permissions that the user didn’t initially explicitly
- // allow… it would be nice to have some better way to handle
- // this situation.如果平台的SDK版本和上次启动时相比发生了变化,可能permission的定义也改变了,因此需要重新赋予应用权限
- final boolean regrantPermissions = mSettings.mInternalSdkPlatform
- != mSdkVersion;
- if (regrantPermissions) Slog.i(TAG, “Platform changed from “
- + mSettings.mInternalSdkPlatform + ” to “ + mSdkVersion
- + “; regranting permissions for internal storage”);
- mSettings.mInternalSdkPlatform = mSdkVersion;
- updatePermissionsLPw(null, null, UPDATE_PERMISSIONS_ALL
- | (regrantPermissions
- ? (UPDATE_PERMISSIONS_REPLACE_PKG|UPDATE_PERMISSIONS_REPLACE_ALL)
- : 0));
- // If this is the first boot, and it is a normal boot, then
- // we need to initialize the default preferred apps.
- if (!mRestoredSettings && !onlyCore) {
- mSettings.readDefaultPreferredAppsLPw(this, 0);
- }
- // If this is first boot after an OTA, and a normal boot, then
- // we need to clear code cache directories.如果这是执行OTA后的第一次启动,需要清除cache
- mIsUpgrade = !Build.FINGERPRINT.equals(mSettings.mFingerprint);
- if (mIsUpgrade && !onlyCore) {
- Slog.i(TAG, “Build fingerprint changed; clearing code caches”);
- for (String pkgName : mSettings.mPackages.keySet()) {
- deleteCodeCacheDirsLI(pkgName);
- }
- mSettings.mFingerprint = Build.FINGERPRINT;
- }
- // All the changes are done during package scanning.所有操作执行完成,更新数据库版本
- mSettings.updateInternalDatabaseVersion();
- // can downgrade to reader
- mSettings.writeLPr();把mSettings中的内容保存到packages.xml
- EventLog.writeEvent(EventLogTags.BOOT_PROGRESS_PMS_READY,
- SystemClock.uptimeMillis());
- mRequiredVerifierPackage = getRequiredVerifierLPr();
- } // synchronized (mPackages)
- } // synchronized (mInstallLock)
- //创建PackageInstallerService./data/app
- mInstallerService = new PackageInstallerService(context, this, mAppInstallDir);
- // Now after opening every single application zip, make sure they
- // are all flushed. Not really needed, but keeps things nice and
- // tidy.启动内存垃圾回收
- Runtime.getRuntime().gc();
- }
PackageManagerService构造方法的执行过程就是先读取保存在packages.xml文件中的上次扫描的结果,保存在mSettings的成员变量中,然后扫描设备中几个应用目录下的应用文件,并把扫描的结果保存在PackageManagerService的成员变量mPackages中,通过对比上次扫描的结果来检查本次扫描到的应用中是否有被升级包覆盖的系统应用,如果有,则从mPackages中去除掉。这样mPackages的记录和mSettings的记录就一致了,最后,将本次扫描的结果写回packages.xml文件中。
PackageManagerService的初始化工作都是在它的构造方法中完成的,主要完成以下任务:
(1)、添加一些用户id,如shell、phone等;
(2)、建立并启动PackageHandler消息循环,用于处理apk安装请求,如adb install,packageInstaller安装过程中就会发送消息。
3、添加用户
添加用户调用的是Settings类的addSharedUserLPw方法。
[java]
view plain
copy
- /**
- * 检查mSharedUsers中是否有这个用户,没有则创建一个SharedUserSetting对象,
- * 保存到mUserIds或mOtherUserIds中,并添加到mSharedUsers中
- * @param name
- * @param uid
- * @param pkgFlags
- * @return
- */
- SharedUserSetting addSharedUserLPw(String name, int uid, int pkgFlags) {
- SharedUserSetting s = mSharedUsers.get(name);
- if (s != null) {
- if (s.userId == uid) {
- return s;
- }
- PackageManagerService.reportSettingsProblem(Log.ERROR,
- “Adding duplicate shared user, keeping first: “ + name);
- return null;
- }
- s = new SharedUserSetting(name, pkgFlags);//创建SharedUserSetting对象
- s.userId = uid;//将uid赋给SharedUserSetting对象的userId属性
- if (addUserIdLPw(uid, s, name)) {//保存到mUserIds或mOtherUserIds中
- mSharedUsers.put(name, s);//添加到mSharedUsers中
- return s;
- }
- return null;
- }
首先检查mSharedusers数组中是否含有对应name的SharedUserSetting对象,如果没有则创建SharedUserSetting对象,调用addUserIdLPw方法添加到mUserIds或mOtherUserIds数组中,并添加到mSharedUsers中,返回查询的对象。
[java]
view plain
copy
- /**
- * 将uid及对应的SharedUserSetting对象添加到mUserIds或mOtherUserIds
- * @param uid
- * @param obj SharedUserSetting对象
- * @param name
- * @return
- */
- private boolean addUserIdLPw(int uid, Object obj, Object name) {
- if (uid > Process.LAST_APPLICATION_UID) {//大于应用程序最大的id,19999
- return false;
- }
- if (uid >= Process.FIRST_APPLICATION_UID) {// 10000
- int N = mUserIds.size();
- final int index = uid – Process.FIRST_APPLICATION_UID;
- while (index >= N) {//先添加元素,后设置值
- mUserIds.add(null);
- N++;
- }
- if (mUserIds.get(index) != null) {
- PackageManagerService.reportSettingsProblem(Log.ERROR,
- “Adding duplicate user id: “ + uid
- + ” name=” + name);
- return false;
- }
- mUserIds.set(index, obj);//把该uid和对应的SharedUserSetting保存
- } else {//系统用户
- if (mOtherUserIds.get(uid) != null) {
- PackageManagerService.reportSettingsProblem(Log.ERROR,
- “Adding duplicate shared id: “ + uid
- + ” name=” + name);
- return false;
- }
- mOtherUserIds.put(uid, obj);//保存到mOtherUserIds中
- }
- return true;
- }
在构造方法中添加了6个系统用户:android.uid.system、android.uid.phone、android.uid.log、android.uid.nfc、android.uid.bluetooth、android.uid.shell。
4、建立并启动PackageHandler消息循环机制
PackageHandler用来处理安装apk等过程中的各种消息。这里比较简单,这要是建立一个PackageHandler,来处理消息。
5、处理permission文件
在PackageManagerService的构造方法中,调用了SystemConfig的getSystemPermissions()方法来获取系统的Permission列表。getSystemPermisssions()方法返回的是保存在对象内部的变量列表,如下:
[java]
view plain
copy
- public SparseArray<ArraySet<String>> getSystemPermissions() {
- return mSystemPermissions;
- }
这个列表的建立是在SystemConfig的构造方法中完成的,如下:
[java]
view plain
copy
- SystemConfig() {
- // Read configuration from system /system/etc/sysconfig
- readPermissions(Environment.buildPath(
- Environment.getRootDirectory(), “etc”, “sysconfig”), false);
- // Read configuration from the old permissions dir <span style=”font-size: 11.8181819915771px; font-family: Arial, Helvetica, sans-serif;”>/system/etc/permissions</span>
- readPermissions(Environment.buildPath(
- Environment.getRootDirectory(), “etc”, “permissions”), false);
- // Only read features from OEM config /oem/etc/sysconfig
- readPermissions(Environment.buildPath(
- Environment.getOemDirectory(), “etc”, “sysconfig”), true);
- readPermissions(Environment.buildPath(// /oem/etc/permissions
- Environment.getOemDirectory(), “etc”, “permissions”), true);
- }
Permission的读取是通过readPermission()方法完成的,代码如下:
[java]
view plain
copy
- void readPermissions(File libraryDir, boolean onlyFeatures) {
- // Read permissions from given directory.
- if (!libraryDir.exists() || !libraryDir.isDirectory()) {
- if (!onlyFeatures) {
- Slog.w(TAG, “No directory “ + libraryDir + “, skipping”);
- }
- return;//如果目录不存在,或libraryDir不是一个目录,退出
- }
- if (!libraryDir.canRead()) {
- Slog.w(TAG, “Directory “ + libraryDir + ” cannot be read”);
- return;//如果目录是不可读的,退出
- }
- // Iterate over the files in the directory and scan .xml files
- File platformFile = null;
- for (File f : libraryDir.listFiles()) {
- // We’ll read platform.xml last
- if (f.getPath().endsWith(“etc/permissions/platform.xml”)) {
- platformFile = f;
- continue;//先不处理platform.xml
- }
- if (!f.getPath().endsWith(“.xml”)) {
- Slog.i(TAG, “Non-xml file “ + f + ” in “ + libraryDir + ” directory, ignoring”);
- continue;//仅处理xml文件,其余文件忽略
- }
- if (!f.canRead()) {
- Slog.w(TAG, “Permissions library file “ + f + ” cannot be read”);
- continue;//如果文件不可读,忽略
- }
- readPermissionsFromXml(f, onlyFeatures);//解析xml文件
- }
- // Read platform permissions last so it will take precedence
- if (platformFile != null) {//单独处理/etc/permissions/platform.xml文件
- readPermissionsFromXml(platformFile, onlyFeatures);
- }
- }
readPermissions()方法的工作就是读取指定目录下的xml文件,然后调用readPermissionsFromXml()方法来处理文件。目录下存放的是和permission相关的文件,其中platform.xml文件的内容和其他文件的内容不同。
[java]
view plain
copy
- <?xml version=“1.0” encoding=“utf-8”?>
- <permissions>
- <permission name=“android.permission.BLUETOOTH_ADMIN” >
- <group gid=“net_bt_admin” />
- </permission>
- <permission name=“android.permission.BLUETOOTH” >
- <group gid=“net_bt” />
- </permission>
- ……
- <assign-permission name=“android.permission.MODIFY_AUDIO_SETTINGS” uid=”medi
- a” />
- <assign-permission name=“android.permission.ACCESS_SURFACE_FLINGER” uid=”med
- ia” />
- ……
- <library name=“android.test.runner”
- file=“/system/framework/android.test.runner.jar” />
- <library name=“javax.obex”
- file=“/system/framework/javax.obex.jar”/>
- ……
- <allow-in-power-save package=“com.android.providers.downloads” />
- </permissions>
platform.xml文件主要有3块内容组成。
- 标签<permission>表示把属性name中的字符串表示的权限赋予<group>标签中的属性gid中的用户组。
- 标签<assign-permission>表示把属性name中的字符串表示的权限赋予属性uid的用户。
- 标签<library>表示除了framework中的动态库以外,系统将为应用自动加载的动态库。
readPermissionsFromXml()方法主要的工作就是解析上面的标签,看下解析结果。
(1)标签<permission>中的属性name字符串和<group>标签中的gid都放到了变量mSettings的mPermissions中,而所有gid也被收集起来放到了PackageManagerService的成员变量mGlobalGids中。
(2)标签<assign-permission>的内容放到了PMS的成员变量mSystemPermissions中,定义:
[java]
view plain
copy
- final SparseArray<ArraySet<String>> mSystemPermissions;
(3)标签<library>的动态库字符串放到了PMS的成员变量mSharedLibraries中。
(4)其他xml文件的标签<feature>定义的字符串放到了PMS的成员变量mAvailableFeatures中。 Android的很多功能是通过所谓的permission字符串来保护的,应用中如果需要使用某项受保护的功能,需要在它的AndroidManifest.xml文件中显示的声明该功能对应的permission字符串。但是,有些功能只能由特定用户组的应用使用,在platform.xml文件中定义的就是这种限制规则。
4、扫描应用目录的过程
PMS的构造方法中调用了scanDirLI()方法来扫描某个目录中apk文件,如下:
[java]
view plain
copy
- private void scanDirLI(File dir, int parseFlags, int scanFlags, long currentTime) {
- final File[] files = dir.listFiles();
- if (ArrayUtils.isEmpty(files)) {
- Log.d(TAG, “No files in app dir “ + dir);
- return;//如果扫描的目录是空的,返回
- }
- if (DEBUG_PACKAGE_SCANNING) {
- Log.d(TAG, “Scanning app dir “ + dir + ” scanFlags=” + scanFlags
- + ” flags=0x” + Integer.toHexString(parseFlags));
- }
- for (File file : files) {//判断文件是否是应用文件
- final boolean isPackage = (isApkFile(file) || file.isDirectory())
- && !PackageInstallerService.isStageName(file.getName());
- if (!isPackage) {
- // Ignore entries which are not packages忽略非应用文件
- continue;
- }
- try {//调用scanPackageLI扫描文件
- scanPackageLI(file, parseFlags | PackageParser.PARSE_MUST_BE_APK,
- scanFlags, currentTime, null);
- } catch (PackageManagerException e) {
- Slog.w(TAG, “Failed to parse “ + file + “: “ + e.getMessage());
- // Delete invalid userdata apps删除安装失败的文件和数据目录
- if ((parseFlags & PackageParser.PARSE_IS_SYSTEM) == 0 &&
- e.error == PackageManager.INSTALL_FAILED_INVALID_APK) {
- logCriticalInfo(Log.WARN, “Deleting invalid package at “ + file);
- if (file.isDirectory()) {
- FileUtils.deleteContents(file);
- }
- file.delete();
- }
- }
- }
- }
scanDirLI()只扫描指定目录下的文件,不会去扫描子目录,同时只扫描后缀为“apk”的文件。调用scanPackageLI()方法来继续扫描过程。在scanDirLI方法中调用的参数是File对象,因此scanPackageLI调用第一个参数为File对象的方法,作用是把File对象解析成PackageParser.Package对象,这个结果会传递给scanPackageLI方法的第二个实现,用来创建PackageManagerService中和应用相关的各种内部数据结构。如下:
(1)解析文件:
[java]
view plain
copy
- /*
- * Scan a package and return the newly parsed package.
- * Returns null in case of errors and the error code is stored in mLastScanError
- */
- private PackageParser.Package scanPackageLI(File scanFile, int parseFlags, int scanFlags,
- long currentTime, UserHandle user) throws PackageManagerException {
- if (DEBUG_INSTALL) Slog.d(TAG, “Parsing: “ + scanFile);
- parseFlags |= mDefParseFlags;
- PackageParser pp = new PackageParser();//创建文件解析器对象
- pp.setSeparateProcesses(mSeparateProcesses);
- pp.setOnlyCoreApps(mOnlyCore);
- pp.setDisplayMetrics(mMetrics);
- if ((scanFlags & SCAN_TRUSTED_OVERLAY) != 0) {
- parseFlags |= PackageParser.PARSE_TRUSTED_OVERLAY;
- }
- final PackageParser.Package pkg;
- try {
- pkg = pp.parsePackage(scanFile, parseFlags);//创建PackageParser.Package对象
- } catch (PackageParserException e) {
- throw PackageManagerException.from(e);
- }
scanPackageLI方法创建一个文件解析器PackageParser对象,然后调用它的parsePackage()方法来解析参数中传递的文件对象scanFile,得到一个PackageParser.Package对象。
(2)处理更改了包名的应用。
这里是在检查应用是否属于<renamed-package>标签标记的改了包名的应用,如果是,则使用原始的包的信息:
[java]
view plain
copy
- PackageSetting ps = null;
- PackageSetting updatedPkg;
- // reader
- synchronized (mPackages) {
- // Look to see if we already know about this package.获取旧的包名
- String oldName = mSettings.mRenamedPackages.get(pkg.packageName);
- if (pkg.mOriginalPackages != null && pkg.mOriginalPackages.contains(oldName)) {
- // This package has been renamed to its original name. Let’s
- // use that.
- ps = mSettings.peekPackageLPr(oldName);
- }
- // If there was no original package, see one for the real package name.
- if (ps == null) {
- ps = mSettings.peekPackageLPr(pkg.packageName);
- }
(3)处理安装了升级包的系统应用。
[java]
view plain
copy
- // Check to see if this package could be hiding/updating a system
- // package. Must look for it either under the original or real
- // package name depending on our state.检查应用是否存在升级包
- updatedPkg = mSettings.getDisabledSystemPkgLPr(ps != null ? ps.name : pkg.packageName);
- if (DEBUG_INSTALL && updatedPkg != null) Slog.d(TAG, “updatedPkg = “ + updatedPkg);
- }
- boolean updatedPkgBetter = false;
- // First check if this is a system package that may involve an update如果扫描的是系统应用并且有升级包
- if (updatedPkg != null && (parseFlags&PackageParser.PARSE_IS_SYSTEM) != 0) {
- // If new package is not located in “/system/priv-app” (e.g. due to an OTA),
- // it needs to drop FLAG_PRIVILEGED.
- if (locationIsPrivileged(scanFile)) {
- updatedPkg.pkgFlags |= ApplicationInfo.FLAG_PRIVILEGED;
- } else {
- updatedPkg.pkgFlags &= ~ApplicationInfo.FLAG_PRIVILEGED;
- }
- if (ps != null && !ps.codePath.equals(scanFile)) {
- // The path has changed from what was last scanned… check the
- // version of the new path against what we have stored to determine
- // what to do.如果包名和上次扫描的结果不相同了,根据版本号来决定如何处理
- if (DEBUG_INSTALL) Slog.d(TAG, “Path changing from “ + ps.codePath);
- if (pkg.mVersionCode <= ps.versionCode) {//如果扫描文件的版本号低于升级包的版本,忽略这个文件
- // The system package has been updated and the code path does not match
- // Ignore entry. Skip it.
- Slog.i(TAG, “Package “ + ps.name + ” at “ + scanFile
- + ” ignored: updated version “ + ps.versionCode
- + ” better than this “ + pkg.mVersionCode);
- if (!updatedPkg.codePath.equals(scanFile)) {
- Slog.w(PackageManagerService.TAG, “Code path for hidden system pkg : “
- + ps.name + ” changing from “ + updatedPkg.codePathString
- + ” to “ + scanFile);
- updatedPkg.codePath = scanFile;
- updatedPkg.codePathString = scanFile.toString();
- }
- updatedPkg.pkg = pkg;
- throw new PackageManagerException(INSTALL_FAILED_DUPLICATE_PACKAGE, null);
- } else {
- // The current app on the system partition is better than
- // what we have updated to on the data partition; switch
- // back to the system partition version.
- // At this point, its safely assumed that package installation for
- // apps in system partition will go through. If not there won’t be a working
- // version of the app
- // writer如果扫描文件的版本号高于升级包的版本,则把升级包删除掉
- synchronized (mPackages) {
- // Just remove the loaded entries from package lists.
- mPackages.remove(ps.name);
- }
- logCriticalInfo(Log.WARN, “Package “ + ps.name + ” at “ + scanFile
- + ” reverting from “ + ps.codePathString
- + “: new version “ + pkg.mVersionCode
- + ” better than installed “ + ps.versionCode);
- InstallArgs args = createInstallArgsForExisting(packageFlagsToInstallFlags(ps),
- ps.codePathString, ps.resourcePathString, ps.legacyNativeLibraryPathString,
- getAppDexInstructionSets(ps));
- synchronized (mInstallLock) {
- args.cleanUpResourcesLI();
- }
- synchronized (mPackages) {
- mSettings.enableSystemPackageLPw(ps.name);
- }
- updatedPkgBetter = true;
- }
- }
- }
- if (updatedPkg != null) {//如果升级包存在,把属性设为系统应用
- // An updated system app will not have the PARSE_IS_SYSTEM flag set
- // initially
- parseFlags |= PackageParser.PARSE_IS_SYSTEM;
- // An updated privileged app will not have the PARSE_IS_PRIVILEGED
- // flag set initially
- if ((updatedPkg.pkgFlags & ApplicationInfo.FLAG_PRIVILEGED) != 0) {
- parseFlags |= PackageParser.PARSE_IS_PRIVILEGED;
- }
- }
这段代码的作用就是处理带有升级包的应用。
(4)扫描文件的签名。
[java]
view plain
copy
- // Verify certificates against what was last scanned
- collectCertificatesLI(pp, ps, pkg, scanFile, parseFlags);
(5)处理应用的包名有冲突的情况。
[java]
view plain
copy
- /*
- * A new system app appeared, but we already had a non-system one of the
- * same name installed earlier.
- */
- boolean shouldHideSystemApp = false;
- if (updatedPkg == null && ps != null//如果扫描的文件是系统应用,但是也存在一个同名的普通应用
- && (parseFlags & PackageParser.PARSE_IS_SYSTEM_DIR) != 0 && !isSystemApp(ps)) {
- /*
- * Check to make sure the signatures match first. If they don’t,
- * wipe the installed application and its data.
- */
- if (compareSignatures(ps.signatures.mSignatures, pkg.mSignatures)
- != PackageManager.SIGNATURE_MATCH) {//比较它们的签名,如果不相同就删除扫描到的系统应用
- logCriticalInfo(Log.WARN, “Package “ + ps.name + ” appeared on system, but”
- + ” signatures don’t match existing userdata copy; removing”);
- deletePackageLI(pkg.packageName, null, true, null, null, 0, null, false);
- ps = null;
- } else {
- /*
- * If the newly-added system app is an older version than the
- * already installed version, hide it. It will be scanned later
- * and re-added like an update.如果扫描的系统应用和安装的应用签名相同,则比较他们的版本;
- */
- if (pkg.mVersionCode <= ps.versionCode) {//如果安装的应用版本高,则构成了升级关系,把系统应用隐藏。
- shouldHideSystemApp = true;
- logCriticalInfo(Log.INFO, “Package “ + ps.name + ” appeared at “ + scanFile
- + ” but new version “ + pkg.mVersionCode + ” better than installed “
- + ps.versionCode + “; hiding system”);
- } else {//删除安装的应用
- /*
- * The newly found system app is a newer version that the
- * one previously installed. Simply remove the
- * already-installed application and replace it with our own
- * while keeping the application data.
- */
- logCriticalInfo(Log.WARN, “Package “ + ps.name + ” at “ + scanFile
- + ” reverting from “ + ps.codePathString + “: new version “
- + pkg.mVersionCode + ” better than installed “ + ps.versionCode);
- InstallArgs args = createInstallArgsForExisting(packageFlagsToInstallFlags(ps),
- ps.codePathString, ps.resourcePathString, ps.legacyNativeLibraryPathString,
- getAppDexInstructionSets(ps));
- synchronized (mInstallLock) {
- args.cleanUpResourcesLI();
- }
- }
- }
- }
(6)处理应用的代码路径和资源路径:
[java]
view plain
copy
- // The apk is forward locked (not public) if its code and resources
- // are kept in different files. (except for app in either system or
- // vendor path).
- // 如果一个应用的代码路径和资源路径不相同,则加上PARSE_FORWARD_LOCK标记,这类应用是forward locked类应用
- if ((parseFlags & PackageParser.PARSE_IS_SYSTEM_DIR) == 0) {
- if (ps != null && !ps.codePath.equals(ps.resourcePath)) {
- parseFlags |= PackageParser.PARSE_FORWARD_LOCK;
- }
- }
- // TODO: extend to support forward-locked splits
- String resourcePath = null;
- String baseResourcePath = null;
- if ((parseFlags & PackageParser.PARSE_FORWARD_LOCK) != 0 && !updatedPkgBetter) {
- if (ps != null && ps.resourcePathString != null) {//如果是forward locked类应用,且他们的资源路径不为空,单独设置他们的资源路径
- resourcePath = ps.resourcePathString;
- baseResourcePath = ps.resourcePathString;
- } else {
- // Should not happen at all. Just log an error.
- Slog.e(TAG, “Resource path not set for pkg : “ + pkg.packageName);
- }
- } else {//如果是普通应用,设置他们的资源路径和代码路径一致
- resourcePath = pkg.codePath;
- baseResourcePath = pkg.baseCodePath;
- }
- // Set application objects path explicitly.
- pkg.applicationInfo.setCodePath(pkg.codePath);
- pkg.applicationInfo.setBaseCodePath(pkg.baseCodePath);
- pkg.applicationInfo.setSplitCodePaths(pkg.splitCodePaths);
- pkg.applicationInfo.setResourcePath(resourcePath);
- pkg.applicationInfo.setBaseResourcePath(baseResourcePath);
- pkg.applicationInfo.setSplitResourcePaths(pkg.splitCodePaths);
(7)调用参数为PackageParser.Package对象的scanPackageLI方法。
[java]
view plain
copy
- // Note that we invoke the following method only if we are about to unpack an application
- PackageParser.Package scannedPkg = scanPackageLI(pkg, parseFlags, scanFlags
- | SCAN_UPDATE_SIGNATURE, currentTime, user);
(8)结束:
[java]
view plain
copy
- /*
- * If the system app should be overridden by a previously installed
- * data, hide the system app now and let the /data/app scan pick it up
- * again.
- */
- if (shouldHideSystemApp) {
- synchronized (mPackages) {
- /*
- * We have to grant systems permissions before we hide, because
- * grantPermissions will assume the package update is trying to
- * expand its permissions.如果扫描的应用带有升级包,把他们的关系保存到mSettings中
- */
- grantPermissionsLPw(pkg, true, pkg.packageName);
- mSettings.disableSystemPackageLPw(pkg.packageName);
- }
- }
- return scannedPkg;
scanPackageLI方法在解析出了apk文件的信息后,主要是通过对比上次启动的结果来检查系统中是否存在和扫描的文件相冲突的应用包存在,如果有scanPackageLI方法会设法纠正错误,保证系统启动后的一致性。完成错误检查后,将进入第二阶段,调用PackageParser.Package对象的scanPackageLI方法来构建PackageManagerService中的数据结构。