Android: Address API 35 UI behavior changes

[m4gr3d]

Follow-up to #106810 (see #106810 (comment)).

Android 15+ (target SDK 35+) enforced edge-to-edge mode for all apps. Most Godot games are immersive by default, so they should be unaffected (system bars auto dismiss), but non-immersive Godot apps and games will now have part of their UI covered by (transparent) system bars.

#106810 addressed the issue for the Android editor by opting out of that behavior, however the opt-out request is no longer respected in Android 16 so it wasn't a full solution.
This PR instead addresses the issue for Godot apps and games (including the Android editor) by updating Godot's layout padding to take into account the system bars and the display cutout.

It also add a new screen/edge_to_edge export option to allow apps / games to enable edge to edge support.

In addition, the PR also fixes an issue on foldable where the embedded window would obscure the main window when launching.

[syntaxerror247]

I don't think this is a good idea. This PR automatically adjusts the layout padding, which effectively disables edge-to-edge mode for all Godot apps.

While it might make sense to disable edge-to-edge for the Android editor but for exported projects, we should leave this decision to the users. Godot already provides methods like get_display_safe_area() and get_display_cutouts(), which can be used to handle edge-to-edge layout properly.

Also, Android 15 deprecates the ability to change system bar colors programmatically. So, if we go ahead with this change, every non-immersive Godot app would end up with black bars on the top and bottom, which would clash with the app theme.

Personally, I would prefer keeping my app in edge-to-edge mode, rendering the background across the full screen, and placing the main content within the safe area using DisplayServer.get_display_safe_area(). This way, the system bars remain colored and match the app theme.

There's already ways for users to workaround this new restriction without disabling the edge-to-edge mode entirely.

[m4gr3d]

I don't think this is a good idea. This PR automatically adjusts the layout padding, which effectively disables edge-to-edge mode for all Godot apps.

While it might make sense to disable edge-to-edge for the Android editor but for exported projects, we should leave this decision to the users. Godot already provides methods like get_display_safe_area() and get_display_cutouts(), which can be used to handle edge-to-edge layout properly.

This PR maintains the current behavior prior to the bump to target SDK 35, which is that we only allow the app to be either immersive (system bars auto dismiss) or not edge-to-edge (system bars show and the content don't overlap them); you can test with a 4.4 build and validate that it's the case.

Supporting edge-to-edge would be a new feature and that's not the role of this PR. Also given that we're in feature freeze, that would be something to discuss for 4.6 if we want to consider it.

Also, Android 15 deprecates the ability to change system bar colors programmatically. So, if we go ahead with this change, every non-immersive Godot app would end up with black bars on the top and bottom, which would clash with the app theme.

The PR uses enableEdgeToEdge() which is recommended by Google to make the system bars transparent, so we're following the guideline.

[m4gr3d]

In short the primary requirement for this PR should be does it maintain the existing behavior as in 4.4 when exporting to Android.

That's all this PR should be tested against, because for most users not paying close attention to Android changes, a change in layout behavior from one version of Godot to the next, in the same project is a breaking change.

Once we validate we are maintaining the existing (expected) behavior, we can then discuss how to surface the new edge-to-edge functionality in a way that's easy to integrate.
That'll be a new feature (so likely 4.6) and that'll be off by default, so users that don't want the feature don't have to deal with it.
For a proper integration, we'll also need to update the documentation and provide tutorials for how to enable it and use the existing APIs to figure where to safely draw content.

[syntaxerror247]

I don't think this is a good idea. This PR automatically adjusts the layout padding, which effectively disables edge-to-edge mode for all Godot apps.
While it might make sense to disable edge-to-edge for the Android editor but for exported projects, we should leave this decision to the users. Godot already provides methods like get_display_safe_area() and get_display_cutouts(), which can be used to handle edge-to-edge layout properly.

This PR maintains the current behavior prior to the bump to target SDK 35, which is that we only allow the app to be either immersive (system bars auto dismiss) or not edge-to-edge (system bars show and the content don't overlap them); you can test with a 4.4 build and validate that it's the case.

Yeah, This PR does maintain the behaviour prior to the bump. However, edge-to-edge was achivable using a plugin but that won't be possible after this PR.

[m4gr3d]

Yeah, This PR does maintain the behaviour prior to the bump. However, edge-to-edge was achivable using a plugin but that won't be possible after this PR.

Well it sounds that in either case the plugin is obsolete:

• without this change, apps are edge-to-edge by default, so there's no longer a need for the plugin
• with this change, we'll add the edge-to-edge capability in Godot 4.6 in the engine, so the plugin will be obsolete then

The only issue is that the capability may be lost in Godot 4.5.. If we think that's an issue, then adding an export option to enable edge-to-edge should be trivial; but that means updating the documentation and providing tutorials for 4.5.. if you're up for it, it's worth considering..

[syntaxerror247]

without this change, apps are edge-to-edge by default, so there's no longer a need for the plugin

This is only the case for Android 15+ devices. Without this PR, plugin would work as expected on older devices.

[syntaxerror247]

The only issue is that the capability may be lost in Godot 4.5.. If we think that's an issue, then adding an export option to enable edge-to-edge should be trivial; but that means updating the documentation and providing tutorials for 4.5.. if you're up for it, it's worth considering..

Yeah, that's my concern, the capability would be lost in 4.5. Okay, Let's go with this PR for now. I'll send one to enable edge-to-edge.

[m4gr3d]

The only issue is that the capability may be lost in Godot 4.5.. If we think that's an issue, then adding an export option to enable edge-to-edge should be trivial; but that means updating the documentation and providing tutorials for 4.5.. if you're up for it, it's worth considering..

Yeah, that's my concern, the capability would be lost in 4.5. Okay, Let's go with this PR for now. I'll send one to enable edge-to-edge.

@syntaxerror247 I've updated the PR and included an export option for edge-to-edge. Can you take another look.

[syntaxerror247]

Looks great!

[Alex2782]

Looks good! Tested on Pixel 8a - Android 16

Suggestions:

---

• mention in the documentation that edge_to_edge does not support every device
• Reference to the Android documentation, there are probably few users who even know what this is https://developer.android.com/develop/ui/views/layout/edge-to-edge
• Is it possible to change edge_to_edge at runtime?

---

https://docs.godotengine.org/en/stable/classes/class_displayserver.html#class-displayserver-method-window-set-mode

• WINDOW_MODE_FULLSCREEN = 3 without edge_to_edge?
• WINDOW_MODE_EXCLUSIVE_FULLSCREEN = 4 with edge_to_edge?

---

• In the Window Management demo, I was also able to change Immersive Mode at runtime. Perhaps the export settings could be removed(?) if it works at runtime and can be changed via the project settings.

func _on_button_fullscreen_pressed() -> void:
	if DisplayServer.window_get_mode() == DisplayServer.WINDOW_MODE_FULLSCREEN:
		DisplayServer.window_set_mode(DisplayServer.WINDOW_MODE_WINDOWED)
	else:
		DisplayServer.window_set_mode(DisplayServer.WINDOW_MODE_FULLSCREEN)

[syntaxerror247]

• mention in the documentation that edge_to_edge does not support every device

I think, edge-to-edge should be supported for every SDK 24+ device. I haven't tested though.

• Is it possible to change edge_to_edge at runtime?

Not yet! Let's not block this PR, I'll send one to change it at runtime using WINDOW_MODE_MAXIMIZED (for Godot 4.6).
Ideally, WINDOW_MODE_EXCLUSIVE_FULLSCREEN should be for immersive and WINDOW_MODE_FULLSCREEN for edge-to-edge but currently both are used for immersive and changing that would break compatibility.

• In the Window Management demo, I was also able to change Immersive Mode at runtime. Perhaps the export settings could be removed(?) if it works at runtime and can be changed via the project settings.

We are keeping the export option to instantly apply the immersive/edge-to-edge mode on launch otherwise it would create a slight noticable delay. ProjectSettings are initialised a bit late in the process.

[akien-mga]

Thanks!

[Alex2782]

• mention in the documentation that edge_to_edge does not support every device

I think, edge-to-edge should be supported for every SDK 24+ device. I haven't tested though.

I wanted to try it on my Samsung Tab S7 first, but the device itself doesn't have it. (This setting has no effect.)

[m4gr3d]

• mention in the documentation that edge_to_edge does not support every device

I think, edge-to-edge should be supported for every SDK 24+ device. I haven't tested though.

I wanted to try it on my Samsung Tab S7 first, but the device itself doesn't have it. (This setting has no effect.)

@Alex2782 What Android version is your tablet running?

And can you send a screenshot or recording of what the test app looks like with the following options:

• immersive enabled and edge-to-edge disabled
• immersive disabled and edge-to-edge enabled
• both immersive and edge-to-edge disabled

[Alex2782]

And can you send a screenshot or recording of what the test app looks like with the following options:

• immersive enabled and edge-to-edge disabled
• immersive disabled and edge-to-edge enabled
• both immersive and edge-to-edge disabled

Samsung Android 13.

Okay, it's a different issue (theme / style). I was able to identify the edge-to-edge impact (Default 2D project). It's harder to see on the tablet because the status bar is completely black. (and takes up very little space)
A few days ago, I tested it with another project, and the app background color was darker than here.

[m4gr3d]

And can you send a screenshot or recording of what the test app looks like with the following options:

• immersive enabled and edge-to-edge disabled
• immersive disabled and edge-to-edge enabled
• both immersive and edge-to-edge disabled

Samsung Android 13.

Okay, it's a different issue (theme / style). I was able to identify the edge-to-edge impact (Default 2D project). It's harder to see on the tablet because the status bar is completely black. (and takes up very little space) A few days ago, I tested it with another project, and the app background color was darker than here.

So it seems to work as expected. I would also expect the navigation bar to be affected when edge-to-edge and immersive are enabled.

[syntaxerror247]

I noticed one issue. On dark mode, the status bar icons auto adjust it's color (white/black) based on the background, as expected. However, on light mode it doesn't adjust the color and stays black as seen in screenshot in Alex's comment.
It might be a device/Android issue though.