• GeneralSolved
  • Should we rename "Google Play Services" to "Google Mobile Services"?

I think GrapheneOS should rename Google Play Services to Google Mobile Services (in OS itself, on GrapheneOS website, and everywhere else it can) because:

  • Google Mobile Services (abbreviated as GMS in package names) is the correct term
  • Google Play Services is often misread and/or misinterpreted as Google Play Store

"Play services" app is not GMS. Its internal name is "GmsCore".

GMS is "a collection of Google applications and APIs that help support functionality across devices":
https://www.android.com/gms/

GrapheneOS devs cannot rename it. Google gave the app the package name com.google.android.gms, but the name of the app is Google Play services. The package name and app name are coded into the app itself. Renaming the app would be virtually impossible. The only way they could change the name would be to get the proprietary source code, change the name, then compile the app with Google's signing key.

Yes, GmsCore is the core of Google Mobile Services. Part of the latest GrapheneOS updates includes:

Sandboxed Google Play compatibility layer: add back Bluetooth shim unable to be covered by GmsCompatConfig hooks
Sandboxed Google Play compatibility layer: redirect privileged settings APIs to partial implementation by GmsCompat app

Hulk changed the title to Should we rename "Google Play Services" to "Google Mobile Services"? .