After updating to 2023120700 on:
- Call Of Duty (all security function is disabled)
- Need For Speed (all security function is disable)
On launching app system just rebooting without any crash dialog, etc. Just reboot.
After updating to 2023120700 on:
On launching app system just rebooting without any crash dialog, etc. Just reboot.
secure_adict all security function is disable
Can you clarify what this means? I'm assuming you're saying that you've enabled Exploit Protection Compatibility mode for the two apps?
other8026
Yes, I mean turning on Exploit Protection Compatibility
secure_adict When you say reboot, are you sure that it actually does? Do you see the yellow boot screen?
If you don't, it is more likely a system UI crash, not an actual reboot.
secure_adict I just tried Call of Duty and NFS No Limits, and they both work on my phone. Not sure if you have some other variation of either of those apps, but I didn't find any with another name.
I'm having this same issue on my Pixel 7 Pro with Call of Duty Mobile and EA FC Mobile (the mobile game, not the FC 24 companion app). Both games worked fine before this last update but now cause the phone to go black, show a GrapheneOS splash screen, and then redirect me to the unlock screen. This happens regardless of the state of the Exploit Protection Compatibility setting.
I don't believe this is a full reboot because the yellow boot screen does not show up but there are no error messages or anything like that. I also briefly lose cell service when this occurs but perhaps that's tied to the UI somehow?
For some contrast, this error does not occur with Grimvalor, Combat Master, or Metal Mind. I don't know what the games that are crashing have in common. I've installed all of these games by way of the Play Store rather than something like Aurora.
I tried to edit my previous post again but was unable to. Sorry for the double post. Here's some additional information:
Uninstalling and then reinstalling Call of Duty Mobile did not resolve the issue. It may be worth noting that with both COD:M and EAFCM, it's possible to get past the authentication and update downloading screens. It's when the main menu of the game loads that the crash occurs.
eFootball appears to be another game that runs without any issues.
matchboxbananasynergy
I see a normal reboot of the device. From the initial boot screen: "Another operating system is booting"
other8026
Pixel 8 Pro?
nilmethod
In my case, a complete reboot.
As of the 2023120800 update, this issue is still present.
So, to be clear, all of the games you've mentioned worked previously?
Can you share some info about your setups?
secure_adict Pixel 8 Pro?
no, so maybe you can check if memory tagging is enabled for those apps. If it is, disable it.
other8026
No Google Play Service. And yes, games works without any problem before update.
ALL Security function is disabled, MTE - too. Here is problem with GOS, not with my settings. And not only I have it.
secure_adict okay. I just tried on my non-Google Play profile and both of the games you listed in your OP worked without any issues. So, it's confirmed that neither rely on Google Play or Google Play Games to run. But it should be noted that I installed them with Google Play and used ADB to install the existing apps in the other profile.
secure_adict Here is problem with GOS, not with my settings. And not only I have it.
Not sure how this can be a "problem with GOS" when both games work on my phone which is running GrapheneOS. They both worked after I enabled exploit protection compatibility mode for both games.
If I were in your situation, some of the things I'd try to troubleshoot are as follows:
logcat
, then triggering the reboot by launching either of those games to see if logcat
catches anything before the reboot.So, to be clear, all of the games you've mentioned worked previously?
Yes.
Do you have Sandboxed Google Play installed in the same profile?
Do both Google Play and Google Play Services have the network permission granted?
Have you installed Google Play Games, and does Google Play Games have network permission granted?
Yes, Yes, and No.
no, so maybe you can check if memory tagging is enabled for those apps. If it is, disable it.
I'm on a Pixel 7 Pro, does this apply to me? If so, how can I check for it?
both games work on my phone which is running GrapheneOS.
Were you on a brand new install or one that was upgraded? Did you manage to load into the game and actually play or simply get to the menus?
Connecting via ADB, running logcat, then triggering the reboot by launching either of those games to see if logcat catches anything before the reboot.
Trying to launch the games in another profile.
I'll try these in a bit. I did clear the cache for both of my games (cod:m and eafcmobile) with no success. I'll report back soon.
Thanks for the replies!
Trying to launch the games in another profile.
The game exhibits the same crash behavior but rather than giving me the unlock screen for the new profile, it gives me the unlock screen for my main profile.
I'll try ADB next.
Here is a crash from cod:m from yesterday. I don't end up with any sort of crash details in the logs for ea fc mobile (fifa mobile), just some stray bits of information about it.
I'm happy to post the full logs somewhere if it's safe to do so from a privacy perspective. It's about 40k lines going back over the last day or so and there's plenty of attempts to run the games in there.
12-08 23:13:11.664 9925 10001 E AndroidRuntime: FATAL EXCEPTION: UnityMain
12-08 23:13:11.664 9925 10001 E AndroidRuntime: Process: com.activision.callofduty.shooter, PID: 9925
12-08 23:13:11.664 9925 10001 E AndroidRuntime: java.lang.Error: signal 11 (SIGSEGV), code -6 (?), fault addr 000027db000026c5
12-08 23:13:11.664 9925 10001 E AndroidRuntime: Build fingerprint: 'google/cheetah/cheetah:14/UQ1A.231205.015/2023120800:user/release-keys'
12-08 23:13:11.664 9925 10001 E AndroidRuntime: Revision: 'MP1.0'
12-08 23:13:11.664 9925 10001 E AndroidRuntime: pid: 9925, tid: 10001, name: UnityMain >>> com.activision.callofduty.shooter <<<
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x0 0000d00d06df2710 x1 0000000000000800 x2 ffffffffffffffd8 x3 0000d07f64f99340
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x4 0000d07f64f99378 x5 000000000009abc0 x6 6d6067731f64716e x7 7f7f7f7f7f7f7f7f
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x8 000000000002e930 x9 0000000000000000 x10 0000000000000002 x11 0000000ffffdffff
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x12 0000000fffffffff x13 0000d32424db4880 x14 0000d32424db5780 x15 0000000ffff9ba3f
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x16 0000d3343618fe00 x17 0000d33436183030 x18 00000000ffffffff x19 0000d00cc127ebb0
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x20 0000d2c49e8be010 x21 0000d00cc127ec00 x22 0000000000000022 x23 0000000000000008
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x24 000000000000004f x25 0000000000000023 x26 0000d00cc0ed5000 x27 0000d00cc0c45e5c
12-08 23:13:11.664 9925 10001 E AndroidRuntime: x28 0000d240b7607d40 x29 0000000000000000 x30 0000d00cbffc4168
12-08 23:13:11.664 9925 10001 E AndroidRuntime: sp 0000d00d06df27f0 pc 0000d00cbffc41a8 pstate 0000000080001000
12-08 23:13:11.664 9925 10001 E AndroidRuntime:
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.0071d5f0(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.006e2cfc(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libsigchain.art::SignalChain::Handler(int, siginfo*, void*)(SignalChain:1152)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at [vdso].__kernel_rt_sigreturn(__kernel_rt_sigreturn:0)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.001951a8(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00194cd4(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00197b48(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00e16e98(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00d3771c(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00cecaa8(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00cd7c48(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00c88044(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00c72e74(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00c72ebc(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00c6f37c(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00557160(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.00556df8(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.001ba464(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.003d2b10(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.003d2678(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.006e6110(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.006e7274(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at libunity.006ea2a4(Native Method)
12-08 23:13:11.664 9925 10001 E AndroidRuntime: at base.0336d0b8(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: FATAL EXCEPTION: UnityMain
12-08 23:13:16.061 10051 10127 E AndroidRuntime: Process: com.activision.callofduty.shooter, PID: 10051
12-08 23:13:16.061 10051 10127 E AndroidRuntime: java.lang.Error: signal 11 (SIGSEGV), code -6 (?), fault addr 000027db00002743
12-08 23:13:16.061 10051 10127 E AndroidRuntime: Build fingerprint: 'google/cheetah/cheetah:14/UQ1A.231205.015/2023120800:user/release-keys'
12-08 23:13:16.061 10051 10127 E AndroidRuntime: Revision: 'MP1.0'
12-08 23:13:16.061 10051 10127 E AndroidRuntime: pid: 10051, tid: 10127, name: UnityMain >>> com.activision.callofduty.shooter <<<
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x0 0000dc0f0c85d890 x1 0000000000000800 x2 ffffffffffffffd8 x3 0000dc8289b6bc70
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x4 0000dc8289b6bca8 x5 000000000009b3e0 x6 6d6067731f64716e x7 7f7f7f7f7f7f7f7f
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x8 00000000000312aa x9 0000000000000000 x10 0000000000000002 x11 0000000effffffff
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x12 0000000fffffffff x13 0000df2cc625ac40 x14 0000df2cc6259b00 x15 0000000cf2fff7ff
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x16 0000df4321138e00 x17 0000df432112c030 x18 00000000ffffffff x19 0000dc0f0f8aebb0
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x20 0000de526cdb1010 x21 0000dc0f0f8aec00 x22 0000000000000036 x23 0000000000000008
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x24 0000000000000036 x25 0000000000000023 x26 0000ddffaa60d468 x27 0000000000000070
12-08 23:13:16.061 10051 10127 E AndroidRuntime: x28 0000de441e098540 x29 0000000000000000 x30 0000dc0f0e5f4168
12-08 23:13:16.061 10051 10127 E AndroidRuntime: sp 0000dc0f0c85d970 pc 0000dc0f0e5f41a8 pstate 0000000080001000
12-08 23:13:16.061 10051 10127 E AndroidRuntime:
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.0071d5f0(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.006e2cfc(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libsigchain.art::SignalChain::Handler(int, siginfo*, void*)(SignalChain:1152)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at [vdso].__kernel_rt_sigreturn(__kernel_rt_sigreturn:0)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.001951a8(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00194cd4(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00197b48(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00e16e98(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00cb52b8(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00d37650(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00cecaa8(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00cd7c48(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00c88044(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00c72e74(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00c72ebc(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00c6f37c(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00557160(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.00556df8(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.001ba464(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.003d2b10(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.003d2678(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.006e6110(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.006e7274(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at libunity.006ea2a4(Native Method)
12-08 23:13:16.061 10051 10127 E AndroidRuntime: at base.0336d0b8(Native Method)
12-08 23:15:42.626 27598 27598 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x38 in tid 27598 (surfaceflinger), pid 27598 (surfaceflinger)
12-08 23:15:42.851 11145 11145 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-08 23:15:42.851 11145 11145 F DEBUG : Build fingerprint: 'google/cheetah/cheetah:14/UQ1A.231205.015/2023120800:user/release-keys'
12-08 23:15:42.851 11145 11145 F DEBUG : Revision: 'MP1.0'
12-08 23:15:42.851 11145 11145 F DEBUG : ABI: 'arm64'
12-08 23:15:42.851 11145 11145 F DEBUG : Timestamp: 2023-12-08 23:15:42.715505797-0600
12-08 23:15:42.851 11145 11145 F DEBUG : Process uptime: 1391s
12-08 23:15:42.851 11145 11145 F DEBUG : Cmdline: /system/bin/surfaceflinger
12-08 23:15:42.851 11145 11145 F DEBUG : pid: 27598, tid: 27598, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
12-08 23:15:42.851 11145 11145 F DEBUG : uid: 1000
12-08 23:15:42.851 11145 11145 F DEBUG : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
12-08 23:15:42.851 11145 11145 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000038
12-08 23:15:42.851 11145 11145 F DEBUG : Cause: null pointer dereference
12-08 23:15:42.851 11145 11145 F DEBUG : x0 0000000000000000 x1 0000000000000000 x2 000001f6f34e136b x3 0000000c89c4f833
12-08 23:15:42.851 11145 11145 F DEBUG : x4 00ffffffffffffff x5 00000000000ad414 x6 0000000000000000 x7 0000f62ef7ef8458
12-08 23:15:42.851 11145 11145 F DEBUG : x8 0000000000000001 x9 75af5b5f4f6ec400 x10 000000003b9aca00 x11 000000003b9ac9ff
12-08 23:15:42.851 11145 11145 F DEBUG : x12 0000c91563cd3030 x13 000000007fffffff x14 00000000000ad414 x15 0000000c89c78451
12-08 23:15:42.851 11145 11145 F DEBUG : x16 0000aeb2eb3650b0 x17 0000c9155cb5dfb0 x18 0000c91563398000 x19 b400c6ddba88c080
12-08 23:15:42.851 11145 11145 F DEBUG : x20 0000aeb2eb360f68 x21 b400c70d03425780 x22 0000000000000000 x23 b400c6c92fc4f7c0
12-08 23:15:42.851 11145 11145 F DEBUG : x24 b400c62de1b24d50 x25 00000000ffffffff x26 0000000000000000 x27 b400c809bc192000
12-08 23:15:42.852 11145 11145 F DEBUG : x28 b400c809bc499000 x29 0000f62ef7ef8f60
12-08 23:15:42.852 11145 11145 F DEBUG : lr 0000aeb2eaeaad50 sp 0000f62ef7ef8f60 pc 0000c9155cb5dfc4 pst 0000000060001000
12-08 23:15:42.852 11145 11145 F DEBUG : 9 total frames
12-08 23:15:42.852 11145 11145 F DEBUG : backtrace:
12-08 23:15:42.852 11145 11145 F DEBUG : #00 pc 000000000002afc4 /system/lib64/libui.so (android::FenceTime::getSignalTime()+20) (BuildId: d2b383707511abe9bd896052a175b0ce)
12-08 23:15:42.852 11145 11145 F DEBUG : #01 pc 0000000000213d4c /system/bin/surfaceflinger (android::SurfaceFlinger::composite(android::PhysicalDisplayId, android::ftl::SmallMap<android::PhysicalDisplayId, android::scheduler::FrameTargeter*, 3ul, std::__1::equal_to<android::PhysicalDisplayId> > const&)+3516) (BuildId: 74996169538f683e3ab843ce8e4b62ed)
12-08 23:15:42.852 11145 11145 F DEBUG : #02 pc 00000000001ee498 /system/bin/surfaceflinger (android::scheduler::Scheduler::onFrameSignal(android::ICompositor&, android::VsyncId, android::TimePoint)+600) (BuildId: 74996169538f683e3ab843ce8e4b62ed)
12-08 23:15:42.852 11145 11145 F DEBUG : #03 pc 0000000000018b08 /system/lib64/libutils.so (android::Looper::pollInner(int)+376) (BuildId: 8371c3b1bd7778d8ad524c2f5adb64da)
12-08 23:15:42.852 11145 11145 F DEBUG : #04 pc 000000000001892c /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+124) (BuildId: 8371c3b1bd7778d8ad524c2f5adb64da)
12-08 23:15:42.852 11145 11145 F DEBUG : #05 pc 00000000001def0c /system/bin/surfaceflinger (android::impl::MessageQueue::waitMessage()+92) (BuildId: 74996169538f683e3ab843ce8e4b62ed)
12-08 23:15:42.852 11145 11145 F DEBUG : #06 pc 00000000001ee22c /system/bin/surfaceflinger (android::scheduler::Scheduler::run()+28) (BuildId: 74996169538f683e3ab843ce8e4b62ed)
12-08 23:15:42.852 11145 11145 F DEBUG : #07 pc 000000000025b930 /system/bin/surfaceflinger (main+1792) (BuildId: 74996169538f683e3ab843ce8e4b62ed)
12-08 23:15:42.852 11145 11145 F DEBUG : #08 pc 000000000005a6f8 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+104) (BuildId: ffd6f1c31b8e101bb6b86eee2bcdaa01)
nilmethod
com.activision.callofduty.shooter
Before, I was testing with a different game, so I tried this one. This game is also working fine.
nilmethod
SIGSEGV
This is a memory error, and considering the stack trace has a lot of Unity stuff and Unity is written in C++, a language where this kind of error is very common, it is not surprising there's a memory bug in there somewhere.
Are you sure you enabled Exploit Protection Compatibility Mode in Settings > Apps > All apps > Call of Duty > Exploit Protection Compatibility Mode
? The game crashes for me if I forget to enable this. It won't get past the splash screen before restarting non-stop.
nilmethod I did clear the cache
There should be two options there. Did you clear the storage?
Also, just to make sure we're on the same page it's here: Settings > Apps > All apps > Call of Duty > Storage and cache
@other8026 Trying to launch the games in another profile.
The game exhibits the same crash behavior but rather than giving me the unlock screen for the new profile, it gives me the unlock screen for my main profile.
When trying in another profile, did you turn on Exploit Protection Compatibility Mode in that profile as well before attempting to launch the game?
nilmethod I'm on a Pixel 7 Pro, does this apply to me?
No. That feature is only available on the two Pixel 8 models.
Are you sure you enabled Exploit Protection Compatibility Mode in Settings > Apps > All apps > Call of Duty > Exploit Protection Compatibility Mode? The game crashes for me if I forget to enable this. It won't get past the splash screen before restarting non-stop.
yes. that's always been necessary for either of these games to run.
There should be two options there. Did you clear the storage?
Also, just to make sure we're on the same page it's here: Settings > Apps > All apps > Call of Duty > Storage and cache
yes. i cleared both on both games before launching.
When trying in another profile, did you turn on Exploit Protection Compatibility Mode in that profile as well before attempting to launch the game?
yes.
another person in my household has a pixel 7 pro with grapheneos running on it as well. after they run the update i'll see if they're able to run cod:m and eafc mobile as well. they don't play either game so it'll be fresh installs. will report back soon.
other8026
Please stop told that game work. Coz today I bought new P8P, fresh GOS and game not working. After system crash I got 5 errors with: surfacefinger has crashed
So that's problem with GOS and stop tell me that it works. Thank you.
nilmethod
That's problem with surfacefinger