yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 sorry for slow reply, but I'm unsure if it's maybe due to the lack of QTI Telephony Injection on A14 but that would be my guess...

Afaik the only sm8550 device on custom ROMs without RIL issues is OnePlus devices as it seems Sony and Xiaomi have issues too and tbh I haven't heard anything about Samsung as I don't know any devs there. Taking a look at their setup? OnePlus did customize it, so tbh I'm unsure if I can Kang their full stack to our device as Motorola also customizes their IMS stack... I might still try this though but that will take me a bit of time as there's a few extra changes I'll need to do to our configs and device tree too it seems. I think Motorola uses a newer RIL stack so I'd technically be doing a little bit of downgrading
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
im using this as daily driver,

20-20231207-UNOFFICIAL-rtwo

i had to return to this android 13

no bugs, exept the famous motocam ,i love the colors in satured mode and bluetood working good unlike the lineage android 14 i was having annoying bug disconecting bluetood, every time and i have sms working fine until now
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@clubwagon I have a fix for MotCamera4 in my recently released build (I haven't had any feedback yet but so far it seems fine on my rtwo so I might still merge it)

A14 QPR2 definitely created some Bluetooth issues for me too... There's supposed to be some system-side fixes for it coming so hopefully that's true. I need Bluetooth for work when driving our frac equipment for my electronic logbook and A14 QPR2 broke connecting automatically to the electronic logging devices so I have to manually find them and pair lol oof... At first I thought it was the app but I think it's AOSP that broke it meow
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Anyone test this by chance? Seems fine to me, but a second option would be nice. I might just merge anyways for tomorrow's official build
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Works here, just go for it ; )
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@mxz55 thanks bro, I merged the kernel upstream and also the MotCamera4 fix so it'll all be in tomorrow's official build (y)

Also, I think AOSP actually fixed my Bluetooth bug with that Motive Electronic Logging Devices issue! Two days meow I've been able to automatically Bluetooth pair via their motive app! It's an early Christmas miracle haha
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Nice. Just to have said it, i didn't encounter any BT auto pairing issues at all.. my headsets auto pair when turned on. Maybe bt device specific?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@mxz55 yeah I'd get pairing problems with my BT receiver that has aptX Adaptive. I couldn't switch aptX on and off on the fly either or audio would fail until I toggled BT off and on again. I didn't have this problem on my Dubai though same BT receiver too and there toggling aptX audio would keep working

Dubai did have the same BT pairing bug with Motive ELD's, but it seems solved there too! So something on AOSP this month fixed it lol thank god... I was getting tired of it randomly disconnecting me on drives and getting company emails about driving while not connected... XD
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
This sounds awfully similar to a long-standing issue with only one of my many headphones (but more of the ones i previously owned); no sound until i connect twice in a row. Seems to be audio device dependent, it's been annoying me for over a year however, also on my Edge 30 running LOS.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I've just successfully done the OTA update to yesterday's official LOS build, so even though there's a gap in feedback and it may have been fixed a while back, we know it works now.
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Hey brother. I'll likely try the new 5-25 build this weekend. Thanks for your work. If the signal issue still exists for me, I'm much more flexible now, so I can run the phone erratically for long periods of time/days. If the issue persists, do you think I would be able to provide you with any logs or any behaviors/mechanics etc to try and at least see why the drops happen to me? I know it's a very small affected user base (just me lol), but idk... Sorry to bother
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 is your unit an edge+ 2023? I think they have a different slot ID than edge 40 pro and moto x40 is the culprit. I tried adding the slot ID to my device but it caused the sim slot on the other two variants to not work...

A fellow sm8550 dev on a different brand is trying to find a better solution for all of us but tbh I'm unsure if he has made any progress as I haven't heard back

For the mobile data dropping until reboot? Tbh I'm unsure for that issue either... since OP11 isn't affected by any of these bugs? I think I will try hanging their RIL, QMI and IMS stack and see what happens but that will take time to figure out as their blobs are pretty different there and I dunno if it'll even work since Motorola and OP customize their stacks...
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Yes sir. Edge+ 2023 on T-Mobile.

Also, when it would happen, not even reboots would fix it. It would just eventually finish it's handshake or w/e it's doing until it finally worked. Nothing would fix it except time. And the time was always varying.
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
@ThE_MarD just wanted to say thanks for the new build (6-1-24). However, issues have seemingly gotten worse for me, but perhaps may help in understand what is happening.

Now, my device on LOS21 simply doesn't acknowledge that it has a SIM. I can add an e-SIM if I connect to WiFi. I tried airplane mode toggling, and physical removal of SIM card. After inserting, the phone still doesn't even know there is a SIM card.

Update : I took the SIM card out, and boot the phone again. After inserting the SIM, it was recognized and registered to T-Mobile. I will now re-reboot and keep the SIM card inserted.

Update 2 : After the previous SIM-less boot, I was able to reboot with the SIM still inserted. Phone boot registered to T-Mobile, Data remains active. I will post of anything that happens (if it happens). Thanks again, brother.

Update 3 : Hours later, heavy usage. I have no issues with data dropping!
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi and thanks for the official Build from yesterday. The Display light flickering is fixed.

SMS works after Fligh mode and all Sims, e-sim and sim card.

After reboot is the Display no more black screen. The display go automatically on when rebooting is finished.

My Moto Edge 40 Pro is buy in Germany. So i think is Europe version.

Thanks for the good work!
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Test build is up! lineage-21.0-20240601-UNOFFICIAL-rtwo contains a fix for sim slot restart script (thanks to GreyElaina) that should work for all 3 variants of rtwo so please I need lots of testers to confirm this works for the three variants and that no one has a disabled sim slot

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240601-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)] Tilde88:
Yes sir, posted earlier/last night that its working for me too. (I was the guy with the weird connection drops recently)
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 yeah it's a weird thing that happened on your device. Can you please test this build though if possible? If sounds like if a device is gonna have a problem with adjusting the sim slot restart script it might be yours
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Oh I hadn't realized it was a different build. Yes I'll upgrade shortly.

Worth noting : on the official build, I had it drop data while on a phone call once. Data came back once the I hung up the call. And the other thing I see is that the 5G symbol sometimes disappears (leaving no other symbol - just blank.) But data continues to work. I will upgrade shortly.

I appreciate your continued support
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
I always forget to ask, so I'm bringing it up now lol.

I will keep this specific post on the subject of APN.

I noticed that on this ROM, it has a pre-made, and pre-selected APN called "US Mobile" (in addition to my *actual* apn). It has an APN of "PWG", and uses different APN settings than my carrier actually uses. However, using this US Mobile APN seems to be better in terms of signal connectivity. Can anyone give me some insight on this APN? Is this a generic APN (kinda like a pointer, or proxy?). Any info is appreciated.

And the other question, I can't seem to add 'dun' as one of the APN Types. On stock, if I create a new APN, not only does it pre-include 'dun', but it also includes other APN Types, and they all allow me to save. On CFW, however, when I try to save with 'dun', I am given a notice that my carrier does not allow adding this APN type. (I don't actually need this, I am just curious on what is happening). Again, any info on this is appreciated. I just like to know/learn things sometimes, I don't necessarily need this 'fixed', just talking for the sake of discussion.

Thanks everyone.
[Motorola Edge 40 Pro  / Moto X40 (China)] ghjw35hgfd:
English is not my first language. My grammar and diction may be wrong.

lineage-21.0-20240601-UNOFFICIAL-rtwo solved the SIM card problem, my phone is Motorola moto X40.

Before installing this version, every time I restarted my phone, card 2 was preferred, and card 2 didn't work (couldn't receive sms), but now it's fine

By the way, the official build lineage-21.0-20240601-nightly-rtwo-signed, webview implement in Development options works abnormally

Google's webview disappear, no matter how much I uninstall and reinstall Google's webview, it still can not be found in webview implement

lineageos's webview doesn't work on a lot of Chinese application, so i must use Google's webview

lineage-21.0-20240525-nightly-rtwo-signed didn't have this problem
[Motorola Edge 40 Pro  / Moto X40 (China)] bartko4321:
hello, does the brightness bar and automatic brightness work?
[Motorola Edge 40 Pro  / Moto X40 (China)] TsFeng:
will you add face unlock in future builds？
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 the apns list is here:

android_vendor_lineage/prebuilt/common/etc/apns-conf.xml at lineage-21.0 · LineageOS/android_vendor_lineage

Contribute to LineageOS/android_vendor_lineage development by creating an account on GitHub.

github.com

If there's any outdated apns we could try to submit updates for it

@ghjw35hgfd thank you for testing! Hopefully more testers on the other variants can confirm it's safe for everyone

As for changing WebView? Tbh I've never tried so maybe someone else knows what's going on? Afaik that's purely system side and nothing on the device trees I work on can affect that

@bartko4321 unfortunately that's a bug that still needs to be fixed

@TsFeng LineageOS won't support 2D face unlock as there isn't a safe and open source solution to it
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Gotcha thanks for that. I was able to see that US Mobile is some other T-Mobile APN.

By the way, the unofficial 6-1 build seems to be perfect with QTI/SIM issues. Not a single.drop, or missing 5G symbol. Did a clean flash last night to avoid potential issues from official build (I know, not likely, but clean is clean lol).

Thanks for your hard work. Wish there were something i could do for you
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@Tilde88 thanks for testing! Tbh that's the most helpful thing anyone can do for me as I can't test for every situation, especially VoLTE and WFC as my carrier doesn't seem to have it lol oof

Btw what variant is your rtwo?
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
I am happy to help. Still no issues btw. I have an Edge+ 2023 US Model
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Short Update with stable version.

SMS doesnt work after activating/deactivating flymode.

But works when deactivate/activate Sim card.

Backlight flickering is resolved.

I registered that the display "pumps" like a hearthbeat. You can see it only when the screen is on and use black wallpaper.
[Motorola Edge 40 Pro  / Moto X40 (China)] JonathanZ:
What was the issue with aptX adaptive and has it been fixed by upstream changes?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@debx can you please try the latest test build? That's specifically the fix that needs testing

@JonathanZ the issue is the QTI BT stack is being depreciated and AptX full suite isn't compatible with AOSP BT stack... On Android 15 though it is supposed to be. Currently LOS has zero plans to try and reimpliment QTI BT stack as it's a massive pain to maintain and it's only a few codecs that act up and AOSP for A15 will probably be available later this year anyways
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Hi, after crashing and formating my whole phone cause the beta want accept further rom updates. Im secure with using the official versions. Sry.
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Still no issues on 6-1 unofficial. I thought I got a data drop, but it's just a 5G symbol visual glitch. Confirmed with speed test while driving. Over 600 Mbps
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
Small issue it seems. RCS seems a little wonky. Day 1, it wouldn't change to "Connected" status (just stuck at "Setting up...") until I moved it to Wifi. I just tried to send an RCS, but it failed, and I had to switch to SMS. Turning off and on RCS made it go through the same thing, where I had to connect to WiFi for it to Connect. And even though it is "Connected" now, I still can't do RCS.

Update : I noticed mindthegapps doesn't include Carrier Services. I installed it, and it connects RCS over 5g now. I still can't send RCS messages, but I'll wait it out and see if it resolves itself. (Airplane mode switch on/off, sim removal, reboot, nothing fixes it).

Update 2 : Nevermind, the installation of Carrier Services was just a fluke. Now I can't connect to RCS on 5G or wifi, just stuck "Setting up...". I'll still just give it some time... Apparently there is a massive outage affecting other carriers in the US (but not T-Mobile specifically). But AT&T, Verizon, US Cellular and more, all having issues. Hoping this is somehow related and not a ROM issue.

Update 3 : Unfortunately, RCS is indeed broken for me on 6-1 unofficial
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
@ThE_MarD i got data disconnected fully while on a phone call. changing APN, toggling mobile data off and on, enabling/disabling 2G access, none of that fixes it. 5G symbol shows, signal bars show (intermittently gets (!) on the signal bars, but no internet regardless of what it says). I am positive that the moment i hang up this call with my gf, the internet access will be restored.

Will a logcat help in this manner?

Update... OK some weirdness about to be read... Here is a curveball... The INSTANT that I plugged in my USB cable for ADB, internet access/mobile data was restored on my phone. I had an instagram page trying to load for maybe 15 minutes as I attempted little fixes and whatnot. The browser remained open while I plugged in the phone. This is how I know it was instant upon USB plugin; because the page loaded literally within a fraction of a second when the USB C connection was made. I did not hang up the call, and am still on it. But be advised this was a 3-hour long call... Not sure if/when it will occur again. I'm sorry, I swear I'm not making this up, I know how it sounds...

Mind you, I didn't even open up a console or have an ADB session running. i simply plugged in my USB C from PC to phone. Logcat is useless now. I will see if i can get data to drop while on this call, WITH the cable staying in. The symptom is entirely random, I cannot reproduce it (yes, i've tried) - it just happens when it happens.

another update : 4 hours later (yes I intentionally left the call active), no data drop. Remember, the USB C cable is still plugged in from my PC to the phone, im not running ADB or anything, it's just plugged in. ADB is of course enabled in Dev settings. I'm going to download an app to catch the logs instead. I just don't know what the simple USB connection was able to trigger, the the phone was not able to do on its own. i am at a loss for words.
[Motorola Edge 40 Pro  / Moto X40 (China)] Soketto:
Hey just to chime in, I recently got interested in phone chargers, and as an aside installed the Wattz app on F-droid to check charging voltage/current.

On my X40 I noticed that I'm unable to get any voltage over 5v and around 8A (40W) charging. This is with stock cable and stock 125W fast charger. Have tried multiple different cables/charger combinations.

Occasionally the phone will say it's charging but draw nothing from the charger.

I'm wondering if it might be related to what @dvaldes409 said:

Also a possibly related

Not a huge issue but it seems like maybe some firmware for PD is not working as expected?
[Motorola Edge 40 Pro  / Moto X40 (China)] nTOHS:
Hello!Maybe someone knows how to start gpay.

Playintygritynext no work now.Can I ask you to sign Los with a digital key?Read about it on 4pda.If it possible to make google walet work without Magisk
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
New test build is up! lineage-21.0-20240611-UNOFFICIAL-rtwo contains changes to carrier configs so please test all carriers, especially users who have any potential carrier-related issues. I also boosted mic volumes as requested by some users so please test all mic instances if there's any distortion from further boosting (voice recording, VOIP, VOLTE, UMTS calls, etc). It also contains vendor blob and device firmware updates from rtwo_g-user 14 U1TR34.8-30-13-2-2 5b4b0d-dde58 release-keys - RETAIL variant.

Any bugs please report with logcat

LineageOS for rtwo - Browse /lineage-21/lineage-21.0-20240611-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)] mxz55:
I have used 165hz screen refresh rate for months on LineageOS, and it has minimal to no implications on battery life. I use it as both minimal and peak, as well im an all-day long multimedia user.

I propose to improve rtwo's out of the box configuration; the default right now is 60hz, which produces an experience as if this powerful device has very poor performance. But in reality it's down to using a low Refresh rate; of course it's customizable, but some users may never realize.

Let's change it to 165hz or at least 120hz? Any other opinions?

@ThE_MarD
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Hmm, well stock ROM in Auto which I believe is the default (I haven't used stock since like, week 3 I think with my rtwo? So memory is a bit fuzzy lol) does 60 min and 120 peak, so we could set that?

PS, anyone who wants to try RCS on Google Messaging app? You must pass device integrity as it meow checks for that... The annoying thing is it will still let you toggle on RCS if device integrity fails, but it won't tell you that's why sending and receiving fails...
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
You're correct, that's what it does, but LOS doesn't (so we get a subpar experience out of the box). Let's change it to that

How about also overwriting the setting once (if it's not customized to 165hz), so ppl with existing installations will benefit right after OTA
[Motorola Edge 40 Pro  / Moto X40 (China)] syrkles:
Even people passing device integrity on pixels are having issues...I know a few devs working to relock bootloader's on custom to get rcs working properly
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@syrkles I know on Lenovo phones it is possible to relock bootloader on custom ROMs, but afaik on Motorola it'll give you a corrupt bootloader message and then you're super screwed as you can't unlock bootloader again

Also on Moto X40 variants, you can only unlock bootloader once. If you relock? Flashing locked gets triggered and then you're stuck with bootloader locked forever... So for those models I'd recommend never relocking
[Motorola Edge 40 Pro  / Moto X40 (China)] syrkles:
Yes I understand that I would never dare to try it.....just stating that pixel devs are doing it just to get rcs working....I think us moto people are going to have to go without rcs if we want to run custom roms is all I'm saying
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@syrkles it should be possible with mods for us but I haven't tried. Afaik we need to hide bootloader unlock and also pass device integrity.

Maybe someone here who has been able to do so and can confirm RCS works has a guide?
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
yes, rcs is tied into root checking now, and device integrity.

also, roms signed with test_keys, nor can it contain any of the banned strings in the kernel. (lineage is one of the banned strings)
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
@ThE_MarD I have a strange bug: sometimes the touch stops working (tapping/swiping the screen don't do anything), while buttons work and I have to reboot it to get it working again.

I've captured some logcats (attached), but I can't find the cause of it, I don't know if it's something related to LOS (it mentions it can't change display mode).

Any ideas?

Thanks
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I've never had or heard of touch issues like @Tilde88 so I hope you don't have a faulty unit or physical damage to the screen/connectors you're unaware of. Do you recall any impact or fall to your phone?
[Motorola Edge 40 Pro  / Moto X40 (China)] Tilde88:
I think you mentioned the wrong person lol
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
ah yeah, it was for @maicol07
[Motorola Edge 40 Pro  / Moto X40 (China)] maicol07:
No, It happened recently (some week ago) and it has never fallen
[Motorola Edge 40 Pro  / Moto X40 (China)] debx:
Thanks for new official build.

Bootlogo works fine.

Sms i have to check till monday and give resumee

Bluetooth bug still there. See the pictures. After first disconnecting an reconnect. No more show all informations.

Update:

Logo works after few times of rebooting

Sms works for now

Next bug, i add a screenshot.

After rebooting, all apps are closed, the phone become hot as ****! I can only see that the space become high using. After a while and sucking a lot of battery goes down on low using mode.

Update 2:

I reproduce the hot bug.

After restart. Tipe only the sim code and leave the phone for five minutes. The temerture is normal.

When you after restart tipe the sim code an directly use your phone. Becomes verry verry hot !
[Motorola Edge 40 Pro  / Moto X40 (China)] ghjw35hgfd:
Still have some questions about sim cards

Before the reboot it was card 1 priority, but after the reboot it's card 2 priority. It happens sometimes, not 100%.

Maybe this is still caused by the QTI Telephony Injection
[Motorola Edge 40 Pro  / Moto X40 (China)] inkaine:
That's correct. I never touched the refresh rate settings and it's on Auto. I turned on refresh rate display in developer settings and seems to stay on 90 during general use and goes down to 60 in gaming mode for me.

Edit: interestingly enough it goes to 120 on the lockscreen.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Heyyo, new test build going up! It may take 30 mins from this post to be available. lineage-21.0-20240625-UNOFFICIAL-rtwo contains compatibility fixes for Android 14 QPR3 and the whole device must be tested and confirmed ready for daily driver before LineageOS official builds can resume for us.

Any bugs please report with logcat

Special thanks to Syrkles Hernandez for assisting with working on the compatibility fixes

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

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

sourceforge.net