[3.2] Fix splash screen loading on Android

[m4gr3d]

Fix issue #21824

This is done by leveraging the Android theme to setup the app splash screen (reference).

Note:

• The splash screen fullsize and use filter parameters are not supported due to limitations of the Android theme api
• The PR is made against the 3.2-android-app-bundle branch since that branch includes numerous updates to the Android build process.
• The feature targets the Godot 3.2.4 release.

master PR

[akien-mga]

Thanks!

[NightBreather]

I have a problem with it unfortunately sometimes the splashscreen doesn't look like it should. Sometimes it shows twice.How should i use this feature

[akien-mga]

Please file a dedicated bug report.

[NightBreather]

Please file a dedicated bug report.

I couldn't understand very much what kind of error report you are talking about. It is not a recurring situation but when opening the application, sometimes my png file appears again after it has appeared once.

The source code I used to try 👍

https://s4.dosya.tc/server12/nwqmh5/circle_jump-master.rar.html

I'm using a png logo in here

Godot 3.2.4 Beta 2

[akien-mga]

I mean that it's more convenient for us if you create a new issue with all the information asked for in the issue template: https://github.com/godotengine/godot/issues/new?assignees=&labels=&template=bug_report.md&title=

Having one issue for each bug enables us to focus on debugging each issue separately, and eventually fixing them. This here is a merged Pull Request, and while it might be related to your issue (as it aimed to fix a similar problem), it may also not be.
So an actual bug report (issue) would be better (but you can reference this PR by its name: #42389 for additional context).

[NightBreather]

I mean that it's more convenient for us if you create a new issue with all the information asked for in the issue template: https://github.com/godotengine/godot/issues/new?assignees=&labels=&template=bug_report.md&title=

Having one issue for each bug enables us to focus on debugging each issue separately, and eventually fixing them. This here is a merged Pull Request, and while it might be related to your issue (as it aimed to fix a similar problem), it may also not be.
So an actual bug report (issue) would be better (but you can reference this PR by its name: #42389 for additional context).

thanks for information