sendBroadcastToAll is a duplicate broadcast of MASTER_MUTE_CHANGED_ACTION. The same broadcast is called by sendMasterMuteUpdate.
Test: make
Bug: 144352459
Change-Id: I0f5283fe35521f04c04c159d42bd907fccfb226f
(cherry picked from commit 1ae52c25c81bab7d0aa5c1994ea604a4836027eb)
ACTION_USER_ADDED is a broadcast that is sent once when the user is
created. TrustManagerService resolves the enabled trust agents for an
user only when the user is created. However, if there is a reboot or
power loss before the broadcast is received, the trust agents are never
resolved for that user.
This change also registers for ACTION_USER_STARTED, so the service
checks for enabled trust agents on every boot. If the trust agents have
been already resolved and initialized for that users, there is already a
Secure Settings key (TRUST_AGENTS_INITIALIZED) that is turned on, so we
wouldn't be doing this more than once per user.
Bug: 150145767
Test: TrustManagerService resolves trust agents only once - either on
USER_ADDED or USER_STARTED.
Change-Id: I83c2dd02d4b476f8b85af1aa4d9d0c77095207ce
Devices with a DisplayCutout configured may want to add some extra area
of turned-off pixels around the cutout in order to keep light from
leaking into camera hardware. This CL adds two new config values to
sysui to enable the configuration of this cutout protection, and listens
for CameraManager events telling us that a relevant camera has turned
on.
Test: manual
Bug: 145095085
Change-Id: Ifce67a593247e3a2151d41800ae46a50478e0b7d
Assume there are 2 applications A, B with different uids.
There are 4 activities A1, A2, B1, B2 with default task
affinity and launch mode.
After A1 called startActivities(B1, A2, B2):
Original : Task(A1, B1, A2, B2)
This Change: Task(A1, B1), Task(A2, B2)
In other words, the source caller cannot launch its activity
above the activity of other application in the same task, and
it can still launch activity of other application in its task.
Bug: 145669109
Test: run cts --test android.server.cts.StartActivityTests \
-m CtsServicesHostTestCases
Change-Id: I97bd875146a52f62b8fe82235487ccefb2955e8e
Assume there are 2 applications A, B with different uids.
There are 4 activities A1, A2, B1, B2 with default task
affinity and launch mode.
After A1 called startActivities(B1, A2, B2):
Original : Task(A1, B1, A2, B2)
This Change: Task(A1, B1), Task(A2, B2)
In other words, the source caller cannot launch its activity
above the activity of other application in the same task, and
it can still launch activity of other application in its task.
Bug: 145669109
Test: atest StartActivityTests# \
testStartActivitiesWithDiffUidNotInSameTask
Change-Id: I97bd875146a52f62b8fe82235487ccefb2955e8e
Make sure that opening the notification panel doesn't result in a "blip"
in the nav bar visibility
Bug: 147427386
Bug: 149021759
Bug: 149115608
Test: on hawk
adb shell settings put global policy_control "immersive.navigation=*"
swipe up from bottom of screen - make sure it autohides
pull down notification panel - make sure the panel doesn't blip
on sdk_gphone_x86 - atest SystemUITests
Change-Id: I4b5244e5ff26fb23e687cd46bc105d4fb8251bc6
Suppose vendors will customize rounded.xml with corresponding
multiple radius path and size, ScreenDecorations should not resize it
by rounded_corner_radius in case jagged edges problem
Test: atest SystemUITests
Test: atest ScreenDecorationsTest
Bug: 145707162
Bug: 148912090
Change-Id: Ie33526214072ad324ca00a10074ad212dfbf4258
Put the background drawable on status_bar_container instead of
status_bar because we always want the status bar background to
fill the entire container.
status_bar receives new margins when corner display cutouts are enabled
which may prevent status_bar from taking up the entire
status_bar_container space.
Test: atest SystemUITests
Bug: 148355955
Change-Id: Ic7e0c0a79908d2a58d4595d239062435253edfda
This allows new phones to use a sensor with a different
theshold when attempting to determine the devices proximity
to surfaces.
Bug: 149420648
Test: manual
Change-Id: Iee8568f7d9f58359dc1e72fd195a42abeaf2ddf3
Register a receiver that listens for Intent.ACTION_CLOSE_SYSTEM_DIALOGS
and dismisses the volume UI when such an intent is received.
Bug: 149228466
Test: Manual
Change-Id: Iabb706b1d4cc54cb84f228aad95bfdb7e6f75851
Update keyguard locked state from TrustManagerService
TrustManagerService holds the ground truth about whether a user is
locked or not, so update keystore using the information there,
instead of doing it from KeyguardStateMonitor. This fixes the issue
of work profile locked state not being correctly pushed to keystore.
Note: since this change is likely to be backported as a security
patch, I'm refraining from doing major refactoring right now.
Bug: 141329041
Bug: 144430870
Test: manually with KeyPairSampleApp
Change-Id: I3472ece73d573a775345ebcceeeb2cc460374c9b
Applying theme on start
update system properties on startup to apply the updates
Fixes: 149441632
Fixes: 149385662
Test: UiModeManager tests
Change-Id: I7f71e27a43eb24be833b3003340653fefc75d0cc
Merged-In: I0bee6517b39216146681097262cf55c7192b0131
This fixed the keypad remains ON when switch facet issue.
BUG: 130573446, 149228466
Test: Manual
Change-Id: Ia449fb41a03bc02498471ded660d573d5b1ad141
(cherry picked from commit 82298783683ebe82a5847dfd35fc8b3528709930)
(cherry picked from commit ebff32a5d6)
Previously, while restarting the Navigation Bar, we omitted the step where we
apply the selection state that reflects the current task stack.
This omission caused CarFacetButtons to lose their selection state on
certain events, such as the day/night toggle.
Bug: 148211695
Test: Manual -- Verify that the selection state is preserved between
day/night toggle.
adb shell dumpsys activity service com.android.car/.CarService day-night-mode day
adb shell dumpsys activity service com.android.car/.CarService day-night-mode night
Change-Id: Ic07b8b66aa531436ce4f23d56bb3c11a79b7cb46
Add padding from cornerCutoutMargins.
Test: manual on device with and without cutout
Fixes: 147708367
Change-Id: I21a9b71c34664982b4e14dd4372638e405a5046e
Merged-In: I665c8c76a2a057e9a30bce7c28fdbe7a249bb5c2
Force displaying system bars can cause app screen compatibility issues
in non-Automotive Android.
Bug: 148407132
Test: CTS Test + Unit Tests
Change-Id: Ia433572650760e3b85954724c63084dca769eaa0
Merged-In: Ia433572650760e3b85954724c63084dca769eaa0
We nullify mWorker right in ImageWallpaper#destroy(),
we might get NPE if postRender is invoked later.
Thus, we add null check to avoid NPE.
Bug: 144039509
Bug: 146167292
Test: atest com.android.systemui
Test: atest CtsMultiUserHostTestCases
Change-Id: I209673bdac7dcfee765006568583b5a9d6037b95
Merged-In: I243274af54538fc89268c448aa2c5a95f63c7ae3
If the Keyboard is shown, then margin bottom is 0.
Otherwise, the margin is the height of the NavBar.
Bug: 149022190
Test: Manual. Verify that NotificationView's margin adjusts based on
whether keyboard or IME is shown.
Change-Id: I96c50a4d773dfac9b57ab1c15cfc59d315da4605
Voice Assistant can be disabled on a user-level. Adding this null check
prevents crash for when Assistant is enabled for the system in general but
disabled for a specific user.
Bug: 149112015
Test: Manual -- Change config_disableLockscreenByDefault to true to
emulate the environment in which Volvo observed the bug. Verify that
switching to user0 through adb shell switch-user 0 causes the same crash.
Verify that the crash does not happen with the new null check.
Change-Id: I5b8ede1e5bd8c1bc047bc6d6220b425dea8f50ea
Merged-in: I5b8ede1e5bd8c1bc047bc6d6220b425dea8f50ea
