Not able to reproduce what's in the original bug report, this null check
is added as a safe guard. A possible scenario is
PipTaskOrganizer#exitPip is called twice and there is a race condition
that the first applySyncTransaction is not ready yet and leave the
internal state as it was, the second call tries to get configuration and
it is null, which leads to a NPE.
Bug: 169173459
Test: N/A
Change-Id: Ie5292e8749bc186fba930dfee59c26d10ea680cd
When setNightModeActivated is called, the change affects the current logged in user
Also, permission checks are made before changing dark theme
Test: manual
Bug: 168039904
Merged-In: I7786d9dde10f7547f5dd9fb00661fb89fde9f05c
Change-Id: I7786d9dde10f7547f5dd9fb00661fb89fde9f05c
(cherry picked from commit f16e87a992)
This allows headless media applications to access the location if they
have the permission and is needed for AAOS apps in particular.
Bug: 169242810
Bug: 156904507
Test: manual with AAOS Media app
Change-Id: I1196718638fba336a815809578f643814545baf4
Bug: 165267251
Test: manual -- ensured that the time needed to hold is 0ms if the
screenshot_keychord_delay debug value is not set, and that the
delay can still be changed using
adb shell device_config put systemui screenshot_keychord_delay <ms>
Change-Id: Iab989ecf14ef379658130adbced241e084554e63
Merged-In: Iab989ecf14ef379658130adbced241e084554e63
(cherry picked from commit bf82822698)
Allows overriding the configured keychord delay (the time it takes,
after both the power button and volume down have been pressed, for
a screenshot to be registered/taken). If not set, reads from the
config file (as before). Can be updated with
adb shell device_config put systemui screenshot_keychord_delay <n>
where <n> is the desired timeout, in ms.
Bug: 165267251
Test: manual -- tried setting multiple values, ensured that deleting
the override reverts to the configured value
Change-Id: I2f86abe0332f8072ab4f53baa55f1999aed3865a
Merged-In: I2f86abe0332f8072ab4f53baa55f1999aed3865a
(cherry picked from commit 6e44e9d5b4)
Screen decors is not well supported in WM since
PRIVATE_FLAG_IS_SCREEN_DECOR is no longer supported.
Bug: 169115543
Test: atest ScreenDecorWindowTests
Change-Id: I27cdc1d882f770b1567984ffbda6b55ce6f41c69
This solves the issue where the device would forget the learned state
when restoring from a backup.
Test: Tested locally
BUG: 159807978
FIX: 159807978
Change-Id: Ia1d5926621c4b45402036aaf06cbab19c12869bd
Merged-In: Ia1d5926621c4b45402036aaf06cbab19c12869bd
Bug: 160161606
Test: Switch darkmode serveral times and verify there aren't
old refs in the heap dump
Change-Id: I1678d10e725f6bdcbc807064413b4bc549ef8ef2
Merged-In: I1678d10e725f6bdcbc807064413b4bc549ef8ef2
(cherry picked from commit 469a3084b7)
Cancellation was not being propagated to the system server due to a
misunderstanding on how CancellationSignal functions. There is no
noticable impact for the user, as cancellation did properly prevent any
further locations, however this would have resulted in extra
power draw since the system server would not have canceled the
associated provider location request. This would have left
getCurrentLocation() as equivalent to requestSingleUpdate() where it was
supposed to be an all-around improvement that could save power.
Bug: 168666216
Test: manual + presubmits
Change-Id: I5c77db4cc56cce1b984587f65d2bcfb488436bb8
1. So that the IME position won't be affected by the status bar
position.
2. When status bar is hidden, the fullscreen IME can fill the status bar
area.
Since IME can be behind status bar now, we set the status bar color to
be transparent, so that there won't be a visible color view at the
status bar area.
Fix: 168657591
Test: 1. Steps in the bug.
2. Play WindowInsetsTests with combinations of system bar
visibilities, navigation mode, screen orientation, and display
cutout.
3. Show/hide status bar while IME is visible, and see if there is
any flicker.
Change-Id: Ia133a62cfa98c47c0d3f8d118947a18246dd8d4f
- IMEs would like to receive touches that are near the bottom
of the screen under the nav bar so we should allow this
Bug: 168552683
Test: Verify touchable region from dumpsys input in all nav
modes w/ ime switcher
Change-Id: Ic2ee8cc8ce59c4025c6730195d6e1050daddf87a
Merged-In: Ic2ee8cc8ce59c4025c6730195d6e1050daddf87a
(cherry picked from commit fc53675a40)
Views were not properly getting reinflated due to font/display size
changes. When this happens, remove the views and recreate them.
Fixes: 168812862
Test: manual, follow bug steps
Change-Id: I1390110f33eb9ac9a7c616fbde281186c34d2f3d
As WMS#mForceDesktopModeOnExternalDisplays is a flag to force enable
desktop mode on public secondary display.
Since some code points didn't check if the display is public
& secondary display, it may cause some issues like Bubbles using
private virtual display but the content can show system decorations and
IME always failed to show, if user enabled force desktop mode config
from developer option.
Add DC#forceDesktopMode to make sure the check is proper and consistent.
Fix: 163333691
Test: manual as test steps:
1) Enable "Force Desktop Mode on External display" from Settings ->
Developer option.
2) Launch Message or FB messenger with chat head bubbles
3) Taping EditText and check if soft-keyboard can show up correctly.
Test: atest DisplayContentTests#testForceDesktopMode
Merged-In: I6ec52b6b1642fd547ebc222ae1bf9a2958e5fb2d
Change-Id: I6ec52b6b1642fd547ebc222ae1bf9a2958e5fb2d
bug: 157104172
Test: m gcar && emulator; cts-tradefed run cts -m CtsPermission2TestCases -t android.permission2.cts.PrivappPermissionsTest
Test: With a package set as <install-in user-type="FULL" />, but not SYSTEM, run: adb shell cmd package get-privapp-permissions <packagename> and get the expected output.
Change-Id: I816fc36b448856a0e0244211549b54e0a95f277e
the non-SDK API list to the blocklist in Android 11 back to the non-SDK
API list.
Tag: #feature
Bug: 168812851
Test: atest BluetoothHostTest#testCodecMethodsAccessible
Change-Id: I29983284b1a1c271d983c99b286e204604abdc72
