Age | Commit message (Collapse) | Author |
|
Change-Id: I2325ba5c76e7dba314bdcd5b53fdc36b5e90fb31
|
|
Bug: 220074017
Change-Id: Idfdd94e902f656ac65a2a75dfdd199f6f85ba472
|
|
Before this CL, SystemUiContexts were fixed to the Display metrics
when the SystemUiContexts were created. It is the same mechanism
as DisplayContext but applies to SystemUiContexts unexpectedly.
This CL makes SystemUiContexts associate with DisplayContent with
the corresponding display ID. In this way, SystemUiContext would
receive updates when there is a Display property change.
Bug: 220022170
Bug: 194262507
Bug: 191064581
Bug: 205859784
Test: atest InputMethodMenuControllerTest WindowContextControllerTest
Test: atest NexusLauncherTests
Change-Id: I64a1614f32d097785915f6105b1813a929e0fe32
(cherry picked from commit 46ffd51d0723ad18b82d1093814ed7995996c8b9)
|
|
Bug: 205836329
Test: atest AdbDebuggingManagerTest
Change-Id: If18a874c6d6232d9131f2cc3de3614ef67a58bbd
(cherry picked from commit b139e9966102ba6fa1a4801214ea92e8afe376a6)
(cherry picked from commit dc7d96c9e50fb2cc38c1c53eb03b975f6de9d0e7)
Merged-In:If18a874c6d6232d9131f2cc3de3614ef67a58bbd
|
|
Without this fix, after display density change, clicking size compat
restart button won't relaunch the app in new density.
Fix: 214339093
Fix: 209389023
Test: atest WmTests:SizeCompatTests#testClearSizeCompat_resetOverrideConfig
Change-Id: I6db7a2c2250c17d735938acc84e39d883d466aa6
(cherry picked from commit a9c24f5e8e2f8868c4a0d783678e83ebf2e08817)
Merged-In:I6db7a2c2250c17d735938acc84e39d883d466aa6
|
|
This was changed in ag/15886711, but it shouldn't be needed anymore as
for case we need to animate the close transition, isVisible() will stay
true until the app transition is finished. Otherwise we shouldn't need
to keep the surface as visible even if it is in the closing app list.
Without this fix, we may accidentally show the surface that has been
commited to be invisible, such as enter pip onUserLeaveHint.
Fix: 216145863
Test: manually verify with Google Meet.
Test: atest WmTests:ActivityRecordTests
Change-Id: Ib28651f5c4dc728d19f968adc56015836e307ef8
Merged-In: Ib28651f5c4dc728d19f968adc56015836e307ef8
(cherry picked from commit 0207f039d25eece5f04512bfc1198ef72e5c2e4f)
Merged-In:Ib28651f5c4dc728d19f968adc56015836e307ef8
|
|
CL[1] to add InsetsStateController#updateAboveInsetsState in
DC#updateImeInputAndControlTarget that after setting
mImeInsetsFrozenUntilStartInput as false to unfreeze IME insets,
so that increases the possibility to deliver the last IME insets
change to non-IME input target window that didn't request show IME.
(Since updateImeInputAndControlTarget will call
WindowState#insetsChanged to client eventually)
As typically the new IME insets change will deliver to the client when
server receives InsetsStateController#onInsetsModified(InsetsControlTarget)
from the client requests IME visible after
DC#updateImeInputAndControlTarget.
So in DC#updateImeInputAndControlTarget, we should ensure to unfreeze
IME insets after the input target updated, in case updateAboveInsetsState
may deliver unrelated IME insets change to the non-IME requester.
[1]: I57357ba85501397fa5926ab4dee116c42df24506
Bug: 213522825
Test: atest ActivityRecordTests#\
testImeInsetsFrozenFlag_noDispatchVisibleInsetsWhenAppNotRequest
Test: atest WindowStateTests#\
testAdjustImeInsetsVisibilityWhenSwitchingApps
Test: Verify Bug 195385541 and Bug 195846009 that keyboard
won't cover the edit text.
Change-Id: I95c5b45bd4cf9c30ff7771b2db485c8ae2b0c6db
(cherry picked from commit 938eb8fd2ded04bbcd5f32576a7bb4eaf186d56a)
Merged-In:I95c5b45bd4cf9c30ff7771b2db485c8ae2b0c6db
|
|
|
|
...only when the Task has no more running activities.
Send a TaskFragment info changed callback if the
callback is for the last activities to finish in a
Task so that the TaskFragmentOrganizer can delete
this TaskFragment. Otherwise, the Task may be
removed before it becomes visible again to send this
callback because it no longer has activities. As a
result, the organizer will never get this info changed
event and will not delete the TaskFragment because the
organizer thinks the TaskFragment still has running
activities.
Bug: b/214090984
Test: atest TaskFragmentOrganizerControllerTest
Test: atest ActivityEmbeddingLaunchTests
Change-Id: Idb58975f4bfb6c67ed6cda3dc6b7c33abd960bbd
|
|
* changes:
DO NOT MERGE Revert "[2/n] Camera Compat UI: Add interfaces for client-server..."
DO NOT MERGE Revert "[3/n] Camera Compat UI: Add a camera compat control."
DO NOT MERGE Revert "Log the CameraCompatControlEventReported atom."
|
|
am: a4b7960b60 am: 7c7930e536 am: a3426965e2" into sc-v2-dev
|
|
client-server..."
Revert submission 16468379
Reason for revert: Feature development is moving to T.
Reverted Changes:
Id9b9a8930:[3/n] Camera Compat UI: Add a camera compat contro...
Id6be4a954:Enable a camera app compat control on Large screen...
I083aa6718:[2/n] Camera Compat UI: Add interfaces for client-...
Bug: 206602997
Change-Id: I9ad876043fd61f708a8f468fffd1ef371bfa0866
|
|
|
|
a4b7960b60 am: 7c7930e536 am: a3426965e2
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1937410
Fixes: 212652242
Change-Id: If85c2cc2697056256b440b2e5db89cf035a8f2e8
(cherry picked from commit dad4818bdcd777e245494aa9ee503c971f1a00a9)
|
|
setBlocked is a hidden API, so apps should not be calling
the method, but fix up the data in case they do
Test: PreferencesHelperTest; manual with ApiDemos FGS
Bug: 209966086
Change-Id: Icc709a6b0d0a8c5f2d9243959992f1b6764354db
Merged-In: Icc709a6b0d0a8c5f2d9243959992f1b6764354db
|
|
The generic pattern coded in the notification service ignores the user
settings for vibration intensity because of the current PWLE
implementation in Android S.
Moving this to a device-specific configuration (empty by default). Each
device-specific pattern should be designed to accomodate the vibrator
frequency response curve that will be exposed by the Vibrator API.
Fix: 212366218
Test: VibratorHelperTest + manual
Change-Id: I8807ede4a13e4880f51a0075ff7c658724649265
Merged-In: I8807ede4a13e4880f51a0075ff7c658724649265
|
|
|
|
|
|
Before allowing the group to be deleted, by updating
the current check to the method that populates the channel
list
Test: NotificationManagerServiceTest
Bug: 209965481
Change-Id: I9db781c300e96e9c80bd5d21585b8be9b4db08c8
Merged-In: I9db781c300e96e9c80bd5d21585b8be9b4db08c8
|
|
transiently" into sc-v2-dev
|
|
|
|
Change-Id: Ie250e3592a53519f58f691675a61adf7fddc335c
|
|
(Cherry-picked from sc-qpr branch)
Bug: 199933856
Bug: 212462949
Test: Manual
Change-Id: I13c5986e28e7a1a9277518ca96da9a22c5e1c21e
|
|
(Cherry-picked from sc-qpr branch)
Test: Manual
Bug: 191608501
Bug: 212462949
Change-Id: Ib3ff55ab509b5794e2ed0aa0b3a805a6baee8246
|
|
|
|
- This won't be needed in T when immersive mode gestures are moved
to SysUI (b/161689946)
Bug: 208886351
Test: atest SystemUITests
Test: In both 3button/gestural (all orientations), swipe from bar
areas, swipe from sides show entry point only when swiping over
bars
Change-Id: Ie8f15a5fbd3248bc86a50ffcd1fc73cd08c4e214
|
|
Fix deadlock issues by ensuring that calls to activity manager and
package manager are done without holding the hibernation lock.
This will loosen some guarantees on the hibernation state (e.g. there
may be a brief period of time where an app is hibernated but not
force-stopped), but none of the callers currently need that strong
guarantee.
Bug: 196535754
Test: atest AppHibernationIntegrationTest
Test: atest AppHibernationServiceTest
Test: adb shell cmd jobscheduler run -u 0 -f
com.google.android.permissioncontroller 2
Change-Id: Ic67d9a93565a935c077707e3c34a4c6605f041d1
(cherry picked from commit d41db18129f4119218c6eda21a7d51c0313b18c1)
|
|
When an activity is resumed, it will call to pause the activity behind,
which can cause a loop of resume/pause if the top resume activity is
translucent.
Fix: 209356462
Test: atest WmTests:TaskTests
#testResumeTask_doNotResumeTaskFragmentBehindTranslucent
Change-Id: Id9bf75c4e623fd382a5ca619ea742a1e86059ec2
|
|
Verifies that printing domain verification state asserts that
the caller is an approved querent, to match the
getDomainVerificationInfo Java API.
Also allows callers with the DUMP permission to be a querent, so that
dumpsys package still works.
Bug: 200035185
Test: atest DomainVerificationEnforcerTest
Merged-In: I9ad409ba15ce1a358ca8c0e047444a2fa6d2140b
Change-Id: I9ad409ba15ce1a358ca8c0e047444a2fa6d2140b
(cherry picked from commit e466493f72c05a607fc3de1fac9f8d943e5f6729)
|
|
CL[1] fixed the IME flickering issue when switching recents tasks with
specifying to set IME relative layer until the layering target is not
animated and be IME control target.
However, it didn't consider the case that the IME layering target could
be the drop down box window that not same as the IME control target,
so that the issue happens when we didn't set IME above this window,
the app drop down box will be above IME and cosumed the input to hide
the keyboard.
Fix this regression by checking the token of the layering target to set
IME relative layer if the target isn't transitioning and same as the
token of the control target.
[1]: Iae65d6047c02dae241f2df21c666a03cca58fd0b
Fix: 209722479
Test: manual as test steps
Test: atest ZOrderingTests#\
testAssignWindowLayers_ForImeOnPopupImeLayeringTarget
Change-Id: Id2e700c20b964e296576c49391853b680418bf57
|
|
Previously, it was implemented based on java.util.Timer, which uses a
wall clock. That is problematic, because that clock doesn't stop when
the system goes to sleep, and so if that happened in the middle of
executing soundtrigger HAL code, the watchdog would fire as soon as
the system woke up.
This change implements the watchdog using an uptime-clock-based timer.
Fixes: 199798343
Test: atest FrameworksServicesTests:com.android.server.soundtrigger_middleware.UptimeTimerTest
Merged-In: I913336837aff3e2c74c77f32aac24348612803f9
Change-Id: I5ce6ba997a7af616785634223af8c6139d030111
|
|
|
|
Change-Id: Ic2889f5eb531008340529eadc36ec8efc62b1984
|
|
|
|
|
|
Make sure all windows with its frame overlapping with navigation bar can
declare light navigation bar color no matter if it's dimming or not.
Fix: 205308712
Test: atest DisplayPolicyTests
Test: verified dimming window with its frame overlapping with navigation
bar can declare light navigation bar color.
Change-Id: I6269547f0dfcd54568fd4f07b2642258f93a2822
|
|
- This ensures that the caller can synchronously initialize the existing
displays without waiting for the onDisplayAdded() callback, which can
happen asynchronously (since the callback is oneway).
Bug: 207083059
Bug: 196186963
Test: atest WMShellUnitTests
Test: atest ActivityTaskManagerServiceTests
Change-Id: I0a8d5f9b4ede7b487a8de14bdb6eaacae7d03d9f
(cherry picked from commit 851f1df2f1766b998467a276b0973dbfe1706853)
|
|
throttling interval""" into sc-v2-dev
|
|
throttling interval""
This reverts commit db71562964d5e5862ee08274bf3d2e0dca58a6fb.
Reason for revert: Real root cause found, reverting to original code.
Change-Id: I69df43954a37bb935479cbcb8eae81e8d75c7714
|
|
* changes:
[3/n] Camera Compat UI: Add a camera compat control.
[2/n] Camera Compat UI: Add interfaces for client-server communication.
|
|
into sc-v2-dev
|
|
This reverts commit 943c8287f887ad757b904f55bb7da442857ce093.
Reason for revert: Possible root cause for b/210934408
Change-Id: I1ad30012d062342f21752fcc763e7973d1d1a118
|
|
Changes:
- Listens to changes from the client coming through IActivityClientController#requestCompatCameraControl to ActivityRecord#updateCameraCompatState
- ActivityRecord#updateCameraCompatState sends updated state via TaskInfo to WM Shell
- ITaskOrganizerController#updateCameraCompatControlState to dispatch the user interactions with the control from WM Shell triggers callback to ActivityRecord#updateCameraCompatStateFromUser
- ActivityRecord#updateCameraCompatStateFromUser remembers the user's choice and asks client to apply treatment through ICompatCameraControlCallback
Feature is guarded with config_isCameraCompatControlForStretchedIssuesEnabled
Test: atest WMShellUnitTests:ShellTaskOrganizerTests, atest WmTests:ActivityRecordTests
Bug: 206602997
Change-Id: I083aa6718bd67456bedd9444e9b78740c041f870
|
|
|
|
frame" into sc-v2-dev
|
|
The extra navigation bar should be treated in the same way as the
navigation bar to avoid compatibility issue. There are devices only
contain an alternative extra navigation bar but not the default
navigation bar. The app may receive conflict information from the insets
system and the window configuration in that case.
Test: CtsWindowManagerDeviceTestCases (on device with task bar)
Bug: 205496695
Change-Id: Idef3d09c723ffcd67372db29fc0cc51a59cc0aa1
|
|
The stationary throttling location provider should not attempt to
deliver location more than once a second while throttling.
Bug: 206340085
Test: atest StationaryThrottlingLocationProviderTest
Change-Id: I6928546900ea1c0c744ecb33f8db35a402830837
(cherry picked from commit f2eeda7d8795773cd22375ebfc1d2ce1b70aeccf)
|
|
Change-Id: If7c68a17857eee4194f28413b938d5647820162c
|
|
|
|
relinquishTaskIdentity" into sc-v2-dev
|