GmsCore
docker-lineage-cicd
GmsCore | docker-lineage-cicd | |
---|---|---|
430 | 36 | |
7,043 | 473 | |
5.8% | 0.6% | |
9.5 | 8.7 | |
6 days ago | 8 days ago | |
Java | Shell | |
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
-
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/)
- New version out 0.30
docker-lineage-cicd
-
Ubuntu ISO Image with all build tools installed?
That is a great idea. Googling this gave me a great docker lineage ubuntu build image here: https://github.com/jfloff/docker-lineageos (or alternatively for microg? https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd ). It looks like some older images (6+years) are in dockerhub as well. I like the approach by João (first link above) and will give it a go on my Intel i7 machine. I have an old school rotating HDD with enough space for the 80GB+ that lineageos seems to need for building.
-
Is there a build howto for Lineage + MicroG
In the FAQ of the official website this docker image is linked.
-
Is it safe to do a minor system update on lineage os microg
You're right, it's specific to LineageOS for microG, and https://github.com/lineageos4microg/docker-lineage-cicd/issues is the right place to report issues about it.
-
NVIDIA Shield TV Pro 2019 - Questions about running LineageOS
It uses this docker microservice to do the job.
-
Building LineageOS for MicroG for (Terminal) Emulator/AVD
However, I cannot find instructions on how to do it on the LineageOS for MicroG Docker GitHub page (link: https://github.com/lineageos4microg/docker-lineage-cicd). There has even been a issue/feature request opened for it, but it was closed as "Completed" without any response (link: https://github.com/lineageos4microg/docker-lineage-cicd/issues/336).
-
Two Questions Regarding MicroG and LineageOS with MicroG
AFAIK signature spoofing is only activated for privileged aka system apps.
-
lineageos 20 for MicroG
January 15th
-
LineageOS for MicroG Docker Build Error (error: vendor/lineage/build/soong/Android.bp:24:8: module "generated_kernel_includes": cmd: unknown variable '$(PATH_OVERRIDE_SOONG)')
These are the patches that enable signature spoofing permissions https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/android_frameworks_base-S.patch https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/packages_modules_Permission-S.patch you can see exactly what you need to change in the source files according to this. Also add https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/frameworks_base_config.xml#L19-L25 to your device overlay properties. Clone https://github.com/lineageos4microg/android_vendor_partner_gms into vendor/partner_gms (or anywhere else really for that matter, you can just copypaste it into your device tree) and add -include ../../../vendor/partner_gms/products/gms.mk (or whatever directory you have this in) into your device.mk
-
Error Building LineageOS for MicroG for Unsupported Device Using Docker (>> [Sun Dec 4 07:08:58 UTC 2022] breakfast failed for unsupported_phone-userdebug, lineage-19.1 branch)
I am trying to build LineageOS for MicroG for an unsupported device by following the last example for building for unsupported devices on the GitHub page for building LineageOS for MicroG using Docker (https://github.com/lineageos4microg/docker-lineage-cicd). However, when I run the docker command, everything goes fine until it crashes and I get the following error:
- Updates vor LineageOS vs. Updates for LineageOS for microG
What are some alternatives?
MinMicroG - Sources and scripts for MinMicroG installers. You shall find no prebuilt releases here.
FakeGApps - A better approach for microg
docker-lineageos - A more automated Docker-based build environment for LineageOS
openauto - AndroidAuto headunit emulator
proprietary_vendor_google
UnifiedNlp - Alternative network location provider for Android, with plugin interface to easily integrate third-party location providers.
NanoDroid - [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository
opengapps - The main repository of the Open GApps Project
FakeGApps - Signature spoofing for MicroG as an Xposed module
anbox - Anbox is a container-based approach to boot a full Android system on a regular GNU/Linux system
LineageOTA - A simple OTA REST Server for LineageOS OTA Updater System Application