GmsCompat / gms crashes after update to 25.10.36

RIC98

I've just updated Google Play services from version 25.08.32 to 25.10.36.

1) When I tap on Apps | Sandboxed Google Play | Google Location Accuracy, GmsCompat crashes:
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.google.android.gms/com.google.android.gms.location.settings.LocationAccuracyV31Activity}; have you declared this activity in your AndroidManifest.xml, or does your intent not match its declared <intent-filter>?
Workaround: Apps | Sandboxed Google Play | Google Settings | Location Accuracy is working.

2) When I restart the phone or unlock private space there is another crash message:
type: crash
package: com.google.android.gms:251036035
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.StatsManager.setBroadcastSubscriber(android.app.PendingIntent, long, long)' on a null object reference

other8026

RIC98 When I tap on Apps | Sandboxed Google Play | Google Location Accuracy, GmsCompat crashes

I just tried on my phone and it doesn't crash.

RIC98 When I restart the phone or unlock private space there is another crash message:
type: crash
package: com.google.android.gms:251036035
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.StatsManager.setBroadcastSubscriber(android.app.PendingIntent, long, long)' on a null object reference

Have you updated your OS? As far as I can tell, this should be fixed after the 2025040400 release. Try updating your device.

RIC98

other8026 Yes, that's correct, I am still on version 2025021100. I have motor impairments and therefore have difficulties performing fine movements. Because of this, I rely on the 3-button navigation, as gesture navigation is very difficult for me.
With Android 15 QPR2, Google introduced two changes:

The vibrations or haptics were made worse, see here and here
and even more critically: The sensitivity of the 3-button navigation was changed.
Previously, the touch area for the buttons was pleasantly large, as shown here:
https://ibb.co/v4VNKWpJ
With QPR2, the touch area was drastically reduced (see yellow marking), making it hard for me to hit the buttons accurately:
https://ibb.co/x8DWGtjW

For these two reasons, I am currently unable to update to a newer GrapheneOS version and waiting for Google or the GrapheneOS team to fix these two bugs, because I am unable to use it due to my disability.

Is there a way to prevent the crashes when restarting or when unlocking the Private Space?
Or is it possible to reinstall version 25.08.32 of the Google Play Services?

other8026

RIC98 Sorry, I'm afraid I don't know a way to help you with the problems you've listed.

RIC98 The vibrations or haptics were made worse

I personally haven't noticed a single difference on either of my phones.

RIC98 and even more critically: The sensitivity of the 3-button navigation was changed.

I can see how this can be a problem. I just tried on my old phone and could only make the buttons bigger by changing accessibility settings. Might that be a solution? I changed "display size" in accessibility settings, but that makes everything bigger, not just the buttons, which may not be what you want.

RIC98 Is there a way to prevent the crashes when restarting or when unlocking the Private Space?

I don't believe so.

RIC98 Or is it possible to reinstall version 25.08.32 of the Google Play Services?

In short, not any way that I'd suggest.

I definitely wouldn't suggest getting apks from elsewhere on the Internet. I do know that there's some process that the developers use to get a version of Play and or Play Services that has support for multiple locales (if I'm remembering the right word here). All the files for installing older versions of Play Store or Play Services are probably not on the servers anymore. Also, I don't know if other apks that you can find elsewhere on the Internet will even work or be compatible with GrapheneOS's compatibility layer. Another problem, if I'm remembering correctly, is that installing Google Play can only be done by the GrapheneOS App Store app. There's a way to get around that, but I can't remember how right now.

Sorry, not sure what to suggest. Staying on an older version will result in more things breaking as time goes on. Maybe the best way forward would be to update and use the display size accessibility setting?