Blocks all Touch Input in certain Apps/parts of Apps

[Caver1K]

Hello, I'm posting here because ive been encoutering this issue for quite a while now. Whenever I'm inside the settings app and going into the WiFi settings, all input to the app ist gone. I can still press back, which works just fine, and everything is back to normal. Its just in the WiFi settings and no where else. It is also in other parts for example when trying to do an ingame purchase using Google or when adding a Passkey(via Windows the QR Code feature). Once I disable the Data Stats, everything works just fine as if nothing ever happend. Thats all. Thanks for reading and I'd be glad if this gets fixed cuz it drove me crazy for a few days(prob Like 1.5 weeks) untill i found out why the Apps where broken.

Device Specifications:
Manufacturer: Motorola
Device: Motorola Edge 30 Neo
Version: Android 14
App Version: Data Stats 2.8.6

[sudo-py-dev]

I have the same issu

[Caver1K]

Edit: I had to disable the Data Stats cuz all input in the GitHub mobile App is also being blocked/non existent.

[alvarogzp]

I think this is due to some apps (and Android system components) blocking all input events when there is an overlay displaying in the screen. They do this for security reasons as the overlay could completely modify what you see and trick you into pressing a dangerous button or make you type a password where you shouldn't.

This happen to me sometimes too, for example, in Google Photos when I try to save an edited photo, I cannot press the Save button if there is an active overlay. What I do in these cases is disable DataStats temporarily (pressing the Clock or the Eye button in the DataStats notification), do the action I want, and then re-enable it.

I understand it's a confusing behavior because you don't know what's happening and why the app isn't reacting to input. I'm starting to see that some activities (like Settings), instead of disabling input, they disable overlays while running, so we can't see the overlay, but input isn't affected. I prefer this behavior for secure apps, as it's less confusing and easier to understand what's happening (you're in a secure screen and overlays aren't permitted here). Hopefully this become more used as an alternative to disabling input.

[Caver1K]

I think this is due to some apps (and Android system components) blocking all input events when there is an overlay displaying in the screen. They do this for security reasons as the overlay could completely modify what you see and trick you into pressing a dangerous button or make you type a password where you shouldn't.

This happen to me sometimes too, for example, in Google Photos when I try to save an edited photo, I cannot press the Save button if there is an active overlay. What I do in these cases is disable DataStats temporarily (pressing the Clock or the Eye button in the DataStats notification), do the action I want, and then re-enable it.

I understand it's a confusing behavior because you don't know what's happening and why the app isn't reacting to input. I'm starting to see that some activities (like Settings), instead of disabling input, they disable overlays while running, so we can't see the overlay, but input isn't affected. I prefer this behavior for secure apps, as it's less confusing and easier to understand what's happening (you're in a secure screen and overlays aren't permitted here). Hopefully this become more used as an alternative to disabling input.

Yeah i just came back here to mention the Google Photos one and saw your reply. Thanks for letting me know and im also temporarly disabling Data Stats to do what i want and then reactivating it again. At least i now know what the Problem is. Thanks.

[xa4hf8]

Also blocks KeepassDX

@takke
Please test the following changes to LayerService.kt, i dont have a build environment set up at this time

LayerService fixed

• Replaced full-screen window (MATCH_PARENT) with WRAP_CONTENT so overlay window matches widget size
• Saved LayoutParams so the service can reposition the overlay (x/y) instead of using full-screen padding
• Explicitly cleared clickable/focusable/touch/key listeners on the overlay root and MySurfaceView child so no view-level handlers accidentally consume input