yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 40 Pro  / Moto X40 (China)] Jackdm1:
Hey guys. It's an honor to read your posts and show gratitude to the developer, the donor of the device and the testers.

I have a Galaxy Note 3 and have been running Android 7 (Nougat) to LOS 18.1 (Android 11) which I currently run on device. There is a huge Note 3 community and there is Android 12 rom for this device but it's unstable.

My screen is cracked and I'm in need of a new phone and while researching the Edge Plus 2023 was the second phone I came across. I loved it from the start and have not looked at any other devices. My first ever device was a Motorola so I felt good about this device.

I have committed to buying this this device in December while I travel abroad, I do not live in USA or Europe so it would be too difficult to have it shipped safely on my neck of the woods. There is nothing that will change my mind from this device and I look forward to testing and having this phone as my daily driver.

By the way, I also run a custom kernel on my note 3, I hope a developer comes forward to work on stuff like that.

Thanks.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@mxz55 I downloaded the latest RETUS from lolinet (there's currently only one build right meow) https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETUS/

and also the TinyFastbootScript and the instructions are in this link too. I performed a full firmware and factory reset https://mirrors.lolinet.com/software/windows/TinyFastbootScript/

data did work for me on the RETUS device firmware on my RETEU model variant
[Motorola Edge 40 Pro  / Moto X40 (China)] lanbui:
Hi, after using this ROM for 2 days, I found some issues (maybe bugs), my device is moto x40:

1. After added trusted device to smart lock, the lock screen didn't responce to my swiping

2. Some apps don't use the vpn after I toggled vpn on

3. Fingerprints can't be registered

Btw, I'm not sure if anyone else met the same issues.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@lanbui there seems to be an issue that seems more device firmware related. My unit is a RETEU, yet flashing RETUS fixes the lockscreen crashes and some apps crashing too. You might need to experiment with different device firmware to see if it solves the issues for you
[Motorola Edge 40 Pro  / Moto X40 (China)] ryansff:
Just checking in after trying all the firmwares available on lolinet. My US Edge+ 2023 8/512GB version still has the mobile data issue and won't connect, constantly resets over and over until the phone crashes back to recovery. There must be some kind of difference between the Edge 40 Pro and Edge+ 2023 that makes this build untenable. I may just buy a Edge 40 Pro so I can use Lineage and sell my Edge+. Thanks for all the great work.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
@ryansff At this point we're waiting for @SGCMarkus to return (he's on vacation) and when he has time, work on the remaining issues.. weird stuff between firmware versions and rtwo variants is one of the things to pay attention to.

It's up to you if you wait or want to swap for Edge 40 Pro.. as it stands, the 40 Pro with RETUS firmware flashed is entirely stable with unofficial LineageOS and suitable as daily driver, even avoiding keystore crashes. There was even someone that told us the small incremental "July security patch" for Edge 40 Pro, T1TRS33.43-20-28-2 (= RETEU) also solves keystore crashes

Since the crashing of certain apps as well as lockscreen/pincode troubles are all caused by the keystore issue, RETUS or possibly that latest RETEU fw gets it out of the way and makes the device daily driver suitable. I will be testing if RETEU update really solves it, in which case it can be used by Edge 40 Pro users as well as possibly Moto X40 users and tell the results. We also still need an X40 owner to test RETUS/latest RETEU (in case my results are: it fixes it) to see if it works as fine as on Edge 40 Pro

Of course, all that messing around with firmwares may become unnecessary if SGCMarkus returns and feels like working on it soon. Maybe all we need to do is pull more stuff from each variant firmware, and rebase the fw we brought LOS up with, to a newer one. I write it down just in case someone can't wait.
[Motorola Edge 40 Pro  / Moto X40 (China)] SGCMarkus:
Im back since saturday, just .. otherwise busy (*cough* Baldurs Gate *cough*).

The whole firmware situation is ... weird. I *assume* moto messed something up in the first release(s) and (hopefully) fixed that now... That parts all proprietary and we cant do much there.

Keystore (system service) talks to keymaster/keymint in vendor, which offers the android expected functionality. Its "execution" on the other hand *should* be handled by firmware (I remember on older devices trying different keymaster versions from the same soc family/oem and it complained about firmware not capable of <feature>).

Cant really do much about that :/

Can run a diff later, but unlikely the relevant blobs actually changed (they really rarely do, unless theres an android upgrade).

Maybe @ThE_MarD has another idea, except requiring users to flash newer firmware.

PS: i remember something (more or less) similar happening on the G8X. After unlocking the bootloader, the fingerprint (also firmware/trustzone communication) didnt work. During the unlock process something got messed up, which made it not work. The only way to get it working again were flashing stock Pie, enter the LG hidden menu, and run some fingerprint tests (that wasnt available anymore on later stock versions). Or you relocked the bootloader...

At some point they admited they messed something up there, but im not sure if they ever fixed it.
[Motorola Edge 40 Pro  / Moto X40 (China)] ryansff:
The previous model, the edge 30 pro/x30/edge+2022 needed 2 different aosp builds, one for x30/edge 30 pro, and one for the us edge+2022. The phones were all codename hiphi. Could it have something to do with the storage size? 512gb roms are all that is offered for the edge+2022 and 2023 in the US. Does the edge 40 pro have that too? All I can find for sale is the 256gb version. Is the testing device a 12gb/256gb edge 40 pro?
[Motorola Edge 40 Pro  / Moto X40 (China)] jimmie32:
This reminds me, I've had issues with GSIs on moto devices before where I updated the radio but not the vendor partition and had similar issues disconnecting. It's not the issue here since I did a full flash of RETUS/RETEU/RETAIL/BOOST then flashed lineage on top, but it may be possible that there are edge+ specific files necessary to get radio working on the US variant device. edge+ (2022) in US definitely needed a separate build for the US variant vs. the other variants worldwide, so maybe there is the same issue here.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Well a user on Telegram rtwo group @Firstinout (some1) mentioned he would mix RETEU stock ROM flashed and then only BP/AP from RETUS helped him and then he also mentioned the latest RETEU stock ROM full seems to work fine.

I tested it on my RETEU and overnight on the stock ROM with bootloader unlock I could still use my lockscreen pin and the UDFPS still worked too which is great news, so Motorola must have changed something there.

I used XT2301-4_RTWO_RETEU_13_T1TRS33.43-20-28-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC as found on the lolinet servers. My rtwo is an RETEU aswell.

So I'll definitely be upgrading our LOS builds with 43.20-28-2 vendor blobs as well since that could also help us too and it'll help if anyone also upgraded to that device firmware too.

I also tested that device firmware version on LOS and so far no lockscreen crashes for me which is good news too!
[Motorola Edge 40 Pro  / Moto X40 (China)] derekcorleone:
Sincere thanks to all developers on this project, giving X40 users a cleaner ROM option. Though I'm wondering whether this release supports rtwo (XT2301-5), since that's the only model we can get in China, where third-party ROMs are, arguably, most urgently needed.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
yes
[Motorola Edge 40 Pro  / Moto X40 (China)] derekcorleone:
Great news! Many folks here will be happy : )
[Motorola Edge 40 Pro  / Moto X40 (China)] fosgate24360:
Quick question, would the kernel from LOS rom work on the stock rom?
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
So now, dirty flashing irrespective of old firmware on the device, should be safer, even though clean install is recommended with major versioned upgrades. Nice to have a more polished second build out.
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
Hi. Can i dirty flash this?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@clubwagon yes definitely if you are coming from the first LOS 21 build. If coming from LOS 20? You can still try but tbh I'm unsure if it'll work.

As always if manually applying update you must reboot to recovery and reflash add-ons like GApps
[Motorola Edge 40 Pro  / Moto X40 (China)] patzek:
Btw, display colors feels a little bit weak on LOS21. Anybody else have this?

Tried to play around with color mode (natural, adaptive...) but that seems not to change anything.
[Motorola Edge 40 Pro  / Moto X40 (China)] xuyh0120:
My mobile network was working with the first LOS 21 build, but stopped working on the latest build.

Edge plus 2023 boost variant, dirty flashed from LOS20.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@xuyh0120 can you please provide which carrier that is please? And which country?

I think I did try to update carrier config overlays from X40 (RETCN) A14 but there could be some it is missing from RETAIL/RETUS variants
[Motorola Edge 40 Pro  / Moto X40 (China)] xuyh0120:
US, ATT.

Correction: my phone is project genesis variant instead of the boost variant. My mobile network issue refers to the physical SIM of project genesis network (which uses ATT), not the esim (which never worked on custom rom).
[Motorola Edge 40 Pro  / Moto X40 (China)] nTOHS:
SMS does not work after the update. Clean installation. Mobile connection works.

Edge+ ,Los 21 (last).

Thanks to your firmware, esim appeared, which was not in the operator's firmware of boostmobile.

Reinstalling the sim card helped.
[Motorola Edge 40 Pro  / Moto X40 (China)] Soketto:
Just updated here, thanks for the work!

So far the only issue I have is SMS not being received, like as reported above by nTOHS. (x40, clean install).

For those who use root or microg I had no issues getting it running (well apart from seeing LSposed now being archived 😭)
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I should add my own experience to that: my Edge 40 Pro already couldn't receive SMS (unless reinserting SIM card) on the last LineageOS 20 builds i used.. can't confirm the situation on LOS 21 with my carrier/country yet, as i will only upgrade my personal device later this week

Marc is preparing a build with some more updates, unmerged picks and above all the fix for that LOS 21 fingerprint enrollment overlay issue, so we'll be left with the only known bug in this ROM being SMS issues that several users report? Sounds like a pretty decent result to me, of course i hope we can get to the bottom of every last issue, so SMS as well.
[Motorola Edge 40 Pro  / Moto X40 (China)] xuyh0120:
Update to my situation:

Today the mobile data suddenly started working again. Did not change any config, only rebooted my phone a few times.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
New build is up! lineage-21.0-20240117-UNOFFICIAL-rtwo contains a fix for UDFPS overlay when registering a new fingerprint, it also contains a fresh repo sync of LOS 21 sources, a lot more repopicks of pending changes to fix issues like the volume bars not displaying correctly (if you guys see any UI bugs please let me know as I might have missed some repopicks).

There's also some codec repopicks that fixes where if you pause a video for more than 20 seconds or so and try to resume the video freezes but the audio keeps going.

I also did a revert of CarrierSettings to the RETUS ones we had and only kept some newer RETCN ones that didn't exist on RETUS so anyone with carrier issues please let me know.

Just as before too, there isn't any QTI Telephony Injection on LOS 21 still

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240117-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)] nTOHS:
Thank you for your work!

Please give detailed instructions on how to update without rearranging all applications. Is it possible to update without a laptop?The last time I couldn't update, I had to do a clean installation.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@patzek Color mode Saturated was apparently dropped on A14 which I think is what you're referring to. I did try with and without our source-built HW Composer which was a recent display change and that didn't affect it

@xuyh0120 @nTOHS @Soketto so from asking other devs yeah QTI Telephony Injection was a workaround that QCOM made to handshake with certain carriers for SMS that they added for sm8450 (Snapdragon 8 Gen1) and higher, so unfortunately not unique to our device and even 8G1 devices would have the same issue 🙈

Seems Motorola also did some weird haxxs for bootanim on stock ROM... Markus just noticed stopping and starting bootanim service can make boot animation at least kind of work, so there's some weird checks they're doing in order to make it work on stock ROM... Weird earlier devices weren't like this as the current boot animation on Motorola devices have been around a few years

Also nTOHS since you're already on LOS 21 you can try to push the ROM and MTG zips to a USB drive and then plug that into your phone and reboot to recovery and apply update on the zips in it
[Motorola Edge 40 Pro  / Moto X40 (China)] MrIndieJ:
Hi, really appreciate the development on this device! I was having some issues with the fingerprint sensor, but after enrolling multiple fingers, it started recognizing them all. Working great so far on US Unlocked Moto Edge+ 2023.
[Motorola Edge 40 Pro  / Moto X40 (China)] xuyh0120:
Thank you for your work! Mobile network is working for me stably again with the latest update.
[Motorola Edge 40 Pro  / Moto X40 (China)] Soketto:
After installing the 21.0-20240117 build, I cannot get a connection to 4G, only 3G. When running the previous build 21.0-20240115 I had no issue. This issue also happened to me on a prior LOS 20 build.

I'm wondering if its caused by the carrier settings changes?

I have an x40.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Soketto which carrier is that and country? I did keep the RETCN CarrierSettings that didn't exist on RETUS but I can double check
[Motorola Edge 40 Pro  / Moto X40 (China)] Soketto:
Thanks, NTT DOCOMO in Japan, MVNO Asahi Net

. I see the APN setting and can still force 4G through the secret Phone Info/Testing menu but it won't auto negotiate to 'LTE', just 'H'
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
Hi,

I'm trying the ROM, the only issue so far is I can't receive SMS. Is there a fix (also with Magisk)?

My carrier is FASTWEB (Italy)

Thanks
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
It's being worked on, we are looking for an alternative workaround (QTI Telephony Injection doesn't work in Android 14, due to architecture & deprecations). Marc is consulting with the LineageOS team/other devs to figure it out, as for instance OEM's serving carriers that relied on this feature must've been provided alternatives by Google, out of the Android team.

Scroll back in the topic to see more discussion on it. That not all carriers can receive SMS (btw: reinserting SIM after boot is a workaround) is the only known bug right now, even more so one that's not our fault and if Google/Qualcomm doesn't become transparant about any proposed solution, it will for sure affect other custom ROM's on different devices. We are thinking about a workaround that consists of re-initializing RIL shortly after boot, to emulate the events that fire natively in Android as a direct result of reinserting SIM tray, the currently known 'fix'.
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
Also, it seems fingerprint scanner is not as accurate as stock (in stock it accepts the finger almost all times, Lineage accepts it after 1–2 tries most of the time)
[Motorola Edge 40 Pro  / Moto X40 (China)] stenmarsh:
Good day.

When i try this version LineageOS 21 on my device with XT2301-5_RTWO_RETCN_14_U1TR34.8-19-11 firmware, then after fasboot all files from source forge - recovery menu not booting and device going to loop with yellow 'no recovery' message. Everything doing three times with lineage, crdroid and official manuals. Any opinion what can doing wrong?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
I had the same issue testing device firmware from that version.

I'd recommend reflashing full firmware and factory reset to latest RETUS 13

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com

And here's TinyFastbootScript to do it with

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com
[Motorola Edge 40 Pro  / Moto X40 (China)] nTOHS:
Thanks for your work!

Some store applications(like Lidl) do not work with the mobile Internet. I don’t understand the reason.Who have the same problem?Los21 root.

There are no other problems, everything works well
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@nTOHS can you please provide logcat after you try using that app?

I noticed that there's a weird camera bug due to the RETCN 14 blobs where photos taken will have a grey thint to them... Every app except for Moto Camera app lol... So after testing reverting camera blobs to RETUS 13 again fixes it.

I'll also try to completely revert Carrier Settings to how we had it on LOS 20 too. There's a chance it's just QTI Telephony Injection causing us grief on LOS 21 but just in case RETCN 14 is still causing issues there we can stick with what definitely works.

As for an automated reset of RIL when a new SIM card is inserted? I'm Still not exactly sure if we can do it but we will keep checking as the main issue is not making an accidental loop of resetting RIL... Workarounds are reinsert Sim card or toggle airplane mode on, wait 10 seconds and then toggle airplane mode off

Markus has found a haxxs for boot animation too so I'll check that out and see if somehow I can help tweak it if possible...

Also, Markus found a fix for the touch sampling rate toggle (y)
[Motorola Edge 40 Pro  / Moto X40 (China)] nTOHS:
Журналы

***Translation***

Journal
[Motorola Edge 40 Pro  / Moto X40 (China)] nTOHS:
Sorry, I can’t post the log files. I’m posting a screenshot.
[Motorola Edge 40 Pro  / Moto X40 (China)] V0latyle:
@nTOHS Please post in English per the Forum Rules:

Also...What are you trying to post? If you were attempting to provide a logcat as requested by @ThE_MarD, there is no file attached to your posts.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Heyyo, new test build is going up! lineage-21.0-20240123-UNOFFICIAL-rtwo contains a fix for photos having a grey tint when taken in apps other than Moto Camera app, a fresh sync of LOS sources and repopicks on top, a fix for high touch polling rate. I've also fully reverted Carrier Settings to how we had it on LOS 20 builds and a boot animation haxxs (which doesn't seem to work for me though)

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240123-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)] Soketto:
Hey, thanks for the release. Still no luck on 4G for me, let me know what I can do to get you more information. This is maybe (probably not) relevant stuff from a logcat I could find so far:

// Error and Warning Logs
01-24 20:14:05.245 1657 1945 W SDM : HWDeviceDRM::GetSupportedBitClkRate: Requested rate not supported: 1102000000
01-24 20:14:06.717 3693 4159 W IWlanNetworkService: 49 > Response Processed
01-24 20:14:06.719 2554 9073 E RIL-MOTEXT: qcrilUpdateOperator, called
01-24 20:14:06.721 3693 4159 W IWlanNetworkService: 50 > Response Processed
01-24 20:14:06.753 1555 3516 W LOCRIL_SESSION: operator():286] cellInfo list size is 0
01-24 20:14:06.813 3726 3726 E QImsService: ImsConfigImpl : onSubscriptionsChanged unable to process due to SubscriptionInfo is null

// Other Info
01-24 20:14:06.896 3741 3741 I Telephony: isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
01-24 20:14:06.896 3741 3741 I Telephony: isRttSupported: false
01-24 20:14:06.896 3741 3741 I Telephony: alwaysAllowWhileRoaming: false
01-24 20:14:06.896 3741 3741 I Telephony: isRoaming: false
01-24 20:14:06.896 3741 3741 I Telephony: isOnWfc: false
01-24 20:14:06.899 3762 3762 D EnabledNetworkMode: enabledNetworkType: ENABLED_NETWORKS_EXCEPT_GSM_CHOICES
01-24 20:14:06.900 3762 3762 D EnabledNetworkMode: getPreferredNetworkMode: 26
01-24 20:14:10.985 3762 3762 D SubscriptionUtil: getSelectableSubscriptionInfoList: [[SubscriptionInfo: id=1 iccId=xxxx simSlotIndex=0 portIndex=0 isEmbedded=false carrierId=2529 displayName=NTT DOCOMO carrierName=NTT DOCOMO isOpportunistic=false groupUuid=null groupOwner= isGroupDisabled=false displayNameSource=SIM_SPN iconTint=-15502541 number=xxxxxx dataRoaming=1 mcc=440 mnc=10 ehplmns=[] hplmns=[xxxxxx] cardString=xxxxx cardId=x nativeAccessRules=null carrierConfigAccessRules=null countryIso=jp profileClass=-1 mType=LOCAL_SIM areUiccApplicationsEnabled=true usageSetting=DEFAULT]]
01-24 20:14:10.985 3762 3762 D SubscriptionUtil: remove cached display name : 1
01-24 20:14:10.994 2598 2682 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{network{102} handle{xxxx} ni{MOBILE[HSDPA] CONNECTING extra: lte.mobac.net} created=2024-01-24T11:14:10.994Z Score(Policies : ; KeepConnected : 0) lp{{LinkAddresses: [ ] DnsAddresses: [ ] Domains: null MTU: 0 Routes: [ ]}} nc{[ Transports: CELLULAR Capabilities: MMS&SUPL&FOTA&CBS&IA&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=14Kbps LinkDnBandwidth>=14Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 1]> SubscriptionIds: {1} UnderlyingNetworks: Null]} factorySerialNumber=x}

Can see it's connecting to HSDPA when it should be connecting to LTE.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Hmm... Well I'm unsure if QTI Telephony Injection affects networks tbh, afaik it's just SMS, but maybe it's also the RETCN 14 RIL/IMS stack we are using causing extra grief. I'm pretty sure it's still very open beta

Speaking of blobs? It seems that RETUS 13 camera blobs did indeed fix the grey tint for me... But it brought back the bug where apps like WhatsApp, Facebook Messenger and Telegram cannot take pictures lol FML....

Albeit, I've heard that Motorola started releasing RETUS A14 stock ROM, but I'm unsure if that is also open beta or if it's stable and I haven't seen it pop up on lolinet either... But definitely once it releases we will be checking it out as it might work better for us, or at least I'm hoping so lol...

The touch sampling rate toggle is indeed fixed so I removed that from known bugs

I've also added eUICC (SIM card manager) doesn't want to update via the play store. I'm guessing RETUS 14 blobs would help with that
[Motorola Edge 40 Pro  / Moto X40 (China)] cascade128:
You can overcome this problem by turning off the "video call effects" feature.

Not MFN(open beta), finally official stable release😪

👇🏻
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@cascade128 interesting! Well hopefully it's more stable than RETCN 14 lol
[Motorola Edge 40 Pro  / Moto X40 (China)] frilalo:
Can anyone help me? Goole Wallet (Google Pay) not working after flashing this ROM. What can I do? Phone is not rooted. Would like to lock bootloader with this rom, but dont have the option in developer settings.