COD Warzone Mobile crashing on launch every time

randomgosuser

Hi there,

I have a Pixel 8A running GOS build 2024112700 (Alpha channel).
Today I tried to install COD Warzone Mobile on a secondary user that I created just for the purpose. Besides the default apps, the only apps installed in this user are Google Play Services, Google Services Framework, and Google Play Store. I downloaded COD Warzone Mobile from the Play Store using a real Google account that I own. However, after the download whenever I try to launch the game I get the following error:

`type: crash
osVersion: google/akita/akita:15/AP3A.241105.007/2024112700:user/release-keys
userType: full.secondary
package: com.activision.callofduty.warzone:3462, targetSdk 34
process: com.activision.callofduty.warzone
installer: com.android.vending

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000013

backtrace:
#00 pc 0000000002965148 /data/app/52F4fq5GxYlED8YNGISv9Q==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#01 pc 0000000002e518f0 /data/app/52F4fq5GxYlED8YNGISv9Q==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#02 pc 0000000002e54374 /data/app/52F4fq5GxYlED8YNGISv9Q==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#03 pc 0000000001c71588 /data/app/52F4fq5GxYlED8YNGISv9Q==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#04 pc 0000000001689640 /data/app/52F4fq5GxYlED8YNGISv9Q==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#05 pc 0000000002966c74 /data/app/52F4fq5GxYlED8YNGISv9Q==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#06 pc 0000000002964b10 /data/app/~_{52F4fq5GxYlED8YNGISv9Q}==/com.activision.callofduty.warzone-cfmNIAiTvhoFoN2Ib_oTYw==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#07 pc 000000000007afe8 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*)+200) (BuildId: b71d8a57f89af8d59ea1cbb4ebf7d951)
#08 pc 000000000006b164 /apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68) (BuildId: b71d8a57f89af8d59ea1cbb4ebf7d951)
`

Turning Exploit protection compatibility mode ON or OFF has no impact on the crash. App has been granted all permissions and unrestricted battery usage. I also tried to uninstall the game, reinstall it and turn on Exploit protection compatibility mode and all the permissions, but still nothing. Also tried multiple reboots.

I only post this because, to my very limited understanding, this crash is related to the app being unable to access a certain memory location, and I was wondering if this was related to the hardening performed by Graphene OS.
FYI, the regular COD Mobile (not Warzone) always crashes if Exploit protection compatibility mode is OFF, but works perfectly fine if it is ON (as expected).
Or maybe this is because I am using a secondary user? I can't test this on the Owner profile right now, as it would mess up my setup too much.

Thank you in advance.

DeletedUser69

randomgosuser rest easy, it fails on Owner too, even with sandboxed Google. Reports survivor for life, Old Surehand. Issue is quite severe. Recommend sticking with CODM.

randomgosuser

Update: I just tried to install everyhtinig in Private Space of Owner profile and I basically get the same error log:

type: crash
osVersion: google/akita/akita:15/AP3A.241105.007/2024112700:user/release-keys
userType: profile.private
package: com.activision.callofduty.warzone:3462, targetSdk 34
process: com.activision.callofduty.warzone
installer: com.android.vending

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000013

backtrace:
#00 pc 0000000002965148 /data/app/zn8SmpN87afDArhKLpbRLA==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#01 pc 0000000002e518f0 /data/app/zn8SmpN87afDArhKLpbRLA==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#02 pc 0000000002e54374 /data/app/zn8SmpN87afDArhKLpbRLA==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#03 pc 0000000001c71588 /data/app/zn8SmpN87afDArhKLpbRLA==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#04 pc 0000000001689640 /data/app/zn8SmpN87afDArhKLpbRLA==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#05 pc 0000000002966c74 /data/app/zn8SmpN87afDArhKLpbRLA==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#06 pc 0000000002964b10 /data/app/~_{zn8SmpN87afDArhKLpbRLA}==/com.activision.callofduty.warzone-iv6iwSyGodoeYTi9MvUr2g==/split_config.arm64_v8a.apk!libgame.so (offset 0x1b0000) (BuildId: 52ffcddc91b984d4fe3110c9d090cf53)
#07 pc 000000000007afe8 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*)+200) (BuildId: b71d8a57f89af8d59ea1cbb4ebf7d951)
#08 pc 000000000006b164 /apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68) (BuildId: b71d8a57f89af8d59ea1cbb4ebf7d951)

de0u

randomgosuser signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000013

This likely means that the program dereferenced a null pointer, perhaps because some library code returned an error and the main program didn't check for that. Beyond that the stack trace is not very informative (since it's a game, the executable may well have symbols stripped and may even be obfuscated).

It is possible that the system log for the app might shed light on what went wrong. But interpretation of the crash dump may not be feasible except by the game's development team.

Frenly-Skitzo

I see the same thing happening on the Pixel Tablet. COD Warzone used to work back on GOS 13 (or 14?), but stopped after upgrading to a newer android version. Currently on 15 and COD Warzone still crashes; even with exploit compatibility settings. Not sure if there's a way around it, but at least there are many other games to play.