Skip to content

WmTests: adapt home action tests to current settings - #1349

Open
CeRRiLLo89 wants to merge 1 commit into
crdroidandroid:16.0from
CeRRiLLo89:fix-wmtests-home-actions
Open

WmTests: adapt home action tests to current settings#1349
CeRRiLLo89 wants to merge 1 commit into
crdroidandroid:16.0from
CeRRiLLo89:fix-wmtests-home-actions

Conversation

@CeRRiLLo89

Copy link
Copy Markdown
Contributor

Summary

  • Adapt the WmTests HOME long-press and double-tap tests to the current DeviceKeysConstants.Action mechanism.
  • Configure HOME actions through the corresponding LineageSettings.System settings instead of writing removed PhoneWindowManager behavior fields directly.
  • Update the notification-panel case to validate the current panel-toggle path.

Root cause

KeyGestureEventTests still configures HOME behavior through test helpers that write:

  • mLongPressOnHomeBehavior
  • mDoubleTapOnHomeBehavior

Those fields are no longer part of the current PhoneWindowManager implementation.

The production code now reads HOME actions from:

  • LineageSettings.System.KEY_HOME_LONG_PRESS_ACTION
  • LineageSettings.System.KEY_HOME_DOUBLE_TAP_ACTION

using DeviceKeysConstants.Action.

The tests therefore no longer compile against the current implementation.

Validation

Current base:

71eec03efd654a4d14995b198566df9225015bb1

m -j6 WmTests completed successfully with this patch.

PR #1341 was applied locally only as an independent temporary build dependency because the current base contains a separate natural-rotation WmTests compilation issue.

PR #1341 is not included in this branch.

Runtime execution on the official raphael ROM was not performed because the locally built WmTests.apk is signed with the AOSP platform test key, while the installed crDroid framework uses the crDroid platform key. Package verification was not bypassed.

This changes test code only; no production behavior is modified.

Stable patch-id:

371ea11a821e2556222e91d24e4699c9eb119311

@CeRRiLLo89
CeRRiLLo89 marked this pull request as ready for review September 6, 2026 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant