Can someone explain or point out resources where I can read how Android app upgrades actually work on an OS level of detail?
Asked
Active
Viewed 2,076 times
3 Answers
13
From the package manager logs,it seems following steps are taken for upgrade:
1) Download the package at temporary location.
act=android.intent.action.PACKAGE_NEEDS_VERIFICATION dat=file:///data/app/vmdl1854135520.tmp typ=application/vnd.android.package-archive
2) Do package verification.
06-30 17:59:02.751 3701 3751 D PackageManager: [MSG] PACKAGE_VERIFIED: observer{237546897}
3) Rename the package.
06-30 17:59:03.361 3701 3751 D PackageManager: Renaming /data/app/vmdl1854135520.tmp to /data/app/com.vzw.hss.myverizon-1
4) Kill existing app
06-30 17:59:03.361 3701 3751 D PackageManager: !@killApplicatoin: 10031, replace sys pkg
5) Dexopt the apk
06-30 17:59:03.381 3701 3751 D PackageManager: Running dexopt on: /data/app/com.vzw.hss.myverizon-1/base.apk pkg=com.vzw.hss.myverizon isa=arm64 vmSafeMode=false interpret_only=false
**06-30 17:59:02.741 3701 3751 D PackageManager: [VERIFY] Found 1 verifiers for intent Intent { act=android.intent.action.PACKAGE_NEEDS_VERIFICATION dat=file:///data/app/vmdl1854135520.tmp** typ=application/vnd.android.package-archive flg=0x10000001 } with 0 optional verifiers
06-30 17:59:02.741 3701 3751 D PackageManager: [VERIFY] sendOrderedBroadcastToRequiredVerifier:
06-30 17:59:02.741 3701 3751 D PackageManager: PackageVerificationState{
06-30 17:59:02.741 3701 3751 D PackageManager: verifier packages=com.android.vending(10034),
06-30 17:59:02.741 3701 3751 D PackageManager: intent=Intent { act=android.intent.action.PACKAGE_NEEDS_VERIFICATION dat=file:///data/app/vmdl1854135520.tmp typ=application/vnd.android.package-archive flg=0x10000001 (has extras) }
06-30 17:59:02.741 3701 3751 D PackageManager: others=28, false, false, false, false, false
06-30 17:59:02.741 3701 3751 D PackageManager: }
06-30 17:59:02.741 3701 3751 D PackageManager: remove MCS_UNBIND message and Posting MCS_UNBIND 10 secs later
06-30 17:59:02.751 3701 3701 D PackageManager: [VERIFY] onReceive for RequiredVerifier id=28
06-30 17:59:02.751 3701 3701 D PackageManager: [VERIFY] send delayed message for CHECK_PENDING_VERIFICATION after : 10000
06-30 17:59:02.751 3701 4589 D PackageManager: [VERIFY] verifyPendingInstall(28, VERIFICATION_ALLOW), uid=10034
06-30 17:59:02.751 3701 3751 D PackageManager: [MSG] PACKAGE_VERIFIED: observer{237546897}
06-30 17:59:02.751 3701 3751 D PackageManager: [VERIFY] PACKAGE_VERIFIED:
06-30 17:59:02.751 3701 3751 D PackageManager: PackageVerificationState{
06-30 17:59:02.751 3701 3751 D PackageManager: verifier packages=com.android.vending(10034),
06-30 17:59:02.751 3701 3751 D PackageManager: intent=Intent { act=android.intent.action.PACKAGE_NEEDS_VERIFICATION dat=file:///data/app/vmdl1854135520.tmp typ=application/vnd.android.package-archive flg=0x10000001 cmp=com.android.vending/com.google.android.vending.verifier.PackageVerificationReceiver (has extras) }
06-30 17:59:02.751 3701 3751 D PackageManager: others=28, false, false, false, false, false
06-30 17:59:02.751 3701 3751 D PackageManager: }
06-30 17:59:02.751 3701 3751 D PackageManager: [VERIFY] broadcastPackageVerified(28, VERIFICATION_ALLOW, file:///data/app/vmdl1854135520.tmp)
06-30 17:59:02.761 3701 3751 D PackageManager: /data/app/vmdl1854135520.tmp already staged; skipping copy
06-30 17:59:02.761 3701 3751 D PackageManager: remove MCS_UNBIND and Posting MCS_UNBIND
06-30 17:59:02.761 3701 3751 D PackageManager: [MSG] PROCESS_PENDING_INSTALL: observer{237546897}
06-30 17:59:02.761 3701 3751 D PackageManager: currentStatus{1}
06-30 17:59:02.761 3701 3751 D PackageManager: installPackageLI: path
06-30 17:59:03.321 3701 3751 W PackageManager: verifying app can be installed or not
**06-30 17:59:03.361 3701 3751 D PackageManager: Renaming /data/app/vmdl1854135520.tmp to /data/app/com.vzw.hss.myverizon-1**
**06-30 17:59:03.361 3701 3751 D PackageManager: replacePackageLI**
**06-30 17:59:03.361 3701 3751 D PackageManager: !@killApplicatoin: 10031, replace sys pkg**
06-30 17:59:03.371 3701 3751 W PackageManager: Trying to update system app code path from /system/priv-app/MyVerizon to /data/app/com.vzw.hss.myverizon-1
06-30 17:59:03.371 3701 3751 I PackageManager: scanFileNewer : com.vzw.hss.myverizon
**06-30 17:59:03.381 3701 3751 D PackageManager: Running dexopt on: /data/app/com.vzw.hss.myverizon-1/base.apk pkg=com.vzw.hss.myverizon isa=arm64 vmSafeMode=false interpret_only=false**
06-30 17:59:06.861 3701 3751 I PackageManager: do mInstaller.dexopt : 0
06-30 17:59:06.861 3701 3751 D PackageManager: Time to dexopt: 3.482 seconds
06-30 17:59:06.861 3701 3751 D PackageManager: !@killApplicatoin: 10031, update pkg
06-30 17:59:06.861 3701 3751 W PackageManager: Code path for pkg : com.vzw.hss.myverizon changing from /system/priv-app/MyVerizon to /data/app/com.vzw.hss.myverizon-1
06-30 17:59:06.861 3701 3751 W PackageManager: Resource path for pkg : com.vzw.hss.myverizon changing from /system/priv-app/MyVerizon to /data/app/com.vzw.hss.myverizon-1
06-30 17:59:06.961 3701 3751 D PackageManager: New package installed
06-30 17:59:06.971 3701 3751 I PackageManager: Un-granting permission android.permission.sec.ENTERPRISE_DEVICE_ADMIN from package com.samsung.mdmtest1 (protectionLevel=2 flags=0x89be44)
06-30 17:59:06.971 3701 3751 I PackageManager: Un-granting permission com.sec.enterprise.knox.permission.KNOX_ENTERPRISE_BILLING from package com.samsung.mdmtest1 (protectionLevel=2 flags=0x89be44)
06-30 17:59:07.141 3701 3751 D PackageManager: doPostInstall for uid{10031}
06-30 17:59:07.151 3701 3751 D PackageManager: [MSG] MCS_UNBIND
06-30 17:59:07.151 3701 3751 D PackageManager: [MSG] POST_INSTALL: observer{237546897}
06-30 17:59:07.151 3701 3751 D PackageManager: Handling post-install for 29
06-30 17:59:07.661 3701 3751 D PackageManager: result of install: 1{237546897}
rupesh jain
- 3,287
- 1
- 10
- 21
6
I can't find a good resource, but here's what I understand about the process.
APK's are stored in a private directory on the phone when they are installed. When an upgrade happens, the new APK is downloaded from the store, and then the old APK is replaced with the new one. The new AndroidManifest is parsed and installed as if it was a new installation, and checks for version, signing key, and etc. are done to make sure the upgrade is allowed. The actual application data is stored in a separate location and is not touched during the upgrade. If you change your database schema or something, you will need to migrate your data when you first launch.
Jschools
- 2,416
- 14
- 16
-
thanks for your answer. I am thinking more from the perspective where current app stays as is, and upgraded one only takes control from previous version. – Ankit Garg May 14 '15 at 16:31
-
I have seen during development that when the app is about to be updated, if you click on the icon, it says, xyz not installed. So definitely, data should be in separate area, and app is stored in private sandboxed storage. – Ankit Garg May 14 '15 at 16:34
-
On Android, the current application's processes are killed during the upgrade process, so there is any "taking control" going on here (at least if I understand you correctly) – David Wasser Jun 30 '15 at 17:09
3
Source: http://java.dzone.com/articles/depth-android-package-manager
I'm not so sure if thats what you're after, but the best I could find was this.
The Package Manager API is is the responsible for managing installing, uninstalling, and upgrading APK files.
It calls the method "InstallPackage" with the 'uri', 'installFlags', 'observer', and 'InstallPackageName' parameters, it then starts the service named "package" that will actually install/upgrade it.
Package Manager Service runs in system_service process and install daemon (installd) runs as a native process. Both start at system boot time.
Overview of the process:
- Waiting;
- Add a package to the queue for the installation process;
- Determine the appropriate location of the package installation;
- Determine installation Install/Update new
- Copy the APK file to a given directory;
- Determine the UID of the app;
- Request the installd daemon process;
- Create the application directory and set permissions;
- Extraction of dex code to the cache directory;
- Reflect packages.list /system / data / packages.xml the latest packages status;
- Broadcast to the system along with the name of the package the effect of the installation;
- Intent.ACTION_PACKAGE_ADDED: If the package is new // ( Intent.ACTION_PACKAGE_REPLACED) If the package is updated
The package manager stores application information in three files, located in /data/system :
- packages.xml - With permissions that belong to the package
- packages.list - It is simply text file containing package name, user id, flag and data directory
- packages-stopped.xml : This file contains the package list which has stopped state. Stopped state applications cannot receive any broadcast.
The links to relevant source code for the package manager (and the package installer) are below:
Package installer
Waldez Junior
- 367
- 4
- 11