android:hardwareAccelerated is forced false in all Activities

I'm not sure when this change happened but the built in android post processor is forcing all activities in the manifest to have android:hardwareAccelerated=false

This means it is impossible to override without writing out own post processor to undo this change. It should never be forced to be false or true on all activities as this could negatively interfere with other native activities a developer adds.

It would be helpful to have this at least as a flag in the editor settings along with the correct name of the main activity (for the times when you need to override the default Unity activity)

EDIT: This occurs in Unity 2018.1.0f2

 

It is required for using webview to load HTML5 content on android in any sort of performant way

 

Anyone know what's the workaround for this? I tried using a PostProcessBuild and it still gets overriden

 

Maybe but, our plugin adds webview to existing unity activity as we can pass the information from webview to unity very quickly.

Whereas, if we go for a new activity, all unitysendmessage calls are queued and won't fire until we finish the new activity where webview is rendered. As hardware flag was disabled, the scrolling of webviews and other content was too slow.
Glad I found this thread! Thanks to @KJoanette for creating a thread on this!


Anyways, thanks for pointing at IPostGenerateGradleAndroidProject as it should be good enough for handling the situation. It would be great if you can let us know from which unity version this was changed so that we can add the fix accordingly.


Cheers,
Ayyappa

 

Hi,

I'm stuck with this issue too. I'm using @Voxel-Busters ' plugin and without this flag set to true gifs won't be animated in the webviews.

I've tried to use IPostGenerateGradleAndroidProject but it's 2018 only, and although I've been able to use it to fix the manifest there are too many new bugs for me to do such an update, as I'm close to the release date.

Using IPreprocessBuild/IPostprocessBuild isn't a solution, because the first one is called too early and the latter too late.

The only workaround I have is to export the gradle project, patch the manifest myself and then build the apk, which is painful.

 

@Tagazou Please ping us on skype. I will get you the file which should work without any issues.

However, the mentioned interface seems to be from 2018.3

 

You can enable hardware acceleration for whole app by forcing a manifest change but I have observed various negative side effects of this in the Unity content (apart from the possible slowdown mentioned above) so I suggest only enabling hardware acceleration for a webview activity and not the unity activity - you can do on per-activity basis as detailed here: https://developer.android.com/guide/topics/graphics/hardware-accel

 

This will not work in 2017.4.11/LTS and nor does adding a root manifest with hardware acceleration set to true as somewhere between 2017.4.0 and 2017.4.11 you/Unity changed the unity content to use an activity with hardware acceleration off.

 

I am using Unity 2017.4.3f1.
In the same way, "android: hardwareAccelerated = false" is set on all screens.
How can I make it true? I am very embarrassed.

 

Because graph drawing is slow, I'd like to confirm it by setting it to true.

 

Actually I'm experiencing issues with this, because I'm using package to add WebView to Unity app with AR also inside it.

All Android phones, even top tier, experiencing lags-to-freeze and heat the phones with hardwareAccelerated=false.
Package developer recommends to set to true, and it worked for some times, as I see it, but now Unity, as I suspect, overrides it and just uses false instead.

 

thanks!

Solved this by exporting to Android project and changing option there. It works.

 

There are obviously legitimate use cases. Why are we not given any options here? Not every plugin can be modified and this was something that could much more easily be controlled in previous Unity versions...

 

For webviews, we don't see any other option if Unity chooses this way. Also, I need to accept this was mentioned sometime back that its better to avoid adding to Unity's default activity. But we mostly use because of the ease it gives us for better handling.

However, do you have any restrictions on using fragments with in Unity's default activity?

Thanks,
VB Team

 

admob native video ad need it

 

Yeah, Admob Native Video MediaView need hardwareAccelerated=true to working on UnityPlayerActivity.
I try to add another Manifest file to Plugins/Android folder of UnityPlayerActivity but it's still force hardwareAccelerated=false.

How can i change it?

 

We're using UniWebview, and this package is also recommending setting hardware acceleration to true. Unfortunately, it does not use a separate activity for the webview, it just sub-classes UnityActivity. And Unity overrides the acceleration setting for this, most likely because it is still marked as being the Unity activity.

How can we change this behaviour?

 

Just an additional note. For me it seems like the best way for this to work is to have hardware acceleration enabled for all native views except for the unity ones. This way unity drawing procedures will not be slowed down while the native views (like the mentioned Webview) will be as performant as expected. As I can tell from the generated android code there is a couple of unity views which are added to the activity (like a SurfaceView). To enable the logic I described, it can be enough to enable acceleration in the manifest for the activity and call this code for every unity rendering view:

Code (csharp):

1. unityView.setLayerType(View.LAYER_TYPE_NONE, null);

according to this: https://developer.android.com/guide/topics/graphics/hardware-accel#controlling. Though, I don't really know unity internal logic; so, I can't guarantee that will work

 

How can that be done, if the activity comes from a third party package (in my case UniWebView) which runs in the main activity?

 

We also have this issue -- in this case not with a WebView, but rather with using the ExoPlayer movie player within native 2D UI which is laid out over part of the Unity 3D view. This therefore has to be in the UnityPlayerActivity.

 

The input field after Android 9.0 cannot work because android:hardwareAccelerated is set to false! Causing the last line of the text cannot be shown. Please fix it!

Details can see here:
https://stackoverflow.com/questions...xt-when-typing-while-using-the-on-screen-keyb

 

For any one who wants to automate adding the flag, we made a script which will cover it.
Check out this script.

 

Same Issue，open keyboard and input multiline enough（fill keyboard input preview）, the input preview will display error.

 

when android:hardwareAccelerated set false, the keyboard preview display error, after input multiline. It's 100% happen, once input multiline enough.

 

Does it also happen in Unity > v2018 also? Is there any documentation from Unity on tracking the support for
android:hardwareAccelerated across versions?

 

Unity team, please tell is if this is 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.