d8597aa9a5bc8def9520bb78bb6e9b368292cbdc
It is possible for a system app to leave shared user ID by an update. We need to keep track of this in case the upgrade is uninstalled. In this scenario, the shadowed system package will be reinstalled using the original shared UID. This has the side effect of the app ID used by the shared user group being held forever even if no apps is actively using it, because only the app ID is stored in packages.xml, not the sharedUserId name, and we have to use the app ID to link the disabled PackageSetting with the corresponding SharedUserSetting. Test: tracking with b/202993696 Bug: 179284822 Fixes: 201509122 Change-Id: If48aeb7d63daf1ef8bdf06a9d2dd34c1de8603c8
Merge "Rename merged services.txt module" am:
74b15ca3c5 am: 58ae8524f5 am: 590544a108 am: 2e4629a729 am: 7fafe71ffc
…
…
RESTRICT AUTOMERGE: Give the priv permission CONTROL_CAR_APP_LAUNCH to KitchenSync and CarLauncher. am:
e5581e9925
…
…
…
…
Merge "AudioTrack: Fix track creation of 9.1.4 and 9.1.6 streams" into sc-v2-dev am:
f79e42539f am: fdc8a891c7
…
…
…
Merge "Add empty package + OWNERS file for critical event protos" am:
ae99d9ba9c am: d27b7d3952 am: 259ca6f387 am: 169b1b9f79 am: c806e66504
…
…
…
…
Merge "Update doc of ServiceState.getChannelNumber about NR" am:
bbed692810 am: 355d9d3d56 am: b86f78e02d am: c000cd9372 am: 1bb591608a
…
…
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%