Replace ArrayList by SparseArray to track each pointer by pointer id, so
we could avoid generating lots redundant PointerStates if the event has
an unexpected pointer id value (such as 0xFFFFFFFF).
This also fix text size and path width when the density has changed.
Bug: 243548346
Test: enabled pointer location
Change-Id: I0a5b04b3034f02c3b06803a90d9b97561afdd9e0
Add new APIs for select and delete with two rectangles.
Test: atest InputConnectionEndToEndTest
Test: atest StylusHandwritingest
Bug: 239783077
Change-Id: Ia7240d3eaac8610c774c3a4aad074a4b84b71521
This method combines values into a smaller array
by using an index map.
Bug: 244623253
Test: atest com.android.internal.os.LongArrayMultiStateCounterTest
Change-Id: Ic35d30cc1f8765cd4e21366943da8291355a0047
Revert "Update the class name of jank related atoms"
Revert "Add TEST_MAPPING file for checking jank atoms"
Revert submission 19784398-jank_presubmit
Reason for revert: see b/246684475
Reverted Changes:
I3880fa2bb:Enable presubmit for com.android.internal.jank
Ia1c4e3214:Add TEST_MAPPING file for checking jank atoms
If8a041770:Update the class name of jank related atoms
Change-Id: I7ab08b691f15647ca026e55e3cf115c9edcd9160
In case seeing the unexpected fallback keyboard layout when focusing to
the window without an editor from the app has shown the IME.
Note that this behaviour change affects when the IME focus switching to
the next window with following configurations from an IME shown window:
1) SOFT_INPUT_STATE_UNCHANGED state without an editor
2) SOFT_INPUT_STATE_VISIBLE state without an editor
3) SOFT_INPUT_STATE_ALWAYS_VISIBLE state without an editor
Also, we guarded this platform behavior with DeviceConfig platform flag
in input method manager namespace.
Fix: 240701729
Bug: 243897178
Test: manual as issue steps
1) In Launcher, swiping up to enter all apps page.
2) Tap the search bar to show IME
3) Type "Keep" to show Keeps app's shortcut
4) Tap Keeps app's shortcut
5) Verify IME won't be shown on top of Keeps app's activity
(As the app set SOFT_INPUT_STATE_UNCHANGED without focusing an
editor by default)
Test: atest KeyboardVisbilityControltest#\
ImeInvisible_softInputAdjustNothingFromImeShownApp
Change-Id: I0c502bec5c5e21dabde08d610a9a1969c1229b08
We would like to have userdebug builds as close to user builds as
possible so don't enable jdwp by default on userdebug builds. This
means that we won't be able to attach a debugger to non-debuggable
builds in userdebug builds by default. However, this support can
be enabled by setting persist.debuggable.dalvik.vm.jdwp.enabled
property. Eng builds still enable jdwp by default.
Bug: 240410400
Test: System boots
Change-Id: Iad52254be9b9bc8c9deac8b3ad46e9db1b610160
Tracks the resolutions of the displays and includes the appropriate
resolution in the tracked stats.
Bug: 241174561
Test: atest com.android.internal.jank
Change-Id: I57d9d02f2b9bd9cf451ee4466f3c65b1bb1cf7b4
Talkback can now correctly focus the collapse button before going to the action list when expanded. To know why mExpandButton is dynamically placed, check commit: 54fe9ad2dc
Bug: 237505828
Test: Visual, see the STEPS TO REPRODUCE section of bug 237505828, the focus order of talkback should be collapse button then actions.
Change-Id: Id0cf8730b00e0e7636a163fb5d51e37e8e0a3e84
The native VelocityTracker has been refactored to allow support of axes
beyond X and Y axes. To conform to this change, we are updating calls to
the native VelocityTracker. Furthermore, to support independent velocity
tracking for separate axes, we are updating the native/JNI methods
accordingly. With these changes, supporting new axes for velocity
tracking would only require changes at the native VelocityTracker level
only (besides creating a public API for our clients).
Bug: 32830165
Test: android.view.cts.VelocityTrackerTest unaffected; touch fling works
Change-Id: Ib0be0fc38c315ade2475cd53597a846e58016d14
