System server can only be compiled and signed by odrefresh in early
boot, so it is no use capturing dex load events for it.
Test: Build & boot
Bug: 254043366
Change-Id: If27569b784aeb882d3a20bd21a30137e6530e663
Start status bar manager service but not register global actions
provider on watches.
Bug: 257861786
Test: device can boot
Test: atest StatusBarManagerServiceTest
Change-Id: Ib9a13f159084f8970628a5eb89ca9aa88b2d050e
This adds an API to determine if the context user is the designated
main user on the device. This user may have access to features which
are limited to a single user on the device.
In Android U, this will be the first user to go through setup.
On regular devices, this will be the system user, but on devices in
No Primary User / Headless System User Mode, it will be a different
user.
The isPrimaryUser System API is confusing because it actually always
returns the system user, even in headless mode. That API is deprecated
in this change.
On devices that are upgrading, if they are non-headless, the system user
will be the main user. If they are headless, the full user with the
earliest creation date will be given the flag.
Bug: 256624031
Test: atest UserManagerTest
Change-Id: Ib36f3b372f9bf33cbb097c4af63eb43515ac835b
For now we can register both HIDL and AIDL sensorservice, and the vendor
can choose which one to use.
Test: atest VtsHalSensorManagerTargetTest
Bug: 205764765
Change-Id: I26ee176baea59f86281ae3a46ea580443064b5ef
On upgrade from Android 13 or earlier, LockSettingsService is creating a
synthetic password (SP) for all users that didn't have one before, and
re-encrypting the user's CE key with the SP. Currently this happens at
PHASE_BOOT_COMPLETED, since Weaver is not yet guaranteed to be available
at the previous phase, PHASE_THIRD_PARTY_APPS_CAN_START.
An issue with using PHASE_BOOT_COMPLETED is that during an upgrade,
PHASE_BOOT_COMPLETED happens after the userdata filesystem checkpoint
has already been committed. Therefore, if a problem occurs with the
migration to SP, the changes won't be rolled back and the device will be
left in a broken state, recoverable only via a factory reset.
Important migrations like this should happen before the checkpoint is
committed. Therefore, replace the use of PHASE_BOOT_COMPLETED with a
direct call into LockSettingsService in an appropriate place, similar to
the existing LockSettingsService.systemReady() call.
I also considered creating a PHASE_THIRD_PARTY_APPS_STARTED boot phase.
However, any new boot phase would become part of the services API
(services/api/current.txt), which is more than I'd like to do here.
Test: Made an intentionally broken build with
LockSettingsService.onThirdPartyAppsStarted() changed to throw a
RuntimeException at the end, crashing system_server. Tested an
OTA from tm-qpr2-release to that build, on a device that didn't
have a lockscreen credential set on user 0 (so that user 0 was
migrated to SP-based credentials just before the crash). The OTA
failed as expected and successfully rolled back to the original
build, with user 0's data still accessible (this was not possible
before this change).
Bug: 232452368
Change-Id: I77d30f9be57de7b7c4818680732331549ecb73c8
The service has been removed, so the init logic in the SystemServer
should also been removed.
Bug: 200706260
Tested: build passes
Change-Id: I3955571b66e7748f54b8136318a8d141c2dbcd15
(cherry picked from commit 7a5641422fe84106fced84daba3a0ee34f0d6aab)
(cherry picked from commit af07c8b703ae63666481fe89cc0b3f5c11c98741)
The BackgroundInstallControlService monitors background installed apps.
It can provide the list of those apps to the service clients via binder.
See the following desgin doc and PRD for more details.
go/bg-install-control
go/BIC-prd
Bug: 244216300
Test: manual test (verify the binder service is published)
Change-Id: Ic45770061c1291ef3e650337514fca99e0c683b8
Needs to be called by doing `adb shell dumpsys statusbar --proto`
because using `dumpsys activity service` adds text to the dump.
Will also be dumped as part of the BR
Test: atest SystemUITests
Test: Used in CTS
Test: manual dump and BR
Fixes 237786667
Change-Id: I74abf65a76c059ea9bb5a14728192b6b683b7fc7
Migrates getDefaultVrComponents used by SettingsProvider and
adds a flag for hidden API enforcement to ApplicationInfo.
This removes any dependency on SystemConfig from core/ and
so it can be moved into services/core and exposed as a
mainline API.
This was done instead of exposing all of the methods through
SystemConfigManager, as that is designed for use across
processes, and it's more efficient to expose SystemConfig
directly for modules running in the server process.
Although VrManager is a nullable service, so getDefaultVrComponents
had to live there to simplify the logic and maintain the existing
behavior.
Bug: 236389629
Change-Id: I4c2b14e1d34aaf439ceb1a3f9c8207e5d39fa6c2
Test: Local testing. Successfully able to call publishBinderServie and register service with system server
Bug:250713478
Change-Id: I5aec8b67ad81a38992d59c01efedfd55832d570e
Setup scaffold for the Health Connect system service.
This service will provide system APIs to read and write
health data.
Bug: 249321392
CTS-Coverage-Bug: 248508112
Test: atest android.healthconnect.cts
Change-Id: I503c24a039c37d09895fc4f73a1de1a13eeb72b0
Extract time zone storage logic from AlarmManagerService and add storage
for new time zone metadata.
This simplifies the AlarmManagerService, which would otherwise have to
expose the time zone metadata (or more knowledge of the storage would be
duplicated elsewhere).
The new metadata describes the confidence Android has in the current
time zone setting. It is intended to support upcoming APIs for SetUp
Wizard, which should ask the user to confirm the time zone. Currently
the SUW tries to infer this by watching for time zone changes, but this
is error prone and prevents the time zone detector from defaulting the
time zone using low-confidence (but still better than the hardcoded
"GMT") time zones today.
This change also includes small refactorings to how AlarmManagerService
tries to keep the kernel's time zone offset in sync with Android's time
zone setting. Code comments have also been added to try to clarify
behavior.
The system property defaulting behavior previously in SystemServer is
moved to SystemTimeZone too so that all the logic associated with the
system property is now in one place.
Bug: 236612872
Test: manual testing + inspection / treehugger
Test: atest services/tests/servicestests/src/com/android/server/devicepolicy/DevicePolicyManagerTest.java services/tests/servicestests/src/com/android/server/timezonedetector/TimeZoneDetectorStrategyImplTest.java services/tests/mockingservicestests/src/com/android/server/alarm/AlarmManagerServiceTest.java
Change-Id: I493d31043f22d32f12793e0c35110233c850ed85
See related for the refactoring that caused this CL
Bug: 243827192
Test: booted with a Wear devices without an issue
Change-Id: I17fd058033fa49c89dcbab5b826d3be3650b3a06
This reverts commit 888e79f7a0.
Reason for revert: The feature is planned in QPR2. This should be removed before QPR1 deadline.
Change-Id: I8af811935171d7ff51d9ba2a9ea60437695d7966
This reverts commit ade911b9c7.
Reason for revert: The feature is planned to run a study in QPR1
with the aim of launching in QPR-2. The code will be removed from
build time before QPR1 finalized.
Change-Id: Ida04260a1196121bb4084b527216aae1e4e6ec54
Apex name has been changed to com.android.btservices
Changing mount point accordingly
Bug: 235892590
Test: Flash / boot bt / look logs & pair a device
Change-Id: I8cff5f6449ee19466b3df571a40e062964a9e46c
The feature was superseded by tzdata mainline module(s).
Bug: 148144561
Test: m
Test: see system/timezone
Change-Id: I5f67e34e9beb608d3cf3c4c072b268805865f6dd
Merged-In: I5f67e34e9beb608d3cf3c4c072b268805865f6dd
The feature was superseded by tzdata mainline module(s).
Bug: 148144561
Test: m
Test: see system/timezone
Change-Id: I5f67e34e9beb608d3cf3c4c072b268805865f6dd
NetworkTimeUpdateService handles NTP time detection. timedetection (now)
has its own package. Change the package / update references before
proposed refactoring.
Bug: 222295093
Test: treehugger only
Change-Id: Ib5e5738325797dd4cda6c413bcfac8645b95bf59
Since Full Disk Encryption (FDE) is no longer supported, SystemServer no
longer needs to take FDE into consideration when deciding whether a
runtime restart has occurred.
Bug: 208476087
Change-Id: I5150f488f05a2d4ab3e5fcc2b92ec376a569e7e2
The feature punts to QPR so disable or remove code from the build
time.
Bug: 222185402
Test: build pass and can boot to home
Test: make sure the toolbar using local implementation
Change-Id: Idad82c3c46ddce0731a26f4599de01eecb0e52c3
