This also adds the request id to the methods that hide the prompt to prevent stale requests from being handled. I wasn't able to reproduce the bug locally but it appears to be caused by these stale events.
Fix: 225275518
Bug: 213899762
Test: atest BiometricServiceTest AuthContainerViewTest
Change-Id: Iac414763dd0012e51b331abe649a50e353df5e1c
Clean up some leftover references and simplify
Add positive confirmation of flag changes via logcat
Change-Id: Id21b66953bb3b7c810e9d67809a673862a7ea821
Test: m -j update-api. Build and flash and test back behavior throughout
the system.
Bug: 227500290
Change-Id: Ibdb13d02e044741d05d99f1cad96e43dc0129fe4
Using parent view's adapter to prevent getting incorrect item after
filtering the list.
Bug: 227447626
Bug: 227289977
Bug: 227279371
Test: By manual
Change-Id: Ic7dde57cdc0dd44adf803317f836131d578f044b
(cherry picked from commit d3df5bdf84)
Right now the big picutre bitmap was loaded at 480px from URI and unrestricted from any other source. This adjusts that size to always consistently restrict it to 358dp, which is the maximum size of notifications.
Bug:210690571
Bug:218845090
Test: Manually on device
Change-Id: I9586488ba307e19bdc8c1af6f8c99cd369cd94c9
Requesting negative sized bitmap should mean "no restrictions" and not "please resize to -1x-1". This fixes the corner case for pure bitmaps.
Also reduce severity of logging when we're falling back to non-ImageDecoder load since that's not a catastrophic failure.
Bug:227103943
Bug:227008805
Test: tested on device with Notify1.apk while reproducing the issue
atest LocalImageResolver with new tests
Change-Id: I581d3e637fcafaba68856738f90cc72c42442d60
New flag will allow for control via experiment rollout.
Bug: 224544763
Test: Manual test of flag functionality.
Change-Id: I70bc79e12afe4ff629dbd3935c082c51c39a66a7
Also introduce a system property to facilitate debugging of caption in
shell.
Bug: 165794636
Test: Caption shows when the property is unset. Caption goes away when
the property is set.
Change-Id: I57060778c46da217a957910f0cc9d1fe1592cfa1
This encryption warning is never shown, since
StorageManager.isNonDefaultBlockEncrypted() is hard-coded to return
false, since FDE (Full Disk Encryption) is no longer supported.
Therefore, remove an unused TextView and string, and stop calling
StorageManager.isNonDefaultBlockEncrypted().
Remove the word "encryption" from the layout name
"accessibility_enable_service_encryption_warning", since this layout
is still used for other, non-encryption related warnings.
Bug: 208476087
Change-Id: Ic4e9024eadd602205516aa3ba4cc01887a2a7d34
Deprecate also the shadow radius for PiP in Task
Bug: 206508708
Test: Verify the PiP enter/exit/move/resize transitions
Change-Id: I8ff83dd4e626a3455373fed6c908cf131ecae8fe
This logically relands the change [1] which added an @hide api
InputMethodManager#reportActivityView() with renaming as
reportVirtualDisplayGeometry().
Because ActivityView was removed, this API was removed [2] once.
However, because this API is useful for OEM customization, this change
adds the same API with a generalized method name.
Note that there was a change on how cross-display input connection
cursor update is blocked [3]. Thus, this CL adapts to it.
[1] Id0411a80456182111bb5b681c6d1230b58e7ec2e
[2] Idd60d96a39f827197d189beb5de016446576d9cd
[3] Iec12733d37e112b7271436bba15094ae2a55a450
Bug: 224424149
Test: manual. Cursor is updated in cross-display connection.
Change-Id: I35b491da5a340844e17542d7a6198f8152bbeda3
The original intent of the code was to wait until we get one frame
with end vsync id or beyond end vsync id with both HWUI and SF
callbacks being reported such that we can ensure that our data
collection is complete.
However, the logic unintentionally started janky frames after the
end in case there were callbacks missing on the end vsync id,
leading to skewed metrics.
Also expand unit tests to verify jank number results.
Test: FrameTrackerTest
Fixes: 223787365
Change-Id: I90948d9ab2d44bf805e78f5611e072a7cc9ae0cd
In some cases, the InsetsState and the window frame can be changed at
the same time (such as orientation changed). Reporting them separately
might produce incorrect insets.
When the window layout is moved to the client, it uses the configuration
and the InsetsState to compute the window frame. They need to be
reported together as well.
Bug: 161810301
Bug: 160732586
Test: atest ActivityRecordTests WindowStateTests
Test: Add logs to check if we dispatch the correct insets to apps while
rotating the display.
Change-Id: I5c9f628eda40932def97c5caf968cb62db128e80
Move lock_pattern_line_fade_out_duration and lock_pattern_line_fade_out_delay to resources in order to override it for different devices.
Tests: manually
Bug: 204870856
Bug: 199436708
Change-Id: I758871d2d7ea62bd0ad55f83fc39b6d916cb2bba
(cherry picked from commit 7520086bd06737c00772a4526df637156fb983dd)
ModemActivityInfo can now include Radio Access Technology specific information, if the HAL supports it.
If available, utilize the information.
Bug: 207697945
Test: atest BatteryStatsNoteTest
Change-Id: Ifbd3c8cca7baa35cbccf64883ae5ce87ae39ab74
