yashsingh1/xdaforums huggingface dataset:
[Android Software Development] kurtn:
Lineage recovery flashes lineage4microG just fine. And in case of enabled recovery update, it's immediately overwritten with L4M recovery
[Android Software Development] heinhuiz:
I know, I always use it these days. TWRP is not really working for me since Android 12. There is no official version for my device and I don't trust all the unofficial versions going round.
[Android Software Development] mll2:
You assumed right. Thanks for trying, anyway. I feel like it's game over. Too bad for my data. :'(
[Android Software Development] Sarlaytos:
Hi !

This is my first time installing a custom rom, sorry if I don't understand everything right away.

I want to install LOS with micro g instantnoodlep

On lineage.microg.org I downloaded those files (and checked the sha256 hashes):

lineage-20.0-20230411-microG-instantnoodlep.zip

lineage-20.0-20230407-microG-instantnoodlep-recovery.img

lineage-20.0-20230407-microG-instantnoodlep-boot.img

First question: the version number doesn't exactly match, is that an issue ?

Then on the official lineageos.org, I downloaded from the latest instantnoodlep release:

- dtbo.img

- vbmeta.img

But the zip available along with those files is: lineage-20.0-20230423-nightly-instantnoodlep-signed.zip

Which is more recent than the recovery and boot that I downloaded from microg earlier Is that ok ? Will it cause a bootloop ? Should I download an older version of dbto and vbmeta released with the: lineage-20.0-20230416-nightly-instantnoodlep-signed.zip ? or even the 20.0-20230409 version ?

The sha256 hashes of the dtbo.img and vbmeta.img are different from version to version on the official lineageos download page, which is what is worrying me.

Thanks in advance for your awnsers
[Android Software Development] kurtn:
Personal suggestion: install the original lineageOS. Follow the installation instructions to the word. Don't install GApps or magisk. Make sure everything works. You only get official help in that configuration.

If you find out you need microG, you can sideload lineage.microG.org at any time. Preferred with increase of build date.
[Android Software Development] Beer4661:
Good day ,

I have a SM-T725 with lineageOS 20-20230429-NIGHTLY-gts4lv + MindtheGapps installed . Can I install directly the lineage-20.0-20230411-microG-gts4lv without uninstalling anything ?

Can I sideload Magisk.zip before rebooting to root the tablet.

Thanks
[Android Software Development] kurtn:
There is no easy way to remove GApps but keep all your other apps. Do a fresh installation.

Magisk can be installed at any time. I first would check a fresh installed custom rom before torturing it with magisk.
[Android Software Development] Beer4661:
This morning my SM-T725 did reset itself when booting . What could be the problem ?

Thanks.
[Android Software Development] Jazzda:
So, it seems Lineage4MicroG is dead, right?

No updates after may 3 and some builds just disappeared 🤔
[Android Software Development] kurtn:
Not dead.
[Android Software Development] Jazzda:
Nice to hear, but how do you know that? Everything related to it is very quiet :unsure:
[Android Software Development] kurtn:
There is activity in github.
[Android Software Development] ALexus1907:
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.
[Android Software Development] kurtn:
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
[Android Software Development] KenHerman:
When you say "next round", what timeframe is that - monthly?

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...
[Android Software Development] kurtn:
Builds just started. Wait another week.
[Android Software Development] KenHerman:
Great to hear! Thank you for the update. Much appreciated.
[Android Software Development] espionage724:
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
[Android Software Development] espionage724:
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
[Android Software Development] mll2:
Well, reinstalling microG LOS by sideloading didn't work for me.
[Android Software Development] kurtn:
You have to confirm signature mismatch
[Android Software Development] mll2:
Sure

Of course, which I did.
[Android Software Development] espionage724:
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.
[Android Software Development] lvlouro:
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?
[Android Software Development] PerfectJam:
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,
[Android Software Development] KenHerman:
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.
[Android Software Development] 💋 Mumu:
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 😽
[Android Software Development] kurtn:
There is no reason to wait. No matter wen the update will come - it is easy to install.
[Android Software Development] unono:
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.
[Android Software Development] jctghost:
The only thing I would love about the microg lineage project would be a build status page showing when devices are added or dropped. I follow the build releases for Lineage proper, however that does not translate to when those builds will be included in the Lineage for MicroG repos. For example, my OP7T is still being supported by LineageOS, however it has not received an update on Lineage-MicroG since April. I know I could dump and build Lineage with MicroG myself, however I would rather send money to support my OEM dumped but good phone to the Micro-Lineage groups. However, if you cannot tell the status of development and support - well? I know with Android Custom ROMS it's not Linux LTS distributions - but a ballpark would be nice. Again, maybe just a list of abandoned hardware. I fully understand that compiling for the ever increasing number of phones out there is intensive, and maybe it's a 5-10 year window, but the website is almost static other than the download list. Thank you to the developers, I would likely have had to retire my OP7T long ago if it was not for the OSDevgroups!
[Android Software Development] kurtn:
There is a lengthly discussion and a link to matrix published build results.

Have the builds stopped? · Issue #418 · lineageos4microg/docker-lineage-cicd

It looks like the current image builds stopped after DRG a few days ago: https://download.lineage.microg.org/?sort=time&order=desc

github.com

I don't think your phone is dropped. Probably one or two builds failed.
[Android Software Development] CollieBabaX:
Hi,

I would like to put LineageOS for microG on a Banana Pi M5, already supported by LineageOS, to make an Android TV box.

It's possible?

Thank you
[Android Software Development] kurtn:
That? Lineage.microg.org only builds for officially supported devices.

Info about m5 | Odd Solutions Wiki

wiki.oddsolutions.us
[Android Software Development] heinhuiz:
All official builds are automatically included, so this one will come in the next round.
[Android Software Development] CollieBabaX:
I saw that in the LineageOS for microG devices compatibility list there are only smartphones, there are no microcomputers (like the Banana Pi) or TV boxes (like the Dynalink TV box), altought they are supported by LineageOS.
[Android Software Development] espionage724:
Should be easy, relatively speaking :p

It's been some versions since I built LOS (last around version 15 or 16), but for microG I just took two patches from microG's GitHub (allow signature spoofing and location providers outside /system) and applied them as-is to LOS sources. I have some old notes here about it. I don't know about building microG into LOS directly, but for my ROM I added microG's repo to F-Droid and then installed and set everything up from there; basically people could choose either basic LOS, flash traditional Gapps, or use microG all with the same base LOS ROM.

The only thing needed to install microG onto LineageOS and allow it to function is a patch to allow Signature Spoofing afaik.
[Android Software Development] CollieBabaX:
I was thinking of making a de-googled Android TV box. Doing as you say, all the Google apps remain, right?
[Android Software Development] kurtn:
There seems do be a misunderstanding. Official lineageOS is "deGoogled" to a certain degeee. It is built without Google play services and store etc.

Lineage.microG.org does not remove anything. Thy just add microG and f-droid and some modifications to make those run.

You can always start with official lineageOS and f-droid. If you have apps that complain about missing play services, you can always upgrade to the microG fork.
[Android Software Development] CollieBabaX:
Thanks for the explanation, I didn't know that. So "LineageOS for microG" itself is simply LineageOS with microG already installed by default?

What do you mean by "upgrade to the microG fork"?
[Android Software Development] kurtn:
The heavy lifting ist making lineageOS recognize microG as Google play services replacenent. We call that signature spoofing. Official lineageOS people refuse to build signature spoofing into lineageOS. That's why some volunteers have foked lineageOS. And made this thread.
[Android Software Development] CollieBabaX:
But do you can install microG on LineageOS without this signature spoofing? Or do you mean I have to install LineageOS and then upgrade to the microG fork? Sorry I'm noob
[Android Software Development] kurtn:
Yes. You can install microG on official lineageOS without signature spoofing. But it will have very limited functionality. You should try to find out what functions you really need. Based on that you can decide microG or GApps or none of them. - and eventually the installation method.
[Android Software Development] petefoth:
As both devices are officially supported by LineageOS officially (i.e. are they listed at https://wiki.lineageos.org/devices/) then builds should be available. I will go digging into why they are not. In the mean time, you could try building for yourself using docker, as described here. The `BRANCH_NAME` to use for the build would be `lineage-20.0`
[Android Software Development] CollieBabaX:
Ok thank you, I haven't bought the Banana Pi yet, I wanted some info to evaluate the purchase. I'll try

Indeed, it seems strange. If you can get info let us know, thanks petefoth.

And to build it by myself, maybe I'll try
[Android Software Development] petefoth:
Banana Pi M5 `m5`: this was only added to the list of LineageOS-supported devices two weeks ago. So it should be included in the next round of builds. No guarantee that the build will succeed though :(

Dynalink TV box `wade`: the builds for this device have been failing ever since it was added to the list of devices in 2022. New makefiles need to be written for TV box devices. No ETA for when this will be done :)
[Android Software Development] CollieBabaX:
Then I think I'll wait for the next round of builds and see if it will be supported, no rush for this project. Thanks again!
[Android Software Development] raj.ify:
Trying to install LosMicrog 20 on Pixel 5, flashed provided boot image and ended up with screen saying "no command" as i couldn't boot into recovery. Pls someone let me know the installation process.
[Android Software Development] raj.ify:
Few apps are unable to detect the added Google account while restoring backup saved in g-drive, like WhatsApp. When I try adding account it says account is already added but not showing up in the app to select the restore. Any fix?
[Android Software Development] lvlouro:
I've tried with the latest build, 20230706 and have the same problem.

Anyone has any clue what changed since the April's builds?

Until April I had no issues, I'd guess something change thereafter
[Android Software Development] bigsatan:
Make sure debugging is disabled
[Android Software Development] lvlouro:
When updating?
[Android Software Development] espionage724:
Do you have a specific app that could be checked quick to see if it complains about root? I have a OP6 and no root, but nothing I do cares about root afaik.
[Android Software Development] lvlouro:
IKEA (https://play.google.com/store/apps/details?id=com.ingka.ikea.app) is one random app that started complaining along the other ones, although I don't really need it.

The ones I need are a banking app and a government app from my country that I'd rather not disclose ;)
[Android Software Development] heinhuiz:
Check the general discussion of LOS for OP6. Probably you're facing a LOS problem, not a MicroG one.
[Android Software Development] lvlouro:
So I found a solution to my problem

I edited /system/build.prop via root adb

changed under from variable ADDITIONAL_SYSTEM_PROPERTIES

ro.debuggable=1 to 0

And now no more complaining ;)
[Android Software Development] petefoth:
You may have noticed that updates for some devices are missing. Some of the automated builds for `lineage-20.0` devices failed, and the failures caused a chain reaction of failures in the builds for `18.1` and `19.1` devices.

Builds for the `19.1` devices have been manually started and are in progress: `apollon,blueline,bonito,crosshatch,discovery,gauguin,gemini,h830,h850,h870,h872,h910,h918,h990,kirin,liber,ls997,mermaid,miatoll,monet,nash,natrium,parker,pioneer,rs988,sargo,tissot,us996,us996d,us997,vayu,voyager,vs995,z2_plus`

When they are completed (probably in 3 or 4 days time), builds will be started for

`18.1` devices : `a5y17lte,a7y17lte,addison,ahannah,albus,bacon,castor,castor_windy,cedric,debx,ether,flox,foster,foster_tab,FP2,ginkgo,griffin,hannah,hlte,hltechn,hltekor,hltetmo,jactivelte,jflteatt,jfltespr,jfltevzw,jfltexx,jfvelte,klte,klteactivexx,klteaio,kltechn,kltechnduo,klteduos,kltedv,kltekdi,kltekor,marlin,montana,oneplus3,porg,porg_tab,rhannah,s3ve3gds,s3ve3gjv,s3ve3gxx,sailfish,shamu,sirius,victara,x2,z3,z3c,zl1`

the `20.0` devices which were not successfully built automatically (excluding Banana Pi `m5`, Dynalink YV Box (4K) `wade` and Google ADT5 `deadpool` which, are Android-TV devices, and are not currently supported by lineageos4microG): `channel,sagit,sake,starlte,star2lte,sunfish,surya,taimen,TP1803,troika,ursa,vela,wade,walleye,X00TD,xmsirius,xz2c,Z01R,zippo`

As they complete, the new builds should appear as OTA updates,as well as being available for download from the download server

Build progress can monitored on the matrix channel

Work is also happening to try to ensure such problems do not occur again :)
[Android Software Development] petefoth:
Clarification about Android TV boxes

At the moment, lineageos4microG does not support `minimal` devices (Banana Pi `m5`) or Android TV boxes ( Dynalink YV Box (4K) `wade`, Google ADT5` deadpool`) even though these devices are currently supported by LineageOS.

See this issue for more details and discussion
[Android Software Development] petefoth:
19.1 builds *are* still progressing, but progress is not currently being reported to the matrix channel. You can check the latest successful builds by keeping an eye on https://download.lineage.microg.org/?sort=time&order=desc
[Android Software Development] CollieBabaX:
Ok thank you
[Android Software Development] kurtn:
The schedule has changed? Looks like missed 20.0 devices get built now after 19.1
[Android Software Development] petefoth:
Yes,. There are 18 devices for 20.0 builds, and 52 devices for 18.1 builds. At ~2 hours per build, doing the 20.0 devices first fits in better with the stuff going on in the rest of my life ;)
[Android Software Development] petefoth:
The 18.1 builds are in progress and have all completed successfully so far (up to sunfish). There seems to be a problem uploading some of the builds to the download server. This will be adressed when the 18.1 build run is complete, probably sometime tomorrow. The failed uploads that I know about so far are for the following devices. Please let me know if there are any others I have missed:

castor,castor_windy,debx,foster,foster_tab,ginkgo,jfltexx,marlin,porg,porg_tab,s3ve3gds,s3ve3gjv,sailfish
[Android Software Development] heinhuiz:
I think all the 20.0 builds between castor and sagit are missing. For me, I don't see lmi.
[Android Software Development] petefoth:
`castor` is an 18.1 device not 20.0. The latest 18.1 builds for the following devices are built, but not yet uploaded to the server: `castor,castor_windy,debx,foster,foster_tab,ginkgo,jfltexx,marlin,porg,porg_tab,s3ve3gds,s3ve3gjv,sailfish`

`sagit` download directory contains a full set of binary (`boot.img`, `recovery.img`, and .zip`) and `.sha256sum` files dated 23/07/2023. `lmi` download directory contains similar, dated 07/07/2023
[Android Software Development] heinhuiz:
My mistake, I meant between 'channel' and 'sagit'. These are both present with builds dated 07/23/23, but all 20.0 devices alphabetically in between are either not built or not uploaded. For lmi, the lineageos.org download server contains builds from 07/08/23, 07/15/23 and 07/22/23.
[Android Software Development] petefoth:
cheeseburger has a full set of binary (`boot.img`, `recovery.img`, and .zip`) and `.sha256sum` files dated 23/07/2023.

chef has `boot.img` and the main ROM `.zip` file dated 03/07/23

as mentioned above, lmi contains a full set of files dated 07/07/2023

These are the latest builds of lineageos4microg.

If you are not seeing these files, then I have no idea what your problem is - the files are definitely there!

LineageOS make official builds ***weekly*** for 20.0 devices. We only make builds ***monthly***. Our latest build run started on 07/01/23. Some builds failed and had to be re-run but the re-runs completed this morning. The current situation is

for 20.0, 19.0 and ***most*** 18.1 devices, the builds have succeeded, and have been uploaded

for the 20.0 devices you mention, and for the 18.1 & 19.1, the original builds failed, were successfully re-run starting 23/07 and, with the following exceptions have been uploaded

as mentioned above, for the following 18.1 devices, the re-run builds succeeded, but not yet uploaded to the server: `castor,castor_windy,debx,foster,foster_tab,ginkgo,jfltexx,marlin,porg,porg_tab,s3ve3gds,s3ve3gjv,sailfish`. This is being worked on - when the maintainers have time - but I don't have an ETA for the fix
[Android Software Development] heinhuiz:
Oh OK. I assumed you would just build all 20.0 devices, not only the failed ones. My bad.
[Android Software Development] espionage724:
Could someone test Orna the GPS game on LOS for microG?

https://play.google.com/store/apps/details?id=playorna.com.orna

https://m.apkpure.com/orna-the-gps-rpg/playorna.com.orna

I've tried Orna on regular LOS 20 without microG and it's failing to get a location, but GPS on an random GPS stat app and OsmAnd works fine.
[Android Software Development] benhidalgo:
Lineage 20 microG works like a charm on the OnePlus 9p. No bugs so far. Very fast. microG also doing what is supposed to. I had to use the play store to get what I wanted, but that's on me.

TWRP flashed it without any issues.🥸👍
[Android Software Development] humpty321:
The way you are writing dates here 'dd/mm/yyyy' and in the devices list 'mm/dd/yyyy' keep me permanentely struggling to make out what is 'dd' and what 'mm'. And I guess I'm not the only one.

On the LineageOS site they write dates according to https://en.wikipedia.org/wiki/ISO_8601

Is there a special reason for your choice of format and to not follow the ISO standard?
[Android Software Development] petefoth:
That's the date that appears that n my view if the web page
[Android Software Development] petefoth:
The problem was caused by lack of disk space on the download server - it was down to around 67MB!!

Some housekeeping has been performed, and there is now around 50GB free, which should be more than enough for the August build run which is due to start soon.
[Android Software Development] Tarch1:
Hi deve,

I'm running the latest build 20.0 for Samsung galaxy A52s5g (named a52sxq) dated 01 June 2023.

There was 3 new build on lineage server, 16/7 23/7 30/7 but no build from lineage microg, then I read in the previous page that there was some problem when building but I didn't see mentioned my device, is it discontinued by your project?

Best regards
[Android Software Development] petefoth:
LineageOS have the resources to make weekly build for the most recent devices. LineageOS for Microg has fewer resources, so we only make monthly builds. The most recent build for your device is from 1st July 2023, and is available here

There will be a new build this month, probably in the next 7-10 days. This should appear as an update in the Updater app on your phone

No :)