yashsingh1/xdaforums huggingface dataset:
[Android Software Development] gondyydnog:
Any news about current status of the March build ?

My "oriole" would be happy to try it out...
[Android Software Development] petefoth:
Pretty much unchanged from the post you quoted: 20.0 builds are in progress, currently up to `m5` , with around 30-35 more 20.0 devices to build, at ~3hrs per build.

Then there are the 18.1 devices to build.

`oriole` is on the list (30th out of 62) of 21.0 devices still to be built. That may or may not happen this month, or it may wait until the April build run.

And, as mentioned earlier in the thread, you can keep an eye on progress yourself in the Matrix room https://matrix.to/#/#microg-lineage-os-builds:matrix.domainepublic.net: asking for updates doesn't make the builds go quicker ;)
[Android Software Development] gondyydnog:
Sorry!
[Android Software Development] gbtechlab:
I've ended up with a handful of river and lake devices and have been considering a local build possibly more attractive than waiting. But then after catching up on the thread I'm curious about the upstream issue you were mentioning... are the details of the discussion/work related to the issue something public that can be followed?
[Android Software Development] petefoth:
Yes - in this issue in our github issue tracker (You dont need to login to view the issue)
[Android Software Development] petefoth:
Well I think that I have implemented a fix. If you wanted to make a local build for your devices, you could try using this docker image docker pull lineageos4microg/docker-lineage-cicd:pf-fix-posix-spawn-error

I've tried one build which went OK, but I can't fully test while our build server is busy with the 20.0 and 18.1 builds

If you're interested, the fix is in this PR, which wont be merged until it's been tested a bit more :)

https://github.com/lineageos4microg/docker-lineage-cicd/pull/589
[Android Software Development] Gionathan:
I was indeed able to flash upstream LOS 21 on top of LOS microG 20 following the upgrade guide and it was surprisingly seamless, especially because I flashed Magisk (patched lineage-21.0-20240312-nightly-pdx215-signed.zip/payload.bin/boot.img) right after LOS to keep root.

However, I have a bit of a problem here:

I installed microG apps from the official site/F-Droid and device seems to meet the first 3 conditions, but I'm not sure about the 4th from here:

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/383573?tab=comments

Any idea how to activate signature spoofing? The official wiki seems outdated and relevant info is scarce since signature spoofing in LOS is relatively new
[Android Software Development] petefoth:
Sorry, no idea (again). As you're using official LOS and not los4microG, maybe better to ask in the official LOS support channels: Discord or Reddit - it's a bit off-topic here
[Android Software Development] GedeonBlack:
Hey guys, thanks for all the hard work!

I tried to build (lineage-21) for rtwo (will probably become an officially supported device soon) with the lineageos4microg docker buildsystem (tag: latest), but unfortunately couldn't get it to work. Building it for lineage-20 worked fine previously.

I have attached the build log and would be very grateful if you could maybe just briefly comment on whether the error is familiar to you and if you know where it might come from (e.g. if its caused by the lineageos4microg patches).

I also attached the local_manifest files I used for building.

Sorry to bother you, I'm a total noob at building for android 😅
[Android Software Development] petefoth:
The first error in the log is

[ 78% 142313/180940] build out/target/product/rtwo/obj/FAKE/treble_sepolicy_tests_30.0_intermediates/treble_sepolicy_tests_30.0
FAILED: out/target/product/rtwo/obj/FAKE/treble_sepolicy_tests_30.0_intermediates/treble_sepolicy_tests_30.0

That is definitely not familiar and is nothing to do with the signature spoofing patches (which anyway you no longer need because LineageOS have made changes so that they support signature spoofing without our patches).

The log goes on to say about the error

SELinux: The following public types were found added to the policy without an entry into the compatibility mapping file(s) found in private/compat/V.v/V.v[.ignore].cil, where V.v is the latest API level.
system_charging_prop

See examples of how to fix this:
https://android-review.googlesource.com/c/platform/system/sepolicy/+/781036
https://android-review.googlesource.com/c/platform/system/sepolicy/+/852612

I would follow those links and see if they offer any help.

PS You don't say how you are trying to build: are you using our docker image, or building the old-fashioned way?
[Android Software Development] GedeonBlack:
@petefoth Initially, I did the microg build with the microg docker buildsystem (first sentence in my previous post). To eliminate as many sources of error as possible, I just built the raw rtwo the old fashioned way without any patches and that failed with the same errors. So the problem was not with microg. Thanks for your help!
[Android Software Development] petefoth:
Sorry, I missed that

Sorry your build is failing, but happy it's not our fault. Good luck!
[Android Software Development] Gionathan:
Apparently I just needed to install MinMicroG as kurtn suggested, now I got all them checks 👌
[Android Software Development] Luckz27:
No one here is talking about this?

https://www.reddit.com/r/LineageOS/comments/1b11zex
[Android Software Development] gbtechlab:
There has been mention, yes
[Android Software Development] kurtn:
The significant conversations are happening there

Tracking: upstream reconsidering signature spoofing · Issue #575 · lineageos4microg/docker-lineage-cicd

Just saw this, not sure what involvement you guys have so figured I would point it out here: https://review.lineageos.org/q/topic:%22microg-eval%22

github.com
[Android Software Development] petefoth:
March build run status​

20.0 builds and final 18.1 builds are complete

Builds of remaining 21.0 devices started failing - last successful build was `lynx` at 20/03/2024, 20:02:35. see this issue for details

I don't know what has caused the build failure and I have no idea how to fix it. We are running out of time in March, so unless a fix appears in the next day or so, the March build run is finished. Sorry!

The list of 21.0 devices which have not built this month is:

`kane kebab kirin lake lemonade lemonadep lemonades ls997 lynx m5_tab m52xq marlin martini mata mermaid messi Mi439 Mi8917 Mi8937 nash natrium nio nx563j nx606j nx609j nx611j nx619j nx651j ocean odroidc4_tab oriole panther payton pdx203 pdx206 pdx214 pdx215 perseus pioneer PL2 polaris pro1 pro1x pstar pyxis radxa0_tab raven redfin rhode river rosemary rs988 sagit sailfish salami sargo shiba sunfish taimen tangorpro TP1803 troika ursa us996 us996d us997 vela voyager vs995 walleye xpeng Z01R`

The list of 21.0 devices which have built this month is:

`a52q a52sxq a72q a73xq aura avicii axolotl barbet beckham berlin berlna beryllium bluejay blueline bonito bramble caprip channel cheeseburger cheetah cheryl chiron coral crosshatch devon dipper discovery DRG dubai dumpling enchilada equuleus evert fajita felix flame FP4 gemini grus gta4l gta4lwifi gts4lv gts4lvwifi guacamole guacamoleb h830 h850 h870 h872 h910 h918 h990 hawao hotdog hotdogb husky instantnoodle instantnoodlep joan kane kebab kirin lake lemonade lemonadep lemonades ls997 lynx`

I'm away on holiday this week so won't be able to spend much time on this . If anyone has any ideas about how to fix the problem, please add a comment to this issue: 'Builds failing during soong bootstrap #592`
[Android Software Development] mohama071:
oneplus 11 (salami) he has no luck......unfortunately.......
[Android Software Development] petefoth:
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
[Android Software Development] mohama071:
we are waiting for the April version....(OnePlus 11 salami)
[Android Software Development] petefoth:
No guarantees that 21.0 builds will be fixed in time for April. We are dependent on the upstream LineageOS project and their device maintainers to do the necessary work
[Android Software Development] mohama071:
hoping that (op 11 salami) will have LineageOS microG versions 21.0 in April.....Hoping..thanks Mr petefoth
[Android Software Development] heinhuiz:
Came to check this thread to see if there were any problems with the 20.0 builds, since my lmi didn't get updated since February. It seems the builds stopped at that device and came back at m5 or something. Are there any problems with that device?

Also, the latest build overall is almost a week ago.
[Android Software Development] petefoth:
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
[Android Software Development] kurtn:
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:%22R_asb_2024-03%22

Not to forget: the webview can be updated that way.
[Android Software Development] petefoth:
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

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
[Android Software Development] petefoth:
I needed to make a test build (to check some changes made in our docker engine). I chose to build for `lmi` as it missed out in the earlier run. The build is currently at 99% - way past where it failed earlier - so, with luck it should show up at https://download.lineage.microg.org/lmi/ and/or as an OTA update sometime relatively soon. Keep an eye on the matrix room to see when the build finishes
[Android Software Development] Oelmuvun:
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.
[Android Software Development] heinhuiz:
T

Thanks a lot! Am downloading the OTA update.
[Android Software Development] mohama071:
It seems we have to wait a long time for (OP 11 Salami)
[Android Software Development] petefoth:
I am having problems with Ebay in the 21.0 release (the one that got made before 21.0 builds gt broken upstream). Trying to sign in with username and password gives an 'Invalid request` error. I've tried the usual clear storage and uninstall / reinstall magic but no joy. Back to using Ebay via the browser :(
[Android Software Development] borisSweden:
With bugs in building ROMs increases with 13 to 14, is it possible to postpone a build session for hotdogb? I'm on 240308 and 240315 isn't that significant. The next build for hotdogb from LOS looks very big. So its a suggestion to not build a ROM for now until the next big update.
[Android Software Development] petefoth:
We're not trying to make any los-21.0 / Android 14 builds because the upstream LOS builds are broken. We'll start making 21.0 builds when they are fixed upstream
[Android Software Development] petefoth:
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/
[Android Software Development] 2faraway2:
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

Will be interesting upcoming weeks/months, changes everywhere .. ;)

@petefoth : Do you already have an idea how and when integrate a new microG version ?
[Android Software Development] petefoth:
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.
[Android Software Development] heinhuiz:
Do I understand correctly from the github discussions that at this moment only the last stable version (0.2.27.223616) has more or less working location services? Would it thus be a bad idea for me (the average user) to upgrade to the latest version like you did?
[Android Software Development] kurtn:
The average user needs location for outdoor navigation in suburban areas. That's satellite navigation. Not related to microG.
[Android Software Development] petefoth:
Location services work fine for me using the latest beta 0.3.1......
[Android Software Development] 2faraway2:
I wouldn't agree, location services worked on 0.3.0 as well as yet on 0.3.1 !

Although I have to say that I've already collected all towers and wifis in my area and stored them local on the phone (dejavu / local nlp), so that's not a big deal any more ...
[Android Software Development] ToughDBlue:
For me 0.2.27 is the only version that Location Services is actually accurate. On versions above that I have to disable everything in microG Locations Services except Nominatim in order for my weather apps to not be hundreds of miles off whuch means I have to rely totally on GPS for accurate location services those beta versions
[Android Software Development] petefoth:
Upstream lineage-21.0 builds have restarted, and I have resumed the attempt to make 21.0 builds for those devices which didn't get them in the March build run.

a build run is in progress for bramble,pro1,dipper,mermaid,berlin,devon,rhode,bluejay,river,pdx206,gts4lvwifi (the first devices to build successfully upstream)

when that completes, I will start a build run for the remaining devices (m5_tab,m52xq,martini,Mi439,Mi8917,Mi8937,nio,ocean,odroidc4_tab,oriole,panther,pdx203,pdx214,pdx215,perseus,pioneer,PL2,polaris,pro1,pro1x,pstar,pyxis,radxa0_tab,raven,redfin,rosemary,salami,shiba,sunfish,surya,tangorpro,TP1803,ursa,vela,voyager,xpeng,Z01R,zippo)

Not all of the devices that were on the 21.0 list in March have been restored to the list. The current list of build target devices can always be found in this file. As always you can keep an eye on build progress in the dedicated Matrix room
[Android Software Development] petefoth:
Issue with `bramble`. The following issue documents a problem with the latest LineageOS ROM for `bramble`. I don't now whether it will be a problem for our buuld, but you may want to hold off from updating, or at least backu your user apps and data.

https://gitlab.com/LineageOS/issues/android/-/issues/7005
[Android Software Development] winnie_ops:
I guess I was too fast applying the update. Now my bramble shutting itself off after few minutes. It's unusable.

LineageOS team just made a special build for this issue. Can we have its reflection with MicroG as well?
[Android Software Development] petefoth:
I will start a new build for bramble when the current build run finishes: that may not be until tomorrow morning
[Android Software Development] winnie_ops:
It sounds much better than resetting the device from ground zero for downgrading to the previous release.

My respect and appreciation for your work on LOS for MicroG!
[Android Software Development] petefoth:
Builds for pro1,dipper,mermaid,berlin,devon,rhode,bluejay,river,pdx206,gts4lvwifi succeeded. The build for bramble succeeded but had an error, and has now been removed from the download server.

A new build run has started for bramble,salami,m5_tab,m52xq,martini,Mi439,Mi8917,Mi8937,ocean,odroidc4_tab,oriole,panther,pdx203,pdx214,pdx215,perseus,pioneer,PL2,polaris,pro1,pro1x,pstar,pyxis,radxa0_tab,raven,redfin,rosemary,shiba,sunfish,surya,tangorpro,TP1803,ursa,vela,voyager,xpeng,Z01R,zippo
[Android Software Development] winnie_ops:
Just applied the new bramble build. Nasty reboots are gone now. The phone is back to life. Thank you!
[Android Software Development] ToughDBlue:
I see the build for Panther completed but Upstream hasn't updated their build since March. So that means LOS for microG Panther doesn't have Android 14 QPR2. Correct?
[Android Software Development] petefoth:
Not correct. The upstream code including Android 14 QPR2 is available and was used in our latest build.Upstream just haven't got round to making a build yet for this device
[Android Software Development] ToughDBlue:
Ok, I'm confused now. I thought that the reason upstream took about a month to release their updates was because they had to implement QPR2. So I figured since they haven't released an update yet to Panther since last month that LOS for microG didn't get QPR2 yet.
[Android Software Development] petefoth:
No need to be confused, it's quite simple :)

It took LOS a month or so to make the necessary changes to work with QPR2. While they were doing that they disabled builds for 21.0 devices (in this commit to the build target list on 20th March). At that point our 21.0 builds started to fail.

When all the needed code was in place, LOS re-enabled builds for 21.0 devices (in this commit to the build target list on 13th April). Then they started making builds for all devices, and that process is currently still going on - see here and / or here.

We (LOS for microG) started making builds around the same time (see here) using the same code. We started and completed our build for panther before they did.You can see the devices that have had recent builds of LOS for microG 21.0 in the matrix room. We are focussing on devices that did not get a 21.0 build in March because we hadn't made a build for the before the breaking QPR2 changes landed. Builds for bramble,salami,m5_tab,m52xq,martini,Mi439,Mi8917,Mi8937,ocean,odroidc4_tab,oriole,panther,pdx203 have completed. Builds for pdx214,pdx215,perseus,pioneer,PL2,polaris,pro1,pro1x,pstar,pyxis,radxa0_tab,raven,redfin,rosemary,shiba,sunfish,surya,tangorpro,TP1803,ursa,vela,voyager,xpeng,Z01R,zippo will (with luck) complete in the next few days. All of these builds have the QPR2 changes.

Devices which did get a 21.0 build in March, without the QPR2 changes, will get a new build with the QPR2 changes in the May 2024 build run.

Does that ease the confusion? ;)
[Android Software Development] kurtn:
Meybe we get a bunch of new old lineageOS 20 devices to buid

https://review.lineageos.org/q/topic:%22return-to-20%22
[Android Software Development] petefoth:
If / when that gets merged to the build target list then we will pick it up in the next monthly build run after the commit.: we use that list to determine which devices and branches we build for
[Android Software Development] ToughDBlue:
Got it! Thank you for clearing that up. So then all the changes that Upstream shows for theier next Panther 21.0 run you have already included even though they haven't yet. Correct?
[Android Software Development] borisSweden:
Absolutely, we really don't want bugs because QPR2 is huge.
[Android Software Development] petefoth:
There will always be bugs - we just haven't found the yet ;)
[Android Software Development] marmistrz:
Hi, is there an archive available with last available builds for device that are no longer supported? I'm looking for lineage-18.1-20240219-microG-oneplus3.zip, which is no longer there on https://download.lineage.microg.org/oneplus3/
[Android Software Development] petefoth:
Last available builds for devices that are no longer supported by LineageOS have been moved to https://download.lineage.microg.org/archive/

The last available build for oneplus3 is lineage-18.1-20240318-microG-oneplus3.zip
[Android Software Development] marmistrz:
Thank you very much! I think it would be nice to have it linked on the main website.
[Android Software Development] petefoth:
Agreed. I have raised it as an issue which will be addressed when I have the time to get round to updating the website.

Until then I have added some words in the README.md
[Android Software Development] ToughDBlue:
Does LOS for microG support locking of the bootloader for a Pixel 7?
[Android Software Development] kurtn:
No. Use calyxos or divestOS
[Android Software Development] petefoth:
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
[Android Software Development] petefoth:
The May build run has started and can be followed:

in the Matrix room

in this issue

Note that, because of an error I introduced in the main build script, the first builds made on 1st and 2nd May were not properly signed. The affected builds have been removed from the download server and will be rebuilt. Sorry!
[Android Software Development] mohama071:
is there a lineage update lineage-microG-husky (Google Pixel 8 Pro) from 03/09/2024
[Android Software Development] petefoth:
Not yet, but it is on the build target list for the current build run
[Android Software Development] heinhuiz:
Just a small off-topic question, does anybody have the new BBC News app working? I only get a small yellow triangle with a exclamation mark inside, I wonder if it's caused by the lack of Google services.
[Android Software Development] petefoth:
Working fine for me. What los4microG version and what device are you running?
[Android Software Development] hulkjulk:
I've seen that m5 and the others (deadpool, odroidc4, pstar, radxa0, wade) are expected to fail. Are there some tries to get these work or won't they work at all because of the core?

Am I correct that the 20 builds are also not supported, or?

Thanks a lot for your work!
[Android Software Development] mohama071:
THANKS @

petefoth​
[Android Software Development] petefoth:
See Note 2 in this section of our README

That is true for all recent android versions.

This is because no-one has yet done the necessary work to make these devices build successfully