LineageOS for microG
- Thread starter Simon94
- Start date
Thanks; I flashed it this weekend and everything seems to be working, including Sprint data.
Are you cholin? Or can you help cholin with that issue?
https://github.com/lineageos4microg/docker-lineage-cicd/issues/105#issuecomment-700155321
Now that you mention it, I did see some errors when I ran the install. I tried rebooting and, because I was able to boot, I assumed the installation had been successful despite the errors, but maybe it wasn't and I'm still running the same LineageOS/Gapps build I was before.
My build number says lineage_sargo-userdebug QQ2A.200501.001.B2 1796 dev-keys. Is that the right build number, or am I still running the old build?
You flashed microG version on official lineageOS with GApps? That's not the procedure from lineage.microg.org . do you still see play store app?
I thought I did a clean flash, but maybe I just wiped data and not system.
Yes, the Play Store app appears in my app drawer.
There is no wipe of system partition mentioned, but a factory reset plus format data
https://wiki.lineageos.org/devices/sargo/install#installing-lineageos-from-recovery
Yeah, I did that; I ran "Format data / factory reset" from LineageOS recovery. I sideloaded the zip, got some errors (I think they were the same ones cholin mentioned but I didn't keep notes), and decided to try rebooting anyway. I got a working installation on boot. It has the Google and Play Store apps but not the rest of the default Google apps (Maps etc.).
Format data and factory reset are 2 different things. To actually format data in TWRP, you must type "yes" to confirm. If you did not type yes at some point while installing, you did not format data.
That's really bad timing on September 21st. Round of 17.1 build started just before build target was merged. Hope for next round.
https://review.lineageos.org/c/LineageOS/hudson/+/287029
I haven't used TWRP recently so I can't speak to that, but I used LineageOS recovery and "Format data/factory reset" is a single menu item.
Here's what it says in the Installing LineageOS from recovery link that kurtn provided:
Last edited:
So you still can't get rid of GApps. Is your phone rooted or can you work with adb shell?
So you still can't get rid of GApps. Is your phone rooted or can you work with adb shell?
Delete the GApps entry in system/addon.d maybe you should boot recovery for that. Then wipe and flash ROM.
tek3195
Senior Member
Lineage recovery on my device has factory reset and then when you click on it, it opens to three tabs format /data, /cache and one more. Not looking at it right now cant remember
Similar threads
Top Liked Posts
-
11
For device-specific information like this, best to look in the LOS Device Wiki pages for your device
The default for most devices re-locking bootloader is not possible. If it is possible for a specific device it will be mentioned in the device's LOS Wiki pages. Nothing mentioned there for this devices so it seems it's not possible -
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.
