Is there an e/OS build of the GmsCore apks available anywhere?

Using /e/OS
1

Hello all,

Short summary of my issue:
Because of a naive attempt to fix my microG, I uninstalled my GmsCore applications (com.android.vending and com.google.android.gms) breaking all the applications relying on it. Is there an official e/os build of the GmsCore apks with the right signatures so I can reinstall them manually over adb? Or any other fix that does not require complete reinstall?

Device: Fairphone 4
e/os version: 3.1.1-a14-20250828521479-official-FP4 (updating to 3.2 at the moment)

Long version:
My google maps did not work anymore so I tried to update GmsCore. The official GmsCore build however has different signatures so I came to the idea to uninstall the current one first to I can install the build from microG. I removed them with adb uninstall com.google.android.gms and adb uninstall com.android.vending, but was not able to install the build from microg (at github microg/GmsCore/releases). Now I completely destroyed microG service on my phone. I tried to update to a new minor version 3.1.0 e/os with the hope that it is reinstalled but it did not work. I looked into the e/os fork of GmsCore e / os / GmsCore · GitLab but could not find any installable apk there. Also when looking at the e/os builds /e/OS official FP4 download I had troubles to locate a GmsCore apk that I could install separately. Currently I am updating up to 3.2 to see if it fixes it but I don’t have much hope since the update to 3.1.0 did not do so.

I would be grateful for some help.

Best
alexgo

3

To be successful you usually have to do this for user-0 only, otherwise I would expect a terminal reported error.

Once you do user0 uninstall you must reverse the command, else updates will retain the user0 “changed” situation.

If you did not create a user0 difference, then update or upgrade is expected to fix.

2 Likes
4

Thanks for the quick replies. Indeed I only uninstalled it for user 0. I was not aware that I was only uninstalling it for a certain user and that the package is still available for reinstallation. I thought I was doing something something like sudo when specifying user 0. So just undoing it for user 0 fixed the issue. What I did exactly before was
adb shell pm uninstall --user 0 com.google.android.gms
adb shell pm uninstall --user 0 com.google.vendor
and what reverted these changes was:
adb shell pm install-existing com.google.android.gms --user 0
adb shell pm install-existing comcom.google.vendor --user 0
Thanks again. Problem solved.

2 Likes
5

This topic was automatically closed after 66 days. New replies are no longer allowed.