Move system_icons_super_container_margin_start to parent ViewGroup
to ensure both multi_user_avatar system_icons_container can share
the padding
Test: make and check visual, enable multi user and check keyguard
Bug: 194324044
Change-Id: Iab2803dfb2b609b98eb8053e3b81bd6731857a2b
Starting in R, some methods in ConnectivityManager like
getNetworkCapabilities started passing the package name from
the context stored in CM to check that the package is really
whom it pretends to be. Unfortunately, in some cases, the
context contains package "android" for an app, and since the
app is not the system, the check fails and crashes the app.
It seems the culprit is updateHttpProxy, which is called by
ProcessList when the PROXY_CHANGE_ACTION broadcast is sent.
If this happens to run between the time the process is created
and the activity thread is "bound", then the mInitialApplication
member is not set, and updateHttpProxy uses a system context.
Since ConnectivityManager caches the context forever in a
static, this leads to subsequent legitimate calls crashing.
Setting the proxy can be deffered until such a time that the
app is bound, as it can't run any code before then. The member
is never reset to null, so it's guaranteed to be non-null at
bind time.
An alternative would be to post a runnable on the handler
thread if the member is null to try again later. This
could however run the lambda a considerable number of times
as binding can be delayed, and risks causing an infinite loop
if some invariants are changed in the future.
See also b/73572062 and ag/4056059
Bug: 155549446
Bug: 189360509
Test: ActivityThreadTest FrameworksNetTests NetworkStackTests
Test: Manually set a proxy, observe the broadcast being sent and
apps not crashing
Change-Id: I956f76be2e0a1a675576511fb394d7ed4354b28a
(cherry picked from commit b0d13e29515d5b7c82daed7533b78ac57e46bd93)
It is possible to receive SIM events that alert the keyguard to show
the SIM PIN unlock screens. However, if these events are received
after keyguard has been told to dismiss but before it is actually
dismissed, this event gets ignored.
The fix: add a flag to look for this state. If we get the keyguard
dismissed event and the bouncer has not shown, bring back to the
keyguard.
Fixes: 192048149
Test: atest KeyguardViewMediatorTest
Change-Id: I43de785252827d78a86d075ee7ec0861778e3360
Only setDeviceEntryIntent=true if we're on the lock screen (not on AOD).
We do this b/c the tap on the udfps area on AOD could have been an accident.
Test: manual, UdfpsControllerTest
Fixes: 194921838
Change-Id: Ief2518f88f27fae01abe4bd72cb677b03e4e525a
When we migrate a partially loaded app off incremental, the incomplete
progress could still be reported by incfs, right before the incfs
instance is deleted. This partial progress could override the full
progress reported by the update installation. And after the incfs
instance is deleted, there will be no more progress update. As a result,
the launcher gets the last progress update as a partial progress, and
the progress loading icon remain partially loaded until reboot.
This CL fixes the problem by rejecting partial progress reported from
incfs after the progress has already been changed to 100%. In reality it
could only happen during off-incfs migration. It also applies in general as
the progress number should never go from 100% to below 100%.
BUG: 187762951
Test: manual
Change-Id: I3b87226a4e75d71f0d8e4886917e4456b355e1fa
Ensure that the logical display is valid before calling getPrimaryDisplayDeviceLocked() on it first.
Bug: 194542389
Test: Manual
Change-Id: I788527a3cd02fcc12efe0b8d84e26d5d66f53762
This reverts commit 002e656a51.
Reason for revert: Setting brightness using adb (adb shell settings put system screen_brightness ...) results in different brightness being set by DisplayPowerController each time.
Bug: 194791517
Test: atest HighBrightnessModeControllerTest
Test: manually test `settings put system screen_brightness 23` yields
consistent results
Change-Id: I6b49253b46e4d09a1f4129d3df950c9d36eb6ede
It was skipped to reduce rotation latency. But it may look
flashing if the top app is redrawn much faster than the
notification shade or the background colors are not similar.
Bug: 194610242
Test: Expand notification shade and rotate device while the
foreground app can handle orientation change quickly.
Change-Id: I1a4870d9f237bad9088159f5979048b4cdcbf287
To get around a race in InputDispatcher between the removal of the input
channel throught nativeRemoveInputChannel and the InputChannel#dispose
call, we remove the former call from InputManagerService.
This means it is now the responsibiity of the client to properly close
the input monitor by disposing of the InputChannel and all of its
duplicates.
Bug: 189135695
Test: manually try to reproduce the flaky conditions through a shell
script
Change-Id: Iba9f7c2428229ff6e2a7450a39828aed61160a3d
