yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
@ThE_MarD i think a large number of users are unable to OTA update while already on official. I will be performing a manual update in recovery now, but that's not ideal for the average user.

I just experienced the same problem as above ppl, today i tried updating to the new Official Build (20th April 2024 - from today) coming from official build version 2024-04-13, using OTA updater in settings failed with "Install Error".. sequence of events:

1. Successful download of OTA package, so "install" button appears. Click it, and it will start progress of "Preparing first boot" and "Finalizing package installation", the fail will occur in the "Finalizing" step, it wont really progress and after a short while, this bar:

Will return back to:

As if you didn't click "install" before (you did).. it's back there because it failed. You will only see the corresponding install error if you pull dropdown menu, as here:

Because i want my post to be a comprehensive bug report, i carefully filtered adb output while reproducing this issue, to keep only "updater" relevant lines. Attached below, the log file that captures the entire updating process from the very beginning to the end where it exited with "Install error" at the log's bottom (alternative: https://pastebin.com/mHUrXyWD):
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Following up on the above.. the way OTA fail ends in log is similar to mudtub's provided log.. from my log file in last post, i mean this part:

update_engine: [ERROR:postinstall_runner_action.cc(532)] Postinstall action failed.
update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished last action PostinstallRunnerAction with code ErrorCode::kPostInstallMountError

If it's some sort of mount failure due to QPR2, search this AOSP file for references of kPostInstallMountError: https://android.googlesource.com/pl...payload_consumer/postinstall_runner_action.cc to gain insights or searches for other devices and scenario's of similar faults: https://www.google.com/search?q=kPostInstallMountError

This is relevant to rtwo (sm8550 change) and to do with the same fail/error: https://review.lineageos.org/c/LineageOS/android_device_motorola_sm8550-common/+/379736

Jan 15, 2024
By: Marc Bourgoin

sm8550-common: Disable sparse for ext/f2fs images
* Sparse images cause kPostInstallMountError

Regression and again a bug related to sparse images? I provided some clues here, right?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Hmm, I'm thinking disabling sparse images was not the proper solution to the issue which is why we are experiencing it now when trying the Lineage Updater, so I'll try to revert it and try and figure out the real root cause to the bug
[Motorola Edge 40 Pro  / Moto X40 (China)] snlavaise:
Hi! The builds are getting stabler with each new reléase. As far as I tested the 20/4 release, i can say this is the only thing that don't work. The phone is not charging and it says that the battery data it will be displayed when the phone is fully charged. Also, it informs wrong estimated fully charge times when the phone it's pluged in.
[Motorola Edge 40 Pro  / Moto X40 (China)] snlavaise:
No. I'm with the last official nighlty build, rooted with magisk and with okay integrity fix module installed vía magisk. And of course, configured the denegation list in magisk app. I Even didn't needed to hide magisk app to get the phone certified by Play Store and all my banking apps seems to work fine.
[Motorola Edge 40 Pro  / Moto X40 (China)] snlavaise:
Have you enabled Zygisk and configured the denegation list in magisk app like this? Also remember to enable denegation list to system's app Google Play Services, then stop both apps from app config menu, and delete both cache and user data storage.
[Motorola Edge 40 Pro  / Moto X40 (China)] snlavaise:
This is the result I'm getting, the magisk modules i've got installed and the build I'm running. Wich by the way, with the Turnip GPU driver for Adreno 740, the system animations seems to run smoother as hell. Recognise i don't know if it's related with that or the build itself.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
A new test build is going up! It's uploading meow so it might take 30 mins. lineage-21.0-20240421-UNOFFICIAL-rtwo includes a sim slot stop/restart script to see if that helps those with SMS issues (please note! This build is SELinux Permissive for testing this! Tbh I'm not even sure if this works how I might even be able to make this script SELinux compatible) and also includes kernel platform updates including updating the display HAL to DISPLAY.LA.3.0.r1-10700-KAILUA.0 that matches our blobs too. I also reverted the disabling of sparse images to see if that helps fix using Lineage Updater so once this is flashed to your device please also try to local update with the same zip

Any bugs please report with logcat

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240421-UNOFFICIAL-rtwo at SourceForge.net

LineageOS for rtwo (Motorola Edge 40 Pro / X40 / Edge Plus 2023)

sourceforge.net
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi,

thanks for the update.

So the official one and the beta cant be installed.

I get the following Error:

Error applying update: 7 (errorCode: :kInstallDeviceOpenError)

Error: recovery: Error in /sideload/package.zip (status 1)

Install completed with status 1.

Installation aborted.

Edit./

Wow greate. Now i cant start my phone. It stucks on the Moto Logo.

Edit./

After screaming and installing the ven, boot etc. from signed version. Start the System. The error is displayed every time by installing the past few Images to the present one. Something was wrong between the image from 16th to 21ones

Edit./

So what i can say. I got the Asscard the only chance was to use super_empty to get my device back to live. Im out about Betas and use only signed. All my data was gone into the ****hole. Syncios want to connect , so i think its also an usb bug there.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
A new test build is up! lineage-21.0-20240423-UNOFFICIAL-rtwo contains source built display composer and kernel updates to accomodate it.

I didn't touch sparse images or SMS bug on this build, so if you did try the last build and have problems flashing please reboot to bootloader and reflash the images before rebooting to recovery

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240423-UNOFFICIAL-rtwo at SourceForge.net

LineageOS for rtwo (Motorola Edge 40 Pro / X40 / Edge Plus 2023)

sourceforge.net

@debx sorry that last test build broke flashing but as I just mentioned the solution is to reflash the images via bootloader to fix recovery so please try that. Test builds are to try and test stuff so hopefully they fix things but unfortunately sometimes it does break stuff
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
did you fix your device?
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Nope!

I had to reset and therefor i lost all my data!

Cant safe nothing of the previous apps because there is a usb bug. Only the super_empty.rom was the resolution. Also the official rom has a Bluetooth buh. Its needed few restarts from the phone to got stable work...
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
If anyone's interested, the long-standing SMS bug got fixed in one of the recent system changes (likely around QPR2), all SMS will be received without using airplane mode/reinsert SIM workaround. Random SIM connection loss issue that i may have been the only one to experience, is also resolved.

It's already all fixed in Apr 13's official build, but i would advise anyone to get the upcoming update in 2 days anyways; Saturday's official build will include a bunch of kernel/platform/CLO updates. For me personally, that day seems to be the perfect time for a clean install.

LineageOS for rtwo is in a better than ever shape
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Im on the 4/20/24 release on T-Mobile. The SMS issue is not fixed. The issue is also present in the 4/23/24 nightly.

I use tasker to fix.

But you are right, the team is doing great work!

Thank you all
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
Hi,

What tasker config have you set?

Thanks
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I'm also on T-Mobile in The Netherlands, and it's fixed here. Weird. I wonder what's making the different outcome per person.

Maybe we're missing something here.. such as, when certain carriers rely on QTI (Qualcomm Telephony Injection), and it was no longer technically possible in Android 14, therefore also since LineageOS 21, how did Android teams come to the decision to go ahead with it anyways? What's the solution offered to OEM's, im pretty sure that stock devices don't suffer from it, and then, how can custom ROM's implement it? Doesn't LineageOS have some team members that can dig into it and pry loose some information from the Android team/carrier industry?
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
on boot, disable sim 0, wait a few seconds, enable sim 0 . update : i attached my profile and task if you want to import them. it will shut off the sim at boot, wait 10 seconds, and turn on the sim. this is for slot 0 sim only. you can add slot 1 if you need to

the issue (as i understand it) stems from Qualcomm, and unless they release the source for whatever it is, it won't be fixed. issue is only on custom roms, bc official roms have proprietary code (not fully open source).

i was running crdroid as a test. the dev managed to fix SMS, but it always *says* it failed. however, his implementation does fix the issue. but has that annoying visual glitch. (also, at least for me specifically, i could not get phone calls to work, even with the sim pull-out)

if there is anything at all I can share, just say the word.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
A new test build is going up! It's uploading meow so it might take 30 mins. lineage-21.0-20240501-UNOFFICIAL-rtwo contains some changes to drop some unsupported bluetooth audio codecs from our AOSP bt stack (aptX tws, AptX Adaptive and celt) which is causing problems for bluetooth with a2dp offload which might be affecting the use/quality of some bluetooth audio devices paired to our phone.

This build also contains the SIM restart script and I was able to make it SELinux compatible so anyone with the SMS bug please test this too!

Any bugs please include a logcat with your report

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240501-UNOFFICIAL-rtwo at SourceForge.net

LineageOS for rtwo (Motorola Edge 40 Pro / X40 / Edge Plus 2023)

sourceforge.net
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
hi. im having the bluethood connection problem with the official build. now it disconect ,no stable connection.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
I think I also figured out what's going on with OTA... We were accidentally building with compressed VAB for OTA lol oof, so I changed that already. Originally I thought it was our bootctrl or gpt-utils, but no matter what I changed it wasn't that so that's a week and a bit of no luck there until I stumbled upon the VAB compressed lol

We will probably still need to manually update to latest next official before the next OTA should work though
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
I did get some replies from users on Telegram luckily who helped test the build and said the SMS bug is fixed for them and they tested multiple reboots which is good news and Bluetooth was also fine so both fixes are merged (y)
[Motorola Edge 40 Pro  / Moto X40 (China)] nTOHS:
Hello.After the last update can't instal magisk init.boot .
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
Tested latest official build: updated via LOS Updater without issues and SMS work! Thank you!

That's strange, I've been able to flash the patched init_boot without issues. Try with the --slots=all option.

Do you downloaded boot and init_boot images from LOS website?
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Why are you doing it like this? It is better to let the script run and work in recovery.

Download magisk27.apk. Rename it to magisk27.zip. Then adb sideload it. After boot, load magisk27, and tell it to do a direct install.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@maicol07 Lineage Updater worked without issues? Nice! I was concerned I might actually need to do more with bootctrl and gpt-utils which are super picky so I'm glad I don't have to touch them lol (y)

Also good news that SMS works fine. I did hear from a user with an Edge+ 2023 (RETUS) that they need an extra SIM ID added as theirs is different... I'll do a public test build with that as my concern is if I add an extra SIM ID I hope it doesn't break it for those who don't have that extra SIM ID on their variants
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Oof! The SIM ID that RETUS users might need seems to break SIM on my RETEU... so we probably need to figure out something else...

I heard that using salami (OP11) libqcrilNrSmsModule.so worked for some sm8450 devices so maybe it might fix the SMS bug for us? I'll try a test build with that I guess

Oh, I think I also might have a fix for MotCamera4 so I'll include that in the test build too
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Hmm. Possible to have an extra .zip for RETUS people to flash on top of ROM Including only that change?

Can we just flash to switch to RETEU? I suppose that would mean full data wipe though.

Only other option is two different builds which I know is a pain lol
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Hi. Has anyone else had full signal drop issues the last 2 days?

I'm on 21-20240420-NIGHTLY-rtwo (official). I use T-Mobile, RETUS fw, and have an Edge+ 2023. Signal keeps dropping randomly for no reason. Reboot, Sim toggle, airplane mode toggle, nothing fixes it. Have to wait like 10 mins for it to eventually pop back on its own. Data, SMS, voice, everything lost. No LTE, no 5G, no 2g/3g.

Would the RETEU fw be beneficial for me (based on recent posts). I also still have SMS issues on this build, so I use tasked to turn off and on the Sim at boot. (No, does not help with signal issue)
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 on LOS for rtwo we ship full device firmware to ensure everyone's FW matches the device blobs

I would recommend checking with your carrier as that sounds like they had outages since I've had zero issues where I am and the carrier I'm with. IE, very recently in Canada an outage happened on the Rogers network due to copper thieves https://www.cbc.ca/news/canada/calg...e-to-copper-wire-theft-says-company-1.7195923

I'll try to get out a build with the NR SMS blob change today if I can I've been a bit busy at work
[Motorola Edge 40 Pro  / Moto X40 (China)] TsFeng:
I have two bugs meet（CN,English is poor🥲)

1.bluetooth switch not properly, when I press the button, I need to wait a time to bluetooth state change, sometimes it can't change and the button change to gray and can't touch

2.My sim is China unicom and China telecom, sometimes i restart my phone but there is SIM2 only working,and SIM1 not displayed,i need to restart again to make it normal
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@TsFeng can you please try and cause the issues and provide a logcat?
[Motorola Edge 40 Pro  / Moto X40 (China)] Luci_Americanu:
For those who tried Los on there edge 40 pro, how is it for them having that os knowing that it has another kernel and it saves more battery that the original os
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Um, are you lost?
[Motorola Edge 40 Pro  / Moto X40 (China)] Luci_Americanu:
Wdym ? Im sorry if im on the wrong thread or something, I'm new here
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Oh I must have misunderstood. It sounded like you said the OS, kernel and battery life were better than original, but wanted another person to say the same.

Yes this ROM and kernel run very well.
[Motorola Edge 40 Pro  / Moto X40 (China)] Luci_Americanu:
Ohhh, no no noo, im sorry for misunderstanding, i just wanted to know how it performs in terms of performance and battery life on LOS than the original OS cus my phone probably it's a bad unit and i have only 4-5h of SoT on it when others say that they get almost double from what i get and I'm thinking about switching to LOS for that kernel and battery life improvements
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
@Luci_Americanu yes, it's much better than stock
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Yea on stock I would get like 10+ hours SoT. I can do anything I want all day. Play games, google maps, videos, music, etc. I usually have like 20-30% at the end. And I play State of Survival a lot.

LOS should help if you're struggling with power. Although if you are in a bad cell device area, your device will constantly be pinging out to towers to try and find a better connection. If that is the case, nothing will help that issue.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
@Tilde88 I've had about the same a couple months ago, but determined it was because SIM card was intermittently losing connection to the OS (so there's nothing, not even calls). Please check if when the issue presents, it also says no SIM is present in Android SIM settings. There wouldn't be a SIM 1 or SIM 2, even though you know it's physically in the phone as usual. If so, we are talking about the same thing.

But for me the problem went away after a while, and im still fine. It was also extremely random, and im not sure but i felt it more likely to happen when physically traversing areas (so could be network/roaming/tower selection fault). I am however using Edge 40 Pro, and also on T-Mobile, on a dutch carrier called "Simpel" that shares the T-Mobile network. It was also extremely inconsistent when it came to resolving it, just like in your scenario reboots don't always work, or don't help 10 times in a row, i would be left doing many things to try fix it when out somewhere, in case i had to use Maps, search the web, or place a call; mostly, and increasingly, to no avail.

Because the issue just went poof, and most users aren't encountering this it's no longer on my mind or reported by others. It's not ideal, i would be interested in helping to get to the bottom of it too, because there's no guarantee it won't come back full force and interfere with my reachability one day in the future.

I did store logcats at the time, so a few months ago on older builds, of right after reproducing the problem (not possible for me anymore). I can still post them if @ThE_MarD thinks it'll help to investigate this. I never got around to doing anything with them, all i did the weeks i suffered from this problem is make note about it in private, towards Marc.
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Thanks for the reply. I just went ahead and switched back to stock. The issue is not physical or SIM-related. Thanks, take care.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I know, but i asked you to check SIM settings during the problem, to confirm if it's the same thing we are talking about. Whatever is going on has the side effect of signalling to Android there is supposedly no connection with any SIM card. That's the software side and not a SIM or physical SIM placement fault, you're right about that.

If you can't check anymore, ok, bummer and good luck. I'm pretty sure it's the same thing anyways, your symptoms sound exactly like what i encountered. If no more facts can be investigated, i hope it doesn't happen to anyone else in the future, and also doesn't come back to me.. as it stands it's a very obscure and rare bug, it may even be carrier specific where there's an incompatibility between how that carrier implements/signals something vs. LineageOS for rtwo.
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Ah, apologies I missed the settings part. I'll try again in a month or so. Swamped with work currently.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 btw, did you have the SMS bug before too? I'm unsure if this bug is related to QTI Telephony Injection or not
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
yes, before the 5-11 build, i still had the SMS bug. on CRDroid, the SMS bug was fixed, but it would show an error saying the message did not go through (false negative). but in CRDroid, it (the SMS fix) completely broke the ability to make or receive calls.

i think that the QTI injection fix (or the attempts to it) are related to the signal drop issue. i dont know about other builds, but 4-20 build had the signal drop issue
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
A new test build is going up! It's uploading meow so please give it 30 mins. lineage-21.0-20240521-UNOFFICIAL-rtwo contains ASB and lts kernel upstream merges and also some minor fixes for thermal HAL and also crash fixes for MotCamera4 so please test everything! Any new bug reports please submit with a logcat

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240521-UNOFFICIAL-rtwo at SourceForge.net

LineageOS for rtwo (Motorola Edge 40 Pro / X40 / Edge Plus 2023)

sourceforge.net
[Motorola Edge 40 Pro  / Moto X40 (China)] Big Dumb Object:
Just noticed that this ROM is finally available as MicroG edition.
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
can you elaborate a bit on what this is?
[Motorola Edge 40 Pro  / Moto X40 (China)] Soketto:
Nice! I looked awhile ago but went with magisk to install microg as vanilla lineage also has spoofing for it now.

microg is an open source implementation of google services on your phone. If you want to remove google off your phone for privacy, performance or other reasons (degoogle), many existing apps won't work or have problems. Microg can basically fill in that gap. The microg version of lineage basically includes this by default so you don't have to do any extra flashing or magisk modules

microG Project
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
But why is the MicroG edition behind schedule on official LOS builds? It's not a good sign when they made only an initial build.

Me too please, @Big Dumb Object. Do they tend to support devices as long as official LOS, and do they always include LOS's latest main and device specific code from the official LOS maintainer? If both are the case, and missing a build is just an incident, it's appealing..
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Afaik, LineageOS for microG is a mirror of LineageOS with a few extra commits for extra microG support and integration.

They do go by official LOS device roster, but they only eventually add them, they don't add as soon as they go official as I think someone manually ports the device trees over.
[Motorola Edge 40 Pro  / Moto X40 (China)] Big Dumb Object:
What an unexpected interest! After all, MicroG has been on the scene for years, and is even embedded in some ROMs like CalyxOS and /e/OS. Well, the basic answers are already given, but since the questions were addressed to me, I consider the best answer is just to provide links to the original sources:

https://lineage.microg.org/

https://microg.org/

To complete the answers above, I can add that LOS for MocroG is a de facto official LineageOS with full OTA support and a maintenance period equal to the vanilla LineageOS (sometimes longer). In my opinion MicroG is the best replacement for GApps, unless you are a hardcore Google fan. With it, all the basic GApps features (i.e. GPS, Push etc.) work as they should, with benefits for battery and of course privacy. In turn, LOS for MocroG provides the most fulfilling MicroG experience right out of the box. Just add Aurora Store as the cherry on cake.

And don't forget that discussing LOS for MicroG in official LineageOS threads is not welcome and basically is off-topic.

I didn't know! It seems there was nothing about Signature Spoofing in the changelogs for the latest major releases.