yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
G

@ThE_MarD

Good Morning,

i have some problems to use apps cause they "see" the phone is rooted.

Maybe you can make a fix for the SafetyNet?

Zygisk and Magisk want help here in this case.

Thank you
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@debx LineageOS doesn't officially support mods and tbh I haven't tried but maybe another user can comment on how to do that stuff?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
err, I haven't received any test feedback either on Telegram or XDA... but from my testing, it seems fine, so I think I'll still approve official builds resuming and hope for everyone else it's also daily driver ready 😂🙈
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
hi the mard, how can find your group on telegram? thanks.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@clubwagon https://t.me/motox40official
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi,

the stable version is stable 😅

Firstly thanks for the work.

All is for now fine. But mean not the but ...

The good old little blue-tooth.

When i send a voice message over Threema, Signal, Telegram and Bluetooth handsfreeset in the car. The received person tell that the message is stucking. When i send the message over the phone its all good.

This phenomenom is since the previous version and its in the actually stable present.

Update:

Sms works great for now. After reboot, after flymode also!

Good job. Thanks!!!

Update 4.7.

Bluetooth is very very bad. Since last two Stable Updates.

No automatically connecting

Connecting but handsfree speaking doesnt work over the car speaker

Bad sound
[Motorola Edge 40 Pro  / Moto X40 (China)] vasilkotsov1:
Is there any way to implemet Ready For on LineageOS or made of Magisk module.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
New test build is up! lineage-21.0-20240702-UNOFFICIAL-rtwo contains the latest kernel CLO tags for the kernel and kernel modules, a tweak to lower mic volumes in only calls and some fixes for hermetical images (essentially avoid using "BUILD_BROKEN_INCORRECT_PARTITION_IMAGES" cflag. It also contains the MotoNrEnabler service so if you wipe your modemst partition this service can fix it so you can enable and use 5G only mode

Please test all functions and report any bugs with logcat

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240702-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)] HackVasant:
Hi,

Is this compatible with Google's GKI kernel ?. The kernel naming doesn't seem to match GKI kernel naming.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@HackVasant unfortunately we aren't true GKI as we have to use the wrong toolchain to be compatible with AOSP

So what we are following is the LineageOS QCOM sm8550 kernel setup which has Linux upstream, ASB and CLO tags
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
hi . i would like to try lineage os for microg for this device, but i dont know how to flash the files from lineage os for micro g. i see some differences between the lineage os files for microg and this lineage from the mard. the installation instructions are not clear for me. can somebody show me the steps if possible for installation process? thanks in advance.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@clubwagon the LineageOS for microG has some instructions but they are a bit vague

LineageOS for microG

lineage.microg.org

It should be the same instructions as regular LOS just no need for extra flashing of GApps or anything though
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi,

thank you for the new stable version.

Bootlogo works every time by every rebooting.

Sms. All works very fine. After reboot and flymode on off too.

Bluetooth,

Using over phone call. Its much better. The mic is now better. Maybe one tick mic volume down and its perfect.

Using over handsfreeset its better to. I think its the same problem here, maybe one or two tick mic volume down. The stucking its better but is present.

Using Bluetooth music. The title information is now only the title. Nothing other informations. Previously i see the first time the title, singer and album info. But only one time after installing the fresh lios.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Be aware that the new build contains July security patch and all those additional kernel platform updates that the builds page pretends are "To be included in the next 21.0 build"

This is due to a desync in the builds tracking page, brought on by a delay in builds being published while a lot of the build infrastructure was freezing and crashing last Saturday (the day of rtwo weekly builds). You can see the changes it says aren't included yet reflected after OTA, like Android patch date string.. which is a commit, and the build timestamp is post-all of the final changes being merged.

Nothing more than extra good news. Just clarifying.
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
I'm interested on this too.

The only way I think there is is through a port Ayras dev ported.

This is the link https://www.linux-apps.com/p/2128050

It has an APK for installing but I've not tried yet personally.
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
@ThE_MarD do you have any hint for this issue?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@maicol07 tbh for the touch sorry I'm unsure... I haven't had time to check the logs yet I've been busy trying to finish bringing up the remainder of my devices for QPR3 but they should be done so I have time to check some other stuff
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@maicol07 , your logs keep complaining about some unsupported rate so I'm unsure if that could be somehow causing a problem? I don't see any touch errors offhand tbh

Can you please state what do you have for the refresh rate settings?

Also, do you have high touch polling rate on or off?
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
Max 120hz

Min 90Hz

High touch polling rate on
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Hmm, can you please try with high touch polling rate off and see if it's fine?
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi,

few updates to the actually stable version.

Phone microphone is perfect!

Handsfree microphone is perfect and the stucking is no more present.

Bluetooth show only the actually song with no other informations

Sms works after flymode

I tested the folowing settings:

Max 120Hz

Min 90Hz

High touch active

No any problems with frozen screen etc...

Thank you for the very good work!
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
Switched to off. I'll get back to you after some days of testing
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
@ThE_MarD Just happened again
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I think i noticed the battery lasting longer in the new build (could be up to the Linux kernel update to 5.15.150 or another change I didn't identify yet)
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@maicol07 hmm, any chance next time it happens you can try to grab a logcat please? Tbh I'm unsure what all could be causing it, afaik no one else has reported any touchscreen issues, so I'm hoping it is just some rare screen you have and not a defective one
[Motorola Edge 40 Pro  / Moto X40 (China)] ryansff:
I'm going to try flashing the US firmware first since I've been on EU for a while. I'll check back in a bit.
[Motorola Edge 40 Pro  / Moto X40 (China)] ryansff:
Ok so even with the US firmware mobile data is resetting constantly. In airplane mode the phone seems to behave reasonably stable, but the logcat is running a million miles an hour with the telephony errors trying to register on the network. Trying to use the mobile data crashes the phone and it reboots to recovery. I'm willing to test as well, I'm actively monitoring this thread. Thanks for trying!
[Motorola Edge 40 Pro  / Moto X40 (China)] medorex:
Hi, i'm having the same problem with both the stock version

T1TR33.43-20-28 RETEU (Italy) which with later version T1TRS33.43-20-28-2 simply rooted with Magisk, I don't understand why Motorola doesn't give priority to fix this problem, it's really annoying
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I doubt we are talking about the same thing, please attach Logcat for the time around which it happens
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@mxz55 oof wth... Maybe because I've flashed a few different builds and rebooting I'm not observing it yet? But if it's happening to you then odds are it'll eventually happen to me...

As for what @medorex is mentioning? On the older version of the stock ROM even running that with bootloader unlock I'd get the keystore crashes, so he might be correct that it occurs for him there too. What variant is your rtwo? RETEU? RETUS? RETCN?
[Motorola Edge 40 Pro  / Moto X40 (China)] medorex:
@ThE_MarD RETEU

@mxz55
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
@medorex Thanks.. is your bootloader unlocked as well?

If it's a bug in Moto firmware that happens when bootloader is unlocked.. or potentially to all scenario's, we are at the mercy of Motorola to be able to pass their tier 1 support (it's difficult to get anything under the eyes of their real developers im afraid). I hope that if this won't work out/they will never fix it, we can fix it with LineageOS by a workaround like enabling KEYSTORE_OPERATION_CREATION_MAY_FAIL

It has been said before that RETUS doesn't have the bug, but maybe it's one of those things where somehow the device behaves differently under The_MarD's testing environment. I will flash RETUS soon to test, someone could join me in that/be quicker than me
[Motorola Edge 40 Pro  / Moto X40 (China)] medorex:
Yes is unlocked, i had this problem from the first power up and it was brand new. I think it's a problem that only Motorola (maybe) can fix or work around it as you suggest
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@mxz55 for meow I'll stick with that latest RETUS vendor blob build for a few days and I'll try to see if maybe it happens to me and I'm guessing it will...

RIL and WiFi seem to be working fine which is good for me on those blobs too

A Edge+ user on Telegram said this build did fix WiFi for him which is good news. He said it even attempted to initialize RIL which is farther than what RETEU or RETAIL vendor blobs so we will probably just focus on using these blobs.

I'll try to diff RETEU and RETUS vendor blobs to see if maybe there's extra blobs or something on RETUS that might fix RIL for them is my hope.

The TG user did say he tried RETEU stock ROM on his device and eSIM was completely missing, so the issue is either vendor blobs, vendor configs or kernel???
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Oof, I just noticed GPS isn't working for me on that latest build though... Is it working for anyone else?

Can someone on a previous build check GPS there? Not sure if RETUS vendor blobs caused this or something else

The field job I'm on will be ending soon and I'll have some shop time, so I might get a better chance to check logs too and see if there's any errors that give any ideas too

Using the GPS Test app from the play store it's trying to connect to satelites but it doesn't get a lock... So it might need some adjustments in the GPS configs maybe...
[Motorola Edge 40 Pro  / Moto X40 (China)] shamanoid:
this seems to be the case for latest crdroid as well
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Ok I checked with SGCMarkus and odds are even older builds it'll be broken as the source built GNSS aidl is probably on too old of a CLO tag to work, so that's going to be looked into.

Checking OP11 trees they're using prebuilt for it which is probably why they haven't ran into this
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
So I still haven't had any keystore crashes, so I'm unsure if maybe it's because at one point I did flash full firmware via TinyFastbootScript RETUS 33.43.48.21-2 and then later used RSA to return to RETEU 33.43.20.28-2 which might not have changed my device firmware?

Maybe everyone should try using TinyFastbootScript with RETUS 33.43.48.21-2 and full firmware flash and see if it helps?

I also just noticed OP11 is using eqs (Motorola Edge 30 Fusion) Ims Blobs, so we might have to do the same in order to fix RIL on Edge+ ??? I can try to get those same vendor blobs and see what happens
[Motorola Edge 40 Pro  / Moto X40 (China)] patzek:
Is it possible to pass safetynet complete with magisk. I'm currently only get basic integrity pass, cts profile fails.
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
So I finally got around to unlocking my Moto X40 and installing LOS. It was more eventful than it should had been and thank you to all the people in the chat that provided support.

The fingerprint reader is not working but the devs are aware and might already have a solution. I'm having a weird problem with some few Bluetooth devices not being seeing when pairing.

Other than that I have not notice any other issue so far. It is looking really good, even ready to be a daily driver. Amazing job from the developers.
[Motorola Edge 40 Pro  / Moto X40 (China)] kamma:
you should be able to pass check with this: https://github.com/kdrag0n/safetynet-fix/releases
[Motorola Edge 40 Pro  / Moto X40 (China)] patzek:
I already have this module installed. I have "Google Play Store", "Google Play Servcies" and "Google Service Framework" on DenyList, and force denylist enabled.

I have delete play services data, but after a reboot the "Google Play Services" are no longer on DenyList.

Magisk is latest version, and Magisk App is "hidden"
[Motorola Edge 40 Pro  / Moto X40 (China)] medorex:
I did it and after 2 days with the same apps and settings I had with RETEU I had no problems, thanks for the suggestion
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Marc is preparing a new build that includes GPS fix (by using pre-built GNSS libraries for now, until it's figured out). Additionally, syncing with LOS sources brings kalama-specific merges and Qualcomm updates
[Motorola Edge 40 Pro  / Moto X40 (China)] Big Dumb Object:
I've been following this thread for ten months already, still not having the device itself. Now, when production of X40 is discontinued, it's time to dare to spent some money on it (or not). How would you rate the current usability of this ROM as daily driver? I still see a lot of bug reports in that rather long thread, but I'm not sure if that reflects an actual software quality, or if it's just a very active community here.
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
I think im not jump to the p50pro. Why i give money forvsomthing what is worse as the p40pro?

The guys made great job and i use the Rom daily with no limits. My phone is my working place and very important to be work stable. Therefor i jump it to the stable version from prevoious beta.

Take it and have fun.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
The known issues list is outdated, ill ask Marc to clean it out.. for example, the boot animation is fixed, QTI injection (concerns: "SMS bug") is fixed, Brightness slider is fixed.

The rest are niche bugs described in high detail, like who would use 48Hz on a flagship and lag themselves out.. i would advise @ThE_MarD to explain them elsewhere.

Anyways, --

The thread has been re-used since early alpha builds and unofficial releases, and just renamed at the time. So all feedback and progress on old bugs that are long fixed is contained within.

The device is currently extremely stable and perfect for daily driving, as you would expect the quality of an official LineageOS to be. I advise to buy.

I'm also happy for the role i played to have enabled myself and others to use a very good and stable flagship on the latest chip in full freedom (custom ROM), for the coming years until i feel the phone itself is outdated again and then i might just repeat what i did: call on my friend Marc, donate him a new Motorola device, coordinate the project in its early stages and leverage the network of those involved to get more hands and goodwill. Anyone that followed the origin of development here, knows that without my initiative and efforts there would be no development scene for this device, LineageOS trees kickstarted it all.

Just to say, not as an ego boost, i plan to keep that up every bunch of years when one device gets outdated: rinse and repeat. the Qualcomm (last gen) Custom ROM scene needs to have a flagship scene, it wasn't present. By my statement, don't be afraid to get into it now, and as with any superior tech, not being able to go back aka downgrade when the time comes; there'll be a new device by my actions, unless devs, after this milestone, already got the taste of it and will keep the practice (mainstream development scene & LineageOS for Qualcomm flagships) up indefinitely.

Note: when i say those that followed it in its early stages, i mean even as far back as this. Altogether, we've come a long way to the stability we are at now, as you can expect for instantly working on a new SoC that still had lack of research. But as i said, it will be a recurring practice in the flagship realm for as long im around.
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
hi everyone. can anyone confirm if changing color tones does in the last builds? i did only stop testing the builds because of that not working on my device. im still using the based in android 13 build ( very stable) . i would like continue testing the roms but not able to change color tones stop me.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
@clubwagon There's not really a need for testers anymore, because this is now a very stable ROM with official status. Feedback from daily users is what can always be beneficial, though. I hope someone

But here's your answer, a recording by me of the situation today (it works). See attached file.

Edit: damn it looks like not captured using Screen record, as it uses a physical display panel feature instead of software. So you gotta take my word that there's a difference, or wait for me to get a secondary phone to record the comparison externally, so it can be observed.
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi and thanks for the new Stable Version.

Sms, boot logo, display flicker in sun, mic is perfect and resolved.

Battery power is a little bit faster empty.

Update:

Handsfree mic test was succesful

Bluetooth:

I use an Oppo phone with Android flashed regular software. All Bluetooth music informations like Album cover, Music Group and Track are displayed. I tough it was a problem with the Lexus Soundsystem from 2019 this Test show its not. Its definitely LOS based thing. I rechecked also with my LOS flashed edge p30 phone. The same here, no Album cover and other infornations during playing a music. What i wonder is, that works only one time after fresh flashed LOS til i disconnect from the Soundsystem, by parking, and reconnect by drive a way. And from this point never work again.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Apparently there's a bad APN issue so some builds were taken down. The next build should have fixed APN's
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
yeah. I'm wondering if that caused intermittent boot failures and loss of SIM functionality (as if no SIM is present) for anyone else?

For me, if i reinsert SIM in the bugged state, this is entered to logcat that very moment (yet, it does nothing with the SIM):

3758 4045 I SecureElement-Terminal-SIM1: OnStateChange:true reason:Uim Card Status change Indication
3758 4045 I SecureElement-AccessControlEnforcer: Allowed ACE mode: ara=true arf=true fullaccess=false
3758 4045 I SecureElement-AccessControlEnforcer: No ARA applet found in: SIM1
3758 4045 I SecureElement-PKCS15Handler: - Loading SIM1 rules...
3758 4045 I SecureElement-PKCS15Handler: Logical channels are used to access to PKC15
3758 4045 I ACE ARF EF_Dir: Analysing EF_DIR...
3758 4045 I SecureElementService ACE ARF: ReadRecord [1/22b]
3758 4045 I SecureElementService ACE ARF: ReadRecord [2/22b]
3758 4045 E SecureElement-PKCS15Handler: SIM1 rules not correctly initialized! [Parser] Cannot retreive type
3758 4045 E SecureElement-AccessControlEnforcer: [Parser] Cannot retreive type
3758 4045 I SecureElement-AccessControlEnforcer: Deny any access to:SIM1
3758 4045 I SecureElement-Terminal-SIM1: OnStateChange:false reason:Uim Card State absent
3758 4045 I SecureElement-AccessControlEnforcer: Reset the ACE for terminal:SIM1

All mobile networking and SIM settings are greyed out. Well, I won't be calling until i roll back to last build or ill see if i end up waiting for coming Saturday..
[Motorola Edge 40 Pro  / Moto X40 (China)] luuxis:
- Widevine L1 lost upon bootloader unlock (reverting to stock ROM via Motorola RSA Tool and relocking bootloader does restore it)

for my case it works on the version that I have build
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@luuxis that is mentioned in known bugs
[Motorola Edge 40 Pro  / Moto X40 (China)] luuxis:
why mention it as a bug when it is very simple to correct the bug?

I'm new to the world of custom ROM development and I managed to correct the problem

a person like you who has much more knowledge than me can easily correct it too
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Instead of belittling others, how about you tell us the way you achieved it? Go ahead and describe the fix or link to it, please. Thanks

Edit: just noticed that you're the author of unofficial EvolutionX ROM for rtwo.. regarding the attitude of belittling: is it convenient for you to forget that without us (The_MarD, SGCMarkus, and myself) you and the other ROM's would likely not have been here now? This team and all their efforts of bringing the device up has led to the device trees which you and all of the other recently published ROM's are based on.

Please some respect to those who'se stuff you used/are facilitated by, those that made the rtwo's development scene get created and really take off. We also rewrote history by doing this for a phone in the flagship segment. By now, the device is well on its way to be the most widely supported device, a title that the OnePlus 6T once held and is still renowned for.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@luuxis just to check, if you just added liboemcrypto.so blob that doesn't fix it. Apps will report Widevine L1, but if you attempt to stream with an app that uses L1? It'll either fail to render or crash.

Even if you're on stock ROM with bootloader unlocked, it is the same result. it'll show L1 in apps like DRM Info, but as soon as you play L1 content? Black screen or crashes.

If you managed to backup with bootloader locked the DRM keys in /data/vendor/mediadrm and then restore them and have them working with bootloader unlocked? Please provide information on the fix
[Motorola Edge 40 Pro  / Moto X40 (China)] luuxis:
actually I have a crash, I will see what I can do to correct the bug
[Motorola Edge 40 Pro  / Moto X40 (China)] luuxis:
I don’t want to belittle anyone’s work; quite the opposite. When I installed the ROM, I was at work and couldn't test video features on Netflix, for example. I also haven't had time to test it further because I primarily use an S24 Ultra for my accounts. I bought the Motorola Edge 40 Pro just to contribute ROMs to the community and to learn more about the ecosystem.