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
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
This uses logic similar to printBitDescriptions to parse the state
bitmask along with the BitDescriptions to report the information as
a trace counter.
Due to current tracing limitations, values are not remembered outside of
or between tracing. For slow moving things (like wifi enabled/disabled),
we would miss the counter in most traces if using `traceCounter` alone.
The Perfetto team's current solution is to read system properties when
the trace starts in order to fill in the initial value. To limit the
impact of this, this aspect is only enabled in userdebug.
Bug: 245749764
Test: presubmit and local perfetto tracing
Change-Id: Iaae4e9796a44be3ffdaee31b956bbb3e87735ead
When we calculate dismiss target, it will deduce nav bar size from
total height. Remove this rule to make divider always move to end
of screen.
Fix: 232858513
Test: manual
Test: pass existing tests
Change-Id: I34cf12f242daa31bd4dd7d4b202fc43ac0d752b4
This a preperation CL before refactoring ImeFocusController.
To make dumpviewInfo can also be used in other IME related files
like ImeFocusController.
Also, removed unused method InputMethodDebug#objectToString.
This is just a mechanical refactoring and should not have any behavior
change.
Bug: 244504062
Test: build
Change-Id: I9d1a0c2b06e676e40b0e844edb18e8422a67b0ad
