yashsingh1/xdaforums huggingface dataset:
[Android Software Development] humpty321:
I uninstalled Magisk and flashed the original unpatched boot.img (to set the “Patch vbmeta in boot image” option had been a mistake anyway). But the OTA would not succeed after that either. So Magisk obviously was not the culprit. Therefore I started from scratch with the latest factory image. There is no new OTA yet, so I'll have to wait and see if the next one will work.
[Android Software Development] barturblits:
Since a week or so the build system seemed to have stopped. Is the build system under maintenance? And is there any information on the progress?
[Android Software Development] heinhuiz:
I wanted to ask exactly that. All 18.1 builds have finished, and I expected to see 19.1 builds starting a week ago. But indeed nothing happened after zl1.
[Android Software Development] heinhuiz:
It seems like another round of 18.1 builds has started today :confused: totally skipping all 19.1 devices.
[Android Software Development] 30jp:
Hello,

I have a Sony xz2c with LineageOs version 19-20220627-microG-xz2c and since its installation I keep getting a message that "Intent Filter Verification" has stopped. In Netguard I can see that when I restart the Xz2c, "Intent Filter Verification" is looking to connect to over 100 Google and Google maps locations around the world. Netguard blocks them all nicely, but "Intent Filter Verification" keeps after that, saying it has stopped. I did not have this in the last version of LineageOs 18 with MicroG.

Am I the only one with this message or does this happen to others as well?

For the rest I am completely satisfied with 19.1, but I was also satisfied with 18.1.

Regards 30jp
[Android Software Development] kurtn:
That's a know lineageOS bug. Should be fixed soon. You can disable that app.
[Android Software Development] 30jp:
Hi Kurtn,

Thanks for your quick response.
[Android Software Development] heinhuiz:
19.1 builds have started again (y)
[Android Software Development] minax007:
@Simon94

Since one month there aren't any updates for "dipper" and "surya".

The build script seems not to include those anymore.
[Android Software Development] barturblits:
FYI. Latest update for alioth, poco f3, from july 21th gave me a bootloop. First failed LOS update since I guess 5 years or so. Checked logcat but could not find the problem. I made a backup with the latest TWRP from nebrassy, which supports A12 encryption but restoring that also failed. Had to do a fresh install which did work with that latest version. Happy to have neo backup, saved a lot of work.
[Android Software Development] barturblits:
Also a small bug in the last couple of versions. Running on 60 Hz is basically not usable. Extreme stutter and lag. In both browser as the entire UI and apps. 120 Hz is smooth and normal.
[Android Software Development] kurtn:
That's not a microG issue. Maybe ask your device community.
[Android Software Development] barturblits:
Correct, probably a LOS issue.
[Android Software Development] giantflash:
Enchilada hasn't been build for over a month as well.
[Android Software Development] hypern0va:
Seems like the new round of builds got interrupted after blueline
[Android Software Development] notexcited:
Yep, no updates for lemonadep since June 11th. Almost two months now.
[Android Software Development] heinhuiz:
Builds have started again today ... for 18.1 devices.
[Android Software Development] Luckz27:
Clearly there is a problem with the 19.1 ROMs building...

Hope bananer can fix it soon!
[Android Software Development] Steve Graham:
I followed the LineageOS instructions and successfully went from 18.x to 19.x on my Pixel 5a (barbet). However, subsequant OTA updates have not installed. I can download them, but the install always fails immediately with the notification "Install error".

Now, as far as useful error messages go, that isn't one.

So I'm looking for tips about what the cause may be. Or is there another way to install the updates, via ADB, for example?
[Android Software Development] kurtn:
Update LineageOS on barbet | LineageOS Wiki

wiki.lineageos.org
[Android Software Development] humpty321:
Just as a followup, this time the OTA update worked (lineage-19.1-20220804-microG-bramble). But after that root did only work with interruptions. This felt like a loose connection. Finally it stopped working altogether. So I had to install Magisk afresh.

Should I maybe disable "Update recovery" in the Updater options in order to avoid damaging root on a monthly basis, with every new update?
[Android Software Development] kurtn:
Bramble is an a/b device. After installing the update in the other partition, you can tell magisk to install in that partition. Then reboot.
[Android Software Development] heinhuiz:
Now that a new build has been released, the update check is working again. Maybe something was wrong on the server after all.

Edit: I have to be more precise. I still get the message stating that the update check failed, but the latest updates are actually listed.
[Android Software Development] humpty321:
Thank you for drawing my attention to this option! I've found now these OTA Upgrade Guides (https://topjohnwu.github.io/Magisk/ota.html). The steps necessary on A/B devices seem clear to me.

But there are also 2 Non A/B devices running LineageOS in the family. The guide says "you must have your stock recovery installed on your device". Is in this case the LineageOS recovery "stock" or would that be the one from Google?
[Android Software Development] heinhuiz:
These are basically non LineageOS for microG questions that are off-topic here, and that you will be better answered in your devices' LOS threads. But for me TWRP has always worked on any supported device, as did LOS recovery on the few I tried it with.
[Android Software Development] kurtn:
You should add: you use custom recovery method for installing magisk. Boot image method doesn't survive lineageOS updates.
[Android Software Development] budmerman:
Im on ocean. when i upgraded to lineagemicrog 19 my external DAC's would no longer work. anyone have same problem? anyone still able to connect to USB audio? any solutions?

thanks.
[Android Software Development] kurtn:
Doesn't sound like a microG issue. But highly device dependent. You can try to reproduce the bug with original lineageOS and file a bug report.
[Android Software Development] Bracher:
Hello, in the past I've used LineageOS for microG and additional - to get for example the patched Google Store - MinMicroG Installer from FriendlyNeighbourhoodShane. With MicroG version 19 this is no longer possible - MicroG is already fully installed - unfortunately without the patched Store. On most issues Aurora works fine and I hoped I could work without Google. Unfortunately it does not work for DWD Warnwetter. The app has GMS registration, but it does not recognise my in-app-purchase via Google. Is there any solution to get an patched Google Store?
[Android Software Development] kurtn:
We don't talk about piracy here. But is it really piracy, if you make warnwetter useable for you alone without play store? You already played for it. - and dwd doesn't want the meney. They got forced by court to take it.
[Android Software Development] Bracher:
Yes for sure I paid and I would have no problem to pay ones more but it's not possible, I wrote as well to Warnwetter to ask them about this problem they have not reacted so far.
[Android Software Development] heinhuiz:
With Aurora you can log in with your own Google account. That should allow you to download purchased items.
[Android Software Development] Bracher:
The problem is I can download this app but despite his registration with GMS and beside the fact that I paid it and it worked till MicroG LOS 18.1 it now no longer accepts the payment or let me pay ones more - it seems a problem with in-app-purchases, but ok I have to find an alternative
[Android Software Development] Psk.It:
download mickgapps core

open It, in /appset/core there is the GooglePlaystore.zip

copy "___etc___permissions" to /system/etc/permissions and "___priv-app___Phonesky" to /system/priv-app/phonesky

if unable to keeps changes.persistent you can build a magisk module on the fly

on reboot, you will have a working PlayStore, and your purchaised apps will work
[Android Software Development] humpty321:
Thank you both for answering my question. The non A/B devices I mentioned are both cheeseburger. This phone has a ramdisk and no separate vbmeta partition. Therefore following the installation guide I have to patch boot.img.

While these devices still were on 18.1 I used TWRP. When I had patched boot.img for the first time in 18.1 I let TWRP make a backup of it, placed on the phone. For all the following updates I used OTA only to download them. To install them I manually rebooted to recovery, installed the update from /data/lineageos_updates/, made TWRP restore the backup of that first patched boot.img and then rebooted to system. Never had a problem with this procedure.

When I installed the upgrade to 19.1 I guessed OTAs might become even easier to handle for the users of those two phones, if I installed the stock (?) LineageOS recovery. And I had always felt unsure if the updates might bring along changes in boot.img. These would have been discarded by always restoring that very first patched one.

So my question is: How often does LineageOS for microG updates contain modified boot.imges, especially if a device like cheeseburger has ceased to receive updates from the manufacturer? If changes to boot.img are not to be expected I'd return to TWRP and that previous procedure for updates.
[Android Software Development] kurtn:
Keeping old boot.IMG is no good idea. The updates contain mainly security patches. Many of them are for the Linux kernel. The kernel is in boot image.

Rename magisk.apk to magisk.zip and flash it in recovery. If it doesn't work, use older magisk or lygisk.

Lygisk is a Magisk fork correcting addond's requirement of decrypted data in recovery.

GitHub - programminghoch10/Lygisk: Your Lie in Android

Your Lie in Android. Contribute to programminghoch10/Lygisk development by creating an account on GitHub.

github.com
[Android Software Development] kurtn:
We are talking about in app purchases. For that use case nanolx patched a play store. That is still part of many microG installers. But not shipped with nikgapps.

I prefer methods I can't talk about in XDA
[Android Software Development] Psk.It:
What I experienced (since I have been flashothic) is about PlayStore and A12

the patched PlayStore does not work proprtly

that's the reason i suggested to use a most recent version

(you can just try, or find a differenti way)
[Android Software Development] Steve Graham:
To answer my own question: yes, there is another way to install OTA updates.

The OTA zip can be installed from recovery. However, the LineageOS recovery on my phone did not offer the option to install an update from phone storage.

So it was necessary to copy the zip to my PC (Linux) and select "Apply update from ADB" on the phone's recovery menu.

The phone then tells you to use adb sideload on the PC:

$ adb sideload lineage-19.1-2022mmdd-microG-barbet.zip

There is a known issue that the % progress on the PC can appear to stall at 47%, but in fact it is continuing to download.
[Android Software Development] humpty321:
I will follow your suggestions. Do they work with TWRP as well as with LineageOS recovery? If yes, I'd seize the opportunity to return to TWRP.
[Android Software Development] Psk.It:
LOS19 Is based on android12

Twrp (the most) Is based on A11

you have to check twrp development for your device
[Android Software Development] 30jp:
Hello,

August 10 came a new update of LineageOs for microG 19.1 for my Sony XZ2 compact. OTA took 13 minutes and my phone works like a charm again.

"Intent Filter Verification" keeps giving a notification that it stops, but I turned that off again.

The only downside of 19.1 compared to 18.1 is the camera.

A different camera is used than in 18.1.

I find it less pleasant to work with, it has less settings and it saves the files in "Pictures" and not in "DCIM".

I don't know why a different camera was chosen, but I like the one in 18.1 better.

Greetings and thanks for the update,

30jp
[Android Software Development] kurtn:
Intent Filter Verification bug should be fixed with thiat:

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683

Camera: There was no-one to continue maintaining of old camera app. So it was replaced with something less in need of care.
[Android Software Development] 30jp:
Hi Kurtn,

To fix that error I would have to install Googlemaps.

I prefer not to have Google apps on my phone.

I had "Intent Filter Verification" turned off completely and haven't noticed that giving a problem in the last month and a half. So I'll leave it that way.

As a camera I now use Open Camera, which is a bit better anyway.

Thanks for your response,

30jp
[Android Software Development] kurtn:
Haha, Google maps installation is not the bug fix. It's a recommended test by a Google employee.
[Android Software Development] humpty321:
As it is designed to phone home, there is another good reason to disable it.
[Android Software Development] FoxOfArtconomy:
Hello!

I noticed that the lemonadep builds are incomplete-- https://download.lineage.microg.org/lemonadep/

The files have recoveries and images, but they're all different dates. I've not been able to upgrade to 19.1 because of this, and I'm sure there are others who are affected. Could you please build the most recent version with your signature and upload it, Linage4MicroG team?

Thank you!
[Android Software Development] Psk.It:
you can:

- follow lineage install instructions and get dtbo, vendor_boot and boot from the linked repo (here), the closed date before the rom date (for lineage-19.1-20220806-xxx, keep files from 20220802 directory)

or

- use dumper (this or that) to exteaxt them from the rom

once you have those 3 files:

- flash dtbo

- flash vendor_boot

- flash boot

reboot recovery

- sideload rom.zip
[Android Software Development] kurtn:
There is no need to have a recovery the same date as the ROM.

Upgrade LineageOS on lemonadep | LineageOS Wiki

wiki.lineageos.org
[Android Software Development] FoxOfArtconomy:
Thank you. I've tried this, however now it doesn't boot at all. When trying to install the ROM, the recovery informs me it can't validate the signature, and forcing forward does complete installation, but the install never boots, seemingly turning itself off after the initial bootloader screen.

Edit: I have just finished a local build of the image and recovery using the docker-ci container, and it works. However this leaves me without a signed build/OTA updates, as I understand. Would it be possible for you to post a fresh build?
[Android Software Development] Psk.It:
I am not the builder, i can't build the rom

How did you flash the images?

from fastboot, you have to flash dtbo, vendor_boot, boot, in order to be able to sideload the rom using lineage recovery (there should not be any kind of warning since rom and recovery are compatible)

did you flash via twrp?
[Android Software Development] FoxOfArtconomy:
I did the flashing of all three from here: https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220816/

I flashed the latest recovery from here: https://download.lineage.microg.org/lemonadep/

...and then sideloaded ROM.

Since that failed, instead built from the repo here: https://github.com/lineageos4microg/docker-lineage-cicd/

In fact I had started the build before posting, since I had no idea if I would succeed. I followed the directions here: https://github.com/lineageos4microg/docker-lineage-cicd/#gms--microg

...and here: https://github.com/lineageos4microg...re-spoofing-with-integrated-microg-and-fdroid

I took the results from the zips folder, which contained a freshly built recovery and ROM. I flashed the recovery and then sideloaded the ROM. This worked, though it also complained about signatures. I now have a working Lineage build with MicroG preinstalled. However it's not properly signed (it generated keys for me and signed it with those, rather than the Lineage4microG team's) and I expect it won't work with OTA.

Since you are not the builder, do you know someone who is? I'd consider the fact I could build a recovery and ROM from source and get it to work to be strong evidence that there's something incompatible with the recovery/ROM combo currently available here: https://download.lineage.microg.org/lemonadep/
[Android Software Development] Psk.It:
No, you should get recovery from previous date, rom is dated 06-08 you should get images from 02-08 folder (or from the payload.bin file inside the rom.zip using a payload-dumper)

No other recovery is neded (boot.img is recovery)

Once you got (downloading or extraxting) the 3 img files, flash them in fastboot, them reboot to recovery for sideloading the rom (and magisk if you want and/or kernel, as you prefer)
[Android Software Development] FoxOfArtconomy:
OK. I deleted all my old image/recovery/rom files to ensure no confusion. I downloaded the .imgs from that directory you linked in particular and flashed them, and then used the recovery named lineage-19.1-20220802-microG-lemonadep-recovery.img

I formatted away the data, and then sideloaded lineage-19.1-20220806-microG-lemonadep.zip. Once again, I got the warning about signature verification failing. I went forward to install anyway.

The install completed. I rebooted. I got my standard warning message about the bootloader being unlocked, and then after that, black screen. After a while, I get the message 'QUALCOMM Crashdump Mode'
[Android Software Development] Psk.It:
what is your OOS base?

I mean the firmware version
[Android Software Development] FoxOfArtconomy:
I'm not sure what that means. Is it Original OS? Before trying to install 19.1, I was running the last update of the 18.x series. Before that, I'm unsure. That was a year ago or so-- it was whatever was stock on the T-mobile OnePlus 9Pro (lemonadep)

But I do know that if I create a fresh build of 19.1, it works. I'm able to flash the ROM and the recovery produced by a fresh build without issue (other than a complaint of signature verification problems, which I override). This is why I'm confident something is wrong with the files provided, even if I don't know what.
[Android Software Development] Psk.It:
No you need at last C48 (most probably) or C61 or C62 firmware (i am not sure) you can check in custom rom threads for oneplus9pro (there are some spare firmware, the links below are taken from there)

Or better, install OOSC48 for your specific model, then install lineage

you can check what's the required firmware making a call, covering top si de of phone should turn screen off)
[Android Software Development] FoxOfArtconomy:
I don't understand-- can you link me to the directory that contains this firmware? How would I flash it? Or is it somewhere on my phone?

How do I check which version I currently have? I made a call and covered the phone-- the screen did turn off.

Why would I need this firmware if I'm able to load my fresh build without issue?

Thanks for your patience in answering my questions!
[Android Software Development] Psk.It:
I updated the prev reply with some links, but, since lemonadep has different model number depending on the zone (US / IND / EU) it should be better installing the OOS12 C48 via ota (to be sure you get the right firmware for your phone, all versions are collected here) then restart flashing lineage

May be, it's preferibile to continue here since your troubles are device-specific

maybe
[Android Software Development] FoxOfArtconomy:
I think at this point I'm going to stop and just use the build I made, since it works. I don't see why I should need to do any of this if I'm able to build a version of Lineage with MicroG. If this were truly necessary, the build wouldn't work.

Maybe I just won't get OTA updates. I'll live. Thanks anyhow.
[Android Software Development] Psk.It:
for my point of view, it's a bit strange you can run los19 with firmware from a11

In any case, if modem is OK, and also proximity is OK, well, you can stand untill it works
[Android Software Development] FoxOfArtconomy:
OK, so I wrote my last reply after running into a wall flashing one of the packages that you had linked (this one). I flashed all the images that were in that package and the phone loaded the ROM-- but the touch screen didn't work.

That's when I posted that message. Anyhow, I went to go back and flash the ROM I built as planned. But the touchscreen didn't work for that either. I realized then I'd made a big mistake and went down a rabbithole trying to figure out what to do next. Turns out that the link there was for the global edition of the phone, not for the T-mobile one that I had.

After a lot of searching and reading I discovered it was possible to reset to factory and unbrick using a package with MSMDownloadTool preloaded with T-mobile's firmware. I ran that and it worked-- my phone was operational again. However, it was Android 11. So, I went through updating it all the way to the latest update, which was a version of Android 12.

After that, I went through the installation process fresh, unlocking the bootloader and all of that, flashing the dbto and vendor_boot partitions, flashing the recovery for lineage4MicroG, and then installing the ROM for microG, aaaaand...

It worked! So, thank you. I understand better what you were trying to tell me now and while a lot of it still remains arcane to me, it is working. I still don't know precisely why my build was ever able to work. But now I suppose I don't have to-- I have the real thing! Yay!

UPDATE: No it didn't, it just looked like it did. The touchscreen still does not work. But there's an open issue and I'm following the directions in it now: https://github.com/lineageos4microg/docker-lineage-cicd/issues/326

UPDATE 2: And that worked! It's all working now :D
[Android Software Development] hannesknutsson:
Hi,

Firstly, I am not sure if this is the right place to ask this. If not; Have patience with me and point me in the right direction.

I have been running LineageOS for microG for a couple of years now and it has all been working great.

A couple of days ago I realized I have not received any of the bi-monthly OTA updates that the microG homepage is mentioning since April 15 this year (2022). This used to work great and I would update as soon as I got the option to do so.

Has something happened with how the OTA updates are delivered, or has my installation broken somehow?

The troubleshooting flowchart on the homepage directed me to "the XDA thread" which after some googling led me here.

Are any of you experiencing something similar to this? Is this a known issue? Is there something I can do to resolve this? I appreciate any help I can get.
[Android Software Development] Aqq123:
What updates? LOS 17.1 has reached EOL in February. The latest update for davinci (the device you have, according to your posting history) is from April 15 in the repository you linked to and this is the version you have installed, according to the screenshot.
[Android Software Development] hannesknutsson:
I have been assuming there were security updates and similar. That type of stuff is usually updated frequently.

I just noticed a sudden change from receiving regular updates to not receiving any updates for six months.

Based on your response it seems I have wrongfully assumed there is a problem with my device.

I guess I'm fine then. Thanks for your response :)