LineageOS for microG

Search This thread

xda9mwi

New member
Nov 8, 2017
4
0
LeEco Le 2 support

Would it be possible to add LeEco Le 2 (s2)?

Thank you for your work.
 

undefyned

New member
Dec 12, 2016
3
0
Mumbai
undefyned.carrd.co
Did u miss out taoshan (Sony Xperia L) or is there some other issue?

Would like to know, since you've removed the device names from the OP and there's no download section for my device on the website.

Thanks!
 

cvbrt

Senior Member
Jan 19, 2015
57
23
For now we stick to a small script doing the magic along with a rewrite rule.
PHP:
<?php
define('ARCHIVE_PATH','/data/archive/full');
define('ARCHIVE_URL','https://download.lineage.microg.org/ota/full');

if(!isset($_GET['request']))
	die('Invalid request');

$parts=explode('/',$_GET['request']);
if(count($parts) != 4)
	die('Invalid request');

$request=array(
	'apiversion'=>$parts[0],
	'device'=>$parts[1],
	'romtype'=>$parts[2],
	'revision'=>$parts[3]
);

if($request['apiversion'] != 'v1')
	die('Unsupported API version');

if(!is_dir(ARCHIVE_PATH . '/' . $request['device']))
	die('Unknown device');

$files=glob(ARCHIVE_PATH . '/' . $request['device'] . '/*.zip');
$roms=array();

foreach($files as $file)
{
	$filename=basename($file);
	$version=explode('-',$filename)[1];
	$rom=array(
		'datetime'=>filemtime($file),
		'filename'=>$filename,
		'id'=>filemtime($file),
		'romtype'=>$request['romtype'],
		'url'=>ARCHIVE_URL . '/' . $request['device'] . '/' . $filename,
		'version'=>$version
	);
	$roms[]=$rom;
}

$output['response']=$roms;
echo json_encode($output, JSON_UNESCAPED_SLASHES);
?>

Code:
location /api {
	rewrite ^/api/(.*)$ /ota.php?request=$1 last;
}

Thanks for the information Simon.:D
 

r@nsome

Member
Aug 22, 2009
46
7
I am desperately trying to get MicroG on my paella (BQ X5) with no root ... without success so far :(

Would so much appreciate if you could provide LineageOS / MicroG for paella! :victory:
 

bernhard.reiter

New member
Nov 8, 2017
1
0
A build for the Sony Xperia Z Wiki Tablet (pollux_windy) would be nice, it is supported by LinageOS.

Great Initiative! Is there a way to financially support you?

Best Regards!
 
hero2lte still not added even tho the main device herolte was added. I saw it would be made in next build but when will that be?
Edit:
It seems you made a typo and the next batch should include it automaticly, hope it'll be soon.
 
Last edited:

daloonik

Member
Sep 5, 2016
14
1
Can I use the LineageOS updater under the system menu? If not, what's the best way to update LineageOS for microG without losing all my preinstalled apps?
 

Simon94

Senior Member
Oct 27, 2011
114
425
Sorry to not reply to non rom specific questions.

All devices which were mentioned here and are official lineageos devices are added to the build list. Due to the massive increase of devices to build we had to overcome some difficulties in our build environment which slowed the builds down a lot. Now it seems to be fixed. Now the build duration is around 27 hours, thats why you cannot expect a new device to be built within one day. First the current build has to finish. The fresh builds are synced once in a hour to our webserver. The list on OP is back and i try to update it.

Using the LineageOS updater under the system menu is the way to go, correct!
@money Donations: Please consider to donate to microg project, or setup feature bountys there. We as the ROM builders work independent from microG and have no demand for donations.
 

kurtn

Senior Member
Can I use the LineageOS updater under the system menu? If not, what's the best way to update LineageOS for microG without losing all my preinstalled apps?
There are several reports of lineageOS>settings>about phone>lineageos updates not working correctly in official ROM. In that case you can try to flash the zip file manually. Located in root /data/lineages_updates/
 
Last edited:
  • Like
Reactions: daloonik

diafero

Member
Jul 24, 2015
49
8
(Stupid XDA lost my post. :( )

This is awesome! Thanks so much for your work :D

Any chance to get support for surnia <https://download.lineageos.org/surnia>?
 

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,544
11,630
@Simon94, I recommend that you add to the installation instruction that the users are wiping /system before flashing the ROM. A factory reset wasn't enough for me to fully remove the Gapps. Was really confused why I couldn't find the microG app and all the Google stuff was working even though the PlayStore was missing.

Other than that it's a really great project, thanks a ton to everyone involved.

Sounds like the LineageOS backup script is still being invoked during the flash - it would preserve the gapps.

One approach would be to disable this script on this version of the ROM, but there's potential for this to break other things (I don't know any examples) if anyone's use case used the backup method to preserve something between flashing.

Either wiping /system or stopping the backup script from running ought to do the trick.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I 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 then
    2
    Hi guys, it seems that we have to say goodbye the mozilla location service (MLS), it will be retired soon ..
    Imho that meens, that shipping the mozilla location location service will be no longer necessary.

    The question is, which version of microG should be included in the upcoming builds ?
    More about mar-v-in's future plans here
    <snip>

    @petefoth : Do you already have an idea how and when integrate a new microG version ?
    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.
    2
    Some more information on why the March QPRS update caused the 21.0 builds to fail: https://www.reddit.com/r/LineageOS/comments/1bp83tb/_/kwvut4m
    The 18.1 branch still has security patches. They don't get merged. So you have to pick them
    https://review.lineageos.org/q/topic:"R_asb_2024-03"

    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't
    2
    All 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/
    2
    Keep an eye on the matrix room to see when the build finishes
    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.
  • 168
    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
    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
    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.
    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.