Not dead.
So, it seems Lineage4MicroG is dead, right?
No updates after may 3 and some builds just disappeared
LineageOS for microG
- Thread starter Simon94
- Start date
There is activity in github.Nice to hear, but how do you know that? Everything related to it is very quiet
Hi, any chance to get a build for the sony xperia 5 III (pdx214)? The site says it LOS for microg supports all devices supported by regular LOS and yet the build for this one is nowhere to be found.
It's just 3 weeks ago. No build since that day. But should be included in next round.
hudson: Add Xperia 5 III (pdx214) · LineageOS/hudson@62ba37b
Change-Id: I08be71d60ef15275dbc3fdb79dde50a9edd000dd
github.com
When you say "next round", what timeframe is that - monthly?It's just 3 weeks ago. No build since that day. But should be included in next round.
hudson: Add Xperia 5 III (pdx214) · LineageOS/hudson@62ba37b
Change-Id: I08be71d60ef15275dbc3fdb79dde50a9edd000dd
I see that LOS is now official for the Sony Xperia 1 III also - but no LOS for MicroG build on their site. Can I expect that build in the "next round" also?
Love this ROM looking forward to it...
Has anyone tried Pokemon GO or Ingress lately? I know PoGO worked fine about a week or two ago but when I last tried a few days ago I couldn't authenticate. I'm not sure if I just missed something but I'll try again soon. I have a OnePlus 6
If I recall right for OP6 the microg boot.img didn't work for me for some reason and I just ended up sideloading the microg build with official LOS recovery
I did it about again 20 minutes ago. I went from official LOS lineage-20.0-20230606-nightly-enchilada to lineage-20.0-20230604-microG-enchilada by adb sideloading the microG-enchilada zip from LOS recovery. I got the signature mismatch prompt, and a prompt about downgrading. I wiped all partitions and factory reset prior to flashing microG.
Did another clean install a minute ago coming from that recently-flashed microG image, and was able to boot into the device recovery and adb sideload the microG zip without any prompts.
Navigating through device settings seems a tiny bit more snappy with microG compared to fresh LOS with Gapps yesterday
There's also a newer 0.2.28.231657 microG build available. I installed the apk from USB debugging seemingly without issue, and this time updated from F-Droid (had to show all versions) also without issue.
For OP6 and Pokemon GO, Device registration needs Native (not Moto G or it fails SafetyNet), and Google sign-in for both returning and new players doesn't work (fails to authenticate). Returning player with Facebook said on FB's end that they prevent log-in from an embedded browser, and also presumably doesn't work.
Returning player with a Trainer Club account signed in fine. Not sure about Niantic child account, or anything with Ingress.
Last edited:
Hey guys,
I've been running LineageOS for microg on a oneplus 8T for some time now.
Up until April's build (20230412) I was able to use every app with no problem, but since the latest update (20230606) I get a lot of apps complaining the device is rooted, I never rooted the device and just sideloaded latest update as I did the ones before.
Any clue if something changed in this build that might justify this behavior?
I've been running LineageOS for microg on a oneplus 8T for some time now.
Up until April's build (20230412) I was able to use every app with no problem, but since the latest update (20230606) I get a lot of apps complaining the device is rooted, I never rooted the device and just sideloaded latest update as I did the ones before.
Any clue if something changed in this build that might justify this behavior?
Hello,
Currently running Lineage 20.0 for microG on my Sony XZ2 Compact, I want downgrade to Lineage 18.0.
I can download the ROM here : https://download.lineage.microg.org/xz2c/
But I don't find the boot.img, am I missing something ? From what I understand, I need the correct boot version to install the ROM.
Thanks for the help,
Currently running Lineage 20.0 for microG on my Sony XZ2 Compact, I want downgrade to Lineage 18.0.
I can download the ROM here : https://download.lineage.microg.org/xz2c/
But I don't find the boot.img, am I missing something ? From what I understand, I need the correct boot version to install the ROM.
Thanks for the help,
Just a FYI - Looking at the builds for Sony Xperia 1III and 5III, I see the following issues:
pdx214 (5III):
^ Missing the recovery file (only the boot and os files exist)
pdx215 (1III):
^ Missing both the recovery and the os files (only the boot file exists)
And, I was so looking forward to using this build. Any update on when this might be corrected? Thanks.
For now I'm using standard LineageOS 20 with Magisk, LSPosed, FakeGapps, and Universal Safety Net. Not ideal, but it works fine.
Hi everyone, 
No pressure, no ETA.
I know that volunteers dedicate their time to provide us with these valuable LineageOS with µG ROMs.
I'm only asking this to plan myself ahead: I noticed that for Gauguin the Boot and Recovery were updated on june, 11 of 2023.
Does that mean it's better for me to wait a bit because the ROM will also be updated soon, or are this files aren’t related and it's unnecessary to wait then I should flash the version of april, 16 of 2023 instead?
Sending kisses
No pressure, no ETA.
I know that volunteers dedicate their time to provide us with these valuable LineageOS with µG ROMs.
I'm only asking this to plan myself ahead: I noticed that for Gauguin the Boot and Recovery were updated on june, 11 of 2023.
Does that mean it's better for me to wait a bit because the ROM will also be updated soon, or are this files aren’t related and it's unnecessary to wait then I should flash the version of april, 16 of 2023 instead?
Sending kisses
There is no reason to wait. No matter wen the update will come - it is easy to install.Hi everyone,
No pressure, no ETA.
I know that volunteers dedicate their time to provide us with these valuable LineageOS with µG ROMs.
I'm only asking this to plan myself ahead: I noticed that for Gauguin the Boot and Recovery were updated on june, 11 of 2023.
Does that mean it's better for me to wait a bit because the ROM will also be updated soon, or are this files aren’t related and it's unnecessary to wait then I should flash the version of april, 16 of 2023 instead?
Sending kisses
Just wanted to say thanks to those that maintain this project.
It's real pain in the ass for average user to manually get microg installed and configured properly.
It's real pain in the ass for average user to manually get microg installed and configured properly.
Similar threads
Top Liked Posts
-
1
The plan is to update it with some of the information that is now in the README, but at the moment I am not able to modify the web site. Until I am able to modify the web site, I will continue to add documentation in the README -
1
Install official lineageOS without GApps first!
Info about m5 | LineageOS Wiki
wiki.lineageos.org
Maybe you can self-build
Builds for Minimal devices and TV boxes failed · Issue #436 · lineageos4microg/docker-lineage-cicd
Builds failed for the following Android TV box...
github.com
1
As this comment in the issue you linked, building los4microG for the Banana Pi (m5) will currently fail.Install official lineageOS without GApps first!
Info about m5 | LineageOS Wiki
Maybe you can self-build
Builds for Minimal devices and TV boxes failed · Issue #436 · lineageos4microg/docker-lineage-cicd
Builds failed for the following Android TV box...
github.com
1
You don't need microG for newpipe or apps from f-droid.Thank you kurtn, but I don't think I'm capable of self-build, I don't have coding skills.
But I need microG if I want to use apps like NewPipe, SkyTube, Xtra and Twire? Don't even know if I need it
1
Sorry that needs a longer reply, because we have such a wide variety of devices an recoveries and user preferences.I've been doing some digging into why we are shipping various `.img` files in addition to our main ROM zip file. From what I have found out so far, it seems that we started to do this back in January 2021 because LineageOS Recovery would refuse to install ROMs signed with different keys from the recovery itself, giving an error like ` Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)`.
I have used LineageOS recovery to flash a variety of ROMs (los4microg, /e/OS official & unofficial, IodéOS) on Pixel 4a sunfish, so is this limitation not a problem anymore? Or is it still a problem for some devices?
Some of the issues raised about this mentioned a 'migration script`. Looking into that I came across this page on the LOS Wiki. Is ***this*** an issue that we still need to be concerned about, given that all our official builds are siged with the same keys?
Thanks in advance for any help and advice on these points. I want to make sure I understand the issues before I work out what changes (if any) are needed to the build artifacts we make available
PS I just found this `lineageos-for-microg-keys-migration.zip`from 3 years ago
TWRP (and similar recoveries) checks signature of wannabe installed build in comparison to already installed ROM. It throws error 7 in case of a mismatch. To migrate from official lineageOS to L4µg you either wipe system partition or flash that migraion zip you found. Once on L4µG, OTA updates should work fine.
Lineage Recovery (and similar) checks signature of wannabe installed build in comparison to a in-recovery stored signature. In manual flashing you can override a mismatch warning. For OTA update that mismatch is a show-breaker. In many devices you can enable "update recovery". That will overwrite the current recovery with L4µG recovery.
You will typically find TWRP on a-only devices and lineage recovery on a/b devices. But be prepared to find stranger combinations. -
165Android 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
Simon15Hey 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.14Current 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,Z00L13
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.
