Sensors included:
- FEATURE_SENSOR_ACCELEROMETER_LIMITED_AXES
- FEATURE_SENSOR_GYROSCOPE_LIMITED_AXES
- FEATURE_SENSOR_ACCELEROMETER_LIMITED_AXES_UNCALIBRATED
- FEATURE_SENSOR_GYROSCOPE_LIMITED_AXES_UNCALIBRATED
These changes will enable support for automotive style IMUs that have
more limited axes for accelerometers (x-axis and y-axis) and gyroscopes
(z-axis).
Bug: 187342209
Test: Compiled
Change-Id: I28dbf664f607a183a36a71f07f5c6d1aba31f39c
Follow up of ag/16417696
Pass the new UID in the broadcast via a new Intent extra with the name
Intent.EXTRA_NEW_UID. This is necessary for many system components to
migrate data structures linked with the old UID to the new one.
Test: SharedUserMigrationTest#testDataMigration
Bug: 217762162
Change-Id: I24f6707cf0fa0ed5acf6836cb803ce96df6f78fc
In the previous CL (Ib53e2cdf45a10454), I mistakenly deprecated the wrong
flag. This CL fixes it.
Bug: 189235490
Test: prebuilt
Change-Id: I79c1f63475d80e0b077b577f32ae2cbca37edad2
Each app will have it's own supplemental process with a different uid
that uniquely maps to the uid of the application that this supplemental
process corresponds to.
This will impact some of the PackageManager and PermissionManager APIs
(e.g. PackageManager.getPackagesForUid, or
PermissionManager.checkPermission). In order to make it possible for
PackageManager to correctly treat supplemental process uids, we first
need to teach it about the supplemental process APK itself, hence this
change.
Bug: 215241564
Test: atest PackageManagerShellCommandTest
Change-Id: I28f4a382900f276170c51e8c92d8fcde8419ddb1
+ Renaming to reflect the actual functionality of the class.
+ Move freeStorage related code to PackageManagerService, we will want
to clean that up later.
BUG: 198177734
Test: atest InstallLocationUtilsTest
Change-Id: I951129ffb5e53df548ef78fcd9de79c0ef994914
Switched CrossProfileApps#getProfileSwitchingIconDrawable to use
PackageManager#getUserBadgeForDensityNoBackground which returns a
drawable that could be updated by the device management role holder.
Test: manual
Bug: 203548565
Bug: 188410712
Change-Id: Ia4246d7196b9d16e940d19752076b7d7f8916120
Sample of results:
history
0
class=class android.content.res.Resources
resourcesImpl
class=class android.content.res.ResourcesImpl
assets
class=class android.content.res.AssetManager
apkAssets=
0
class=class android.content.res.ApkAssets
debugName=<empty> and /system/framework/framework-res.apk
assetPath=/system/framework/framework-res.apk
1
class=class android.content.res.ApkAssets
debugName=/product/overlay/GoogleConfigOverlay.apk
assetPath=/product/overlay/GoogleConfigOverlay.apk
Fixes: 206615535
Test: Called from custom app to confirm format and info
Change-Id: I19a9fc60b61fff86e5b41a2d789d6dde8acf51a3
CTS-Coverage-Bug: 210528288
Bug: 216507592
Test: RBE Built redfin-eng and tested on a physical device
Change-Id: Ic9505f659befa01938b413e1e1944c3aaa0e8a0c
This change adds all existing package manager tests we've considered for
the platinum test suite to TEST_MAPPING.
Bug: 140252512
Test: N/A
Change-Id: Ib1e27820a093198c7dcc0343fa36002dd19174e9
* changes:
Expose the bg restriction exemption list as an internal API.
Add an action button to the notification for bg battery abusive apps
Exempt certain app behaviors for their background battery usage
Add tracking on abusive broadcast and service binding requests
Add exemption cases for app background restrictions
Monitor long-running foreground services
Post notification on abusive background current drain
Allow limited alarms/jobs when background restricted
Cap the LRU position of broadcast receivers in bg restricted apps
Add a tracker on background current drains for each uid
Add background restriction levels definition and its controller
CTS-Coverage-Bug: 210528288
Bug: 210528288
Test: RBE Built redfin-eng and tested on a physical device
Change-Id: I640be77dbf05633b7a17ada73ea261dbd0027697
Augment the "apparent" display information in configuration
from just the display bounds (maxBounds) to also include the
display rotation and cutout. Like maxBounds, these will be
expected to always be set as basically "the display that this
configuration was built against".
This heavily simplifies fixed-rotation since now we don't
need to deal with the "are we overriding?" question and also
don't need extra activity servertransactions. The configuration
is also in sync (since it is the source of truth used by
resources). Additionally, this means that even the current
legacy fixed-rotation model should work with in any
mixed-rotation situtaion, not just fullscreen.
Bug: 202201326
Test: atest DisplayTest
Change-Id: I6232f74c74324b70b1b0c9f46448c509c2694310
