yashsingh1/xdaforums huggingface dataset:
[Android Software Development] heinhuiz:
I'm running LOS20 on lmi. It might be caused by Magisk, I didn't hide root. Thanks for trying.
[Android Software Development] enodo:
I got a Pixel 6a (bluejay) for my son, whose carrier is Mint (MVNO of T Mobile). I flashed LOS4mg (20240303) on it, and it worked, except that after about 1/2 hour or so it always fell off the Mint network. Rebooting the phone would sometimes, not always, fix this issue. I saw some posts on reddit that said that the 6a has some bug in the modem code, and that in particular it can have trouble with Mint (pixel_6a_and_mint_i_keep_falling_off_the_network). Everything works fine with his sim card in my phone (a Pixel 5a - a much better phone, BTW), so that lends some credence to that.

I have gone back and reflashed the April Android 14 stock image on it, and it appears to be staying on the network. Will it work to simply perform an "upgrade" to LOS4mg without going through flashing all the other partitions (boot, dbto, etc)?

Has anyone else seen this sort of issue?
[Android Software Development] mohama071:
the appearance of lineage-21.0-20240508-microG-husky I want to try it later...thanks developer
[Android Software Development] borisSweden:
I got to ask this as people here don't use Google Apps. Do you have a very low download speed for Wifi. Because something missing or there is a Google dependency that enables high speed.

I tested with real MAC address, no special DNS, no VPN and yet the download is still low compared to upload. I get on 5Ghz AX mode 200 down, 500 up.

So is this very common in the custom ROM world?
[Android Software Development] kurtn:
That's not missing GApps. That's your internet service provider. They sell ADSL - the A stands for asymmetric
[Android Software Development] borisSweden:
Naw its fiber and cabel does deliver 500/500. On a iphone it does get up to 400/400ish mbit/s
[Android Software Development] petefoth:
No. WiFi download speeds on my devices with custom ROMs - all without GApss - are comparable with speeds on other devices using WiFi
[Android Software Development] kainisenni:
Please pull the latest build for kane, it contains a bug that prevents the phone from recognizing its password, as I just learned the hard way.

Then a related question: Can I sideload the next version of official LOS 21 over the current LOS for MicroG 21 version?
[Android Software Development] petefoth:
Done. Thanks for the tip

You should be able to, but you may lose the microG components, including F-Droid. If you try it, please do report back and let us know how it went
[Android Software Development] kurtn:
I've been flashing lineageOS nightly/microG back and forth. It's easy with lineage recovery, as long as you don't install GApps.
[Android Software Development] petefoth:
According to this change, that bug also affects troika. I'll remove that build as well once it is made
[Android Software Development] kainisenni:
I really needed a device with mobile data, Signal, and a convenient camera quickly due to some... events... going on at my university, so I ended up resetting and installing the April 29th build of official LOS (did a reboot as well, it recognized my pin).

I tried sideloading that (older) build at first, but whether it worked or not, it didn't recognize my password (and switched from slot A to B).
[Android Software Development] yipeekayay:
is there a reason RCS chat blobs have been removed from carrier in los4microg, RCS chat seems to work fine in Los with gapps.

just curious if it was because of security? or just a choice as in divestos

thanks
[Android Software Development] petefoth:
We don't remove anything. We build from the LineageOS rrpos, with binary blobs from TheMuppets repos
[Android Software Development] heinhuiz:
I used the old version until it stopped working today. For the new app, just adding it to Magisk's denylist was enough.
[Android Software Development] rucolar:
Hi, i noticed that there has been no monthly build for FP3 so far, which also got added to the 21 device roster recently. I assume it will be created once the current run is finished?

Anyway, thanks for your work and support!
[Android Software Development] petefoth:
FP3, along with akari, akatsuki, alioth, aurora, chiron, sagit, &xz2c, got 'promoted' to 21.0 after the 21.0 builds started on May 1st, and before the 20.0 builds started yesterday.

I will try 21.0 builds for all these devices once the 20.0 builds have completed
[Android Software Development] rucolar:
That makes sense, thank you for clarifying.
[Android Software Development] david003:
I notice there's nothing for sweet this month, either. Is it the same thing (21.0 coming soon)? Not a big deal if this month gets skipped, just curious.
[Android Software Development] Malko007:
I do not understand David. 21 is available on the website but not direct update
[Android Software Development] Malko007:
Anyone has some issue with the fingerprint sensor since the update?
[Android Software Development] petefoth:
It's on the list of 20.0 devices so it will be built quite soon: the 20.0 build run has reached `quill`, so not long to wait https://github.com/lineageos4microg/docker-lineage-cicd/issues/623
[Android Software Development] david003:
I think 21 is coming soon for sweet, but it's not ready yet.

I'm on the Matrix chat, but for some reason it takes a long time (several minutes) to load new messages, so I didn't see there's still builds running.
[Android Software Development] petefoth:
Each build takes between 2 & 3 hours. Matrix channel reports start and finish of each build
[Android Software Development] david003:
Right, what I mean is that it takes several minutes for the new matrix messages to load. Maybe it's my client. I'm using fluffychat. So I started it and went to the last message, and it showed the last build on Wednesday or Thursday, so I thought they were done. After maybe 5 minutes, reports of new builds started to show up.
[Android Software Development] Omar_62:
pls make for i9500!
[Android Software Development] kurtn:
The exynos S4 ? Not officially supported by lineageOS. But if you have a no-GApps custom ROM, i can help you with microG.
[Android Software Development] espionage724:
I'm not sure how LOS4mG handles it, but with LOS they usually release a new build Wednesday morning, and I just change some dates around on the URL if it's not on the downloads page; usually works :p
[Android Software Development] petefoth:
If it's supported by LineageOS we build it. If it's not supported by LineageOS, we don't.
[Android Software Development] Omar_62:
there are unofficial builds
[Android Software Development] Omar_62:
I do have one
[Android Software Development] petefoth:
I can't find any recent unofficial LOS builds for this device. The latest I could find in XDA is LOS / CM 14.1. If you can ind an up-to-date unofficial build of LOS, then building LOS 4 microG is very straightforward, as described in our documentation
[Android Software Development] Omar_62:
okay, will try :D
[Android Software Development] kurtn:
Or that patcher

Nanolx.org Downloads Archive
[Android Software Development] masscream:
Hello, please is there a plan to make a ROM for version LOS 21 for Google Pixel (sailfish)? It's confusing cause 20 is available since February, then a brand new official LOS 21 (without MicroG) has been released and then the whole phone was removed from support. So, it's hard to think about the future. Thank you, also for your hard work.
[Android Software Development] kurtn:
In your case i would try DivestOS. It has slightly restricted microG support.
[Android Software Development] petefoth:
No plans at the moment.

In the February build run, it was in the list of 20.0 devices, and was successfully built.

In March it was in the list of 21.0 devices, but didn',t get built before the builds started failing due to the build-breaking QPRS2 changes

In April and May it was not in the list for any builds, because it has been removed from the LOS build target list

If the device is added back to the build target list in future, then we will make a build for it
[Android Software Development] masscream:
ok, thanks.
[Android Software Development] Luchtafweer:
The latest update did not install on miatoll. It gave errors and the phone booted into recovery.
[Android Software Development] petefoth:
Then probably best to try re-installing the previous version

I have created an issue in our issue tracker, and I have removed the latest build from the download server.

Looks like it may be an upstream problem: see https://discord.com/channels/628008280605589549/653821647102672926/1242131093705195521
[Android Software Development] 2faraway2:
Hi Pete, any idea what's wrong with alioth ? Not that it's urgent, just wondering why 21.0 isn't built in may so far ..
[Android Software Development] petefoth:
It wasn't in the 21.0 build list when the build run started on 1st May. It was 'promoted' to 210 two weeks ago, so it wasn't on the list of 20.0 device when we started building them.

I kicked off 21.0 builds for all the devices in the same position (akari akatsuki alioth aurora cheryl chiron davinci FP3 FP5 kane lmi sagit sweet troika xz2c) a couple of days ago. All those builds succeeded except alioth and lmi, which failed with the same error, caused by a missing vendor-specific module. This will probably be fixed the next time we build. If I have time I could try another build for these two devices, but you may have to wait until next month's build run
[Android Software Development] 2faraway2:
Ok, no worries, take your time and thanks for clarification !
[Android Software Development] heinhuiz:
Ooh is lmi going to 21.0 now too!? Then soon I'll have work to do :cool: I just updated mine to the latest (and last) 20.0.
[Android Software Development] petefoth:
Don't hold you breath! The 21.0 builds for lmi & alioth are still failing, so I've kicked off 20.0 builds so you at least habe an up-to-date build to install. We'll see what happens with 21.0 builds in the June build run
[Android Software Development] heinhuiz:
Oh okay thanks I understand. I'll just go back to patient mode 😴

Xiaomi POCO F2 Pro / Redmi K30 Pro - LineageOS 21.0

LineageOS 21.0 Changelog for Xiaomi POCO F2 Pro / Redmi K30 Pro (lmi). This page is listing the official LineageOS 21.0 (Android 14 14) changes and downloads for Xiaomi POCO F2 Pro / Redmi K30 Pro (lmi).

www.lineageoslog.com
[Android Software Development] heinhuiz:
Lmi 20.0 was built again, was there a special reason for that?
[Android Software Development] petefoth:
Because I retried 21.0 builds for alioth & lmi, and the builds failed again. The last successful build for alioth was in April, so I started 20.0 builds for both devices, failing to spot there was a successful 20.0 build for lmi on 17th May. Sometimes I make mistakes ;)
[Android Software Development] ewong3:
Help - cannot change SMS permission for App

on latest 20240508 microg for LOS21 on OP9p, and one of the apps needs to access SMS for verification, but none of the options in settings allows adding of SMS permission to any App.

Is there a way to do this, including CLI? Should this be a feature supported by microg LOS for a future version?

Thank you in advance...
[Android Software Development] petefoth:
If the app needs the 'SMS' permission, you set it via the App info screen: Settings | Apps | Show all |Select the app , and you should see a screen entitled 'App info'. Click on Permissions, and check that SMS is in the Allowed list.

This is normal Android behaviour, not specific to los4microG
[Android Software Development] ewong3:
yes that was what i did, but although the app needed sms access it is not listing one permission as available to activate:

even hitting 3-dot / all permissions does not give SMS as option, so could this be app developer's oversight (unlikely as they may be writing it for gapps support?) or do i otherwise need to CLI add this line?
[Android Software Development] petefoth:
If the app needs the SMS permission, then it's up to the app developer to specify that in their code.

In my experience, most apps that use SMS to get an authorisation / verfification code don't request the SMS permission - you are expected to receive the SMS with the code (in your normal messaging app), then either copy the code or eneter it manually in the requesting app.

Anyway, this is not specific to lineage4microG
[Android Software Development] ewong3:
thank you, it seems using oos does not have the issue, so could be some google close source routine the app was calling to capture the SMS there...
[Android Software Development] EllieCat:
LineageOS for microG

lineage.microg.org

Recommended LineageOS version is 15.1, 16.0, 17.1 or 18.1
[Android Software Development] Mthawk:
Thanks I guess. All I see available in downloads is Lineage OS for microG 21.0
[Android Software Development] EllieCat:
That was for the major version.

I found LineageOS 21, but the files are a bit confusing.

/

For some odd reason, the URL keeps changing to a slash.
[Android Software Development] Mthawk:
I have been using LineageOS for years installed using adb and TWRP without rooting on Motorola G7play .

I am confused by the files listed for the LineageOS for MicroG project here, "channel" for my model phone. With plain LineageOS, there is a single zip file, my last install was :lineage-20.0-20240124-nightly-channel-signed.zip

For LineagOS for MicroG there are 6 files. Three are shasum, but I don't know what I need here, boot file, dtbo file, and what looks to be a standard zip file. Is that zip file all I need same as my previous intstall using TWRP?

These are the latest available from LineageOS for MicroG

lineage-21.0-20240504-microG-channel-boot.img	20 MiB	05/04/2024, 09:27:10 AM
lineage-21.0-20240504-microG-channel-boot.img.sha256sum	112 B	05/04/2024, 09:27:15 AM
lineage-21.0-20240504-microG-channel-dtbo.img	1.5 MiB	05/04/2024, 09:27:10 AM
lineage-21.0-20240504-microG-channel-dtbo.img.sha256sum	112 B	05/04/2024, 09:27:15 AM
lineage-21.0-20240504-microG-channel.zip	910 MiB	05/04/2024, 09:27:04 AM
lineage-21.0-20240504-microG-channel.zip.sha256sum
[Android Software Development] petefoth:
Why are you recommending out-of-date versions? All supported devices now have 20.0 or 21.0 builds. For devices that stopped being supported after 18/0, the final vresions are available at https://download.lineage.microg.org/archive/. i strongly recommend using the most recent version available for your device
[Android Software Development] EllieCat:
Posts were moved from another thread. Just letting you know I was helping someone who had an older device. Sorry for the misunderstanding.
[Android Software Development] heinhuiz:
New 21.0 build for lmi is working fine 🥳 Thanks a million!
[Android Software Development] petefoth:
LineageOS also ships these files: see https://download.lineageos.org/devices/channel/builds

`boot.img` is the recovery - see https://wiki.lineageos.org/devices/channel/install/#installing-lineage-recovery-using-fastboot

`dbto.img` is not mentioned in the LOS installation instructions so is not needed

the main ROM `.zip` file (latest is lineage-21.0-20240603-microG-channel.zip) is the file you need to install. This is a lineage-21.0 / Android 14 build and your last install was lineage-20.0 / Android 13, so you are upgrading, and you should flow the instructions at https://wiki.lineageos.org/devices/channel/upgrade/. These instructions pretty much say 'Flash the new zip file using `adb sideload`', but take note of their warnig:
[Android Software Development] Mthawk:
Thanks, that's really helpful. I'd rather wipe and install as new installation, Can I use TWRP instead of lineage boot?
[Android Software Development] kurtn:
Your device has an a/b partition scheme. Better follow the lineageOS installation instructions.

Install LineageOS on channel | LineageOS Wiki

wiki.lineageos.org
[Android Software Development] petefoth:
New microG location API endpoint​

Check out this comment in the `microg/GmsCore/` issue tracker and subsequent replies.

You can update to v 3.2.2 using F-Droid (by checking 'Allow Beta updates` in the 'three dots' menu for microG Services), by editing microG Settings -> Location -> ... -> Configure service URL

If you try, you could give feedback - positive or negative - by adding a comment to that issue
[Android Software Development] kurtn:
Crazy! And /e/ has also an own provider but different result
[Android Software Development] petefoth:
Why crazy? There needs to be a replacement for Mozilla Location Services, and the microG project seems like a good candidate to implement and maintain such a replacement.

As /e/ are supporting / sponsoring microG development, chances are the two can come together (if they haven't already)
[Android Software Development] heinhuiz:
You mean v 0.3.2.2xxx of microG Services, I suppose?
[Android Software Development] ChotiKing69:
lineageos with micro g is actually a godsend project. My old oneplus still has life in it thanks to you all!
[Android Software Development] petefoth:
Yes
[Android Software Development] heinhuiz:
Can I just uninstall my current version 0.2.27 and then install the F-droid version? I got mine preinstalled with LOS4mG, so it is signed with a different certificate. And will it not get overwritten with the next LOS4mG update?
[Android Software Development] petefoth:
No need to uninstall: you are installing an update. (And F-Droid is a system app: it isn't easy to uninstall system apps, because that's not something you should ever need or want to do)

No it's not. We ship the (prebuilt) version, built by microG, and signed with their key. The update comes from the microG F-Droid repo, is built by microG, and signed with the same key.

No. The original version, shipped with your last update of LOS4microG, is a system app, and lives in the system partition. Any updates since that version, will have been installed to the data partition. If you install the v0.3.22 beta update, that is also installed to the data partition. The next LOS4microG update will include the latest stable version, which will probably be v.2.2.27 again, That version will be installed on the system partition, and - so long as you have 'dirty flashed' and not wiped your data partition - the v0.3.22 beta update will be untouched on your data partition. When the app is run, the system works out that the version in `data` is newer than the version in `system` so runs the newer version.
[Android Software Development] 2faraway2:
Yipp, microG services core ... ;-)

@Pete:

Where is 'alioth' in the current build run ?

I'd expect that it'll get an A14 build, but I can't see any actual june build right now while the A13 builds just started today ..
[Android Software Development] petefoth:
It was near the start - we do them in alphabetcial order - and it failed. It was an upstream problem: at the time of building the last successful upstream build was on 15th May and subsequent builds failed (22nd & 29th May). It seems the upstream problem is now fixed.

It is on the list - in first place - of 21.0 builds to retry when the build run completes.
[Android Software Development] 2faraway2:
Ahh ok, I see, thanks for that positive information :-)
[Android Software Development] heinhuiz:
You are right. I tried it with Droid-ify first, which complained about the certificate even before downloading. But the F-Droid app itself does indeed download and install it :unsure:
[Android Software Development] fassal:
Is there a way to get older builds? I am looking for the latest LineageOS 20 for Pixel 4a sunfish. It is probably named lineage-20.0-20240208-microG-sunfish.zip.
[Android Software Development] kurtn:
LineageOS Build Archive
[Android Software Development] heinhuiz:
Maybe it's good to put this link on https://lineage.microg.org/ and/or in the OP of this thread. It is often asked for.
[Android Software Development] petefoth:
That appears to be normal LineageOS, not los4microg. For the microG builds, I tidied up (i.e. removed) the 20.0 builds from the archive server once we had two 21.0 builds with no major issues reported. We don't have enough disk space to keep more than two builds per device. Sorry
[Android Software Development] petefoth:
In recent semi-official builds of yoshino devices (`lilac`, `poplar`, `maple`) there is an issue with audio playback: playback stops at the end of a track instead of automatically continuing with the next track in the queue. Until a fix is made in the code and included in new builds, it can be worked around using rooted debugging

adb root
adb shell "mount -o rw,remount /vendor"
adb shell "sed -i '/debug.stagefright.omx_default_rank.sw-audio/d' /vendor/build.prop"
adb reboot

The bug can be tracked here:
[Android Software Development] rucolar:
I noticed that the FP3 appears to have been skipped in the current 21 build run. Is there a problem with this device? A timely build would be great to get this months security patch, among other things.
[Android Software Development] kurtn:
It was added to the official list after start of builds

hudson: Revive FP3 · LineageOS/hudson@0a98ff7

Change-Id: I38ce4bf826c9c6fa83eceb5a93290a44e0208b19

github.com

Wait for next month's round
[Android Software Development] petefoth:
As @kurtn says, it wasnt in the list of 21.0 devices when the build run started.

If there's time once the build run is complete, I will try to build for all the devices which have been `promoted` since the build run started: currently that list includes `grus, pyxis, vela, FP3`
[Android Software Development] rucolar:
Thank you for the clarification. I think this exact thing happened like two months or so ago as well, when FP3 was first 'promoted' to 21.0. Last months 21.0 build run went as expected with FP3 tho.
[Android Software Development] humpty321:
Since my device is running 21-20240703-microG-bramble I can no longer edit recurring events in org.lineageos.etar (Version 14). When I try to edit such an event, etar tells me "Before you can add an event, you must add at least one calendar to your device". If I then add yet another calendar, I still cannot use it for the event that I want to edit. The issue does not occur when editing non-recurrent events.

Well, as I said, I only want to edit an already existing event in an already existing calendar.

Is this a known issue? Btw I could not find a better place to ask.
[Android Software Development] petefoth:
That doesn't sound to me like an issue that is specific to LineaageOS for microG. More likely to be a problem in the upstream LineageOS. You could check if it has been reported in the LineageOS

issue tracker

Discord

Reddit

But bear in mind that, in all those communities, if you mention you are running LineageOS ***for microG***, they will likely just say 'We don't support that' and ignore you. And if you try to raise an issue. make sure you follow the guidelines ***exactly*** or your issue will be automatically closed with the comment "You didn't follow the guidelines". Unfortunately, the LineageOS 'support' channels are very far from being the most helpful and supportive :)
[Android Software Development] humpty321:
Thank you! I could not find this issue there and also not at Etar. And I don't ask the LineageOS people any questions for the reasons you gave.

Instead, I chose the simple solution of replacing org.lineageos.etar by org.fossify.calendar (Events exported / imported; Etar disabled).
[Android Software Development] kurtn:
Yes, paranoia can really drive you crazy when not knowing whom to trust.

Signature spoofing is one of the smaller problems in this context. If you flash something or grant root permission, that piece of code can do really bad things. To pretend being an other app is by far not the biggest danger.