yashsingh1/xdaforums huggingface dataset:
[Android Software Development] andy356:
Whoa, dude. 2 out of 4 PRs got *merged* just a few hours ago. (The Android 10 PR wasn't one of them, mind). L4M IS ABOUT TO BE BACK.
[Android Software Development] Master One:
It's actually a good sign, it shows that it is being worked on after that long time (since March?) of neglect.
[Android Software Development] selfishjelly:
A really good sign indeed! Time to test the new capricorn build. (and orher builds are slowly popping up too)
[Android Software Development] Simon94:
Just to give a small heads up. As you may noticed some of the project members the priorities have shifted to other projects.

I was and am still willing to take over some of the tasks, but as microG lacked some bugfixes and support for LineageOS 17.1 i was not sure whether its worth it to spend more time into LineageOS for microG. Once marvin released the new microG update, we still had to check with our team, how we'll proceed.

For now i've taken over the responsibility of the Android Build process, merged some of the fixes and integrated LineageOS 17.1 support. New builds are on their way, both LineageOS 16 and 17.1 based.

Best

Simon
[Android Software Development] Master One:
Which other projects?

Hopefully LOS for MicroG will get going again as it used to, because I really don't know what to do without it.
[Android Software Development] heinhuiz:
I ❤️ [MENTION=4316015]Simon94[/MENTION]
[Android Software Development] kurtn:
Nice. 17.1 roms are starting to appear in downloads.
[Android Software Development] Master One:
Make LOS for microG great again! :D
[Android Software Development] akoyaxd:
Awesome, thank you so much for your work! LOS4MicroG is such am awesome project and makes the access to microg so much easier!
[Android Software Development] Master One:
Now that things hopefully get jump started again, does anybody think it's a good time to order a OnePlus Nord in hope that it will get officially supported by LOS and then by LOS for microG?

Kind of a dilemma, because when a new OnePlus comes out, of course it's not supported by LOS right away and it's not clear at all that it will, but if one waits too long, so till official LOS is available for the latest device, it likely can not be bought as new anymore as there is then already a successor...

For a new phone it seems the OnePlus Nord would be the device that makes the most sense, looking at price and availability (I'm here in Europe).
[Android Software Development] kurtn:
I'm sure, you can wait half a year. Oneplus 7T is still available and 20 % cheaper than last November.
[Android Software Development] Master One:
What's going to happen in half a year? And I've just checked, the OnePlus 7T is currently offered at 529 € (so still 130 € more expensive than the OnePlus Nord), and since I don't do anything sophisticated on my phone or play games, I have no use for the extra power. A phone for less than 400 € is way more plausible, especially as I have to buy two of them (one for me, one for the wife).

P.S. Sorry for slightly OT, but this is of a major concern to me, because when I'm buying a new phone, it has to be supported by LOS for microG!
[Android Software Development] Master One:
The 1st release of LOS for microG 17.1 is now available for my device (OP6)! :good:

OTA update is not possible (as expected), and instead of the "Download" link it shows an "Info" link leading to the official LOS upgrade guide for major versions using adb sideload.

I have TWRP installed, so what's the exact procedure to upgrade from LOS for microG 16 to LOS for microG 17.1 using TWRP?
[Android Software Development] githyanki:
I am not sure myself since I have not done it, so take this with a few grains of salt.

Backup everything. Titanium backup, TWRP backup and anything else you usually do.

In TWRP, wipe system and install new version, then magisk if you use it.

Cross fingers and reboot to system. Should work, but I'm sure you'll need to go through microg setup again.

Any troubles, clean install by wiping system and data, or use TWRP restore.

Good luck and let us know how it goes.

I'm looking forward to Shamu build soon. (Hopefully soon)
[Android Software Development] Master One:
I'd like to prevent a fresh installation (so without wiping) and I don't use Titanium backup, but only TWRP backup, so a dirty flash success story and instructions would be awesome.
[Android Software Development] githyanki:
Only wiping system is a dirty flash. Just a little better than just installing new version. If you do a TWRP backup, you can try without wiping system also.

BTW, I am not on Lineage ATM, so I won't be able to comment on what worked at all. I'll be doing a clean install when it's available.
[Android Software Development] kurtn:
I dirty updated samsung galaxy a3 2016 from official lineageOS 16.0 to official 17.1

I've read through the guides for op6. I'm sure they apply for L4m aswell. In my ecperience risk factors are encrypted phone, magisk, outdated twrp or bootloader or baseband.
[Android Software Development] Master One:
So how was it? Just flashed the LOS zip from TWRP, followed by re-flashing TWRP and then Magisk and everything worked without any further actions?

Or are you supposed to flash latest OxygenOS first, followed by installing LOS + TWRP + Magisk? But that would be a clean install then.

I'm not sure which way to go. Does Titanium Backup provide a way to just backup and restore data + apps + app-data and is there any (free & OSS) alternative for it?

I'm sorry, I'm pretty much a noob when it comes down to this kind of stuff, I'm not into tinkering around with my phone, I'm just a (happy) LOS for microG user.
[Android Software Development] niix:
[MENTION=4316015]Simon94[/MENTION] Lineageos for Redmi Note 7 (Lavender) is official now. Could you please add support for this build?

https://download.lineageos.org/lavender
[Android Software Development] kurtn:
Just wait another day. Edit: lavender made it onto download
[Android Software Development] topecorm:
Hi!

Has anyone the Lineage for microG migration zip? I l lost it and the link in the official home page is broken (404).
[Android Software Development] ffew2:
Hello, can anyone share latest available lineage 15.x+microG for Nexus 5x, it was here few months ago https://download.lineage.microg.org/bullhead/ , but now is gone.
[Android Software Development] JustAnotherAndroidUser:
Seconded. Anyone have it on their computer?
[Android Software Development] bege10:
That's the one I downloaded about a year ago.
[Android Software Development] ramen-udon:
Flashed 17.1 from 16 and it worked, but now my touchscreen doesn't work upon reboot. I'm asked to enter my PIN (fingerprint doesn't work 1st time after reboot), but I can't enter it bcs my touchscreen isn't working. Moto G7 river.

ADDITION: I was able to do an adb shell and input my PIN that way, however the touchscreen still doesn't work.
[Android Software Development] darhma:
Does the touchscreen work in custom recovery? I'd try a clean flash of the ROM. I think that when there is a major version upgrade it is always better to do a clean flash to avoid problems.
[Android Software Development] topecorm:
Thank you! That should be fine.
[Android Software Development] ramen-udon:
No, it doesn't.

I was able to plug in a mouse with USB OTG and all my files and apps are present, the OS shows Android 10. I just need the touchscreen to work again. :( Can I replace the firmware via adb shell? I'm out of my league to know where to find the version that worked, so any advice or help would be super appreciated. Thanks!
[Android Software Development] humpty321:
I would like to migrate two devices of my family from lineageos 17.1 to lineageos for microG. Unfortunately I cannot follow the migration instructions on lineage.microg.org because all the links given there to the "migration ZIP" are void.

Where can I please find that "migration ZIP" ?

---------- Post added at 03:57 PM ---------- Previous post was at 03:43 PM ----------

I saw this one just now. If these keys are still ok, then why were they removed from their original place to where the link in the instructions points ?
[Android Software Development] kurtn:
That zip worked for my migratoin of surnia 17.1 to microG. Maybe you can post in the other thread for lineageOS related talk.
[Android Software Development] ramen-udon:
I did a clean flash and the touchscreen still doesn't work. I think there might be a problem with the 17.1 update for Moto G7. I'm personally not going to touch it again until someone tells me it for sure works. Wasted a weekend.
[Android Software Development] hussaint:
What recovery ROM are you using eg TWRP? Does the touch screen work there and just not in booted Lineage OS for MicroG ?
[Android Software Development] ramen-udon:
TWRP 3.4.0-0-river

The touchscreen does not work in recovery, and not when booted into LOS for MicroG 17.1. I had to use a USB OTG cable and an external mouse to get myself out of the mess. It was really weird.
[Android Software Development] hussaint:
Was the recovery installed for someone prior to Lineage 4 MicroG ? If so, did touch used to work in that recovery for you without problem?

I know I am stating the obvious, but if touch is no longer working in the recovery or the booted OS, you have to consider if by freak coincidence you now have a hardware fault with touch. What about trying to flash stock ROM and recovery for phone and checking if touch works again and if not a hardware fault might be the problem. If it does work then start again with reinstalling TWRP, verify touch works, then flash Lineage for MicroG again and see what happens.
[Android Software Development] ramen-udon:
I can only get the touchscreen to work by returning to LOS4MicroG 16.0. I'm just going to stay there for a good while. :good:
[Android Software Development] humpty321:
As these keys worked for you I gave them a try.

TWRP reported an error "unable to decrypt FBE device". Nevertheless at first sight the phone, a rooted LG D802, seem to work ok. F-droid itself and Local GSM Location from F-droid were not uninstalled beforehand. Obviously they are regarded as official builds (which is not stated clearly in the migration instructions).
[Android Software Development] kurtn:
I don't understand the statement with official builds. L4microG includes a f-droid app. If you had local gsm as user app, it doesn't get touched by migration.

I see a problem with encrypted storage and OTA. Neither lineageOS recovery nor a special twrp that is able to decrypt update sucessfully.
[Android Software Development] slothorentropy:
Anybody know, when 17.1 will be ready for beryllium?
[Android Software Development] kurtn:
Simon is aware:

https://github.com/lineageos4microg/docker-lineage-cicd/issues/97

Today started a new round of 17.1 builds. In around 8 hours we should be able to see if it builds.
[Android Software Development] humpty321:
As far as I know F-Droid build all the apps in their store themselves and sign them with their own keys. So I just was not sure what the LineageOS for microG people meant by "inofficial builds" as they don't say, which ones they regard as "official".

This phone was not encrypted. The files in the internal storage are still there and accessible after the migration. MicroG selftest has all the boxes ticked. So far I did not experience any problem. Updater does check for new updates, but there is none yet. So about OTA I cannot tell yet.
[Android Software Development] Olangu:
I just tried out the build. Was not able to flash the migration zip, as my data partition is encrypted.

The installation was however successful anyway. (Wiped System to get rid of OpenGapps).

I had all the checkboxes in microg checked, but every app that in any way depend on Google Play Services crashed.

Is that expected? Do I need to install anything else? Or is this the current state of MicroG on LineageOS 17.1?

My device is a encrypted starlte (Galaxy S9).

EDIT:

Apparently the apps get registered with the device-id of Google Play Services in some way, that's why they fail, reinstalling the apps work.
[Android Software Development] slothorentropy:
What's different between using LineageOS for microG and using LineageOS itself from this site:

lineageos(dot) org

Why I must prefer this bild?

youtu(dot) be/fhfWJmFMVQw
[Android Software Development] darhma:
MicroG is an open source alternative to google play services. If you want to use lineageos without gapps you can use lineageos with microg to have some functions of google play services. You can install microg also in lineageos but it's a little bit complicated because lineageos doesn't support signature spoofing and you have to patch the ROM. If you need more information you can look at the microg project page: https://microg.org/

Or arternatively just read the first post of this thread ;)
[Android Software Development] kurtn:
You talk about two alternatives, but there are three in in ascending privacy but decending convenience

LineageOS with GApps

LineageOS with microG

LineageOS without any G

.. and that video is not good. Better follow written guides.
[Android Software Development] SchwarzeMinimum:
Hello,

I hava a Galaxy S5 LTE+ here (SM-G901F, kccat6 if I'm correct) where I'd like to install Linage with MicroG. The download page doesn't list any download for kccat6, so how can I go on - either SM-G901F is not kccat6 - what then? - or there is an alternative download location - where? - or it's not built for any reason - then how to change that or do it for myself?

Could you please give some insight into that?
[Android Software Development] darhma:
If there isn't an official build of lineageos for your device then the device is not supported by lineageos for microg
[Android Software Development] SchwarzeMinimum:
Thanks for the response.

What does it need to make it supported - or at least know the reasons? Would it be possible to build it at home for people with some technical background, as the homepage states that there are not much differences from (stock) Lineage to Lineage for MicroG? Forgive my curiousity, but it's a serious question...
[Android Software Development] darhma:
Official lineageos doesn't support signature spoofing that's required to install microg. So lineageos for microg is a patched version of the official lineageos that provide an easy way to use microg. Anyway you can patch any ROM to support microg. I suggest to give a look here https://github.com/lineageos4microg/docker-lineage-cicd or search some guides or howtos
[Android Software Development] SchwarzeMinimum:
Thanks - I'll have to sort my HDs to get some place for that!
[Android Software Development] kurtn:
You could help Simon with this issue

https://github.com/lineageos4microg/docker-lineage-cicd/issues/94
[Android Software Development] SchwarzeMinimum:
Would be willing to - Simon is spolack there? I'd like to discuss that with him.
[Android Software Development] SchwarzeMinimum:
Build was OK, going to try the image tonight.
[Android Software Development] rayman95:
Thanks for your work... I would like to know what's going on with hlte device???

No more release??? There was issue with server before?!?
[Android Software Development] kurtn:
16.0 has only one round of builds. 17.1 has already two. Mainly because some 17.1 failed in the first round. At the moment i see some 15.1 coming in.
[Android Software Development] Simon94:
I didnt set up automated builds yet. For now i trigger all the build runs manually, as there are some constraints on the build host to fullfill.

But for shure i wont abandon any of the devices.
[Android Software Development] JohnFrenchie:
Hi there,

I can see that there is an official build of LineageOS for Samsung kccat6 (S5 Plus), but the download directory of LineageOS for MicroG is empty.

Any explanation?

John Frenchie
[Android Software Development] kurtn:
There seems to be a bootloop issue. Please try official lineageOS and file a bug report if you see the boot loop.
[Android Software Development] JohnFrenchie:
Ok, Thank you. I already tried the last official release (with Gapps), without bootloop.

As I can't help debugging, I'll wait. Thanks to MicroG for the work.
[Android Software Development] acr2d:
Can someone link me the ROM for the moto g Titan? I couldn't find it anywhere.
[Android Software Development] darhma:
Read here: https://xdaforums.com/android/software/lineageos-microg-t3700997/post83367119
[Android Software Development] kurtn:
Old builds habe been taken off the Downloads site. But this looks promising: https://xdaforums.com/moto-g-2014/orig-development/rom-lineageos-16-0-t3833953
[Android Software Development] acr2d:
Thanks. I should have downloaded when it was available.
[Android Software Development] ramen-udon:
8-26-2020 version of 17.1 still bonks touchscreen

So I got a new Moto G7 for development and testing (variant: river XT1962-1). I installed TWRP recovery, sideloaded the copy-partitions.zip, then sideloaded lineage-17.1-20200826-microG-river.zip. I just wanted to give the feedback that this version also resulted in an unresponsive touchscreen.
[Android Software Development] kurtn:
Can you try official lineageOS "nightly"?
[Android Software Development] ramen-udon:
I flashed the LOS nightly (lineage-17.1-20200830-nightly-river-signed.zip) and can confirm the touchscreen works fine. Again, this was the straight-up LOS version, and not the MicroG version.
[Android Software Development] tor-muc:
I don't want to cause confusion with my reply in the middle of your conversation, but I have the same issues with the frozen touchscreen on my river (XT1962-5). The screen stuck in TWRP and the OS itself, I did a clean installation several times already but nothing worked for me. I had the identical issues with the LOS4microG builds from August 20 and August 26. The vanilla nightly LOS 17.1 from 2020-08-16 worked fine for me, touchscreen fully functional in TWRP recovery (3.4.0-0-river) as well as the OS itself.
[Android Software Development] ramen-udon:
I wanted to add that my daily driver that I messed up with 17.1 and referred to in my first post has a variant of XT1962-6. The developer phone referred to above, again was XT1962-1. So, summarizing our two posts, that's now 3 different variants of Moto G7 (XT1962-1, XT1962-5 & XT-1962-6) that have lost the touchscreen with 17.1 LineageOS4MicroG.
[Android Software Development] jay-cp:
Hello. I see that a new update for mido is available on the download page, and it is marked as UNOFFICIAL.

I have tried to update a mido device with it, but it fails the zip signature test. So I didn't proceed.

Is the image file corrupt? Is it ok to use it? Did anyone else install it?

Thanks!
[Android Software Development] kurtn:
You come from official lineageOS? Read the chapter migration in lineage.microg.org and use that migration zip

https://xdaforums.com/android/software/lineageos-microg-t3700997/post83328245
[Android Software Development] 2faraway2:
Just to inform you about an issue in the network location service of MicroG/UnifiedNLP:

https://github.com/microg/android_packages_apps_GmsCore/issues/1150

Rom is lineage-17.1-20200826-microG-lavender (Xiaomi Redmi Note7) with latest Android 10 global firmware.

Anybody else with this problem ?

Thanks in advance :)
[Android Software Development] zeworks:
ROM for Moto G5S (XT1794) aka montana

Hi,

I'm about to try installing microG on my Moto G5S unofficial LineageOS, but if by any chance a bundled LineageOS+microG ROM could be made available, that would be much appreciated :)

Many thanks in any case for the microG dev, a few apps just insist on these services ...

Cheers,
[Android Software Development] jay-cp:
No, I actually have LineageOS for MicroG installed... I got that image from the updater. Then I used adb to open a shell and check the sha256sum of it, and it is correct (same as in hhttps://download.lineage.microg.org/mido/)
[Android Software Development] kurtn:
In that case i would dirty flash the zip in twrp.
[Android Software Development] bian_ki:
I have a slight problem using Youtube Vanced, that applies to both 16.0 and 17.1

Youtube Vanced relies on microG. However, it doesn't detect microG in this build (LineageOS for microG).

I was able to install their .apk and use it without logging in before (on 16.0).

However, currently the official way to install Youtube Vanced app is their Vanced Manager app which forces me to install microg.apk first. Should I agree to it or not?

upd: found my answer here: https://xdaforums.com/showpost.php?p=82516041&postcount=15415
[Android Software Development] kurtn:
YouTube vanced uses a different kind of microG, sorry.
[Android Software Development] thankful_user:
Hello

I'm not sure if this is the correct place to post this, but I could do with some assistance.

After eventually successfully upgrading my enchilada from LOS4Microg 16.0 -> 17.1 (flashed stock OOS 10.3.5, then copy-partitions, then flashed 17.1, kept all apps, settings etc) now I can no longer unlock the phone with just the pin. Upon first boot i can enter the pin successfully to decrypt the phone but still have to unlock with the fingerprint to get to the home screen, any other time after I try to unlock with just the pin it just goes black for a moment then straight back to the lockscreen, the fingerprint is working fine to unlock.

I saw someone elsewhere suggested delteing data/sytem/lockscreen.db but this sounds like a bad idea and a recipe for not getting into my phone.

It's the same problem as the 'lock screen loop' reported on some of the pixel devices.

Does anyone have any suggestions for what I could try to resolve this? When I try to remove the pin in settings it just keeps saying 'settings app has crashed'.

I initially installed lineage-17.1-20200819-microG-enchilada but have since successfully done an OTA update to lineage-17.1-20200825-microG-enchilada

I read somewhere else that this is a problem when the stock rom has not been successfully flashed - on first installation I flashed OOS twice, but this time I only flashed it once followed by a copy-partitions zip - could this be the culprit?

Any help hugely appreciated, and a huge thanks to the devs and especially the maintainers for keeping such a great and essential project going! you guys are the GOATs.
[Android Software Development] Keule-Tm:
Maybe you could try to just rename the db (e.g. 'lockscreen.db.bkp' or something else). That way you could try that suggestion without needing to go all back if it goes sideways.
[Android Software Development] kurtn:
Format data is for removing device encryption

https://wiki.lineageos.org/devices/enchilada/install

The real oneplus expert is in irc channel https://webchat.freenode.net/?channels=lineageos but don't tell him you are on microG fork.
[Android Software Development] gadgetguy08:
Does anyone know what has happened to the builds? There was a flurry of activity including 17.1 builds in the middle to late August. Then they stopped on August 28.
[Android Software Development] akavillian:
Kinda wonder that aswell hopefully they are alright.

Im really curious to test the latest 17.1 for payton cuz it has 2 very critical fixes for me. I'll wait for the microG release of it tho for sure.

Also as a sidenote I'd like the 16 uploads up aswell since it's soo solid in comparison :)
[Android Software Development] tkm89:
I was wondering the same. Hoping a script (or similar) will be implemented for automated weekly builds.
[Android Software Development] kurtn:
Official migration zip

https://download.lineage.microg.org/extra/
[Android Software Development] gongoscho:
microG for beryllium 17.1 available

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

grEEtZ
[Android Software Development] PhatUgly:
How fast do updates to microg usualy make their way into the lineage builds, and is there a way to check which version they contain? I just updated to latest klte weekly and was hoping to get the fresh covid api from microg core 0.2.12, but it still contains 0.2.11
[Android Software Development] kurtn:
F-droid should update microG core as soon as microG repository is downloaded