GmsCore
Magisk
GmsCore | Magisk | |
---|---|---|
432 | 430 | |
7,107 | 44,612 | |
6.7% | - | |
9.5 | 9.6 | |
4 days ago | 4 days ago | |
Java | C++ | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GmsCore
-
Apple Introduces M4 Chip
I, an engineer, am not doing this myself, too. There is a middle ground though: just use a privacy-oriented Android build, like DivestOS. [1]
There are a couple caveats:
1. It is still a bit tricky for a non-technical person to install. Should not be a problem if they know somebody who can help, though. There's been some progress making the process more user friendly recently (e.g. WebUSB-based GrapheneOS installer).
2. There are some papercuts if you don't install Google services on your phone. microG [2] helps with most but some still remain. My main concern with this setup is that I can't use Google Pay this way, but having to bring my card with me every time seems like an acceptable trade off to me.
[1]: https://divestos.org/
[2]: https://microg.org/
-
Google Fit APIs get shut down in 2025, might break fitness devices
I have been running de-googled LineageOS since before it renamed/reformed from CyanogenMod, so since somewhere around 2013/14. That has looked rather different depending on what exactly I need from my phone but I'll share what my current set up looks like.
First, I have don't use any kind of Google/Samsung/Apple Pay wallets so if you do, this may not be helpful; I've never looked into trying to get any of those working. Also, by "de-googled" I mean that I don't have GApps installed on my phone. I do have microG[0] installed as a Magisk[1]/LSPosed[2] module; this allows a few apps to believe I have GApps while most apps do not see/have access. I do not turn on microG for any apps (i.e. no connection to the Google servers/services via microG).
Most of my apps come from F-Droid[3], a few from Aurora Store[4] (a 3rd-part frontend for the Play Store that does not require either an account or GApps installed), a very few from FFupdater[5], and have played with using Obtanium[6] but currently only have one (weather) app updating via it. I have several different repositories configured in F-Droid but I don't generally keep mental track of which repository I am dependent on for which apps; the default, IzzyOnDroid[7], Bitwarden[8], NewPipe[9], microG[10], and Collabora[11] are some of them.
I have two banking apps installed via Aurora Store, one of which requires microG and root-hiding (via Magisk module) while the other doesn't require either. My browsers (Firefox, Firefox Klar, Brave) come from FFupdater and none require microG. My texting (QUIK SMS), email (K-9 Mail), TOTP authenticator (Aegis), password manager (Bitwarden), GPS/Maps (OsmAnd), file syncing (Nextcloud), notes (Nextcloud Notes), HN reader (HN), and Contacts/Calendar sync (DAVx5, ICSx5) apps all come via F-Droid (either the main repo or others). I have many others apps which come from F-Droid or Aurora Store but the above are my most used.
For file, calendar, notes, photo, & contact syncing, I have a Nextcloud server set up and find it to work quite well; the Nextcloud apps are also quite good. Someone who doesn't want to run their own could use a hosted account[12]. Contacts & calendars are synced to Nextcloud via DAVx5 & ICSx5.
The primary challenges I am aware of at this point are hardware (it is increasingly difficult to install LineageOS on most hardware due to bootloader locks), and navigation (OpenStreetMap data usually doesn't include addresses in the USA). For hardware, the solution is essentially just to properly research the phone you want to buy; I always make sure the model is well supported by LineageOS before purchasing and then tend to hang on to it for several years. For navigation, I usually find the address on my desktop or mobile browser (via DuckDuckGo) and then manually input the location into OsmAnd before the trip but I also keep WeGo Here maps installed in case I don't have time for that (it usually takes <2 minutes and rarely more than 5 to manually find & enter the address). Additionally, getting the one banking app to work without GApps was a pain in the butt initially (requiring testing several Magisk & LSPosed modules), but now it just works and I don't really think about it.
Overall, I don't find my version of de-googled to be a detriment; my phone is useful and I have more control over my data and over annoyances (such as unnecessary notifications) than I would otherwise.
[0] https://microg.org
-
LineageOS is currently installed on 1.5M Android devices
Is anyone here daily-driving microg and can share their experiences? https://github.com/microg/GmsCore/wiki/Implementation-Status does not exactly inspire confidence.
-
Google Update Reveals AI Will Read All Your Private Messages
...will need to be rewritten to avoid Google Play Services.
Not true.
All that needs to happen is for open source developers to "re-implement Google’s proprietary Android user space apps and libraries".
https://microg.org/
-
A closer look at e/OS: Murena's privacy-first 'deGoogled' Android alternative
microG itself connects directly to Google: https://github.com/microg/GmsCore/wiki/Google-Network-Connec...
No shit, of course they do.
>In general, we obviously try to minimize the connections to Google, but some services strictly rely on them and would just not work without.
What exactly do you think they should do instead?
-
I need a help
MicroG
-
Plans to update to 0.3 in microg's lineage builds?
In release notes for GmsCore v0.2.29.233013 (https://github.com/microg/GmsCore/releases/tag/v0.2.29.233013), I also see:
-
[Help] Is there a module I can install that enables push notifications on a device without google services?
Yes, the Xposed module is one way. There are also other ways
- Firefox for Android is adding support for 400 add-ons
-
Which MicroG fork and version should I use?
Which one should I use? Is this MicroG's official website right? (https://microg.org/)
Magisk
- Google Fit APIs get shut down in 2025, might break fitness devices
- [Discussion] Can anyone ELI5 what is play integrity, what Google is doing to it, and does it only affect rooted users?
-
⟳ 4 apps added, 39 updated at f-droid.org
Magisk (version 26.4): The Magic Mask
-
⟳ 0 apps added, 15 updated at apt.izzysoft.de
Magisk (version 26400): Companion app for Magisk
-
Rooting the Boox Tab Mini C
At this point download locally the Magisk APK onto your computer found here: https://github.com/topjohnwu/Magisk/releases. Reboot your Tab Mini C by holding the power button until you see the power come back on and the default power on screen begin loading. Once it has fully booted copy the Magisk APK, `boot_a.bin`, and `boot_b.bin` files via USB. Make certain to have backups of the `boot_a.bin` and `boot_b.bin` files in case something goes wrong (such as you bricking your device) and you need the old firmware. Install the Magisk APK. For the rest of this we will be following a summarized version of the instructions here: "https://topjohnwu.github.io/Magisk/install.html". Once the Magisk app is installed open it and press the "Install" button. Then click "Select and Patch a File" and select `boot_a.bin` then `boot_b.bin` files to install Magisk on both. At this point one should rename them to be `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` based on which one Magisk patched to make it easier for you. At this point transfer `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` back to the main computer over USB. Open up QFIL and once again run `adb reboot edl`. FAIRLY QUICKLY to avoid errors click the "Select Port" button and click the USB port which the Tab Mini C is plugged into and then click OK. Still quickly click "Tools" -> "Partition Manager" and then click OK on the popup. Within the partition manager find `boot_a` and `boot_b`. For each individually right click on the partition and then click "Manage Partition Data". Then click "Load Image" and point to the corresponding `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` depending on which partition you're patching. Once both of them are patched, quit out of QFIL. Force the reboot of the device by holding down the power button. Open the Magisk app and click on "Install" at which point their should be a new option "Direct Install". Use that to install directly onto the device after which it should give you the option to reboot. Reboot it and you now have a wonderfully rooted device. Happy reading
- Magisk: The Magic Mask for Android
-
[ROOTED METHOD #2] Smali Patcher Guide for Android 7, 8, 9, 10, and 11 with a Magisk Rooted device
Install Magisk app onto your device: https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
- Magisk v26.3 Stable
-
[Help] I flashed magisk.apk and not the .zip by mistake and phone is bricked!
Magisk Version: Magisk v26.2
- Magisk version 26.2 released
What are some alternatives?
MinMicroG - Sources and scripts for MinMicroG installers. You shall find no prebuilt releases here.
Termux-ADB - Install ADB & FastBoot Tools in Termux!
FakeGApps - A better approach for microg
Xposed-NetworkSpeedIndicator - Network Speed Indicator
openauto - AndroidAuto headunit emulator
Riru - Inject into zygote process
UnifiedNlp - Alternative network location provider for Android, with plugin interface to easily integrate third-party location providers.
safetynet-fix - Google SafetyNet attestation workarounds for Magisk
opengapps - The main repository of the Open GApps Project
LSPosed - LSPosed Framework
anbox - Anbox is a container-based approach to boot a full Android system on a regular GNU/Linux system
universal-android-debloater - Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.