LineageOS for microG

Search This thread

Simon94

Senior Member
Oct 27, 2011
114
409
Android 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-28
 
Last edited:

brutalv4

Senior Member
Jul 24, 2014
54
27
Dnipro
Would like to have build for Nexus 9 aka flounder :eek:
Awesome start! Good luck with that! Cheers! :fingers-crossed:
 

lindworm

Member
Aug 27, 2013
16
19
Is this the thread mentioned in the FAQ where one can request builds for other devices supported by LineageOS?
If so, I'd love to see a build for the LG G5 (aka h850), which is currently the only high-end device by a known manufacturer with a removable battery and high repairability (8/10 from Ifixit).
It's fully supported by LineageOS (https://wiki.lineageos.org/devices/h850) and I'd be willing to report any possible problems and help debug it if necessary.
Thanks in advance and awesome project!
 

Simon94

Senior Member
Oct 27, 2011
114
409
Current 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,Z00L
 
Current 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,Z00L

Please, include piccolo!
 
  • Like
Reactions: Franktdf
Apr 19, 2016
5
1
Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?

Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
 
  • Like
Reactions: cherrygreg

MaStErB_1984

Senior Member
Jul 16, 2016
94
30
Braunschweig
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual :)
 

Simon94

Senior Member
Oct 27, 2011
114
409
@Simon94 does it supports substratum ? and thanks for the modded lineage .
Same feature-set as LineageOS. If LOS supports substratum, we are supporting this aswell.

Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?

Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
Unfortunately we wont remove FakeStore since our goal is to provide a Google free ROM with a fully working ecosystem which requires having FakeStore installed. Sorry for that. What you could do is to write a script for OTA survival / - or removal and put it in the /system/addon.d directory. But we're not going to support this in any way.

Otherwise we can invite you to not use Play Store, but a replacement like Yalp Store.

We like to build as often as we can. Its up to you and your free choice. If you dont want to update on a daily basis, just dont do it ;)

Best, Simon
 

Simon94

Senior Member
Oct 27, 2011
114
409
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual :)
..
https://lineage.microg.org/#faq said:
Can you add support for my device? It is not supported by LineageOS though...
No, I'm sorry.
 

kurtn

Senior Member
Jan 28, 2017
4,515
1,986
Small town in Bavaria
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual :)
There are several methods to get microg. Maybe you should start reading there https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
My preferred method have been nanomod patcher and shadow53's zip.
 
Last edited:
Jan 10, 2017
32
3
I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.
 
  • Like
Reactions: blacm

obrien654j

New member
Nov 6, 2017
3
1
Hey there! I have an old first-gen Moto X as my main android device (ghost) and I'd love to take advantage of your awesome project! I tried to get the docker image up and running myself, but I keep getting random DNS failures in docker, which seem to get silently passed, which results in the build claiming to be successful, yet no builds show up in my "zips" folder when it completes. Only thing that I think needs changed from the default is the lineageOS branch (cm-13.0). Would it be too much trouble to add 'ghost' to your list of builds?

Thank you,
neutral
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Thanks. I'll just wait for now. Is there anything I can/should do if it does not appear in a few weeks time?
    It should be built the same day as guacamole. If guacamoleb doesn't appear then, you can open a new issue in github lineage4microg docker...
    2
    Yes, this what was well known to me.
    But there seem to be exceptions.

    gts210vewifi switched to unofficial 2 years ago.

    Then where do these builds come from?
    lineage-16.0-20210909-UNOFFICIAL-microG-gts210vewifi.zip
    lineage-16.0-20220409-microG-gts210vewifi.zip
    The microG fork is still built for many fallen out of official devices. It's just with all that 19.1 trouble the 16.0 devices haven't been built for a while. But I guess we will see new builds soon.

    I doubt microG fork will follow the unofficial upgrade to 17.1 - better ask the 17.1 dev to include signature spoofing. Or patch it with nanodroid.

    The legacy builds come from official lineageOS sources. Those sources still get security patches. Even for 16.0
    1
    Hi,

    I have a OnePlus 7 (guacamoleb) and I am using LOS for microg with it for a long time now. Thanks for all the great work!

    Unfortunately, OnePlus 7 lost official LOS support some time ago, so there were no new builds. However, it is officially supported again now and there is a new LOS 18.1 build dating 2022-05-02. 😀

    Does this mean, we will also get LOS for microg builds again from now on?

    I checked the LOS for microg downloads. All the builds dating 2022-05-02 for the other devices are already there but the build for guacamoleb is still missing. So I am wondering if there is any manual step involved to include the device in the build process again?
    The microG fork builds are not in sync with official lineageOS. You can just wait and hope. Usually it takes up to two weeks for a new device to appear.
  • 157
    Android 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-28
    24
    Just 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
    Simon
    15
    Hey 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.
    14
    Current 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,Z00L
    13
    today i got my weekly(?) update with november security patches via ota notification.
    thanks for that!

    Yes they are rolling out new builds again :) Thank you everyone who is contributing to this :good:

    Oops. They only build Oreo right now.

    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.