These two PermissionManager methods are using AttributionSource as
metadata only, and aren't interested in the remote caller enforcing
that the claimed UID matches the caller, since they're not actually
being used for permission enforcement.
Thus we pass the metadata using the AttributionSourceState holder
object and reconstruct on the remote side, entirely avoiding the
enforceCallingUid() check.
Bug: 193842956
Test: atest CtsPermission5TestCases
Change-Id: I576b6feb8cc2b0586b4341268866d8027689293f
This reverts commit f1564bc866b1c80fdd26bf2843b7f04735a3a252.
Reason for revert: We now know how to properly fix this
Fixes: 191727929
Change-Id: I6380796dd987b097fe6d9ad36123676b9861ba3a
1. Fix bug in the legacy code flow
- Obtain color from contextThemeWrapper Theme_DeviceDefault_DayNight
- In OneHandedDisplayAreaOrganizer#finishOffset()
Remove redundant call "cb.onStartTransition" due to
ambugiuous.
2. Improve performance
- Remove redundunt callbacks.
- Avoid create/remove leash on each start/end cycle.
- Dispatch Transaction to bkg leash through onAnimationUpdate()
bkg leash apply the same Transaction of display area.
- Adjust animation duration of Tutorial panel.
- Move bkg leash depend on yPos value to reduce SF
componsition overhead.
3. Improve code readibility
- Code flow : Register -> onStart() -> show background ->
detach background -> Unregister -> remove leash.
- Remove redundant synchronization due to wmshell already
guarantee thread safe.
- Move getTranslationFraction to SettingsUtil.
- Move getTransitionDuration to SettingsUtil.
Bug: 194507756
Bug: 193589897
Test: Local verify when changing dark theme and wallpaper theme.
Test: atest WMShellUnitTests
Change-Id: Ib55753be9e9f4665c20ad34437f86bf80cc9f3b4
The GestureLauncherService is used to detect camera and sos emergency
gesture by multi-pressing power, if it intercept power key, we should
return the intercept state that could prevent the following detector
processing the power key cause unexpected single tap.
Bug: 194522413
Test: keep pressing power to see if screen would turn off.
Test: atest GestureLauncherServiceTest
Change-Id: I3db7390df720f24f9b312946b1d8e01d672e6ef3
Fix bug where phone could not unlock if guest user was being created in
the background.
This bug only affected devices with config_guestUserAutoCreated=true.
Test: In scheduleGuestCreation, replace createGuest() with
Thread.sleep(20000). Ensure device can be unlocked within a few
seconds after killing sysui process.
Bug: 194531015
Change-Id: Idc86a7afdb58a64baa3725d8aa56d7c93a409662
Previously, test would fail on wembley with the following errors:
- No service published for: fingerprint
- No service published for: face
- java.lang.AssertionError: expected:<1> but was:<0>
Fixes: 191280089
Bug: 194441567
Test: atest SystemUITests:com.android.systemui.statusbar.policy.UserSwitcherControllerTest
Change-Id: I34539a5e9678b308b4d3a03e4593fb9385e7831f
Merged-In: I34539a5e9678b308b4d3a03e4593fb9385e7831f
Also removes the 'getPulseStackHeight' method which didn't solve any of the issues it was added to solve, and only introduced an issue when expanding a pulse on bypass device.
Fixes: 194513502
Test: on bypass device, expand QS; validate that notifications do not disappear at the bottom.
Test: on bypass device, receive pulse; unlock via bypass; validate that pulse seamlessly transitions to hun.
Test: on bypass device, expand shade from lock screen; validate that notifications all fade in at once, rather than appearing in sequence.
Test: on bypass device, receive pulse; drag to expand it; validate that other notifications appear in sequence, rather than popping in all at once. (Note, this is non-ideal behavior which has always existed, not a regression. ideally other notifications would fade in.)
Test: on non-bypass device, receive pulse; biometric unlock; validate that notifications smoothly animate to open shade.
Change-Id: I8d0968f5a8632bba6b1db5940b933ee53b2abb8a
Parcel implementation would crash the system server otherwise.
Any exception is OK as it'll cause the cache to be invalidated.
Crash is not OK.
Bug: 194632313
Fixes: 194632313
Test: atest PackageParserCacheHelperTest
Change-Id: I58a4496b4646e172e6c3aee9ea17854a7ef55eaa
The original java implementation just passed along whatever the server
returns which is -1 on unsupported devices. So do that here as well.
Test: PerformanceHintManagerTest passes on unsupported device
Bug: 194691581
Change-Id: I8ac07737e6ce52debf55478880d71f038f258056
In order to leave more space for carrier names in QS, do the following:
* Remove enterprise icon from QQS/QS icons
* If screen is less than 390dp wide, don't show battery estimate and
instead show percentage.
Test: manual, multiple densities and landscape
Fixes: 189413614
Change-Id: I4758d3822dc07e42b254b8b48c9905231748165a
In our proximity sensor, ignore events coming from the Primary sensor
when the Secondary sensor can be used instead.
Fixes: 193412708
Test: atest SystemUITests
Change-Id: I763b5541a92956c96445d2d9b3144956cbdccc9a
Bug: 157639992
Test: m droid
Test: Manually verified that libcore's module-lib API is in the generated out/target/common/obj/module-lib-api.xml
Merged-In: I435140f19a0f5a81310154728c828ac70e12192a
Change-Id: I435140f19a0f5a81310154728c828ac70e12192a
(cherry picked from commit 6b107a93e1d5a09e12fcf3f0b92e6514f55fc6b2)
Android 12 has so many new colors. But which to use?
Sounds like you might need some PAINT CHIPS! Stop by your
local hardware store, where you'll find them in the paint
aisle. Grab as many as you can hold---they're free! When you
get home, hold them up to your app or appwidget and see how
they look in different lighting and against different
wallpaper. You'll be soothed by the neutrals and piqued by
the accents!
Test: To enable the widget and activity, use the platlogo, or:
$ adb shell settings put system egg_mode_s 12345 && \
adb shell am start -a android.intent.action.MAIN \
-c com.android.internal.category.PLATLOGO
Then you should be able to add the widget to the
launcher, as well as:
$ adb shell am start -n com.android.egg/.widget.PaintChipsActivity
Bug: 177962166
Change-Id: I0f3907c86f881d92a14d7659388f6a56154d8c10
