"Hold Down" Action Cancels Other Screen Touches

[bread34]

Developer TODO (don't remove)

• update documentation

---

Describe the bug

When I create a Tap screen action with the following settings:

• Repeat: Disabled
• Hold down: Enabled
  • Hold down until trigger is released
  • Hold down until trigger is pressed again

…the action performs a continuous touch as expected, but it cancels all other active screen touches.
This includes any ongoing touches that are made manually on the screen.

As soon as the injected touch begins, other touches are released or interrupted — as if the system is sending ACTION_CANCEL to them.
This makes it impossible to use multiple touch points at once, which is needed in some personal multi-touch use cases.

---

Attach bug report

Here is the link to the bug reporting instructions:
https://docs.keymapper.club/report-issues
(I'm happy to provide logs or additional info if needed.)

---

To Reproduce

1. Create a keymap with a Tap screen action
2. Enable Hold down
3. Set it to release when the trigger is released
4. Bind it to a hardware key (e.g., volume button)
5. While another finger is touching the screen, activate the trigger

Result:

The previous touch is canceled immediately.

---

Key maps

Keymap configuration can be provided upon request.

Follow the guide here

---

Expected behavior

The Hold down touch should be injected without interrupting other active screen touches.
Multi-touch input should remain intact during the injected touch.

---

Screenshots

Can be provided upon request if needed.

---

Device and app info

• Device: [e.g. honor x9b 5g/ Android]
• Android version: Android 15 (non-root، i use shizuku)
• Key Mapper version: [e.g. 3.1.1]

[gltxz]

Did you find any solutions?

[sds100]

Assuming I understand the problem correctly, this is expected behavior with accessibility services and restriction in Android. Gaming Mode #1744 will work around this problem