bug: Walking Mode overlay blocks all touch inputs (UI Unresponsive)

[bugycugy]

Issue type

User interface

Device

spacewar

crDroid version

crDroid 12

Exact version / Build date

17/12/2025

Bug description

When "Walking Mode" (Heads Up) is enabled, the camera overlay appears correctly, but the entire touchscreen becomes unresponsive to any touch input.

Expected Behavior: The user should be able to interact with the UI behind the camera overlay or use the device normally while the overlay is active.

Actual Behavior: The device fails to register any touch events as soon as the overlay is active. The user is forced to reboot or use hardware triggers to exit.

Device & ROM Info:

Device: Nothing Phone (1) (spacewar)

crDroid Version: crDroid 12.4 (Android 16)

SDK Version: 36

Root: KernelSU

Note: I have attached a full logcat captured while I was actively touching the screen during the issue.

yurume_logu.txt

Steps to reproduce

Open the Quick Settings panel or navigate to crDroid Settings.

Enable the "Walking Mode" (Heads Up) feature.

Wait for the camera overlay to appear on the screen.

Attempt to interact with any UI element or use navigation gestures while the mode is active.

Observe that the touchscreen is completely unresponsive, as captured in the provided logcat.

Relevant log (logcat/build log)

The logcat file is attached to this issue as an attachment because it exceeds the 65,536 character limit. The log captures the touch unresponsiveness on SDK 36 (Android 16) for the 'spacewar' device.

Screenshots or videos

screen-20251218-151705.mp4

Solution

No response

Additional context

yurume_logu.txt

Acknowledgements

• I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.

[gwolf2u]

best to check when QPR1 drops
I can't reproduce locally, yet agree not same device
leaving open in case @MySelly wants to check, but will close once QPR1 drops

[gwolf2u]

@MySelly tried this on 12.5 BETA?

[MySelly]

@MySelly tried this on 12.5 BETA?

yeah still same