yashsingh1/xdaforums huggingface dataset:
[Android Software Development] CoLdIcE42:
Hi, Im still unsure about a safe upgradepath to 18.1 with MicroG.

Im running OrangeFox recovery which should be fine ?

So from what I understand I remove my PIN (so it wont get stuck).

Then I flash the newest MIUI recovery to get all firmware/vendor updates.

After that I flash the offical 18.1 to confirm everything is working and then I flash the 18.1 for Micro G ?
[Android Software Development] kurtn:
Upgrading the microG fork should be exactly the same as upgrading official lineageOS - skip the optional GApps part. You will find a guide for your device in wiki.lineageos.org
[Android Software Development] Uumas:
The latest lineage microg build for oneplus3 is from 20210411 while the official los is at 20210503. Why is that? Are the builds going to return soon?
[Android Software Development] kurtn:
An 18.1 round of builds has just started.
[Android Software Development] kurtn:
There are reports from official lineageOS 18.1 users that loose magisk in ota update, too. Best workaround so far: manual update with flashing magisk.

I have seen I can dirty install L4M and official back and forth with lineage recovery

Going to 16.0 needs a clean flash and cuts you off from security patches - or you find a updated unofficial version.
[Android Software Development] CrewParking:
I want to double check because, knowing me, I'll nuke all my data from orbit trying to do this.

I'm on Guacamole upgrading from 17 to 18.

So in other words, follow the exact same instructions here, but use the MicroG zip file lineage-18.1-20210508-microG-guacamole.zip instead?

Edit: That worked. Only issue is that I now have to deal with Magisk, forgot to prep the thing for the update. Thanks kurtn, for the confirmation.

Would be nice if the information was updated on the LOS MicroG website in the Installation section, only tells users what to do if upgrading from 15 to 16.
[Android Software Development] Bifidusse:
On my klte I had to install the microG recovery. With the LOS 18 stock recovery, I couldn't sideload the LOS18-microG zip file (signature verification failed). With the supplied recovery from microG, it worked. I guess it's signature-spoofing related.
[Android Software Development] kurtn:
No, it is build signature related. In lineage recovery you get the message that the signature of the zip file does not the expected signature. You can confirm to install despite mismatch.
[Android Software Development] Ninive:
Hello,

the latest build for Mi 8 lite (Platina) is 2021/04/11 when the latest lineageOS build is 2021/06/03. Will there be an update soon ? Thanks in advance.
[Android Software Development] kurtn:
It's not dead

https://download.lineage.microg.org/ahannah/lineage-18.1-20210617-microG-ahannah.zip
[Android Software Development] Ninive:
Hi, thanks, but I was talking of this one :

https://download.lineage.microg.org/platina/
[Android Software Development] kurtn:
Devices are typically built in alphabetical sequence. So be patient.
[Android Software Development] heinhuiz:
The ones with a June build are all 18.1. Are 17.1 roms still supported?
[Android Software Development] kurtn:
They will probably be built after 18.1 - if your device is not officially supported by lineageOS, you can ask in github for a build.
[Android Software Development] don van vliet:
Ahoj,

there was no June build for X00TD but there already is a 18.1 LOS build for it.

Whats the reason? Could someone explain that to me?
[Android Software Development] kurtn:
There was noone to build. But now the round of builds already reached whyred. Wait just another day.
[Android Software Development] don van vliet:
great, thanks!
[Android Software Development] iooxda:
I just noticed that there is no download for Lenovo Z6 Pro (zippo) on the MicroG website https://download.lineage.microg.org/. There is an official LineageOS version (https://wiki.lineageos.org/devices/zippo/install). I thought according to the microG FAQ:

"We already build LineageOS for microG for every device supported by LineageOS. Find your device in our Downloads page!"

Is this just missing from the website or is this phone not supported by LineageOS for microG?
[Android Software Development] kurtn:
Here you are:

https://download.lineage.microg.org/zippo/

Please report back.
[Android Software Development] patroj:
Installed 18.1 for xz2c yesterday and it works like a charm!

Edit: Maybe update page 1 as we're on R now. 😉
[Android Software Development] Heimu:
Are any LOS 17.1 updates for Fairphone 3 in your pipeline? The latest "regular" LOS nighly is from June 21, while the latest LOS for microG is from April 14...
[Android Software Development] novabright:
Installed 18.1 on Oneplus 3T, so far everything has been pretty good. It's great to have microG and F-Droid integrated into the OS.

Some small issues that I noticed:

Root check

I used the "Root Beer sample" app to check root conditions, and all categories were passed except "Dangerous props". I don't know what this is but I'm reporting it here in case the developers want to take a look on it. The phone is not rooted, I haven't installed any root utilities.

Download signing

I think it would be great if standard GPG signatures were distributed with the downloads. Some people may find the verifier utility less intuitive.

Website information

The installation instructions are slightly outdated I think, they mostly deal with version 16 even though 18.1 is the newest. Not a big issue. Also, there are no complete instructions, I had to use the original LineageOS instructions instead (I guess this is intended).

Slow GPS/location search

I installed OsmAnd and noticed that it didn't find my location. Tried another navigation software, as well as GPS Test and SatStat, neither was showing anything. Then I enabled the Mozilla location backend in microG settings, still nothing at first, only some occasional weak signals in SatStat. I cleaned the AGPS data. I let the phone search for location for 15 minutes or so, and it finally found the satellites and location.

Is this a known problem and how about the next time when I need a navigation app? I hope that location is found faster then.
[Android Software Development] kurtn:
Root check probably sees unlocked bootloader or user-debug build. Those are real vulnerabilities

You need no verifier utility. Calculating sha256 should be enough.

Yes, website is outdated. Wiki.lineageos.org Should be enough for clean installation.

Slow gps is a problem on some devices with lineageOS. You can get geolocation from a good location backend in the waiting time. Apple backend is good in my area.
[Android Software Development] novabright:
Thanks for information, perhaps I'll try the Apple backend too. Is it important to enable the Wifi search in the Mozilla backend or not? I disabled it because I thought that cell towers would be a better option. It was a bit surprising that I encountered problems with GPS. Almost everything else seems to work really well and I thought that GPS wouldn't be the most likely problem.

Is the Google location service actually searching for location continuously, even when location is turned off in the top bar? Could this explain why location is found faster when using Google Play services in the phone, or am I just wrong?

SHA-256 is good but I think GPG signatures might provide slightly stronger security.

What are the recovery image files provided with LineageOS (for microg or not), by the way? Does LineageOS provide their own custom recovery environment? I just installed TWRP before installing LineageOS as it was even recommended in the LineageOS installation guide.

(And had a strange problem with TWRP as the first reboot after flashing it went back to the old recovery. Then I flashed it again and rebooted in a different way, and it got into TWRP.)
[Android Software Development] kurtn:
Yes, lineageOS has a own recovery. I think it's mainly for having a 2nd source in case something goes terribly wrong with twrp, and for a/b devices.

We can't know exactly what google play services do. But location data has a high value for their business model.
[Android Software Development] rogerwilco75:
Hi everyone,

LOS17.1 with microG, Magisk on Samsung Galaxy S9:

> Has the function to block calls & texts, i.e. to "mute" one of your contacts, been removed?

Yes, I did find the option to block individual numbers but IIRC there used to be an option in LOS when you accessed your contacts app, tapped the 3-dot menu while looking at a contact, to block/mute that contact entirely, not having to add all numbers separately to this other blocking list.

What would I need to do to get this function back or what am I possibly doing wrong that it is not shown/offered?

Thanks in advance.
[Android Software Development] kurtn:
Long press entries in call history
[Android Software Development] klaus-hamburg:
Does anyone know the reason for the lack of update to Galaxy S4 i9505 jfltexx?
[Android Software Development] kurtn:
Looks like a failed build
[Android Software Development] klaus-hamburg:
thx

that's sad

I've also microg patching problems in unofficial build LineageOS 18.1

for S4 i9506 ks01ltexx provided by kyasu .

May be the same Problem.
[Android Software Development] rogerwilco75:
Hi kurtn,

thank you very much for you prompt reply. (y)

I had a look at your proposed way of doing it. But realized that that would only be for a single number. If the individual had several numbers for calls&texting which I'd like to easily be able to mute and umute again, this would require quite a good number of steps to carry out, which is why my focus was on the contact object rather than individual phone numbers.

Backstory is, that IIRC CWM supported this many moons ago and I found it quite handy. If I understood things correctly even som stock ROMs do.

The approach which appears to come closest to what i am looking for, would be through the (Ed)Xposed framework (Riru etc.) and then using Xposed Call Blocker. I do not dislike Xposed approaches and would consider it if there were no other options but I would prefer a solution that would not require (Ed)Xposed.

Again, thanks in advance for your input. 🖖
[Android Software Development] aveilleux:
Yesterday I noticed an updated build for star2lte on the microg downloads site, but no such build exists on the upstream LOS nor has its status changed from unsupported. (I'm currently on 2021-01-18, the last "supported" build from LOS on the MicroG site) I can't seem to find any information about this build elsewhere—no changelog, no references to it on XDA, nothing. Is this build legit?
[Android Software Development] kurtn:
This build is untested, but probably OK. Main fault is naming. It should be "-UNOFFICIAL-microG-"
[Android Software Development] aveilleux:
Thing is, I can't find it anywhere else. Where did it come from?
[Android Software Development] kurtn:
It comes from official sources. They are unmaintained but buildable

GitHub - LineageOS/android_device_samsung_star2lte

Contribute to LineageOS/android_device_samsung_star2lte development by creating an account on GitHub.

github.com
[Android Software Development] aveilleux:
What would have changed, here? Just updated deps?
[Android Software Development] kurtn:
Mainly security patches

https://review.lineageos.org/q/q_asb_2021*
[Android Software Development] PhoneThe4th:
I'm not sure if this is the right place for L4M troubleshooting issues on particular phones, but there is a very noticeable display bug for one device, at least.

The Moto G7 Power (ocean) latest build (6-21-2021) has a very noticeable display issue, usually after you wake the device from rest/sleep mode, which seems like a graphics display issue where colors are almost inverted and pixelated. The official LineageOS build has recently added a newer build (6-26-2021) which I haven't tested, may have addressed this issue (though doesn't seem like it's listed on the 'recent changes' link), but I try not to switch between ROMs if I don't have to as I prefer yours for privacy. A quick fix is to adjust the "Colors" to "Saturated," and it usually allows you to go back to any color scheme after that, until you reset or power off the phone, then the issue comes back when you wake it from then.

I saw maybe one other post on reddit mentioning this bug, even on 17.1 builds of the official LineageOS.

https://www.reddit.com/r/LineageOS/comments/mmxvm7

I'll probably bring this up with the LineageOS thread as well if the issue is with them (which I think it is), but I wanted to bring this up to you all so that if they do fix it, if you could kindly update the build of L4M so we can continue using my favorite ROM as normal. Thanks for all your hard work and giving us the ability to continue to keep our privacy on our mobiles as much as we can!
[Android Software Development] novabright:
I encountered a strange crash today - I was checking the APN settings (Settings -> Network and internet -> Mobile network -> Access point names -> <my default APN for internet> -- note that I use localized system so I'm not sure about the exact English names).

Anyway, after browsing these settings for a while, the phone crashed - the display went black, the LineageOS boot screen appeared and I had to enter the PIN code. However, when I went to Settings -> About phone -> Uptime, it was showing about 8 days. So the entire OS didn't crash but something else did??

Has anyone else had this? I searched a bit and it seems that the APN settings tend to crash for many people. But what is weird is that it wasn't just the Settings app that crashed - something else did too. Is there something I can do to investigate?

I tried to reproduce this a few times but it didn't crash. I think I have never seen this with the stock OS (OxygenOS on Oneplus3T) either. (On the other hand I check these settings very rarely.)
[Android Software Development] kurtn:
It's a lineageOS bug. Not a MicroG bug. So its useless to try reproducing it on Lineage4microG. LineageOS people won't accept te bug report.
[Android Software Development] novabright:
Hm, I see. Is this a known problem (something that has been investigated) in LineageOS or recent Android?
[Android Software Development] kurtn:
Search here

issues · GitLab

GitLab.com

gitlab.com
[Android Software Development] prabuddhadg:
Is NFC working on Lineage os 18.1 for micro g? I upgraded from 17.1 to 18.1 on my Asus Zenfone 5Z . On 17.1 NFC was working but now on 18.1, it is not. Is this a micro g problem or a lineageos problem?
[Android Software Development] kurtn:
Sounds like a lineageOS problem. Have you searched for bug reports?
[Android Software Development] prabuddhadg:
You were right. It is. It appears all the bug reports have not been sorted out yet. I guess I need to wait for the next nightly, or the next.
[Android Software Development] fail lg:
hi there , I succeed to install lineageos 18.1 for microg on my lg g3 (d852) but

I'm not succeed to install the addonsu-16.0-arm-signed annd i also try to install supersu to root but it fail also ,

​

​
[Android Software Development] kurtn:
Addonsu 16.0 is only for rooting lineageOS 16.0 - higher Android versions don't have native root solutions. And it is not recommended to have root for apps due to stability and safety reasons.

You have built in root for adb and you can modify system partition with twrp. If that's not enough you have to use magisk.
[Android Software Development] Michu_z:
Hi,

I've installed the latest version of LineageOS 18.1 for microG on my Pixel 5 (July 4th release), but Wi-Fi is down and the GSM network disconnects every minute or so.

I experienced the same problem with the previous release, then I managed to flash the ROM to stock, then go back to working version 18.1 from April 11th.

This time I even changed the kernel to Proton 1.4, it didn't help me - Still Wi-Fi doesn't start and the network is reset every minute, I can't even make a normal phone call.

Does anyone on the forum know how to fix it (maybe a firmware change)?
[Android Software Development] kurtn:
There is an official LineageOS build from today 7.7. After 3 weeks. Maybe the sources had a problem. Can you try official lineageOS?
[Android Software Development] Michu_z:
I'm not using Google Services or any apps from Mountain View company, so I will not use LineageOS, possibly I can install a version without GAPPS and install microG later (however, I would prefer the option with integrated F-Droid and microG).

Newest LineageOS for microG for Pixel 5 is from 4th July: https://download.lineage.microg.org/redfin/ and this is the second in a row release without wi-fi working on Pixel 5...
[Android Software Development] kurtn:
You can run https://mirrorbits.lineageos.org/fu...neage-18.1-20210707-nightly-redfin-signed.zip without GApps
[Android Software Development] Michu_z:
I just installed newest LineageOS (7th July 2021) without GAPPS, no wipe - Just recovery mode installation on existing LineageOS for microG (4th July 2021) - Everything works fine now, I even have a system F-Droid and working microG.
[Android Software Development] kurtn:
Great. What does MicroG self-check say?
[Android Software Development] Michu_z:
Unfortunately not all checks passed (only first from first category, first from second category, and all access rights are ok). A few apps warned me that it wouldn't work without Google Services, but so far they have been working fine ;)
[Android Software Development] kurtn:
Expected. Signature spoofing is the reason why a fork from lineageOS was necessary. All other features could easily be installed on official lineageOS.
[Android Software Development] fail lg:
thank you very much kurtn! so my only option is to install magisk? ok i will try it so I go back reading !

UPDATE: so with adb root i can still use prerooted apps ?
[Android Software Development] kurtn:
No, adb root is not root for apps.
[Android Software Development] cehuisken:
Hello,

don't know if I am right here with my question, so I just try:

I am using a MOTO G3 2015 osprey with Lineage with microG 17.1 since last year, last update from july 7, 2021. Every time I get an update, it downloads without problems, but when I then confirm "install", the phone boots into recovery (TWRP last version für osprey) and shows TWRP-startpage. I have to click „install“, search for lineage-updates (/data/lineage_updates), then select the downloaded file and confirm. Then it installs, but with an error message: „@/cache/recovery/block.map kann nicht zugeordnet werden, Fehler beim Installieren von ZIP”. I ignore that, and my phone works fine with that update.

One of the updates (from 27-06-2021) did it as I knew before: I clicked „install“, phone boots to recovery, install happens an reboot starts phone again. So I had hope that the problem is solved. Unfortunately, it came back on 07-07-2021.

So, I can help myself, but its not really good as it is I think. For a friend I installed the same system on her osprey, but she does not know anything about systems and updates on smartphones – she only uses. So I have to do any update for her. Without that error she could do it by herself.

Does anyone know what to do, or where to ask?

Thanks

cehuisken

EDIT: here last_log.gz for more information
[Android Software Development] kurtn:
You can try lineageOS recovery

https://download.lineage.microg.org/osprey/lineage-17.1-20210707-microG-osprey-recovery.img

Maybe your built in updater shows the option to update recovery in threedotmenu? That will install exactly that.
[Android Software Development] x2k13:
Any chance for 18.1 on jfltexx? Looks like it's stuck on 17.1 for unknown reasons.
[Android Software Development] kurtn:
All jf variants suceeded with 18.1 just jfltexx failed

Failed builds · Issue #197 · lineageos4microg/docker-lineage-cicd

Seems to be various different reasons. Open for suggestions on how to fix any of these. lineage-15.1-20210628-UNOFFICIAL-microG-angler.log lineage-15.1-20210628-UNOFFICIAL-microG-bullhead.log linea...

github.com

Failed again on July 29
[Android Software Development] x2k13:
Oh, bummer. Wonder why it's no issue on LOS 18.1 vanilla.
[Android Software Development] :
Will the new added devices to the list of official lineageos 18.1 be added to Lineageos Microg too? I have a LMI / Poco F2 pro / Redmi K30 pro and hope it will be supported.
[Android Software Development] kurtn:
Yes. Devices get automatically added. No guarantee for success in building.
[Android Software Development] petefoth:
Official LOS has 18.0 builds for Sony Xperia Z3 and Z3 Compact, but Lineageos Microg oly has 17.1 builds. Is there a known problem with Lineageos Microg for these devices, or should I just wait?
[Android Software Development] humpty321:
I neeed to use an app to control some stettings of my bluetooth speaker. This app is Vifa Configurator (com.vifa.vifaconfigurator). Stangely it gets wiped by every update of LineageOS for microG. I cannot tell when this behavior started, but at least this has now happened several times in row without exception, today by installing lineage-18.1-20210810-microG-cheeseburger.zip. As I have a backup in Oandbackup it is not a big deal to restore it, but I think it's very odd.

Can anyone explain this?
[Android Software Development] kurtn:
@humpty321 I haven't seen such a behaviour with microG. From your usage of Oandbackup I guess your rooted your phone with magisk? From magisk we can expect all kind of errors. Including issues with the package installer.
[Android Software Development] humpty321:
Yes, my phone is rooted with magisk. I do want to have AFWall in place, so an unrooted device is absolutely no option for me. Would you suggest another and maybe better way for rooting than magisk?
[Android Software Development] 30jp:
You could also use Netguard instead of Af-Wall. That doesn't need root. Here is all the info and download about Netguard

GitHub - M66B/NetGuard: A simple way to block access to the internet per app

A simple way to block access to the internet per app - M66B/NetGuard

github.com

Very nice app with many possibilities and excellent support from the developer M66B. There is a free version and a pro, pay, version.
[Android Software Development] humpty321:
Thank you for the hint, but I want to have VPN available.
[Android Software Development] gadgetguy08:
From a cursory look, the app doesn't seem to be included in the G*Play store anymore, and on apkpure it doesn't appear to have been updated in almost 4 years. Guessing that there is some oddity with the app.

I haven't seen any behavior like that in any of 100+ apps on my device with Lineageos for MicroG with Magisk.

Also there was a microg update at the end of June (since you indicated the behavior began recently.
[Android Software Development] thomas2403:
I've just installed the latest version for Oneplus8t (13th August 2021). Any idea, why microg doesn't get updated to the latest version 02.21? Are there any problems with this version?
[Android Software Development] kurtn:
No problem. The update in build system is manual work. You can update with f-droid
[Android Software Development] thomas2403:
As far as I know, microg is located in /system/priv-app. Can f-droid update files there? I always thought, I have to use adb push or do it in twrp.
[Android Software Development] humpty321:
Vifa has been taken over by China or someting like that and since that time support has been dropped. Sadly the speaker is very much crippled without the app. A profile called "boosted" is lost even when the app is now freshly installed from the apk (still available at apkpure.com), because this setting had to be retrieved online and that server has gone too. So I am lucky to have said backup in Oandbackup, which includes "boosted". I just hope the app will not be broken by future updates of the OS.
[Android Software Development] kurtn:
Yay we got a new 17.1

https://download.lineage.microg.org/jfltexx/lineage-17.1-20210818-microG-jfltexx.zip
[Android Software Development] x2k13:
Still 17.1 - not 18.1