godotengine / godotengine/godot
SurfaceFlinger error messages on Android device using adb logcat
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
4.3.stable.mono
### System information
Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Mobile) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 31.0.101.5590) - 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 Threads)
### Issue description
When running a basic project using Remote Debug on an Android device (Galaxy S10e) the following message continually appears in adb logcat:
606 E SurfaceFlinger: Attempt to update InputPolicyFlags without permission ACCESS_SURFACE_FLINGER
The messages stop when the app is backgrounded or closed so it's definitely not just the device. Almost looks like some kind of inifinite loop, which is making it impossible to find anything else in the debug log.
Have tried checking the "Access Surface Flinger" permission in the export settings but this doesn't seem to make any difference.
### Steps to reproduce
Reproducible with a minimal Godot project.
No code, just a PanelContainer scene containing a Label.
### Minimal reproduction project (MRP)
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the minimal PanelContainer project on the Galaxy S10e, using Remote Debug and adb logcat. Start by inspecting Android export handling for the “Access Surface Flinger” permission and the path that updates input policy flags. Done means the repeated SurfaceFlinger messages no longer obscure the debug log, or the permission behavior is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100