OpenGL ES3 + 2019.1 + P30 Pro = CRASH before Splash

Hi,

when doing a clean install of a build from 2019.1.11, it crashes immediately before splash screen starts showing. We discovered the problem on a Huawei P30 Pro, our other Android test devices does not crash.

First, we were using Auto Graphics API. Unticking it did not fix the problem right away as it was then set up to use OpenGLES3. Crashes just like before. But if we switch over to using Vulkan, the crash goes away.

We haven't been able to use 2019.1 at all without major problems for any of our games. In the mentioned game we are now stuck with Vulkan rendering - which is not optimal for many reasons. In our other game we are stuck in 2018.4 because of the lack of Camera Stacking in LWRP in 2019.1.

When will OpenGLES3 work on Huawei P30 Pro when building with 2019.1 with IL2CPP and .NET 4? 2018.4 does not have the crash issue on P30 Pro.

Trace from Logcat when the startup crash happens:

2019-07-24 20:29:42.052 22273-22298/? E/CRASH: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 000000746240aff0
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: Build fingerprint: 'HUAWEI/VOG-L29EEA/HWVOG:9/HUAWEIVOG-L29/178C431:user/release-keys'
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: Revision: '0'
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: pid: 22273, tid: 22298, name: UnityMain >>> com.monkeybin.hyspherical3 <<<
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x0 000000747518b190 x1 0000000000000000 x2 0000000000000000 x3 0000000000000000
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x4 000000745d7f2580 x5 0000000000000004 x6 00000075058b1000 x7 000000000055984e
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x8 0000000000005ffd x9 000000000000ffff x10 000000000000571a x11 0000000000000012
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x12 000000000000061e x13 0000000000007880 x14 0000000000000180 x15 aaaaaaaaaaaaaaab
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x16 0000007460375320 x17 00000074ffa07020 x18 00000074750072e8 x19 00000074603d1c78
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x20 0000000000000601 x21 000000746045f000 x22 0000000000000601 x23 000000746045f000
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x24 000000745db6d92c x25 000000745db901d6 x26 000000745fcc9d7c x27 000000745db90188
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: x28 000000746045f000 x29 000000746240b0a0 x30 000000745ed1c6c0
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: sp 000000746240afd0 pc 00000074ffa07258 pstate 0000000080000000
2019-07-24 20:29:42.052 22273-22298/? E/CRASH: backtrace:
2019-07-24 20:29:42.079 1214-1716/? E/InputDispatcher: channel '605fe38 com.monkeybin.hyspherical3/com.unity3d.player.UnityPlayerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
2019-07-24 20:29:42.081 2018-12227/? E/HsmCoreServiceImpl: onTransact in code is: 102
2019-07-24 20:29:42.081 2018-2485/? E/Hicom_PolicyCenterService: handleAppDied. null == mMultipathAppsMap
2019-07-24 20:29:42.103 2125-2582/? E/powergenie_jni: FUNC: setHisiCABCInner() LINE: 60 open /dev/pri_lcd error: No such file or directory
2019-07-24 20:29:42.103 2125-2582/? E/DisplayControl: Fail! set cabc mode: 1
2019-07-24 20:29:42.104 2018-2485/? E/XEngineMpipControl: Invalid SubId
2019-07-24 20:29:42.109 2125-3179/? E/AwareLog: SPKSchedFeature: Uid has been sent, ignore.
2019-07-24 20:29:42.142 1214-1617/? E/WindowManager: win=Window{257c308 u0 Splash Screen com.monkeybin.hyspherical3 EXITING} destroySurfaces: appStopped=false win.mWindowRemovalAllowed=true win.mRemoveOnExit=true
2019-07-24 20:29:42.145 2018-3351/? E/DollieAdapterService: notifyActivityState pkg:com.monkeybin.hyspherical3/com.unity3d.player.UnityPlayerActivity state:18 fg:false mUid:10236
2019-07-24 20:29:42.147 4273-4300/? E/AppLifeChangeSensor: CAWARENESS: activityResumed mAppLifeChangeCallback is null
2019-07-24 20:29:42.147 2018-3351/? E/DollieAdapterService: notifyActivityState pkg:com.huawei.android.launcher/com.huawei.android.launcher.unihome.UniHomeLauncher state:2 fg:true mUid:10087

 

So, use 2018.4 and do a bug report for the 2019.1 issue, so by the time 2019.4 comes along, it's fixed.

 

Unity in a nutshell!

 

Well... sure, but especially for Android I think I sort of give Unity a pass.

Android's the most fragmented platform out there and has a WILD variety of quality of hardware and driver quality (and a lot of those are still released today), you really need the most stable version of Unity to have as few issues as possible.