Android 16 incompatibility and other

[MrCuriowls]

Describe the issue

• Mouse doesn't work because an error appears if certain options enabled. Error: xtmapper is not optjmized for your device. Im using shizuku.

To Reproduce
Steps to reproduce the behavior:

1. Enable show controls on screen or open editor as overlay
2. Start xtmapper
3. click on screen when you are on desktop or other apps

Expected behavior
No errors and working mouse.

Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

• OS: one ui 8.0
• Android 16
• Samsung s23 ultra

[Xtr126]

Show controls does break it, I've fixed this in the code already.

[MrCuriowls]

Please generate a new debug apk. Thanks

[Xtr126]

New debug APK with the right click fix: https://github.com/Xtr126/XtMapper/actions/runs/23684487726

[MrCuriowls]

Show controls unusable anyways even with latest apk :( I noticed too that buttons overlay aren't visualized.

[SoufianoDev]

@Xtr126

[CRITICAL] InputDispatcher Dropping Touch Events Due to Untrusted Overlays (Android 12+)

Visual Evidence (System Warning)

"XtMapper isn't optimized for the latest version of Android. Screen touches may be delayed or not recognized."

---

Description

The application's core functionality (keymapping / touch emulation) is broken on Android 12 and above.

The system InputDispatcher flags XtMapper overlays as untrusted because they exceed the maximum allowed opacity for pass-through touches. As a result, touch events are completely dropped when the overlay is active.

---

Logs / Evidence

Logcat confirms that the system is intentionally blocking input:

W InputDispatcher: Untrusted touch due to occlusion by xtr.keymapper/10389 (obscuring opacity = 0.99, maximum allowed = 0.80)
W InputDispatcher: Dropping untrusted touch event due to xtr.keymapper/10389

Multiple window instances appear simultaneously:

• Window ID: 74366
• Window ID: 74357
• Window ID: 74353

---

Technical Root Cause

1. Opacity Violation

Overlays are created with an opacity of 0.99, which exceeds Android 12+ security limits.

• Allowed maximum: 0.80
• Current value: 0.99

Android blocks touch pass-through to prevent tapjacking attacks.

2. Window Leakage

Multiple overlay windows remain active at the same time, indicating improper lifecycle handling.

This suggests that old views are not being removed correctly from WindowManager.

---

Impact

• Severity: Critical / High Priority

• Functional Impact:

  • Complete loss of touch interaction
  • Keymapping unusable

• User Experience:

  • Unresponsive screen
  • Dead zones
  • System warning toast about app not being optimized

The application is effectively unusable on Android 12+ (12, 13, 14, 15, 16).

---

Proposed Fixes

Immediate Fix

Reduce overlay opacity:

layoutParams.alpha = 0.75f;

Ensure all pass-through overlays stay at or below 0.80.

---

Lifecycle Audit

Ensure proper cleanup of overlay views:

windowManager.removeView(view);

Verify that:

• No duplicate overlays are created
• Views are removed on stop/destroy
• Services do not leak windows