Android One middle-end phone slow perfomance (resolved issue with Unity 2017 resetting hardwareAccelerated to false in the build process)
idchlife opened this issue · 3 comments
Hello! Thank you very much for this fantastic project!
I was wondering, is there way to up the performance on now high-end devices?
Using Nokia 6.1 32GB for testing purpose.
Also, input file not working but I read somewhere here that it can be broken on some Android devices.
Could you please check https://github.com/gree/unity-webview#hardwareaccelerated for achieving a good performance? The implementation should automatically perform the required adjustment for AndroidManifest.xml and you should get a good performance at least after the second build. If you still feel that the webview is slow compared with the ordinal chrome browser, the implementation might fail to perform the adjustment because of some unknown bugs... Anyway, I think it is valuable to check https://github.com/gree/unity-webview#hardwareaccelerated if you haven't yet.
About "input file", I've implemented it once but put it experimental, because it cannot work for some devices as you described: #77 .
@KojiNakamaru I can't understand if this does show something, but when I export project from Unity, Android project, there is AndroidManifest.xml and it has hardwareAcceleration="false", despite manifest file in the Plugins/Android plugin having "true".
I tested Unity build with Samsung s7, s8, s9, all of the phones having very slow performance. s7 even freezes and starts to heat the phone
I discovered that I am able to build in Unity 2017 with hardwareAccelerated=true by exporting Android project (Unty -> build -> android -> checkbox export -> choose folder), opening exported folder with Android Studio, changing hardwareAccelerated to true in AndroidManifext.xml and building project from Android Studio.
After that it worked flawlessly!
I hope it helps everyone who stumbled across this issue.