yashsingh1/xdaforums huggingface dataset:
[Android Software Development] bege10:
The updates for Samsung Galaxy S5 Plus (SM-G901F) caused boot loops for quite some time, also LineageOS without microG. Since the updates from end of October both OS work again, but for LineageOS for microG the updates don't continue. Is there a place to report missing updates?
[Android Software Development] kurtn:
https://github.com/lineageos4microg/docker-lineage-cicd/issues

There was an issue with official lineageOS not booting.
[Android Software Development] bege10:
I know. This has been solved https://xdaforums.com/showpost.php?p=83832517&postcount=2625 and the first update of LineageOS for microG since works on my phone also. LineageOS updates continue (November 5) but not LineageOS for microG updates. That's why I ask where to report the missing update.
[Android Software Development] kurtn:
Kccat6 was not missing. It's just being built inline with all other 16.0 devices. It's not synched to official lineageos.org builds.
[Android Software Development] bege10:
There used to be an update of LineageOS for microG a few days after the weekly update of LineageOS and there was no update of LineageOS for microG for the November 5 update. But I just saw that for both OS there arrived an update a few hours ago. So thanks, the issue seems to be obsolete.
[Android Software Development] KevinCTofel:
After using GrapheneOS for a few days on Pixel 4 (flame), I decided to try LineageOS and then saw LOS with micro G. For some reason, when trying to sideload the latest image, the install fails saying that it would be a downgrade based on the timestamps. I've tried in both the LineageOS recovery and via TWRP with the image on my Pixel 4 but nothing seems to get this installed. I'm sure I'm missing something super simple but I'm at a loss. Any ideas?
[Android Software Development] guillermohs9:
I think I had a similar issue when using a recovery build that is dated as newer than the date of the build of the rom... I may be way off, but I'd check that
[Android Software Development] :
Is /system supposed to be r/w already. I simply flashed the latest 17.1 rom and Magisk 20.4 using the TWRP 3.4.0.

My device is Oneplus 3.
[Android Software Development] kurtn:
No. To write /system you boot recovery or create a magisk overlay. Like systemless hosts.
[Android Software Development] :
Weird, i might just reflash it just to see what causes it to go r/w
[Android Software Development] kurtn:
Or you write in booted 17.1 and check in recovery.
[Android Software Development] heinhuiz:
[MENTION=4316015]Simon94[/MENTION] (or maybe [MENTION=8031265]kurtn[/MENTION]) can you tell more about the current status of this? Currently, builds seem to be about monthly or 3-weekly at best, so apparently not automated yet. Is there something we as users can do to help improve this situation?
[Android Software Development] kurtn:
We are talking about well aged android 9 and 10 versions. There is not much happening besides monthly security patches. I'm fine with monthly builds.
[Android Software Development] heinhuiz:
I can agree with that, although for my device the updates seem to come just before the next security patch. But I was not complaining, just wondering if there is any progress or maybe extra donations are needed.
[Android Software Development] petefoth:
I am trying to build for Sony Xperia Z5 Compact, using the 'Lineage OS for Microg' docker image from https://github.com/lineageos4microg/docker-lineage-cicd

I have a local manifest with the following content

```

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="The-Muppets/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="lineage-17.1">

</manifest>

```

which should pickup the manifests from https://github.com/TheMuppets/manifests/tree/lineage-17.1

When I try to build I get the following error during the 'repo sync' stage

`fatal: could not read Username for 'https://github.com': No such device or address`

Any clues what the problem could be? (I have used DuckDuckGo but not had found anything useful and I'm at a bit of a dead end)

Thanks
[Android Software Development] petefoth:
Solved: The answer is that you get this error message when there are typos / stupid mistakes in your manifest.

The corrected line is

<project name="TheMuppets/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="lineage-17.1">

removing the - character in The-Muppets

Sorry to have bothered you
[Android Software Development] lutz51:
Hi,

I have a question about the update process for los for microg.

I've always assumed that an update would start automatically when an update from LineageOS is available.

It doesn't seem to work with my device (fajita). There have been 2 updates to LOS, but none to LOS for Micorg ...

Can there be an error in the update process?
[Android Software Development] kurtn:
Lineage.microg.org not synced with lineageos.org [MENTION=5966764]lutz51[/MENTION]
[Android Software Development] lutz51:
Thank you very much, then I got it wrong.
[Android Software Development] andruyd:
Is it safe to flash vanilla LineageOS over the LineageOSforMicroG or would it make the system unstable? Lg v20 on 17.1.
[Android Software Development] kurtn:
Should be no problem for stability. But vanilla is signed with a different key. How do you intend to flash it?

Flashing GApps will make the system unstable.
[Android Software Development] andruyd:
I'm already running the latest LineageOSformicroG for my device. I was going to flash the latest mainline image over it. Do you mind explaining what this key is for? What are the consequences of changing the key? Sounds too important for me and makes me think to just stay put. I've been mucking around my phone for a few days now and I just want to stop with all the customization lol

Oh yeah I've got no intention of flashing any official Gapps. I'm just starting on my degoogling|lessgoogling.
[Android Software Development] kurtn:
How about just disabling every microG setting? That should be close enough. The key thing will probably stop twrp from flashing. Try it.
[Android Software Development] Aqq123:
As [MENTION=8031265]kurtn[/MENTION] said, the signatures will be different. If you are keeping the /data partition (I assume this is what you mean by flashing one over the other), the package manager will remove metadata for all packages with mismatching signatures in /data/system/packages.xml and you'll end up with a boot loop. At that point it's also practically impossible to recover because some of the necessary data will be gone.

It'd be best not to do like that but if you really wanted to, you'd have to manually change the signatures in /data/system/packages.xml to match the new build. There is a script to do this

the other way

(from the official LineageOS to LineageOS MicroG). I'm not sure if it's being kept up to date but it's a good start: lineageos-for-microg-keys-migration.zip. It'd be a good idea to have a backup of your /data partition in case things go south.
[Android Software Development] kurtn:
@n0me I see nothing strange except SD card being f2fs. Possible trouble makers: using SD as adopted storage, encryption.

Worst case you have to clean flash 17.1

Can you try to install the twrp version you made the backup for restoring?
[Android Software Development] n0me:
@kurtn Thank you for your quick response!

It's true, I use adopted storage, but the phone isn't encrypted. Is using adopted storage rather not recommended with custom ROMs?

I installed TWRP 3.4.4.0 and made a full backup with it before flashing 17.1. I already tried to restore this backup after doing a factory reset, but I end up in Odin mode bootloop after restoring. Makes me wonder what the backup function is worth after all :confused:

Meanwhile I also tried doing a factory reset and flashing 17.1 afterwards which worked flawlessly. But then I have a clean 17.1 and my data is all gone. I still have a full Titanium backup. But I wonder if Titanium would be able to restore system apps, user apps and app data after upgrading from 16.0 to 17.1, since there should be changes in the Android system with the upgrade. Might this be a working solution to get back all my data?
[Android Software Development] kurtn:
@n0me i usually don't restore backups. I use each chance to get rid of unnecessary stuff. And I use SD only in ext4 and as portable storage.
[Android Software Development] n0me:
Thanks for the reply. So, no luck for me...
[Android Software Development] n0me:
Anyone else who might help me out?
[Android Software Development] n0me:
I did succeed in restoring my phone back to its original condition by following this way: clean install of LineageOS 16.0, install of LineageOS for MicroG 16.0, restoring my original TWRP backup of 16.0.
[Android Software Development] Listerine:
So I recently installed Lineage OS with MicroG; on the official website, it says that it supports weekly OTA updates.

To update the phone, do I just go to System -> Updater and click on the downlink link? Or will that download the other LineageOS branch (w/o MicroG?)

Aurora Store is installed. When I click on apps, it says the MicroG core can be updated. I'm assuming since that comes from google, that I'm not supposed to update it through Aurora Store / Google and to decline those updates?

I wanted to see if I had VOLTE & Wifi Calling. So I dialed the *#*#4636#*#* and it shows that VOLTE and Wifi Calling are "provisioned." But when I click on IMS Status it says that VOLTE is available but Wifi Calling is unavailable. What does that mean?

As far as I know, I installed it correctly, and wiped everything that was recommended for a clean flash as per the guide. I installed my fitness tracker app, and once I logged in my watch automatically connected and synced via bluetooth to the phone. How does that happen - I thought I had to repair all bluetooth devices with my phone once I installed a new ROM and wiped everything.

I factory reset the phone once I got the Lineage with MicroG ROM, but it didn't delete all the stuff on the phone - pictures and other files were still located there. Is that normal behavior? I had to go to TWRP to remove everything.

I admit I'm not terribly knowledgeable about all this stuff but I can follow directions, which is how I was able to install this ROM without any significant issues. Thanks for the help.
[Android Software Development] kurtn:
OTA updates from Lineage.microg.org - no Problem.

Aurora store confuses microG with Google play services. F-droid confuses microG with unifiedNLP. Update that.

I prefer not using proprietary fitness apps. Check gafgedbridge for compatibility with your tracker.

No idea with the other Findlings.
[Android Software Development] esl_dniw:
I've used LineageOS for MicroG for over a year now, and very happy with it. (dipper on Mi 8)

But with the latest update from Jan 8th, all audio is broken. Updating my firmware didn't help. After searching, this seems a generic issue with LineageOS:

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

Suggest you consider taking the latest updates offline

Any advise how I can downgrade to the build from Dec 3rd without having to format data??? After wiping system, dalvik and cache, and installing the Dec build, I don't get past the MI logo and then it brings up TWRP again. Same when doing this without wiping system.

Alternatively, any chance of another build e.g. based on a previous LineageOS update that works without formatting data?

Currently bit of a dilemma: living without the audio until next update, or needing to spend a lot of time on reinstalling apps/data...
[Android Software Development] kurtn:
Already reported

Withdraw & Rebuild builds affected from broken sound · Issue #135 · lineageos4microg/docker-lineage-cicd

Hi, sound is broken on my Mi Mix 2S. Issue has already been reported by many users on XDA: https://forum.xda-developers.com/t/rom-official-lineageos-17-1-weeklies-for-xiaomi-mi-mix-2s.3974661/page-...

github.com
[Android Software Development] Topicat:
Anyone else uses a Samsung S4 (JFLTEXX)? Mine has been resetting a lot for the last month or so after an OS update.

Is it my phone in particular or is this a problem with the LineageOS for MicroG release?
[Android Software Development] John M Michael:
Hi,

I didn't succeed installing lineageos-microg on my Google Pixel 3. Installation in recovery fail. I suspect a problem of signature spoofing (here my post).

My question is : did somebody succeed ? If yes, could you help me by describing the method ?

thanks for all.
[Android Software Development] kurtn:
I think, that is relevant for your case

provide recovery images · Issue #134 · lineageos4microg/docker-lineage-cicd

There are some devices where one cannot use TWRP as recovery to flash lineageos4microg like sargo (pixel 3A). There is one solution described here how to use an official lineageos recovery and exch...

github.com

I would install official lineageOS and nanodroid patcher and minmicroG minimal.
[Android Software Development] John M Michael:
Hi,

Thanks.

That the method i followed before asking for help.

I didn"t found many more ideas, so i tried again then .... alleluia ! all works now.

So i can say now i've got a pixel 3 perfectly functional that turns on lineageos-microg 17.1

If i did it, you can do it too.
[Android Software Development] tommla:
I'm sorry, but I have to ...

When will be a new version Lineage.microG for Ginkgo?
[Android Software Development] kurtn:
One was removed because oft a bug

Withdraw & Rebuild builds affected from broken sound · Issue #135 · lineageos4microg/docker-lineage-cicd

Hi, sound is broken on my Mi Mix 2S. Issue has already been reported by many users on XDA: https://forum.xda-developers.com/t/rom-official-lineageos-17-1-weeklies-for-xiaomi-mi-mix-2s.3974661/page-...

github.com
[Android Software Development] braveheart_7:
Hi, When will Lineage OS with microg be updated for Payton/Moto X4 to include the " persist sehash fixes " ? Latest build on https://download.lineage.microg.org/payton/ causes reboot when botting up.
[Android Software Development] kurtn:
Could you please report here for simon to remove?

Issues · lineageos4microg/docker-lineage-cicd

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

github.com
[Android Software Development] braveheart_7:
The best I can pass on would be these threads:

https://xdaforums.com/t/rom-official-payton-nightlies-lineage-os-17-1.3802265/page-93

https://xdaforums.com/t/rom-official-lineageos-17-1-nightlies.4076569/page-15#post-84231405
[Android Software Development] braveheart_7:
Also posted here: https://github.com/lineageos4microg/docker-lineage-cicd/issues/149
[Android Software Development] nsiti:
Hi, is there a place to check for upcoming official LOS microG builds? In other words, devices that are in the pipeline? Thank you.
[Android Software Development] kurtn:
Depends on what pipeline you mean. The upstream lineageOS pipeline can be seen in gerrit/Hudson.

Running build rounds can be seen if you order download.Lineage.microG.org by date. Usually an android version runs in alphabetical order.
[Android Software Development] nsiti:
Let me clarify. My current phone OG Pixel running LOS microG is reaching the end of its life. I would like to buy a new phone (hopefully less than 1 year since release) that will work with LOS microG. Where can I see which will be the next devices (with dual SIM) to be supported by microG? For example, how can I track when the Pixel 5 or the OnePlus 8T become official? And if anyone has another recommended phone, feel free to let me know. Thank you.
[Android Software Development] kurtn:
T

That's just guessing and extrapolation. And not a microG question. Premium pixels have a good track record. I prefer used phones.
[Android Software Development] ceroberoz:
Hi,

Previously I see falcon on device list but now its gone.

Do you have some archive? I need the last build to resurrect my old good falcon.

Thanks.
[Android Software Development] kurtn:
Sorry, no. Maybe you find non-microG lineageOS.
[Android Software Development] kurtn:
Starting with today's builds, lineage4microG has it's own recovery. Difference to original lineageOS recovery is the changed signature check. So lineage4microG installation and update can run without user intervention
[Android Software Development] Demodroid:
Last official builds were for LineageOS 14.1. You may still be able to build this using Docker, or alternatively, download an unofficial ROM and use NanoDroid to patch.
[Android Software Development] saint6822:
With this require a clean wipe of an existing install with twrp active?
[Android Software Development] kurtn:
Twrp is not "active". In a-only devices you have two independent partitions with two standalone operating systems. When you run lineageOS, twrp is inactive. When you are in fastboot/download mode, both are inactive.

You can replace twrp with each recovery you like. You will see a difference only when booting recovery or during System update.
[Android Software Development] heinhuiz:
Not primarily a LineageOS for microG issue but relevant for everybody that does not want to include Gapps:

I just stumbled upon the fact that LineageOS has included Seedvault backup. It can do automatic and manual backup to the device itself, a plugged in USB flash drive or an external server.

For the moment, there are a few issues that limit the possibilities, like the inability to backup the Work profile when using Shelter (not Seedvault's problem and it will be solved in a new Shelter version), and the current limitation of the use of an external server to Nextcloud only (which should be addressed in a future Seedvault update).

Settings - System - Advanced - Backup. No root needed.

I did not see a major announcement of this important feature, so I thought it would be good to mention it here.

Enjoy :)
[Android Software Development] kurtn:
https://www.xda-developers.com/lineageos-seedvault-open-source-backup-solution/ :)
[Android Software Development] kurtn:
Normally there is no problem. And in case of problems you can always install or deinstall magisk from recovery.

Risk factors are magisk modules, encryption and outdated custom recoveries.
[Android Software Development] heinhuiz:
This is what @topjohnwu himself writes about OTA. I have one A/B device where I use the method described there - it seems complicated at first but is actually very easy.

On my other, A only, device I just flash the new zip from my computer using adb sideload, and on that one Magisk reinstalls itself magically 🧙‍♂️. Never tried OTA on that one because this method is simple enough and I don't want to run into trouble.

Both devices are encrypted, btw.
[Android Software Development] adinechin:
Hi, I'm building my own custom builds of LineageOS because it's not officially supported on my "old" device. Could you just clarify for me how to include microG in my builds using your repos ?

Do I just have to :

add android_prebuilts_prebuiltapks in a folder of my choice

add the apps I want in LineageOS's CUSTOM_PACKAGES (for example in vendor/lineage/config/common.mk).

Is that it ? Thanks for your help !
[Android Software Development] kurtn:
Yes. You should post in your specific device community. I think your device has been dropped by official lineageOS. So you should anyway scan a wider range of ROMs
[Android Software Development] XDADoog:
Good day.

Is there anywhere to find OLD LOS16+microg roms to download?

I´m looking for the last version of LOS16+microg for the Moto Z (griffin).

Yes, I know it has support for LOS17+microg, sadly I innocently updated, and sincerely, I just like the older version better.

LOS17+microg has quite a lot of nice features but LOS16+microg has "something" that makes my phone run just the way I love it.

Please, if anyone has the last version released for the griffin on LOS16+microg, please let me know, I would like to have a copy of that file, please.

Thank you for your attention.
[Android Software Development] HippoMan:
I'm wondering if anyone has come up with a method/workaround/hack/whatever to get LINE Messenger to run under LOS 17.1 with microG? That app normally needs Google access, but I'm hoping that perhaps someone might have come up with some sort of roundabout way to get it to run under microG.

Thank you in advance.
[Android Software Development] HippoMan:
I figured out a way to do most of what I want ...

LINE Messenger can only be associated with one phone number. I have another phone with all my LINE Messenger messages, contacts, etc. And there is a web app that allows any Chrome-based browser that can install Chrome extensions to provide secondary access to that main LINE account. So, here's what I did ...

1. Get a microG ROM installed and configured.

2. Install the "Kiwi Browser". It's a fork of Chrome for Android which allows Chrome extensions to be installed (the normal Android Chrome app does not allow the installation of extensions).

3. Install the Chrome LINE Extension in this Kiwi Browser, and configure it to access my main LINE account.

Now, I can run Kiwi Browser to start up this LINE Extension on the microG-based device, and can access all my contacts and messages for my default LINE account, and I can send messages, etc.

I still can't get the regular LINE app to run under microG (this is the LOS 17.1 version of the microG ROM for the Samsung Galaxy S5 [klte]). It just displays a green screen for a while when starting up, and then it terminates.

I'll still work on that, although my main needs are satisfied for the time being by means of this web-based LINE proxy.
[Android Software Development] paolone1:
Hello, some years ago I have used Lineage with Microg on my HLTE and I miss is semplicity. Now I have a Whyred. Some years ago this rom is nearly nightly, now I see the last build is made the 4 february in the official site.

Sorry to point this but I am using the xda app and there is no the "search" function
[Android Software Development] heinhuiz:
I'm wondering why someone would not want Google but instead use LINE to control their life... :unsure:
[Android Software Development] HippoMan:
Think about it some more.
[Android Software Development] kurtn:
What is the point to have "nearly nightly" ? I don't install custom ROMs that need such urgent bug fixes. An update after a month or two should be OK to get upstream security patches.
[Android Software Development] heinhuiz:
Yes well, that answer was to be expected from anyone that does not have an argument for himself. But this is not the place to discuss that. I'm even sorry I brought it up, I was just wondering. If you feel any urgency to explain why I should trust a Japanese/Korean company over an American one to benefit from collecting all my private details and communications, please do so by PM, but it might be wise for you yourself to think about it some more.
[Android Software Development] HippoMan:
That is not the only reason for such an answer, and you know it.

Anyway, I have business reasons for needing to use LINE. Some colleagues and clients are in Japan and they insist on using that message platform.

Also, I want to minimize my use of Google, but not because of data privacy concerns. They make things more and more complicated with their SafetyNet and other features as time goes on, and I find myself fighting with the OS more and more. I started with Donut years ago, when Android was a pleasure to work with. Now, I'm at Q, and it's getting more and more complicated to root my device because of Android's ever-expanding security model. It's almost as onerous as that of iOS these days. I'm just trying to get Google out of my life as much as possible, and moving away from gapps is a small but meaningful step in that direction.

LINE is a necessary evil for me, given my business. If my arrangements with those Japanese people ever end, LINE will go by the wayside also.

And now, I will ask *you* why you feel it is so important to you to jump to premature conclusions about other people's motives, and to then challenge those people on the basis of your projections.