yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Aqq123:
LineageOS for MicroG updates depend on the official LineageOS builds continuing for the device, and the official LOS policy is to only support two versions at any given time: the latest and the one before that. So when LOS 19 builds started in mid-February, LOS 17 was dropped.

It's not really a great arrangement since there are no security updates as you noted but it's up to LOS project maintainers to decide this, and they say they're strained for resources. At least the LOS for MicroG repository keeps the latest builds for discontinued devices available for download, while they're simply deleted from the official LOS as if they never existed. Example: https://download.lineageos.org/davinci doesn't even tell you there used to be builds at any given point, the page for a nonexistent device looks just the same: https://download.lineageos.org/blahblahblah
[Android Software Development] kurtn:
No. Lineage.microg.org does not depend on official lineageOS building ROM's. Lineage.microg.org can build 17.1 - and there are security patches in lineageOS source code for 17.1

The only problem: It's too much work for a one-man-show to keep building.
[Android Software Development] Aqq123:
As far as I know, LineageOS for MicroG only adds the signature spoofing patch: other than that, no changes are made to the source coming from the official LineageOS for the device. And no builds are made for devices discontinued by the official LOS. I've never claimed it was theoretically impossible, just that it doesn't happen in practice (because it's out of scope for the project as I understand it). Now I might be wrong but if that's the case, can you point to a counterexample of a device that got a LineageOS for MicroG build with updated security patch after it was already discontinued by the official LineageOS? If not, then I believe what we're saying effectively amounts to the same, just using different words.
[Android Software Development] kurtn:
bullhead
[Android Software Development] Aqq123:
Interesting, and good to know. That's still 15.1 by the way.

All the more respect to the LineageOS for MicroG team then! They're doing even more than I thought.
[Android Software Development] flymetothemoon:
Is there a reason lingeage.microg was not updated for Assu Zenfone 8 (sake) since August 26?

The other phones seem to have gotten updates in the meantime.
[Android Software Development] heinhuiz:
19.1 builds often seem to stop after dipper and after some days of silence older builds are resumed.
[Android Software Development] flymetothemoon:
Thank you. So it's a known problem? Then I just wait.
[Android Software Development] b8842dc0:
I don't know how the build server works, but it would appear that there is an issue with the build server and version 19.1. It appears that perhaps a build for one device (discovery, perhaps?) is failing and causing all builds after that to not get built? Perhaps the builds occur in alphabetical order? Some devices, like blueline are getting built every few weeks. However, many other devices, like fajita and flame, haven't been built in over a month.
[Android Software Development] celrau:
Not sure this is the right place to ask but Lineageos official for miatoll has been updated to 19.1, can Lineage4Microg update as well, please? Not that I'm unhappy with 18.1..
[Android Software Development] heinhuiz:
It seems the problem has been solved, last build was for polarise just today. Your device, sake, should follow soon.
[Android Software Development] flymetothemoon:
Thank you. I am also refreshing the page from time to time to see the progress 😁

/

Finally it is there. Upgrade worked perfectly.
[Android Software Development] petefoth:
Is it yet possible to build LOS 20.0 with Docker? I see conflicting messages in this issue: https://github.com/lineageos4microg/docker-lineage-cicd/issues/335

If it is possible, do I need some extra setting in the call to `docker run`? The following call

docker run \
-v "/srv/src:/srv/src" \
-v "/srv/zips:/srv/zips" \
-v "/srv/logs:/srv/logs" \
-v "/srv/cache:/srv/ccache" \
-v "/srv/keys:/srv/keys" \
-v "/srv/local_manifests:/srv/local_manifests" \
-e "BRANCH_NAME=lineage-20.0" \
-e "WITH_GMS=true" \
-e "SIGN_BUILDS=true" \
-e "DEVICE_LIST=lilac" \
-e "REPO=https://gitlab.e.foundation/e/os/releases.git" \
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community

fails with the follwing errors:

/root/build.sh: line 42: DEVICE_LIST_LINEAGE-20.0: invalid variable name
/root/build.sh: line 81: DEVICE_LIST_LINEAGE-20.0: invalid variable name

Thanks for any help
[Android Software Development] borisSweden:
How do you upgrade LOSmicroG 18.1 to 19.1 for hotdogb? Basically major upgrade. Not gonna ask LOS Devs as its off topic.
[Android Software Development] heinhuiz:
It is more off-topic here, because it's exactly the same way as you would upgrade normal LOS. You can find the instructions in the LOS wiki.
[Android Software Development] borisSweden:
But do I keep Magisk, Vanced or whatever hardening I did to LOS? Of course I have zero Gappps but will 19.1 override for example Bromite Webview?
[Android Software Development] joe890:
Hello forum

for testing purposes I re-installed (with twrp-3.2.2-0-surnia.img)

- lineage-14.1-20180811-microG-surnia.zip

- addonsu-14.1-arm-signed.zip

to an old restired MotoE 1525 Surnia (with twrp-3.2.2-0-surnia.img))

Question:

Should addonsu-14.1-arm-signed.zip be listed under the microG settings?

Thank's a lot for any feedback!

Joe
[Android Software Development] kurtn:
Addonsu enables the root settings in developer options. MicroG is completely independent of su
[Android Software Development] joe890:
Thank's Kurtn for that interesting feedback! Nevertheless I don't know if my mobile is really rooted, because:

The following apps which do require root do work:

- AFWall+

- SnoopSnitch

But the following apps do complain:

[Error-message in RootVerifier(com.abcdjdj.rootverifier]:

- Root Permisions not granted or superuser App missing

- Busybox not installed or not symlinked

- Superuser AP: 16cm-su (but I did flash addonsu-14.1-arm-signed.zip !!!!!)

- device MotoE XT1524 (Surnia)

[Error-message in XPosed]:

[but I am not sure if this message has something to do with root]

- Xposed: Could not load available ZIP files. Pull down to try again

Any additional help is apprecaited very much!

Joe

PS:

-> Developer Options -> Root Access: Apps and ADB :)
[Android Software Development] kurtn:
Who needs root verifier?

Current xposed versions need magisk. For what do you need xposed?

https://xdaforums.com/showthread.php?t=3034811
[Android Software Development] joe890:
To my knowledge my LOS fir microG does not support Magisk and if possible I would like to "rebuild" my mobile with the same "components" as in 2018.

->Who needs root verifier?

Just to double check if root does really work
[Android Software Development] kurtn:
You have a built in root verification. In developer options enable terminal. In terminal app enter "su". If prompt goes " #" you have root.

And I'm sure magisk works.

For what do you need xposed?
[Android Software Development] joe890:
Wow thank's kurtn for the root verification recommendation. It does work :)

2.

-XprivacyLua

-XPrivacyLuaPro

3.

You're right it would be a good idea to switch to Magisk.....
[Android Software Development] :
Hello, new to this forum, hope I type the question at the right place... I have a OnePlus 9 Pro running LineageOS for microG 19.1 (lemonadep). I try to use System profiles in order to keep my device unlocked while connected to certain wifi:s and bluetooth devices. It workes sometimes but sometimes I get message "Profiles trust provider keeps crashing" or something similar and the Triggers in the system profile stops working. May this relate to microG-settings, do I need the right settings or is this at all related to microG? Where can I in case it is needed read source-code for Profiles trust provider? Can I enable logging for it somehow?
[Android Software Development] kurtn:
For me it seems not related to microG. If you really want help fixing the bug, install official lineageOS, reproduce the bug, take a logcat and file a bug report with that.
[Android Software Development] joe890:
Hello forum

is there a way to check if lineage-14.1-20180811-microG-surnia.zip (once it is installed/flashed) does contain Storage Access Framework?

The dev of XPrivacyLua told me that SAF is a requirement...

Thank's in advance for any feedback!

Joe
[Android Software Development] KemikalElite:
Sorry if this has already been asked but if the official LineageOS version is upgraded (18 to 19.1) will the microG version automatically start releasing the upgraded version as well or is that something that has to be switched manually by the microG maintainers when they determine its ready?
[Android Software Development] :
Sorry, late answer, but is it possible to install an official lineageOS on one slot while keeping my existing LineageOS for microG on the other so that I can go back to that, totally intact after reproducing the problem on the official LineageOS slot?
[Android Software Development] kurtn:
Hui. That's a really General question about dual boot i n a/b devices. Please report here, when you have the answer.
[Android Software Development] lobotron:
perhaps a problem with my setup, but my pioneer doesn't come up after ota upgrading to lineage-19.1-20221118-microG-pioneer.zip, so probably be wiser than me and backup in advance. ADB ist possible but /sdcard doesn't mount
[Android Software Development] infinity0x:
Running LineageOS 19.1 with MicroG for OnePlus 8T (KB2003).

Magisk works but fails to persist after OTA because it does not install correctly to `/system/addons.d`. Likewise, certain other addons fail because `/system` and `/vendor` are too full to write to, even if you mount it writable.

This is because of an inappropriate usage of `WITH_GMS` and I've filed an issue here, however it seems the actual builds on the website are run by a different person or party. How can I contact them to bring this issue to their attention?
[Android Software Development] kurtn:
You posted in the right repository.

If you can't wait, you can try official lineageOS with magisk, LSPosed, whew-inc fakegapps, nift4 installer module
[Android Software Development] 30jp:
Hello,

I have a Sony xz2c with a clean install of lineage-19.1-20221024-microG-xz2c.zip and it worked fine.

Today came an OTA of lineage-19.1-20221120-microG-xz2c.zip.

I installed that via OTA and then got into a bootloop.

Then via fastboot installed lineage-19.1-20221115-microG-xz2c-recovery.img and via adb lineage-19.1-20221120-microG-xz2c.zip again, but again a bootloop.

Only Lineageos without MicroG (lineage-19.1-20221119-recovery-xz2c.img with lineage-19.1-20221119-nightly-xz2c-signed.zip via fastboot and adb) does boot properly.

The e rom with recovery and and zip of 4-11-2022 also works fine.

Is there sometimes an error in the recovery of lineage-19.1-20221115-microG-xz2c-recovery.img?

Greetings jp30
[Android Software Development] piwei:
I'm having similar issues with booting after update on an Xperia 10 (kirin) with microG.

Thanks to your post I checked, and yes, it also works with the official (microG free) LOS.
[Android Software Development] kurtn:
Or @piwei could you file a bug report, please?

Issues · lineageos4microg/docker-lineage-cicd

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

github.com
[Android Software Development] ale5000:
If it is what I think, it isn't the fault of microG.

The latest version of microG add a new privileged permission android.permission.MANAGE_USB, so if the ROM doesn't add it to the appropriate XML file it will bootloop.

There is already a pull request by fwg-cag: https://github.com/lineageos4microg/android_vendor_partner_gms/pull/15
[Android Software Development] kurtn:
So it's an issue for all Android versions?
[Android Software Development] manµ:
I expirience the same. Is there a workaround for now, except dumping microG?
[Android Software Development] kurtn:
If it's really the permission thingy? You can try to flash that https://github.com/FriendlyNeighbor...MinMicroG-Minimal-UPDATELY-20221030172631.zip
[Android Software Development] ale5000:
If I'm not wrong, declaring priv-app permissions is obligatory (otherwise device doesn't boot) in Android 9+
[Android Software Development] petefoth:
I am seeing this behaviour in my unofficial LOS-20 / Android 13 builds

Flashing that zip file immediately after flashing my ROMs allowed those ROMs to run wothout bootlooping. Thanks very much :)
[Android Software Development] piwei:
Yeah, sorry. Since https://lineage.microg.org/ has details about when to report bugs but not actually where to report them, I posted that at https://github.com/microg/GmsCore/issues/1831 which seemed related. Should I re-report it in that other repo?
[Android Software Development] kurtn:
Yeah. Bootloop of an arbitrary ROM is no issue for microG. In a lineage4microg bug report you can link the merge request posted above
[Android Software Development] piwei:
OK, hope that https://github.com/lineageos4microg/docker-lineage-cicd/issues/360 is now usable and visible to the right folks.

The solution suggested by @ale5000 helped. I had to do this:

- Boot into recovery

- Select "Mount/unmount system"

- Activate ADB

- Run mount -o remount,rw /mnt/system inside an adb shell

- adb pull /mnt/system/system/product/etc/permissions/privapp-permissions-com.google.android.gms.xml

- edit that copied privapp-permissions-com.google.android.gms.xml on the laptop

- adb push privapp-permissions-com.google.android.gms.xml /mnt/system/system/product/etc/permissions/

- Run mount -o remount,ro /mnt/system in adb shell (probably not necessary?!)

- Reboot.

Phone boots again.
[Android Software Development] manµ:
I want to try your fix at https://github.com/microg/GmsCore/issues/1831:

However, I am not able to pull /product/etc/default-permissions/privapp-permissions-com.google.android.gms.xml via adb... do I need to mount something else than /system? How do I do it? Thanks for your help!
[Android Software Development] lobotron:
U made my day
[Android Software Development] wowi63:
My Poco F1 (Beryllium) got the last OTA Update at 17.10.2022 - should get updates around every 14 days. Is there something going wrong?

I hope this is the right thread ...
[Android Software Development] lobotron:
@manµ​

Are you sure system / is mounted rw?
[Android Software Development] manµ:
Thanks, I got it :). I just haven't seen the answer of piwei, wich was posted at the same time I was typing.
[Android Software Development] Waldold:
It was really surprise that updates of LOS4microG 15.1 builds has been suddenly stopped more than half a year ago, but you probably know a huge critical security vulnerability of bypassing the lockscreen was found, so maybe you can do a one more "final fixed build" (at least, for nowadays) for Nexus 5X and other devices, which are using the same outdated 15.1 builds?
[Android Software Development] kurtn:
I don't see that bug fixed in 15.1

https://review.lineageos.org/q/dismiss%20keyguard
[Android Software Development] piwei:
Hmm, am I the only one for whom the microG-based "Google device registration" does not work any more after fixing the boot loop? It says "On" but "Status: Not registered" and "Cloud Messaging: 0 registered Apps". Trying to force Threema to re-register gives me an error message...

Even though "Self-Check" in microG's settings has ticks everywhere. The version displayed is 0.2.25.223616.
[Android Software Development] filtrator:
I am also suffering from a bootloop after updating via OTA from 20221024 to 20221120 (both microG). I already edited privapp-permissions-com.google.android.gms.xml after experiencing several bootloops but unfortunately my Sony XZ2c keeps bootlooping.

Trying to sideload the zip-file kurtn suggested in #2.507 failed with a '!!! FATAL ERROR: Could not find a ROM!' message.

Any suggestions what I might try next?

I wouldn't want to perform a factory-reset and full reinstall (again) :rolleyes: so any help is highly appreciated.
[Android Software Development] petefoth:
My Lineage for microg 20.0 builds for lilac are building now :). The "vanilla" unofficial build runs fine. The Custom build, modified with extra apps is hanging at theLOS boot animation. I've got logcat.txt, dmesg.log and recovery.log files. Any clues to what I should be looking for in these files to find what is causing the problem?
[Android Software Development] kurtn:
Have you picked the pull request for the permission fix?
[Android Software Development] petefoth:
Yes.
[Android Software Development] lobotron:
I had the same FATAL ERROR but could flash it with a twrp booted by a fastboot boot
[Android Software Development] filtrator:
Thank you for the information.

As far as I could find out TWRP for XZ2c is only available up to android 11. Does this version by martinx3 also work with android 12 (LOS 19.1)?

Well, I'll give it a try and report back...
[Android Software Development] filtrator:
Just checked: Latest TWRP is not working for android 12. Fastboot flashing vba.img and fastboot twrp.img results in no error messages but the phone is not restarting to TWRP but rebooting two times. The second time it boots into bootloop again. TWRP is showing up at no time.

@lobotron : what device and LOS-version are you on?
[Android Software Development] stephan_h:
I'm trying to install LOS + microG on an FP3+, but fail to boot into recovery.

In August I had successfully performed the full procedure on one device, so I offered to do the same for someone else.

Then in September when I tried to setup a second device using the same steps, flashing the recovery image (fastboot flash boot <img>) seems to have corrupted the partition table, eventually leading to a hard-brick.

Today, on a fresh device I tried to be more careful by saying fastboot boot <img>, i.e., without "flash", but that command only causes a normal reboot, no recovery menu in sight.

FYI, today I was following this guide: https://forum.fairphone.com/t/fp3-fp3-complete-guide-for-installing-lineageos/69239

The previous two attempts (1 successful, 1 hard-brick) both followed https://wiki.lineageos.org/devices/FP3/install

Questions:

Has anyone recently installed LOS+microG on a Fairphone 3(+)?

Which command should be used to boot into recovery?

Can I freely choose another recovery image (e.g., from upstream LOS), and still install LOS+microG? What about version dependencies between recovery image and target OS image?

How do I verify correctness of the recovery image? On https://download.lineage.microg.org/FP3/ there's no sha256sum of the recovery image...
[Android Software Development] filtrator:
Never mind. I managed to flash the file using LOS-recovery. You just have to mount /system to succeed. Unfortunatly the phone still keeps bootlooping.

Any more ideas, anyone?
[Android Software Development] kurtn:
Clean flash old version
[Android Software Development] Einhornyordle:
Hi, I currently have a OnePlus 8 Pro running with LineageOS for microG 18.1 and tried to upgrade to 19.1 but after I flash the new image via fastboot it refuses to boot. I was able to again boot into recovery and flash back to 18.1 just fine. Any idea what is wrong/how I can successfully upgrade?
[Android Software Development] kurtn:
Looks like you have to upgrade firmware as well

Info about instantnoodlep | LineageOS Wiki

wiki.lineageos.org

And install 20221011 - maybe 0221020 is broken
[Android Software Development] stephan_h:
Two things I can answer now:

On the FP3+, fastboot boot <img> consistently triggers a normal boot, instead of recovery. This is true for LOS+microG and also plain LOS recovery images.

After detecting the active slot to be b, fastboot flash boot_b lineage-19.1-20221201-microG-FP3-recovery.img worked for me.
[Android Software Development] memelover:
It looks like the builds for sake (Asus Zenfone 8) haven't been updated in a month and a half or so. There don't appear to be any issues on the regular LOS side of things (such as the device being EOLed), and the latest build they have is from 2022-12-02. LOS for microg's latest build is from 2022-10-23.

Is there something wrong with the build process, or has this device been forgotton / dropped by LOS for microg?
[Android Software Development] kurtn:
They really had problems in building. And they build alphabetically. Current round looks good so far. Wait a few days.
[Android Software Development] memelover:
Awesome, thanks for the update!
[Android Software Development] raix1415:
Hello All, I have installed LOS for microG 19.1 on Asus Zenfone 5z. Almost all is running ok so far but I have an issue with VPN. When I enable “Always-on VPN” and “Block connections without VPN” options in settings, it blocks also connection for the actual VPN app with these settings turned on. As a result I cannot connect to VPN with these enabled. I tried this with 2 different VPN apps and the behaviour was the same. When I turn them off, connection works perfectly fine but I want to avoid leaks outside of VPN.

I then created a Work profile with Insular, installed the same VPN app and turned the above settings on. In this case it worked as intended – all is blocked apart from the VPN app that can still connect regardless of the status in Personal profile.

I have also LOS for microG 18.1 installed on LG G2 and there seems to be no connection/block issue with VPN.

Has anyone else experienced this issue with VPN on LOS 19.1 or could try it? What is causing this and is there any possible solution, pls? Any info would be appreciated. Thank you.
[Android Software Development] heinhuiz:
I have the same behaviour on my lmi. I didn't even notice before that the VPN would work as intended in the work profile, but indeed it does. To block traffic without the VPN connected I use rooted AFWall.

Should this be considered and reported as a bug? I'm not sure if it is a problem caused by microG.
[Android Software Development] kurtn:
@raix1415 this is no microG issue. Install official lineageOS, reproduce the bug and report it to lineageOS
[Android Software Development] humpty321:
This stems from a phone running lineage-19.1-20221202-microG-bramble.zip

Are there any plans to support german Cell Broadcast?
[Android Software Development] kurtn:
German cell broadcast is not fully implemented by network providers. There is a new approach to additionally send 3-digit-CB. The 4-digit-CB can be only received by newer devices.

MicroG or GApps are not involved in cell broadcast processing.
[Android Software Development] Bracher:
I have installed LOSmicroG and Magisk on maý Fairphone 3+. But with the 19.1 version I had a problem to boot in LOS Recovery. So I did it via PC and twrp (first going in fastboot modus and than boot via fastboot in twrp 'fastboot boot twrp.recovery', after wipe and flashing LOS I did the same procedure for flashing Magisk. Worked well
[Android Software Development] raix1415:
I have searched through open LineageOS issues on gitlab and found this issue to be already open under #5231- https://gitlab.com/LineageOS/issues/android/-/issues/5231

It seems to be general and not device specific so far.
[Android Software Development] kurtn:
Did you know you don't need an app for VPN? You can add one in settings / network.
[Android Software Development] heinhuiz:
If only I new what to select under Type for OpenVPN (piVPN)...
[Android Software Development] raix1415:
yes, I knew that but it does not suit my needs :-)