The proprietary blobs repo is broken and causing build issues, so not today.
LineageOS for microG
- Thread starter Simon94
- Start date
The proprietary blobs repo is broken and causing build issues, so not today.
Hi experts,
I tried to build lineageos4microg v20.0 myself as per
github.com
with the docker provided for Galaxy Tab 5e/gts4lvwifi, worked perfectly fine, but only without including MicroG and FDroid as system apps. Building with them included fails with error:
error: mismatch in the <uses-library> tags between the build system and the manifest:
- required libraries in build system: [com.android.location.provider]
vs. in the manifest: [com.android.location.provider]
- optional libraries in build system: [androidx.window.extensions, androidx.window.sidecar]
vs. in the manifest: [org.apache.http.legacy, androidx.window.extensions, androidx.window.sidecar]
- tags in the manifest (vendor/partner_gms/GmsCore/GmsCore.apk):
uses-library-not-required:'org.apache.http.legacy' uses-library:'com.android.location.provider' uses-library-not-required:'androidx.window.extensions' uses-library-not-required:'androidx.window.sidecar'
I added the xml as instructed into /home/user/manifests, but that seems to be not enough(?). Is there some more to do?
The instruction says "To include microG (or possibly the actual Google Mobile Services) in your build, LineageOS expects certain Makefiles in vendor/partner_gms and variable WITH_GMS set to true."
All I did was set the WITH_GMS, but I could not find any details on these certain makefiles.
Any advice is greatly appreciated.
Thanks,
Georg
I tried to build lineageos4microg v20.0 myself as per
GitHub - lineageos4microg/docker-lineage-cicd: Docker microservice for LineageOS Continuous Integration and Continous Deployment
Docker microservice for LineageOS Continuous Integration and Continous Deployment - lineageos4microg/docker-lineage-cicd
github.com
error: mismatch in the <uses-library> tags between the build system and the manifest:
- required libraries in build system: [com.android.location.provider]
vs. in the manifest: [com.android.location.provider]
- optional libraries in build system: [androidx.window.extensions, androidx.window.sidecar]
vs. in the manifest: [org.apache.http.legacy, androidx.window.extensions, androidx.window.sidecar]
- tags in the manifest (vendor/partner_gms/GmsCore/GmsCore.apk):
uses-library-not-required:'org.apache.http.legacy' uses-library:'com.android.location.provider' uses-library-not-required:'androidx.window.extensions' uses-library-not-required:'androidx.window.sidecar'
I added the xml as instructed into /home/user/manifests, but that seems to be not enough(?). Is there some more to do?
The instruction says "To include microG (or possibly the actual Google Mobile Services) in your build, LineageOS expects certain Makefiles in vendor/partner_gms and variable WITH_GMS set to true."
All I did was set the WITH_GMS, but I could not find any details on these certain makefiles.
Any advice is greatly appreciated.
Thanks,
Georg
Have you seen https://github.com/lineageos4microg/docker-lineage-cicd/issues/335? I think your issue is mentioned there, not sure if it is solved.Hi experts,
I tried to build lineageos4microg v20.0 myself as per
with the docker provided for Galaxy Tab 5e/gts4lvwifi, worked perfectly fine, but only without including MicroG and FDroid as system apps. Building with them included fails with error:GitHub - lineageos4microg/docker-lineage-cicd: Docker microservice for LineageOS Continuous Integration and Continous Deployment
Docker microservice for LineageOS Continuous Integration and Continous Deployment - lineageos4microg/docker-lineage-cicd
error: mismatch in the <uses-library> tags between the build system and the manifest:
- required libraries in build system: [com.android.location.provider]
vs. in the manifest: [com.android.location.provider]
- optional libraries in build system: [androidx.window.extensions, androidx.window.sidecar]
vs. in the manifest: [org.apache.http.legacy, androidx.window.extensions, androidx.window.sidecar]
- tags in the manifest (vendor/partner_gms/GmsCore/GmsCore.apk):
uses-library-not-required:'org.apache.http.legacy' uses-library:'com.android.location.provider' uses-library-not-required:'androidx.window.extensions' uses-library-not-required:'androidx.window.sidecar'
I added the xml as instructed into /home/user/manifests, but that seems to be not enough(?). Is there some more to do?
The instruction says "To include microG (or possibly the actual Google Mobile Services) in your build, LineageOS expects certain Makefiles in vendor/partner_gms and variable WITH_GMS set to true."
All I did was set the WITH_GMS, but I could not find any details on these certain makefiles.
Any advice is greatly appreciated.
Thanks,
Georg
Hui! Every two hours a New lineageOS 20 build. Like a clockwork
Hi all,
I have a problem with MicroG and FDroid included as system apps in the LOS20 build. They say there is no network connectivity, MicroG on trying to register Google accound and FDroid on trying to update the catalog. I tested with my own build of gts4lvwifi and also the official one 20230125 of today.
I can't find a root cause or solution, and this is my only device with LOS20 currently so not sure if this is a device-specific issue. Network connection itself is good, other apps are ok. With the official LOS19 I did not have this problem.
Has anyone observed the same or can confirm things are working ok?
Thanks,
Georg
I have a problem with MicroG and FDroid included as system apps in the LOS20 build. They say there is no network connectivity, MicroG on trying to register Google accound and FDroid on trying to update the catalog. I tested with my own build of gts4lvwifi and also the official one 20230125 of today.
I can't find a root cause or solution, and this is my only device with LOS20 currently so not sure if this is a device-specific issue. Network connection itself is good, other apps are ok. With the official LOS19 I did not have this problem.
Has anyone observed the same or can confirm things are working ok?
Thanks,
Georg
Did you try the usual repair things? Deleting app data, factory reset, installing older versions?
I tried delete app data, and both selfbuilt and official version. I did not do factory reset, that would mean some work I want to avoid. I'm building a version without embedded MicroG stuff now and will check what happens with FDroid installed as normal app instead of system app.
Edit: FDroid as standard non-system app does not have this issue and behaves normally.
Edit: FDroid as standard non-system app does not have this issue and behaves normally.
Last edited:
Hello,
I experienced automatic Factory reset when rebooting after switching on desktop mode in developer options.
The problem occurs on Samsung galaxy tab s5e (gts4lvwifi) running Lineage 20 with micrG. Please note that on Lineage 19.1 there was no problem. I
'm used to Samsung Dex, so after migrating from Lineage 19.1 to 20, I connected the USB-C hub with a screen, mouse and keyboard and turned on developer options and switched ON desktop mode. I was asked to reboot but the tablet rebooted into initial setup as if there was a factory reset. All my data and apps were deleted. I set up my tablet and tried again and got the same error once more. Here's the Lineage with microG version I used: https://download.lineage.microg.org/gts4lvwifi/lineage-20.0-20230125-microG-gts4lvwifi.zip
Lineage with microG site asks to report sduch bugs o Lineage directly. I reported the bug to Lineage but was rejected because I'm not using their build.
So where should I report it then?
I experienced automatic Factory reset when rebooting after switching on desktop mode in developer options.
The problem occurs on Samsung galaxy tab s5e (gts4lvwifi) running Lineage 20 with micrG. Please note that on Lineage 19.1 there was no problem. I
'm used to Samsung Dex, so after migrating from Lineage 19.1 to 20, I connected the USB-C hub with a screen, mouse and keyboard and turned on developer options and switched ON desktop mode. I was asked to reboot but the tablet rebooted into initial setup as if there was a factory reset. All my data and apps were deleted. I set up my tablet and tried again and got the same error once more. Here's the Lineage with microG version I used: https://download.lineage.microg.org/gts4lvwifi/lineage-20.0-20230125-microG-gts4lvwifi.zip
Lineage with microG site asks to report sduch bugs o Lineage directly. I reported the bug to Lineage but was rejected because I'm not using their build.
So where should I report it then?
First you should try to reproduce the bug with official lineageOS. Hurry up, the 19.1 will not stay long time on downloads server and maybe you need a version upgrade for reproducing.
I have lineage.microg 20 on Moto Edge 30. What is the best way to install Aurora Services? I tried sideloading the zip in recovery but this did not work.
Is aurora services still a thing? You have f-droid with privileged extension. And aurora store announced to stop support for services installation method.
But you can try various microG installers.
Thank you for the advice but I can't afford it. I'm using this tablet on a daily basis and it took me two full days to reinstall every thing. (I tried adb backup but couldn't manage to restore apks nor apps data. built-in backup is limited also).
I installed the latest los4mg 20 on a Motorola Edge (racer), factory reset, set up microG account, and spoofing, set up F-Droid, and Aurora.
Paid apps behave the same as on Lineage ('make sure google play services is installed...') So, I built it using the Docker file with identical results (except no audio). This took days.
The spoofing is useful but I don't see what, if anything, microG accomplishes.
Thanks for all the work, but Google's suck factor is apparently limitless. Back to straight-up LOS.
Anyone know the Alphabet CIDRs? I need an iptables block on my firewall.
Paid apps behave the same as on Lineage ('make sure google play services is installed...') So, I built it using the Docker file with identical results (except no audio). This took days.
The spoofing is useful but I don't see what, if anything, microG accomplishes.
Thanks for all the work, but Google's suck factor is apparently limitless. Back to straight-up LOS.
Anyone know the Alphabet CIDRs? I need an iptables block on my firewall.
There is no such ting linke a microG account.
For many paid apps you need the original play store. The minmicrog project has a flashable patches play store.
Thank you for replying.
Yes there is, if only by name. It is the first setting (below check microG installation) in the microG-Settings app. It appears to request a Google log in.
I'll look at the patched Play app, but I've had surprisingly good luck contacting app vendors and saying "I really like you app, and was happy to pay to use it, but I really despise Google and won't allow their software on any device I control. Can you help?"
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2Some more information on why the March QPRS update caused the 21.0 builds to fail:
Thanks, but from my (very limited) understanding of Gerrit, those changes have been implemented, but not been verified or code reviewed. So they are not, and will not be, merged to the main `lineage-18.1` branch, and LineageOS won't be making and publishing builds which include the changes.
Our project scope is to build for the same devices as LineageOS build for, so the changes aren't a lot of use to us. I don't know how we would go about 'picking' them for our builds, even if a: we had the resources to do so and b: we are happy to make builds including unverified, unreviewed code, which we don't2
Just wanted to say thanks for running the nio build. After a couple months of crashing in standby and then the delays related to the recent build issues, I was getting ready to nuke&pave with vanilla lineage until I came across this thread. Started watching the matrix room with bated breath when I saw a nio build begin last night!
I have been hearing a lot of positive things about recent Lineage 21 builds for the nio, so fingers crossed that this stays stable. Thanks again.2
At the moment, our builds include the latest `stable` Microg components from https://microg.org/download.html (currently GmsCore is `0.2.27.223616`). We also include the microG F-Droid repo pre-configured, so that users can receive updates. Users can choose to allow beta updates of microG, allowing them to pick up the latest beta versions. This is what I do, so I'm running `0.3.1.240913` on my daily driver device.
I see no reason to change this approach at the moment. I guess mar-v-in will start by shipping his new versions as betas, which users will be able to try out if they wish. Eventually, with luck, the changes will become stable, and we will then include them in our build for all users. Until that happens, users will have to accept that MLS will stop / has stopped working, and live with the reduced performance: the fix is going to come from mar-v-in, and we will include it as normal.2All the 20.0 builds are complete. Let's hope that 21.0 upstream builds are fixed in time for next month's build run.
The final 18.1 builds have been moved to https://download.lineage.microg.org/archive/1
Yes - there was an error while building the kernel.Probably caused by a change made in the kernel code repo during the build run. With luck it will get built in the next build run - see below
Yes, we run builds once per month. The next build run will start at 00:01 on 1st April. There will probably only be 20.0 builds because
- upstream 18.1 builds have stopped and the 18.1 branch has reached 'end-of-life'
- 19.1 devices were all promoted to 20.0 a couple of months ago
- 21.0 builds are broken upstream
-
168Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)
This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..
You can find us on https://lineage.microg.org
XDA:DevDB Information
LineageOS for microG, ROM for all devices (see above for details)
Contributors
Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
Source Code: https://github.com/lineageos4microg
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-11-06
Last Updated 2020-08-2824Just to give a small heads up. As you may noticed some of the project members the priorities have shifted to other projects.
I was and am still willing to take over some of the tasks, but as microG lacked some bugfixes and support for LineageOS 17.1 i was not sure whether its worth it to spend more time into LineageOS for microG. Once marvin released the new microG update, we still had to check with our team, how we'll proceed.
For now i've taken over the responsibility of the Android Build process, merged some of the fixes and integrated LineageOS 17.1 support. New builds are on their way, both LineageOS 16 and 17.1 based.
Best
Simon15Current device list which will be built tomorrow:
Code:a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855, deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100, i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme, serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L15Hey guys. You are right with your findings. We were testing yesterday LineageOS 15.1. But we rolled it back. Now we have almost everything ready for Lineage 15.1 - In fact there is one minor change outstanding before we're going to release. After release we'll start building the complete LineageOS weekly build roster again.13
Yes they are rolling out new builds again
Thank you everyone who is contributing to this :good:
We have decided to build every device weekly (like before), as we don't have the capacity to build for ~75 devices daily and nightlies are quite useless to the end users. We will build for all the ~200 devices, ~30 devices per day, from top to bottom of the usual hudson devices list (which means that 15.1 builds will appear in the first part of the week and 14.1 in the second one).
As usual, new devices will be automatically added to the build list, no need to ask for them, just wait some days.
New posts
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
Question Fingerprint Sensor Not Working after unbricking phone
- Latest: heartbreakkid58
-
