other8026

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.

          secure_adict Please stop told that game work.

          I don't think other8026 claimed the games work on your device! I think other8026 claimed the games worked on their device. Personally I see no reason to disbelieve either claim.

          It may or may not be possible for people on this forum to help you solve the problem you are experiencing on your device. But people telling other people to stop describing their personal experiences doesn't seem likely to help.

                secure_adict
                The way people configure their device can lead to unexpected issues. It may be that a bug only hits people with their device configured in a certain way.

                There are a number of AOSP bugs which only effect a subset of GrapheneOS users.

                Have you changed any permissions for these apps? Maybe sensors or network? Changed anything in developer options or via adb on your devices? Changed permissions for any system apps?

                    @secure_adict

                    i think that @other8026 was trying to be helpful by describing the state of things on their device.

                    Carlos-Anso

                    Have you changed any permissions for these apps? Maybe sensors or network? Changed anything in developer options or via adb on your devices? Changed permissions for any system apps?

                    in my case i've not done any of this. i was able to play the game(s), i rebooted after the update installed, and then the games no longer worked.

                      I'm having the exact same issue, though I don't have any games installed.
                      It's becoming quite a problem because alarms aren't going off and it can restart whilst I'm driving and using my phone for navigation.

                        Quick update after some experimenting:

                        • I had previously played Diablo Immortal on this phone before the update but it's been uninstalled for some time. I just installed it and it works fine with the exploit setting enabled.
                        • I have never installed need for speed on this phone and I just installed it. It appears to work just fine without the exploit setting enabled.

                        I haven't yet been able to test some of the listed games on the other Pixel 7 Pro running GrapheneOS in my household but this information seems to point to the issue not being the games themselves but something unique to our individual setups.

                        The pattern appears to be that some games installed before the update will no longer run, even after re-installation. What artifacts could they be leaving behind or what new setting did the latest GrapheneOS updates introduce that might be enabled now that weren't before?

                        Additionally, what might have changed that would cause the games to not open even in a brand new profile?

                        A further data point: I installed Genshin Impact and ran it with the exploit setting enabled and it worked fine. This is another game that I had uninstalled prior to the latest update that I played heavily and worked before. It works now.

                        @secure_adict could you try installing EA FC Mobile 24 to see if it runs for you or crashes in the same way? Also, have you installed or played that game on your device before?

                        I am experiencing this issue on P7 Pro: on boot, Graphene loads and shows the lock screen. Once I tap to the screen, it bonces back to Graphene logo (looks like rebooting) and displays the lock screen again and it works.

                        On P8 Pro, I thie issue occurs when changing display resolution from normal to max.

                          Volen i have this lock screen "bounce" when one of the games crashes. hadn't really noticed it before now.

                            Since I can't reproduce any of the issues any of you have been having, I can't check. However, I'm guessing the newest release will fix your problems. See this comment by the project account explaining a couple of the changes: https://discuss.grapheneos.org/d/9582-grapheneos-version-2023121200-released/4

                            The release is in beta. I haven't seen anyone who's had issues, so it will likely hit stable soon.

                              Sunny
                              Thought I'd just add to this;
                              Sometimes when it restarts itself there's no system notifications, my VPN is still running, but the Casio watch app isn't.
                              Sometimes there are GrapheneOS notifications with no VPN running or anything: https://imgur.com/a/7nqgHsl
                              Restarting might remove the notifications as if everything was fine, or it might display the same notifications. It's a 50/50.
                              I've only been having this issue since the same update as OP.