yashsingh1/xdaforums huggingface dataset:
[Android Software Development] kurtn:
Sorry that needs a longer reply, because we have such a wide variety of devices an recoveries and user preferences.

TWRP (and similar recoveries) checks signature of wannabe installed build in comparison to already installed ROM. It throws error 7 in case of a mismatch. To migrate from official lineageOS to L4µg you either wipe system partition or flash that migraion zip you found. Once on L4µG, OTA updates should work fine.

Lineage Recovery (and similar) checks signature of wannabe installed build in comparison to a in-recovery stored signature. In manual flashing you can override a mismatch warning. For OTA update that mismatch is a show-breaker. In many devices you can enable "update recovery". That will overwrite the current recovery with L4µG recovery.

You will typically find TWRP on a-only devices and lineage recovery on a/b devices. But be prepared to find stranger combinations.
[Android Software Development] petefoth:
A recent change appears to have broken the build run which started today. I will revert the change, and restart the build later today.

Apologies!
[Android Software Development] petefoth:
The build run has been restarted, and has got past the point at which it failed earlier. I'll keep my eye on how it's doing
[Android Software Development] kurtn:
Interesting. My devices (and experience) seems to be older than yours. When comparing to other distros we should take into account the device zoo. IodéOS supports only modern devices. /e/ and LineageOS support quite old devices. And many of them. We can't test the installation procedures for all of them. So It is necessary to keep the procedures as close as possible to LineageOS.

"3. Installing an OTA update of L4M. Again, they keys of the two ROMs are going to match, so there should not be a problem" i think that's wrong. It is a problem, when the key of the recovery doesn't match the key of the OTA file. The workaround is to update the recovery from L4M updater. Are we sure that update works for each device?
[Android Software Development] CollieBabaX:
In the installation guide on LOS website says to press SW5 to enter the burn mode, but the banana pi m5 have only 4 switches: SW1, RESET, SW3 and SW4. Do you know which the right switch is?
[Android Software Development] CollieBabaX:
It's funny, it's the first thing to do in the guide and you can't:ROFLMAO: I can try with the other switches but how I know when it is in burn mode?
[Android Software Development] petefoth:
I have made a number of changes in the `docker-lineage-cicd` repo, that I plan to merge tomorrow. I would be interested in any comments - here or in the PR - before I do the merge. The main change is to zip up the `.img` files that we currently deliver for a device, into a single `images.zip` file. This is to save space and clutter on the download server. The 'images.zip' file is not flashable with `fastboot`: after investigation, that change proved to be not feasable.

The PR also includes a number of documentation changes in the 'README.md' file.

Thanks for any input.
[Android Software Development] kurtn:
Nice. So we are writing the important pieces of information to readme.md - what's the plan for the website lineage.microG.org ?
[Android Software Development] petefoth:
The plan is to update it with some of the information that is now in the README, but at the moment I am not able to modify the web site. Until I am able to modify the web site, I will continue to add documentation in the README
[Android Software Development] wowi63:
Option: Update Recovery activated, but does not do.

In our family we got four Xiaomi Poco F1 (beryllium) with L4M and one Samsung Galaxy Tab S6 Lite (Wi-Fi) (gta4xlwifi) running LOS without GApps.

All devices got the activated option options -> system -> updater -> options -> update recovery.

The Samsung Tab does update, the Pocos with L4M doesn't.

In the directory of the installion files of the Tab there is a file "recovery.img".

In the directory of the Pocos was in September a file "lineage-20.0-20230901-microG-beryllium-recovery.img", now in October there is "lineage-20.0-20231001-microG-beryllium-images.zip", including "recovery.img".

The updater offers something in the size of 45 MB from 2. October, (which is the size of "... images.zip") i can download it, but i cannot install it. "Update Check failed"

We got two Pocos, where the version of the recovery is 20.0 (20230123). I think this is the date when i upgraded to LOS 20. I upgraded the recovery of other two Pocos in Septermber manually, 20.0 (20230903). This versions stay after updating to LOS 20231002.

It is possible to get this option running?

​
[Android Software Development] humpty321:
For bramble there ist today a new update: lineage-20.0-20231003-microG-bramble.zip

But this time there is an additional file: lineage-20.0-20231001-microG-bramble-images.zip

What is this second one for?

Need I to install it too?

And if yes , in which order?

And can this be done by the builtin updater?

How to handle it all on rooted device?
[Android Software Development] kurtn:
Use the built in updater.

GitHub - lineageos4microg/docker-lineage-cicd: Docker microservice for LineageOS Continuous Integration and Continous Deployment

Docker microservice for LineageOS Continuous Integration and Continous Deployment - lineageos4microg/docker-lineage-cicd

github.com
[Android Software Development] petefoth:
See this (new) section in the README, which says

The new file is the second item mentoined

No. You only need it's contents if you are installing los4microg for thw first time

No need to do anything different - just install the new update as you did before, either via recovery or using the Updater
[Android Software Development] petefoth:
Sorry - this is a bug, introduced in this month's build run: updating recovery is not going to work. I'm pretty sure I know how to fix it and the fix should be in for next month's build run. In the meantime, there should be no problem using the old recovery.

If you really want to update the recovery then follow the Installing a custom recovery using fastboot section of the LOS installation instructions. You will need to extract the file `vendor_boot.img` from the `images.zip` file
[Android Software Development] petefoth:
Sorry - double post
[Android Software Development] wowi63:
Thank you, Pete!

In the "image.zip" there is no "vendor_boot.img", but "recovery.img" - i think this would be right?
[Android Software Development] petefoth:
Whatever the LOS instructions for your device say. For beryllium they do say

fastboot flash recovery recovery.img
[Android Software Development] humpty321:
Thank you for your helpful explanation !
[Android Software Development] gongoscho:
Thank you!

Yesterday I updated from version: lineage-20.0-20230903-microG-beryllium to version: lineage-20.0-20231002-microG-beryllium automatically via OTA with Magisk without any problems.

grEEtZ
[Android Software Development] espionage724:
Has anyone tested any Niantic games and Google sign-in?

[com.nianticlabs.pokemongo] Google sign-in immediately fails and "Unable to authenticate" · Issue #1979 · microg/GmsCore

Affected app Name: Pokémon GO Package id: com.nianticlabs.pokemongo Describe the bug When trying to log-in with Google, Pokemon GO fails and says "Unable to authenticate. Please try again." To Repr...

github.com

Pokemon GO worked for me, but only from Trainer Club log-in and not Google. Ingress surprisingly worked with Google sign-in. Monster Hunter World didn't work with Google sign-in (the only choice). Since Ingress worked, I expected PoGO and MHW to work too; the other person in the thread reports PoGO and a Google account to work, so maybe there's more to it?

All 3 games can be sideloaded and found on APKMirror. Pokemon GO (likely Ingress and MHW too) requires SafetyNet enabled.
[Android Software Development] chuckt62:
Is there a place (subforum, git repo, readme.md...) somewhere for specific official L4M device builds?

I’m looking to install over my current LOS 20230920, and the latest on L4M is 20230914. There have been 3 new LOS version since then. I just want to see if there are any problems or maybe an ETA. My device is redfin if that helps.
[Android Software Development] kurtn:
There is no per-device forum.

The most up to date info is in this xda thread and in https://github.com/lineageos4microg/docker-lineage-cicd#web-site-text
[Android Software Development] petefoth:
See here: which says

`redfin` is in ~130th position in the list of ~160 20.0 devices. The current build run is up to `equuleus` which is ~50th in the list. Each build takes around 2.5 hours, so you can do the sums :)
[Android Software Development] petefoth:
October build run - status​

docker fell over late last night while building for `equuleus`.

Before restarting the builds I took the opportunity to fix the problems caused by the change to zipping up the extra `.img` files (by reverting the change). I tested the fix by building `equuleus`. I intended to start rebuilding the rest of the `20.0` devices, but I got distracted and kicked off the build of the 19.1 devices instead :)

So

19.1 builds are in progress, and should complete sometime on Sunday morning

then I will start building the 20.0 devices that are not already built - everything after `equuleus` in the build target list

when those are done, I'll kick off the build for 18.1 devices

when all those are done, I could rebuild for the 20.0 devices up to and including 'enchilada`, which have already been built but are suffering from the 'zipped up recovery images' problem. But, unless anyone depreatly needs those, I'll probably just wait for next month's build run, and go for a quite beer and a lie down instead :)
[Android Software Development] heinhuiz:
Just yesterday and today, I've installed a davinci device from stock to the latest 20.0, using those zipped images. I'm happy as a puppy because all went well. Didn't need beer but was drinking wine instead.

Cheers!
[Android Software Development] borisSweden:
Hi, does the builder do anything to the kernel? Would be great if they added Wireguard module in the kernel for all devices.
[Android Software Development] kurtn:
No, they don't.
[Android Software Development] petefoth:
Interesting idea but it's not going to happen.
[Android Software Development] borisSweden:
OK and thanks for the quick answer, I will have to use a custom kernel but will it create more steps when you update the device?
[Android Software Development] petefoth:
Sorry - I have no idea. To be honest, I don't know what you are trying to do, and how it affects our builds. But I hope it works for you
[Android Software Development] david003:
For what it's worth, the stock kernel for me includes the wireguard module. I've tried using it off and on the past few years, but it has issues and I don't think it's worth it. The standard "go userspace" backend works better and doesn't use appreciably more battery or cpu that I can tell (it's so low as it is).

The main issue is that there is no way to set it to be "always on" and when you first login after rebooting, it leaks and opens connections without wireguard for awhile before wireguard becomes active. There's also a disconnect/reconnect issue if you try to start the wireguard app.

The "issue" has also caused issues with MicroG for me, because MicroG may connect to Cloud Messaging without wireguard after booting, but then not receive any notifications after wireguard kicks in until MicroG hits the ping interval and resets itself.
[Android Software Development] borisSweden:
Is your kernel 4.19 and higher? The kernel module version is supposed to be more efficient but it requires root. I have 4.14.

But in the reboot issue, there should be alternative Wireguard apps that allows this without Tasker.
[Android Software Development] david003:
The kernel on my phone is also 4.14, and I have root access. Even without using kernel mode, I haven't noticed any battery or efficiency issue and I keep wireguard connected always.
[Android Software Development] petefoth:
Voice input: someone in the /e/OS forums posted a link to https://voiceinput.futo.org/. IT claims to be

I've installed it on a couple of devices (Sony XZ1 Compact, running IodéOS, and Sony Z Tablet running los4microG) and it seems to work well
[Android Software Development] petefoth:
November build run...

.... is in progress. You can monitor the progress in the Matrix room

I have also created a issue in our issue tracker for logging any failed builds that you spot before I do :)

If there are no problems, I expect 20.0 builds to complete around Tuesday 14th, 19.1 builds by Thirsday 16th, and 18.1 builds by Sunday 19th. But no promises ;)
[Android Software Development] borisSweden:
My question is, if I flash a custom kernel for LOS-microG, would a custom kernel force me to take more steps to update with A/B and magisk enabled?

Also I found this tutorial specifically for LOS for users to compile the same kernel only for Wireguard:

How to compile the WireGuard kernel module for LineageOS - dzx.fr

Guide to download the WireGuard kernel module, patch the LineageOS kernel, make the boot image, and flash it on your device.

dzx.fr

Its still to complicated for me.
[Android Software Development] kurtn:
That's not microG related. Whatever works for your phone and your custom kernel and official lineageOS, will work for lineage.microG.org also.
[Android Software Development] borisSweden:
Thanks for the clarification
[Android Software Development] unclouded:
Hi, I installed LineageOS for microG yesterday and it worked beautifully. I installed the Aurora store and then a couple of apps: Signal and Plugshare and a few others from F-Droid. This morning the phone said "1 update available: Google Play Services". Is this normal? I had hoped (perhaps wishfully) that Google Play Services would not be on the phone. Obviously I didn't sideload any gapps during installation of the ROM yesterday.
[Android Software Development] kurtn:
You did nothing wrong. You have microG. That pretends to be play services. And aurora store believes that, but will not be able to update it with the Google app.
[Android Software Development] petefoth:
Google Play Services is not on your phone; microG is and microG pretends to be Google Play Services, sot hat apps which rely on Google Play Services will work.

The message is from Aurora Store. which sees what it believes is Google Play Services, but is actually microG. When you next see the message, you can add 'Google Play Services` to Aurora Store's 'blacklist', and you wont be offered any more updates for it.
[Android Software Development] unclouded:
Thanks heaps for the explanation and the fix! That sets my mind at ease. It took me a while to figure out, so if anyone with the same problem is reading: You have to long-press on the "Play Services" pending update to get the option to blacklist. I couldn't find it in Blacklist manager because it's called "microG Services Core" there. Cheers!
[Android Software Development] kurtn:
19.1 is obsolete

https://review.lineageos.org/c/LineageOS/hudson/+/373555/2/lineage-build-targets
[Android Software Development] petefoth:
It is now. It wasnt when the build runs started :)

Next month should see no 19.1 builds
[Android Software Development] MikeViller:
install for Sony tablet z with microG and use Aurora to install Google Store apps. But what about apps that you pay for in the Google Store do I need to buy them again?
[Android Software Development] kurtn:
You need original Google play store for paid apps, usually. Maybe minmicrog play addon works for you?
[Android Software Development] petefoth:
Does Fake Store not handle paid apps?
[Android Software Development] kurtn:
License check and In app purchase is in preparation

Move Vending app to GmsCore repository, add Huawei flavor for fake-si… · microg/GmsCore@f5aadc3

…gnature Moving the vending app here is also in preparation for support for various features that have to be provided in the com.android.vending package like IAP, Play Integrity, Split Install, ...

github.com

Is FakeStore as separate app no longer required? · Issue #2047 · microg/GmsCore

Hi . Since recently FakeStore merged into GmsCore repo , FakeStore as a separate application no longer required?

github.com
[Android Software Development] petefoth:
Thanks. I don't use any paid apps or unpaid ones that require a Google account, so I don't have much of a clue aboutthat side of how MicroG works
[Android Software Development] pumana:
Where is the november build for apollon? The file is missing on the server...
[Android Software Development] petefoth:
It isn't missing - it's in the usual place

https://download.lineage.microg.org/apollon/lineage-20.0-20231001-microG-apollon.zip
[Android Software Development] pumana:
This is the october build and not the november build, there are some files dated 20231101 but the actual image file is not on the server.
[Android Software Development] petefoth:
Looks like there was a failure copying the zip file to the download server -it;s there now https://download.lineage.microg.org/apollon/lineage-20.0-20231101-microG-apollon.zip
[Android Software Development] petefoth:
Keep only the two most recent builds rather than three.

We are currently using 99% of the available disk space on the download server (554GB used, 6.2GB free, out of 590GB). This caused a couple of problems with the latest build run, where copying of some files from build server to download server failed due to lack of disk space (see #505 and had to be completed manually after some unneeded files were removed.

The lack of space is party due to the fact we now publish loads of .img files in addition to the main ROM zip files and recovery images - see #405 & #467

Zipping up these images (see #483) caused the 'Update recovery` function of the Updater to fail (see #487), so was reverted - See PR #490

Adding more disk space is problematic for a number of reasons. So I plan to reduce the number of builds we make avaiable from three for each device to two (by setting `DELETE_OLD_ZIPS=2` in the `docker run` command). Unless there are any strong objections, I will do this for the next build run which starts early Friday morning. If anyone has any concerns about this, please let me know before then.
[Android Software Development] petefoth:
December build run...

.... is in progress. You can monitor the progress in the Matrix room

I have also created a issue in our issue tracker for logging any failed builds that you spot before I do :)

There will be no 19.1 builds - all devices that were on 19.1 have been moved to 20.1. Because of that change I can't give an estimated date for when each branch build will complete.
[Android Software Development] petefoth:
I am proposing to make the `cicd` Docker image more flexible, by making the operations performed by the image (`repo init` & `sync`, applying patches, calling `breakfast` & `mka`) 'switchable' using environment variables. Details of the proposal can be found in this issue. Any comments or reactions to the proposal would be very welcome, either here, or as comments to the issue. Thanks
[Android Software Development] nicelydone:
I've just set up this os for the first time, and is working well. Thank you to the developers and all those who've contributed to the knowledge base.

Can anyone tell me what function the Google Assistant (in system apps) serves?

Other apps or services that rely on it?

What information, if any, is being sent to their servers?

Any privacy and/or security concerns?
[Android Software Development] petefoth:
It should not be there - it is not part of the LineageOS for microG ROM. I suspect it is there because you flashed it over the stock Google ROM without wiping or formatting data partition.

Which device are you using, and which version of the LineageOS for microG ROM did you install?

What instructions did you follow to install the ROM? Did you perform all the steps in those instructions?
[Android Software Development] kurtn:
Google assistant is in lineageOS even without GApps. It's not the full app, just a stub to help real Google assistant installation. No privacy concern. For increased security have a look at divestOS
[Android Software Development] petefoth:
Is it also there in LineageOS for microG? In my current installation, there's no sign of it in Settings | Apps | Show a;; | show system
[Android Software Development] kurtn:
It's there in my xz2c but not in bacon
[Android Software Development] nicelydone:
I'm running the most recent release of lineage for microg. It was clean installed over the most recent lineage, which also had google assistant loaded as a system app.

If it's inclusion is 'just a stub to help real Google assistant installation', can it be safely disabled through adb? Are there other apps included in the rom that may be dependent on it?

I have no intention of loading any google products now or in the future.
[Android Software Development] petefoth:
If you wiped or formatted data partition (i.e. factory reset) before installing, then I don;t know what is going on. As I say, it is not present in my devices, but I have never had a 'normal' LineageOS build installed.

Sorry - I have no idea

Clearly not, as it is not present on my devices, and all the built-in apps work with no problems.

You didn't say which device you are running. Helpful in case there are other users of that device who can check whether it is present in their devices
[Android Software Development] kurtn:
What happened zo chef?
[Android Software Development] petefoth:
It is no longer in the list of build targets https://raw.githubusercontent.com/LineageOS/hudson/main/lineage-build-targets
[Android Software Development] petefoth:
Removed in this commit because

> We don't have an active maintainer for it and the device

apparently keeps rebooting upon WiFi connect.
[Android Software Development] kurtn:
I see some development for chef lineageOS 21
[Android Software Development] petefoth:
If it makes it inot the official target list for LOS 21 then we should pick it up again when we start making LOS 21 builds. Tat's the next issue I am going to need to deal with :)
[Android Software Development] petefoth:
The 20.0 builds started failing while building `redfin`. Not sure why. I will rerun builds for the affected devices once the 18.1 devices have been built.

The affected devices are redfin renoir rhode river rosemary rs988 sagit sailfish sake sargo starlte star2lte sunfish surya sweet taimen tangorpro tissot TP1803 troika ursa us996 us996d us997 vayu vela violet voyager vs995 wade walleye X00TD xmsirius xpeng xz2c Z01R z2_plus zippo
[Android Software Development] 2faraway2:
Do you consider to upgrade to the 'new' microG -release 0.3.0 in one of the next builds ?
[Android Software Development] kurtn:
I think it's good to stay on 0.27. There are people using backends like Apple nlp. Those can not be used on 0.3.0 And

it's easy to update to microG 0.3.0
[Android Software Development] petefoth:
We aim to use the most recent stable version: currently for microG Services that is 2.27 (see the microG Downloads page)
[Android Software Development] 2faraway2:
Ahhh ok, never recognized that the releases > 0.2.7 aren't stable .. (y)

Nevertheless, the advantage of the newer releases is that the location providers aren't needed any more .. but let's see which version will become stable ;)
[Android Software Development] Ridge:
Hi, does anyone know how to download and build only the kernel image for this? I want to add KernelSU to my beryllium (Poco F1), but can't figure out how to do that for "LineageOS for MicroG".

I managed to download LineageOS sources, add KernelSU and build only the kernel for that ("make bootimage" in kernel directory), but that's for regular LineageOS.

Regular LineageOS kernel doesn't work on LineageOS for MicroG..

I'm very stumped, some pointers would be very appreciated =)
[Android Software Development] kurtn:
The microG fork doesn't change lineageOS' kernel source. Maybe a incompatibility due to different patch levels?