So you somehow blocked connection of updater to microG.org or it's sub-domains.
LineageOS for microG
- Thread starter Simon94
- Start date
I wouldn't know how. My pi-hole shows queries to download.lineage.microg.org normally answered.
I uninstalled Magisk and flashed the original unpatched boot.img (to set the “Patch vbmeta in boot image” option had been a mistake anyway). But the OTA would not succeed after that either. So Magisk obviously was not the culprit. Therefore I started from scratch with the latest factory image. There is no new OTA yet, so I'll have to wait and see if the next one will work.Wild guess: you can start again with original android 12. Or try without magisk. Or use magisk recovery installation method. Maybe with Lygisk
GitHub - programminghoch10/Lygisk: Your Lie in Android
Your Lie in Android. Contribute to programminghoch10/Lygisk development by creating an account on GitHub.github.com
Since a week or so the build system seemed to have stopped. Is the build system under maintenance? And is there any information on the progress?
I wanted to ask exactly that. All 18.1 builds have finished, and I expected to see 19.1 builds starting a week ago. But indeed nothing happened after zl1.
Hello,
I have a Sony xz2c with LineageOs version 19-20220627-microG-xz2c and since its installation I keep getting a message that "Intent Filter Verification" has stopped. In Netguard I can see that when I restart the Xz2c, "Intent Filter Verification" is looking to connect to over 100 Google and Google maps locations around the world. Netguard blocks them all nicely, but "Intent Filter Verification" keeps after that, saying it has stopped. I did not have this in the last version of LineageOs 18 with MicroG.
Am I the only one with this message or does this happen to others as well?
For the rest I am completely satisfied with 19.1, but I was also satisfied with 18.1.
Regards 30jp
I have a Sony xz2c with LineageOs version 19-20220627-microG-xz2c and since its installation I keep getting a message that "Intent Filter Verification" has stopped. In Netguard I can see that when I restart the Xz2c, "Intent Filter Verification" is looking to connect to over 100 Google and Google maps locations around the world. Netguard blocks them all nicely, but "Intent Filter Verification" keeps after that, saying it has stopped. I did not have this in the last version of LineageOs 18 with MicroG.
Am I the only one with this message or does this happen to others as well?
For the rest I am completely satisfied with 19.1, but I was also satisfied with 18.1.
Regards 30jp
That's a know lineageOS bug. Should be fixed soon. You can disable that app.
19.1 builds have started againIt seems like another round of 18.1 builds has started todaytotally skipping all 19.1 devices.
FYI. Latest update for alioth, poco f3, from july 21th gave me a bootloop. First failed LOS update since I guess 5 years or so. Checked logcat but could not find the problem. I made a backup with the latest TWRP from nebrassy, which supports A12 encryption but restoring that also failed. Had to do a fresh install which did work with that latest version. Happy to have neo backup, saved a lot of work.
Also a small bug in the last couple of versions. Running on 60 Hz is basically not usable. Extreme stutter and lag. In both browser as the entire UI and apps. 120 Hz is smooth and normal.
That's not a microG issue. Maybe ask your device community.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2I got to the bottom of the los4microg build failures: LineageOS merged the March 2024 Quarterly Platform Release and Security update from Android in this commit on 11 March. That introduced breaking changes for 21.0 builds so all 21.0 devices were removed from the target list in this commit on 20 March, to be re-added when device maintainers have implemented the fixes.
So, at the moment, there are *no* official LOS 21.0 build targets. I will check again before the April build run to see if there are any buildable 21.0 devices then2
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.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.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/ -
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
-
-
-
Question Serenity now....been trying to adb sideload stock os to my phone- Latest: TheGhost1951
