Age | Commit message (Collapse) | Author |
|
into sparse-9595452-L55900000958663479.
SPARSE_CHANGE: Iea66d7782b3365dea827b854783aeddaa5c6699c
Change-Id: I744b6d718affa4026a676f92b76c016b36d07592
|
|
This reverts commit ff09044d12f936bab51ed9e7d33016616ce9e87e in
addition to partially reverting ag/20141372.
Reason for revert: b/245778799
Change-Id: Iea66d7782b3365dea827b854783aeddaa5c6699c
(cherry picked from commit 7fd68c74a7fd46c9f460593aa54d03c1d60016fb)
Merged-In: Iea66d7782b3365dea827b854783aeddaa5c6699c
|
|
into tm-qpr2-release.
Change-Id: I042b10ae9f7bd15df457864df9545ff3c584da9a
|
|
This adds validation that the package name passed to
setApplicationRestrictions is in the correct format. This will avoid
an issue where a path could be entered resulting in a file being
written to an unexpected place.
Bug: 239701237
Merged-In: I1ab2b7228470f10ec26fe3a608ae540cfc9e9a96
Change-Id: I56c2fc14f906cdad80181ab577e2ebc276c151c1
(cherry picked from commit 1b9b59c63bffc675a042cba6cd666831abef2c3e)
Merged-In: I56c2fc14f906cdad80181ab577e2ebc276c151c1
|
|
'googleplex-android-review.googlesource.com/21116839'] into tm-qpr2-release.
Change-Id: I3a1a2ca5006b81b4c3bef31af915be727da22db6
|
|
Revert "Change volume ringer icon based on device config"
This reverts commit 903b3025a7e5caaddae848376bd12b62e698315c.
Reason for revert: b/261809910 fixing for qpr2
Change-Id: Ica3ef9df1470fd2b5e20fc8caa3bdf6647a21426
(cherry picked from commit 1bdb0b76bfa439abf6cddb11e752aec3499d8f03)
Merged-In: Ica3ef9df1470fd2b5e20fc8caa3bdf6647a21426
|
|
Revert "Add flag to separate notification audio and ui"
Revert submission 20180104-flag_for_b38477228
Reason for revert: b/261809910 fixing for qpr2
Reverted changes: /q/submissionid:20180104-flag_for_b38477228
Include only in tm-qpr2-release because fix forward is already submitted to tm-qpr-deb at ag/20806122
Change-Id: I35549d7b7b41632c857bdbdda02ddb7220208243
(cherry picked from commit 9fcce567af715a80929a4bbbdfdffa3410ae0d8e)
Merged-In: I35549d7b7b41632c857bdbdda02ddb7220208243
|
|
tm-qpr2-release.
Change-Id: I9e4cdb6a9a8b795c6edae0ac52b693020f5f8eee
|
|
In headless system user mode, USER_STARTING, USER_STARTED, and
USER_SWITCHED broadcasts were not sent for the system user.
It had caused issues for other parts of the system which are expecting
such broadcast messages. For example, VpnManagerService expects
USER_STARTED event for system user but was not receiving it.
This change will only affect headless system user mode. No behavior
changes for phones.
Bug: 263439429
Bug: 242195409
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest
Change-Id: I4a101418c10a2c959c2bfae01b95863aebd521e8
(cherry picked from commit ba0f9f3ad2de99e8f96075db4571e6bf25d6c310)
Merged-In: I4a101418c10a2c959c2bfae01b95863aebd521e8
|
|
is lack of space.
Previously:
There was a chain [date]-[space]-[status icons]-[battery]. That's why we should add bias and space to make it working.
But there're several problems with this:
1) app:layout_width="WRAP_CONTENT" + app:layout_constrainedWidth=”true" != app:layout_width="0dp" + app:layout_constraintWidth_default="wrap". The first one gets view expanded like it's MATCH_PARENT.
2) I've found out that wrapping views in constraint layout 2.0.0 may not always work as expected with app:layout_constrainedWidth=”true" (the view get's stretched as it's match_parent). layout_constraintWidth_max="wrap" should've help with this, but motion layout can't parse this attribute in constraint set. That's why my solution is to reimplement the layout a little bit
This behavior is reported here: https://github.com/androidx/constraintlayout/issues/713
Now:
[date] and [battery] are constrained to the sides and [status icons] occupy the whole space between them.
[date] is always WRAP_CONTENT because there's always some space and we want to show it.
[battery] and [status icons] are wrap content with constraints restrictions to make them fill all the space left
Test: manual: phone + tablet
Fixes: 260364389
Change-Id: I4d54b795cc4e96f6c204f2f00aff7607572d9aa3
(cherry picked from commit 675ff0fe3756eb07baffba4bfc18b5bd2c289b01)
Merged-In: I4d54b795cc4e96f6c204f2f00aff7607572d9aa3
|
|
Test: Auto + manual
- Add work profile -> QS tile is added
- Remove work profile -> QS tile is removed
- Reboot the device -> QS tile is in place
- Reorder tiles, reboot the device -> order is persisted
Fixes: 234639083
Change-Id: I4481a3f28f9d1f0c30618afaf78179e0033f50fb
(cherry picked from commit a240e7eebe6fc81f123150a362c493a6f93b9d2c)
Merged-In: I4481a3f28f9d1f0c30618afaf78179e0033f50fb
|
|
Change-Id: I2f86b8635384aa2a07f47149f3257eb36ef98b9e
|
|
This CL refactors the way the ActivityLaunchAnimator and
DialogLaunchAnimator handle the visibility of the animated View when
that View implements LaunchableView.
Before this CL, a View that is animated would always end up being
VISIBLE, even if something made that View INVISIBLE or GONE before or
during the animation. That is because our animation code would sometimes
change the visibility of the View, using View.setVisibility.
After this CL, when animating a LaunchableView, all the visibility
changes made to the animated View are done using
View.setTransitionVisibility instead. That way, a LaunchableView can
track all calls to View.setVisibility only and restore the last
visibility that was set on the View at the end of the animation. Doing
so ensures that all calls made to View.setVisibility have the expected
result once the animation is done.
Bug: 264728445
Test: DialogLaunchAnimatorTest
Change-Id: I5848d42ef94952ecf058d4e895164389e37e0311
(cherry picked from commit 9ecb3db788b9f6be586c0f4f90c19d6337a7cd1b)
Merged-In: I5848d42ef94952ecf058d4e895164389e37e0311
|
|
This CL fixes the View that is used when showing the Foreground Services
dialog.
Test: Click the FGS button when the Security button is also shown.
Bug: 264728445
Change-Id: Id686279bbfc1e47e28da894342688d44183ebf42
(cherry picked from commit 0e7b6e534c1a818d1539e12d2febe2d26b7fa026)
Merged-In: Id686279bbfc1e47e28da894342688d44183ebf42
|
|
Change-Id: Iad419a04b3c6bdba832006413e8503473b3b6054
|
|
Bug: 255428281
Bug: 265307726
Test: manual: (1) Be in silent mode. (2) Make a phone call. (3) Mute the
phone call. -> Verify that *both* silent *and* mute icons appear in the
status bar. Verify that they can each be toggled independently without
affecting each other.
Test: atest StatusBarIconControllerImplTest (verified that all added
tests would have failed without the changes in this CL)
Change-Id: I54cebf7b9b96c1b333f1f2a9ca3d427e9e765790
(cherry picked from commit afd1fc252bcb0336b300da71178b716767c82f9a)
Merged-In: I54cebf7b9b96c1b333f1f2a9ca3d427e9e765790
|
|
'ag/20931541', 'ag/20946106'] into tm-qpr2-release.
Change-Id: I3b539e4fe213b68109336c1ff1f69640e1dbd30e
|
|
This reverts commit c4d3106e347922610f8c554de3ae238175ed393e.
Reason for revert: b/264884187, b/264885689
Change-Id: I9fb0d66327f3f872a92e6b9d682d58489e81e6ba
(cherry picked from commit 7bb933f48ff15d8f08d2185005b7b3e212915276)
Merged-In: I9fb0d66327f3f872a92e6b9d682d58489e81e6ba
|
|
This reverts commit a331639790fa2bd7b2669d20b3ecfd53970965e1.
Reason for revert: minimize logging for qpr2
Bug: 265067133
Change-Id: Ife9918c947ff521c7b6fb808a4c8d3ce27a02d67
(cherry picked from commit 8e50c40b0563b9dda8bf6a5d66fa2922526feb16)
Merged-In: Ife9918c947ff521c7b6fb808a4c8d3ce27a02d67
|
|
That way, clicks are not relayed to children.
Also, make the Reset menu item surface as action if it fits, for better
discoverability.
Test: manual
Test: atest LargeScreenShadeHeaderControllerTest
Fixes: 255708561
Change-Id: I853736f48ea97560f4b9ff438832d1372e0c59cc
(cherry picked from commit 6d4e7a81629afc17874c7e84e20f74c1470e2066)
(cherry picked from commit 1070f0f01184653a9247e3ba401aa5672c11ad84)
Merged-In: I853736f48ea97560f4b9ff438832d1372e0c59cc
|
|
NotificationHeaderViewWrapper too
Test: atest NotificationChildrenContainerTest
Test: Checking the roundness behavior by disabling the parent (ExpandableNotificationRow) clipping: I override childNeedsClipping() and if (child == mChildrenContainer) return false
Bug: 263822538
Change-Id: I6b08703c4fcf86ca0e939e8adf640053a297f9ca
(cherry picked from commit f3895a1d3a308877e5b2dbae8181d8bc2c9a9cc3)
Merged-In: I6b08703c4fcf86ca0e939e8adf640053a297f9ca
|
|
The race was happening when:
1. STATE_UNKNOWN arrives to PhotonicModulator#setState.
2. Inside PhotonicModulator#setState, mStateChangeInprogress is set to true, and the setState method finishes.
3. in the run loop, in one iteration, we reach mLock.wait() (with mStateChangeInprogress still set to true, as the state changed from something to unknown). Now, setState can be executed again as the lock is not held anymore.
4. A new PhotonicModulator#setState arrives. however, mStateChangeInProgress is true, so mLock.notifyAll() is not called anymore.
It was previously fixed by I903f6392cbe42031aab8ffdbfbe541463d6b5e01 making the display not going to UNKNOWN state anymore, but this cl fixes the general case and revert the changes to set the display to off in `onDisplayChanged`.
Bug: 262294651
Test: Running foldable test suite for 20 times with abtd: before the fix it had high flakiness, after it had 0% flakiness. There are no tests for DisplayPowerState currently.
Change-Id: I165b260d60e03c8e4707c7704847c77a225fd43d
(cherry picked from commit e4fccc2d9fd7382dacb4a546858eca93127c4c50)
Merged-In: I165b260d60e03c8e4707c7704847c77a225fd43d
|
|
tm-qpr2-release
Change-Id: I38b03729fd47e1405c0c72df6122e78ab6c69ede
|
|
|
|
tm-qpr2-release
Change-Id: I65e7cc3c9d1c4b0912d5f15d79a02dfa25f43bd1
|
|
tm-dev am: 7dafec61d9 am: 30433c97d0
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20860700
Change-Id: Ie9eb571cd38151b37988669b8484835ac9a0643a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
tm-dev am: 7dafec61d9
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20860700
Change-Id: I9ac823b5120759a44bbc8e84663d76694698ffb7
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
tm-dev
|
|
|
|
|
|
|
|
tm-qpr2-release
Change-Id: I1b1f0cbb1eed5c29db6b3ce12a6774bcdbe0568b
|
|
changed" into tm-qpr-dev
|
|
Bug: 262735040
Test: atest android.telephony.cts.VisualVoicemailServiceTest
Verified with live test that voice mail is received
Change-Id: Idae7ad9580f3c98e5f253e9e0627f68f5f87967b
|
|
|
|
Bug: 231523547
Test: make
Change-Id: I2b2fb7b4728d9bd4af981fe853eaa69a6b51d33e
(cherry picked from commit 83050a70e0d9091c75d613a1a9427649fcdb05b4)
|
|
|
|
|
|
ImeOnBackInvokedDispatcher#switchRootView." into tm-qpr-dev
|
|
5ebf0a5685 am: bfc6364c74
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20881922
Change-Id: I78121ab86eaa8c8a58995618978b780a5eb0c2ee
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
5ebf0a5685
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20881922
Change-Id: I9dfdd6c824006d32793fbfacaa73745ff48e09ac
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
|
|
|
|
|
|
- When invalidating an existing external interface, we also need to
unregister any listeners to ensure that binder death recipients are
unlinked. Otherwise, a crash in the process for the old listener
can cause the current listener to be unregistered.
Bug: 242377577
Test: atest WMShellUnitTests
Change-Id: Ibb77ac19e4ebc616b8977db70d6269e3b930848e
|
|
This fixes the issue of the display state change always being "in progress". PhotonicModulator thread fails to make any progress while waiting for a notify call to release the lock. This happensbecause the screenState is set to invalid when a device is being folded/unfolded, forcing it to wait until the screen state is recovered.
Bug: 262294651
Test: adb shell dumpsys display | grep "Photonic Modulator" -A 10 ->
Shows mStateChangeInProgress is false
Test: Manually folding/unfolding the device wont cause the display stuck
in the power off state
Change-Id: I903f6392cbe42031aab8ffdbfbe541463d6b5e01
|
|
|
|
This change aims at adding a feature flag for Auto Pin Confirmation
Feature in the auto_pin_confirmation namespace
Test: Tested by building and flashing on local
Bug: b/262928040
Change-Id: I31c46ef63dd5a9feb1aee91e5ce7bd67b7e7e19d
|
|
|