Are android:hardwareAccelerated="false" and android: process=":Unity" still required in GameActivity mode in Unity 2023.1.17f?
- Because with
android:hardwareAccelerated set to false (which is the default in Android project export of Unity 2023.1.17f) I’m getting visibly lagging native UI. I have a lot of Android UI in my app and also WebView in the same activity (as some other people also reported).
- Also, is it necessary to keep the default
android: process=":Unity", because then onCreate of Application gets re-executed twice, which leads to bugs, so for tight integration of Unity and Android’s UI everything should be in the same PROCESS and ACTIVITY.
I found this: Hardware acceleration | App quality | Android Developers
Please Unity, tell us if we can re-enable hardwareAcceleration for the entire Activity or perhaps some Views, because without it the native UI lags too much (it’s like 10-20 FPS instead of regular 30-120 FPS)?
And also if we can remove process=":Unity", because in Android, when you launch a new activity in a different process using the android: process attribute in the AndroidManifest.xml, the activities in the two processes will run in separate processes, and their memory and resources are isolated. This means that the singleton instances of classes that are initialized in the first activity will not be accessible from the second activity running in a different process. We don’t want to re-initialize all the singletons twice in the app.