Whitelisted atoms can be logged from any app so integrity of StateTrackers
for those atoms cannot be guaranteed.
Fixes: 155522551
Test: statsd_test
Change-Id: Ifc64e9168ee5f1f8977b99534319bc65946630f0
This reverts commit 25cbe9d7c7.
Fix resize info activity not showing in some cases
Show all visible activities in split screen primary window.
Add test to verify showing all activities.
Reason for revert: Adding back chagnes to fix original bug.
Seems that the changes in the original CL uncovered a different bug.
Bug: 156314330
Bug: 135520403
Test: atest CtsWindowManagerDeviceTestCases:PinnedStackTests
atest WmTests:ActivityStarterTests
Change-Id: I547e546708b669e055b9b9d9957c53bea50e52a6
Mark WifiTracker/AccessPoint as deprecated and include links to the
successor classes in WifiTrackerLib.
Bug: 153653213
Test: build
Change-Id: I91a40a984b6de32b711dc963186ac5358e053542
It's only used in one place, and just for setShelfHeight. We will just
use PipTaskOrganizer's bounds instead.
Bug: 147155783
Test: atest PinnedStackTests
Change-Id: I3a200a5df65e4e602286e9397b3b4586f9c2952f
This change updates the docs for the MATCH_UNINSTALLED flag to note that
without the QUERY_ALL_PACKAGES permission, uninstalled packages will not
be returned.
Bug: 149846504
Test: builds
Change-Id: Id0c5b7f29172bd334dc1b2a32ce1f4eb7b1f0bd3
Add a list of clients for speakerphone mode requests similar
to Bluetooth SCO clients. This allows to keep track of requests
by different apps in case of overlap or concurrency and to apply
the most relevant mode according to current audio mode owner.
Also:
- Restore requested speakerphone mode when SCO audio is disconnected
instead of returning to earpiece.
- Remove special check on permission while in call in
AudioService.setSpeakerphoneOn because the priority is now
managed by AudioDeviceBroker based on audio mode owner (the owner
for MODE_IN_CALL must have the modify phone state permission).
- Fix condition in AudioService.setMode() preventing from changing
mode while in call. Now allows releasing mode to NORMAL or
reapplying the same mode and just change mode owner.
- Add more information in dumpsys for AudioDeviceBroker and BtHelper.
Bug: 154464603
Test: test transitions between cell call and VoIP calls
Test: Test regressions with calls in speakerphone mode and Bluetooth
Test: AudioManagerTest#testRouting, NoAudioPermissionTest#testRouting
Change-Id: I0d288acf2373c96d52eb91a6ab7142cc3535c719
Update PipTaskOrganizer's last reported bounds as user moves the PIP
around. We then use this bound to calculate the snap fraction, and then
restore it on display rotation.
Bug: 147155783
Test: Start PIP, move PIP to different corner, rotate - same corner.
Change-Id: Ieb7054d9b66557aae63260767689d6523d87cdca
- Because cantReceiveTouchInput() accounts for whether an activity is
being controlled by recents (it shouldn't receive touches), we happen
to skip adding the recents input consumer below. However, because the
activity input window is skipped and the input consumer is not added,
we end up with no focused window, which then means that the next touch
on a nav button will try to inject a keyevent to no focused windows,
which triggers an ANR.
Ensure that we fall through to the logic below to add the recents
input consumer specifically in the case where an app window shouldn't
receive touches, but should have the recents input consumer applied.
Bug: 156394972
Test: Take surface trace while swiping up and ensure the input consumer
is relz to the app window being controlled
Change-Id: I9606dbef4565508514f4ff2f9ef464e9737bd7cc
Signed-off-by: Winson Chung <winsonc@google.com>
It requires a permission which we can't force apps to take to
maintain backwards compatibility. We also arguably cannot because
it leaks visibility, although only for debuggable apps/non-release
builds.
Instead, there's a new static method for getting the raw targetSdk
to gate against and the check is done manually, ignoring
enabled/disabled state. This will cause a mismatch between certain
apps and some system services like AppIntegrityManager, but the
effects should be minimal if we assume that most people ship
valid APKs. At worse the integrity check will pass an APK that
PM will fail, which doesn't break the feature.
Bug: 156356591
Bug: 156778241
Test: manual device boots
Change-Id: I877a5061476b86b9d63c34e75f16b38be8c3e1c2
This reverts commit 293b83d81e.
Reason for revert: May have caused http://b/156697897
Bug: 156697897
Change-Id: I9ce37a54abd25cc6a6dde2c7728d2da1076654c5
