lineageos4microg / android_prebuilts_prebuiltapks Goto Github PK

Currently fresh installs of LineageOS for microG causes bootloops on devices. The problem apparently is the "android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST" permission is missing on "privapp-permissions-com.google.android.gms.xml"

More information, and credits to, cha0sh3r0 on https://forum.xda-developers.com/showpost.php?p=79726273&postcount=1417

TLDR: I propose you include Aurora Services as a system app

Of the three methods for installing Play Store apps mentioned on the website (PlayMaker, GPlayWeb and Yalp Store), none of them appear to be actively maintained and only Yalp Store is usable by those unwilling or unable to set up their own server.

Aurora Store seems to be a (the most?) accessible and well maintained Play store client. It can install apps using root, by prompting the user or with Aurora Services if that is installed as a system app.

Sideloading system apps and keeping them up to date seems to be difficult/impossible if you don't use Magisk (in my case I don't want to deal with the added complexity of OTAs that Magisk incurs). If Lineage for microG included Aurora Services by default, any user who installed Aurora would get auto app installations without the hassle. The value proposition is similar to that of the F-Droid Privileged Extension you already include (which is awesome).

Thanks for all your hard work, please let me know if this isn't the appropriate place to make such proposals.

EDIT: if the idea is accepted and it's just a matter of infrastructure work to make it happen, I'm more than happy to do that if pointed in the right direction.

I started working on this in my PR, but it ended up being more complicated than I had initially expected. Just doing a drop in replacement of the new 2.11 apk results in the phone getting stuck in the boot animation (on Enchilada. ADB still worked.) I'm going to try to work on this with my limited time, but would really appreciate any help.

I am having a problem with apps not drawing maps, they however are able to got a location and draw indicators, the maps themselves are just blank.

I have a fresh install of the Hammerhead zip, I have given UnifiedNlp all the required rights, self-check indicated everything is ok and backends are enabled.

On the microg issues page I have been unable to find any similar problems so I am guessing it is somehow related to lineageos4microg

Hi, there doesn't seem to have been as resolution of the privacy guard feature downgrade for LineageOS17+, and so version 16 seems the most secure one available, from many people's perspective. Versions were available on
https://download.lineage.microg.org/

but are no longer listed. Are they available anywhere, to your knowledge, and if not, would it be possible to create new builds using
https://github.com/lineageos4microg/docker-lineage-cicd

Seems both APIs will be closed. LOS will remove both weather providers when these commits are merged:
LOS 15.1:
https://review.lineageos.org/c/LineageOS/android/+/237893
LOS 16.0:
https://review.lineageos.org/c/LineageOS/android/+/227747

There is a new feature in F-Droid starting in v1.5 that lets the ROM add repos to F-Droid. This is done with an additional_repos.xml file. Here's what it would look like for https://microg.org/fdroid/repo:

/system/etc/org.fdroid.fdroid/additional_repos.xml:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string-array name="additional_repos">
        <!-- name -->
        <item>microG F-Droid repo</item>
        <!-- address -->
        <item>https://microg.org/fdroid/repo</item>
        <!-- description -->
        <item>This is a repository of microG apps to be used with F-Droid. Applications in this repository are signed official binaries built by the microG Team from the corresponding source code.</item>
        <!-- version -->
        <item>19</item>
        <!-- enabled -->
        <item>1</item>
        <!-- push requests -->
        <item>ignore</item>
        <!-- pubkey -->
        <item>308202ed308201d5a003020102020426ffa009300d06092a864886f70d01010b05003027310b300906035504061302444531183016060355040a130f4e4f47415050532050726f6a656374301e170d3132313030363132303533325a170d3337303933303132303533325a3027310b300906035504061302444531183016060355040a130f4e4f47415050532050726f6a65637430820122300d06092a864886f70d01010105000382010f003082010a02820101009a8d2a5336b0eaaad89ce447828c7753b157459b79e3215dc962ca48f58c2cd7650df67d2dd7bda0880c682791f32b35c504e43e77b43c3e4e541f86e35a8293a54fb46e6b16af54d3a4eda458f1a7c8bc1b7479861ca7043337180e40079d9cdccb7e051ada9b6c88c9ec635541e2ebf0842521c3024c826f6fd6db6fd117c74e859d5af4db04448965ab5469b71ce719939a06ef30580f50febf96c474a7d265bb63f86a822ff7b643de6b76e966a18553c2858416cf3309dd24278374bdd82b4404ef6f7f122cec93859351fc6e5ea947e3ceb9d67374fe970e593e5cd05c905e1d24f5a5484f4aadef766e498adf64f7cf04bddd602ae8137b6eea40722d0203010001a321301f301d0603551d0e04160414110b7aa9ebc840b20399f69a431f4dba6ac42a64300d06092a864886f70d01010b0500038201010007c32ad893349cf86952fb5a49cfdc9b13f5e3c800aece77b2e7e0e9c83e34052f140f357ec7e6f4b432dc1ed542218a14835acd2df2deea7efd3fd5e8f1c34e1fb39ec6a427c6e6f4178b609b369040ac1f8844b789f3694dc640de06e44b247afed11637173f36f5886170fafd74954049858c6096308fc93c1bc4dd5685fa7a1f982a422f2a3b36baa8c9500474cf2af91c39cbec1bc898d10194d368aa5e91f1137ec115087c31962d8f76cd120d28c249cf76f4c70f5baa08c70a7234ce4123be080cee789477401965cfe537b924ef36747e8caca62dfefdd1a6288dcb1c4fd2aaa6131a7ad254e9742022cfd597d2ca5c660ce9e41ff537e5a4041e37</item>
    </string-array>
</resources>

0.2.12 was just released, including an implementation of the Exposure Notification API.

Not sure which ROMs are using this repo, but it might be useful to include my repo with additional_repos.xml. As this "stinks" a little like ego-promo 😷, let me give some background:

• my repo currently holds close to 600 apps – usually those not (yet) fully compliant with F-Droid's includion policy, but pretty close to
• my repo is to F-Droid like something in between "nonfree" and "universe" to Debian
• apps in my repo are the originals from their resp. developers, signed with their keys (which is why F-Droid doesn't include it by default: I don't build the apps myself from their resp. sources)
• APKs are checked against various tools (currently: VirusTotal plus a local library scanner; identified libraries are listed on the website)
• no tracking apart from the usual web server logs, which are rotated to /dev/null after a couple of weeks and are only consulted for trouble-shooting (I'm a privacy proponent and known as such)
• and yes, I'm one of the F-Droid maintainers 😉 – but I'm not asking in that role (so this is no "official request from F-Droid", but rather my personal suggestion)

No bad feelings if you say "no", it's just a suggestion. After all you even include tools to access Google Play 🤣 So my suggestion is to include my repo but have it turned off by default, so users can easily enable it if they want to. There's no "archive", just the "main repo".

You might wish to do the same for the Kali Nethunter repo, btw, for another ~50 apps.

F-Droid website still links to 1.9 apk for some reason, but 1.10 has been available from the repos for a little while, it turns out.

https://f-droid.org/en/packages/org.fdroid.fdroid/

Sorry if this isn’t the right forum; I would post in the XDA thread as mentioned here: https://lineage.microg.org but don’t see any link.

I would like to install lineage os for microg on my phone. I wonder why there is a way to verify the system image with the update_verifier.py script but no way to verify the recovery image.

Btw, am also wondering why there are gpg signatures for gmscore apks on github but I was not able to find instructions on verifying those signatures. I tried to search keyservers for the key ID.

I don't know the reason but there is no /system/etc/org.fdroid.fdroid/additional_repos.xml file.

The OpenGapps people had repositories containing prebuilt apks taken down from GitHub. This project should probably consider alternative ways of hosting/obtaining the apks in case GitHub decides to crack down harder on this.

It looks like most, if not all of the binary files in this repository can be downloaded from other locations, so maybe the Android.mk files can be updated to download the files from official locations instead?

Hello lineageos4microg

I am noob!! I don't know where to submit this issue, but I figured somewhere is better than nowhere.

I have a Moto G7 Power and I tried installing both

lineageOS for MicroG (https://download.lineage.microg.org/river/lineage-16.0-20191128-microG-river.zip)

and

Stock lineageOS 16 (https://mirrorbits.lineageos.org/full/river/20191203/lineage-16.0-20191203-nightly-river-signed.zip)

When I booted into lineageOS for MicroG I very quickly realized this was not going to work for me. As soon as the device went to sleep (or, something called "doze" in logcat, it seemed), it would never wake up again. pressing the power button did nothing, no logs were printed, it just sat there silently mocking me. The issue could be re-produced by either letting the device sit for a minute and fall asleep, or by pressing the power button to lock the screen.

The only way to get out of it was to hold the power button and reboot the phone.

I was looking around in logcat and I saw a lot of stuff, but nothing I recognized (I am not an android developer person!) Also this is really embarrassing but I never saved the log output properly. I am looking around at what I did save and its not really good enough for a bug report.

Anways then I used TWRP to format the phones storage again and re-install lineageOS from lineageOS website, not from lineageos for microG. This time it did not have the bug. the phone does not freeze after sleeping.

To be honest I am a lazy pleb user and I don't really want to be bothered to dig too much into this. I do like the idea of your project though so if you really wanna dig into this and you don't have your own Moto G7 device to test with (or if you cannot reproduce) then I can wipe me phone again and do the following test to re-produce:

1. follow the official lineageOS river installations instructions and sideload lineageos4microg
2. boot the phone and go through the 1st run process to get to the home screen
3. turn on developer options and turn on ADB, connect to adb and make sure you can logcat.
4. unplug the phone from the computer (I was most reliably able to reproduce this when the phone was not connected via USB) and let the phone sit until sleep or press power button
5. at this point the phone should be still running in sleepy mode and power button does nothing. no wake up, no screen back light turning on.
6. reconnect and logcat everything that happened since the last logcat

re-do steps 1-6 but this time with the stock lineageOS. The bug should not be present and in theory the difference between the two logcat outputs should point to the issue in question.

The most scary thing I remember seeing in the logcat output when the bug was present (logcat output that my stupid ass didnt save!!!!!!!!!!) was a WATCHDOG KILLING SYSTEM PROCESS message similar to https://forum.xda-developers.com/showpost.php?p=74125072&postcount=8717

Hi,

you might be interested in:

https://github.com/cryptomilk/android_vendor_microg

hi,
last gemini build lineage-20.0-20240106-microG-gemini.zip is not passing the checksum:

$ sha256sum -c lineage-20.0-20240106-microG-gemini.zip.sha256sum
lineage-20.0-20240106-microG-gemini.zip: Échec

$ sha256sum lineage-20.0-20240106-microG-gemini.zip
fd24c00ea7639ef7495f8da59cf85473ffe7d748637288604ed755c9ca605cf8  lineage-20.0-20240106-microG-gemini.zip

$cat lineage-20.0-20240106-microG-gemini.zip.sha256sum
7a0756e8703e44642b47581c363166db4e4c0c81e36098cdd898d02d2db1326b  lineage-20.0-20240106-microG-gemini.zip

Is it possible to include the etar calendar in this ROM, so that it gets updates via F-Droid?

Currently the etar calendar app, doesn't receive any updates from F-Droid, instead one has to install etar from F-Droid as a second calendar app.

Please update microG Services Core to 0.2.21.212158

Not sure if this is a bug of this build or lineage. I'll report it upstream if somebody else has the same problems.

The system ui just crashes if I try to enable wifi.

Lineage OS for microG, polaris (Xiaomi MIX 2S). After flashing the new build 20191005, I found that UnifiedNlp does not work (I tried three backends: Mozilla Location Service, Apple Wi-Fi, Radiocells.org Unified Network Location Provider Backend). Then I go to the microG settings:

microG Settings -> Self-Check:

Network location provider support

• Android version supported:
  Your Android version is not officially supported. This does not necessarily mean anything.

• System supports location provider:
  Your system does not support this UnifiedNlp package. Either install a matching package or a compatibility Xposed module.

UnifiedNlp status

• UnifiedNlp is registered in system:
  The system did not bind the UnifiedNlp service. If you just installed UnifiedNlp you should try to reboot this device.

See also: https://forum.xda-developers.com/showpost.php?p=80443513&postcount=1600 for another Xiaomi device.

Hello,
I was wondering if there is a statement somewhere what actually is the goal of this fork or if someone could give me an clarification here.

Obviously it is to provide microG out-of-the-box and then there is also F-Droid included. But in addition to that? Any plans to de-google, add more privacy or usability features to this fork?

Ty

Could you please provide the sources and the configuration for the build environment for these builds?

The patch in https://gitlab.com/Nanolx/microg-phonesky-iap-support can make Google Play Store work with microg, including in-app purchases. It requires a signature spoofing permission.

Did a clean flash twice using latest santoni build
https://download.lineage.microg.org/santoni/lineage-16.0-20211112-microG-santoni.zip

After flash device stuck at boot screen, lineage logo

Hi,
just a quick reminder, there are new versions of microG and F-Droid available.

GmsCore v0.2.19.211515: https://microg.org/fdroid/repo/com.google.android.gms-211515038.apk
F-Droid Client 1.12.1 (1012051): https://f-droid.org/repo/org.fdroid.fdroid_1012051.apk

Thanks for updating!

@johannesneyer
@corna

The current release is broken for many things.
mar-v-in have released a nightly build for the mapbox version with post-release fixes: https://microg.org/dl/GmsCore-v0.2.8.17785-4-06c8b76.apk

Could you please include it?

The new gsmCore v0.2.13.203915 is available and should be added to the prebuilts:

https://github.com/microg/android_packages_apps_GmsCore/releases/tag/v0.2.13.203915

Also FakeStore seems to have gotten an update: https://github.com/microg/FakeStore/releases/tag/v0.1.0

The yalp store with anonymous login is rarely working. Normally I need to try at least a dozen different accounts, before I am able to download an app. Hence, I would suggest to switch to the aurora store which offers starting from v3 aurora services. The app is well-maintained and offers a more reliable performance than yalp store.

I hope that this is not the – as the Readme states – "official" version, because then it would be proprietary and from Google. That would be exactly the opposite of what this project aims at.

So what is it? And why is it included (and preinstalled?)?

The Dialer from LOS enable/disable call recording based on MCC/MNC which is braindead from the legal standpoint: if you travel with German SIM to Italy it doesn't mean that you bring with you magic bubble of German laws on call recording floating around your SIM card - you're governed by the laws of the country you're in. Hence the sane way to do this is to let user check that it's legal (out of band) and enable/disable it manually (disabled by default) regardless of MCC/MNC.

Would be nice to get this implemented right in L4M.

I've read that http://resurrectionremix.com/ have this enabled by default as well.

see https://github.com/microg/android_packages_apps_GmsCore/releases

March 24 update for a3exlte performed without errors. Only CoronaWarnApp cries: there is no exposure notification framework. Reason see screenshot

Clean flash of April 1st L4M bacon shows no significant microG bugs.
Clean flash of official 18.1 April 1st and migrating to L4M works on lineage recovery without migration zip.
After migration microG self check shows all permission from approximate location to SMS are missing.
Tapping "Location modules" FCs microG service core app.

Edit: exactly same behaviour with jactivelte and twrp. Findings: migration is possible with or without migration zip. No difference in permission/fc issue. Installation can be repaired by wiping data partition in twrp.

I see that this repo doesn't include unifiednlp separately. It includes the other microg stuff, which acts like a superset, but from my understanding, it should be possible to use unifiednlp on its own in less intrusive ways. I would like to use this repo for some builds, and test the following options in increasing order of intrusiveness:

• unifiednlp as a network provider. Doesn't need signature spoofing (this is called gapps mode confusingly in the original repo). config_locationProviderPackageNames should have org.microg.nlp and the app should be a system app from my reading.
• unifiednlp no gapps mode. This needs signature spoofing. This is still useful on its own without using full microg for getting navigation apps to work.
• entire microg. This is already done right now.

F-Droid app and the privileged extension needs to be updated. I'm not very skilled for this, but i can try to help if you want.

Since, builds are happening on a monthly basis, the webview doesn't get updated throughout the month.
Bromite has its own f-droid repository and as such can be updated directly from f-droid, without any rom updates.
Bromite is fully compliant with the f-droid guidelines and isn't in the official repo due to not being able to be built on the f-droid virtual machines.

https://f-droid.org/packages/org.fdroid.fdroid/

Can someone please update mido image to lineage-16.0-20200407? We are waiting for an update for months.

I'm not sure that this is the right place to report this issue but I didn't find a more appropriate one. So the problem is this:

The latest LineageOS for microG release installs and works fine on my Nokia 6.1 (PL2) apart from one "minor" glitch: it fails to detect my SIM. The "About phone" menu also reports that IMEI is not available for either slots.

This is weird because the latest plain LineageOS releases can detect it without issues.

I've tried the following releases so far:
https://download.lineage.microg.org/PL2/lineage-18.1-20211107-microG-PL2.zip
https://download.lineage.microg.org/PL2/lineage-18.1-20211021-microG-PL2.zip

Now that the default branch for the docker image is updated, the current v14 weather provider seems like it should be also.

Thank you for all the great work on these projects.

Using LineageOS Recovery version 17.1 (20201225) on my Xperia XZ2 Compact, when trying to install LineageOS for microG I get the following error:

Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
E:Error in /sideload/package.zip (status 1)

I found a few instances of people finding this issue, but no one actually solving it:

https://www.reddit.com/r/MicroG/comments/idgitj/signature_mismatch_on_microg_los17/
https://www.reddit.com/r/MicroG/comments/j2uyr1/how_to_install_lineageos_for_microg_on_a_pixel_3a/g80axat/
https://www.reddit.com/r/MicroG/comments/i2e5ki/fxtec_pro%C2%B9/
https://forum.xda-developers.com/t/help-how-to-install-lineageos-for-microg.4173783/

Location/map doesn't work on the current, possibly use nightly version as the current stable has a few critical bugs.

LineageOS for microG 18.1 2021-08-11 for FP3 still contained the very old v0.2.19.211515 of microG Core, which caused a bug (microg/GmsCore#1544) in GCM registration for me.

It would be great if that was updated, so the setup works with less problems.
In my case upgrading to v0.2.22.212658 did fix the problem.

Hey,

Marvin has released a new GmsCore: https://github.com/microg/GmsCore/releases/tag/v0.2.18.204714

Would be great if you could pull that in soon. Many thanks!

Please include AuroraServices as a system app the same way it's done for F-Droid Privileged Extension: https://gitlab.com/AuroraOSS/AuroraServices

Hi,

When I tried installing on tissot a version newer than lineage-16.0-20190724-microG-tissot it doesn't work, and if I install this version it works fine, but if I try to do a OTA update afterwards I get a bootloop, which is only fixed by flashing the older version. I saw an issue about bootloop [here](https://github.com/lineageos4microg/android_prebuilts_prebuiltapks/issues/13) but it says it was fixed, so I image this is another issue.
Other than that, LineageOS + microG is great :)