yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
I can confirm 2 sim cards are working fine in the last LOS build, the problem with my mobile internet was not LOS fault and has been fixed
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
Hi.Is there a guide how to do that? Im very interesed in have microg in lineage os. Thanks
[Motorola Edge 40 Pro  / Moto X40 (China)] Big Dumb Object:
Install Magisk. If Magisk doesn't survive during ROM update (it's a known issue) – try the Custom Recovery installation method or switch to Lygisk.

Choose and Install some Signature Spoofing patch if your ROM does not support it.

Now I'm looking in favor of renewed FakeGApps module for LSPosed.

Install the preferred bundle of MinMicroG. MinMicroG can be applied during ROM flashing before the first system startup - this is its advantage.

Recently, I switched to microG Installer Revived because of its ability to self-update with Magisk and better permissions management.

If my guide sucks, learn more from here: https://old.reddit.com/r/MicroG/wiki/index
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
Thankyou
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
The next build (which i expect to arrive in a couple of days) will mainly be to get the September 2023 security patch
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
I am having a few issues with Desktop Mode, I am not sure which ones are the ROM fault or which are because of the sh-itty state of Android Desktop, but I though I'll report them in case the devs can take a look.

One, sound does not work. With Ready For it was working automatically, but now I can not get sound out of the TV. What's even weirder and makes me think it might be a kernel or ROM problem is that, when and only when connected to the TV, if I try to open the sound section of Settings, the Settings app freezes, then the menu opens then freezes again... and the volume changes value on its own. Very weird. When I disconnect the USB cable to the TV, everything starts working fine again.

Two, the apps have a black border on top and sometimes (app and position dependent) in the sides and bottom. The desktop does not have this problem and occupies the full screen fine.

Three, the first time I connect the phone to the TV, I can move the windows of the apps around the desktop, just like you do in a computer. If I disconnect the USB cable and then connect it again, I can no longer move the windows around. The only way to fix it, is to restart the phone. I suspect this is an Android Desktop mode problem, not a ROM one, but just in case.

All of this is with Experimental Desktop Mode enabled in Developer Options, plus the other 3 android desktop toggles enabled. I have tried different combinations of these toggles enabled and disabled but same problems.

I did not though I'd say this but I miss Ready For. It worked solidly.
[Motorola Edge 40 Pro  / Moto X40 (China)] liko9477:
Hello.

I noticed battery life is much worse than with the original ROM, any tips?
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
Yes, I have noticed this too. At least with the last build.

Also with the last build, I am getting random freezes, the whole system. They do not happen often, just like every 2-3 days, and I can not guess the trigger, seems quite random.

Yesterday, the phone even restarted itself after one of these freezes.

How do I get the logs so the devs can take a look at what might be happening?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Edit: build removed

@Drasner if you have crashes please provide logcat when it happens as it could be SELinux related since we are enforcing
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
For anyone trying: the new build failed to upload, im sure it will get fixed when ThE_MarD logs on again
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
I just got a second freeze that ended up in the phone restarting itself.

I am going to try the new update tomorrow and see if the freezes continue. If they do, I'll post the logs.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
New test build is going up! It will be done uploading in 20 minutes. lineage-20.0-20230926-UNOFFICIAL-rtwo is the same as the previous build with September security patch and an selinux display/graphics fix and I tested this one and it boots. Sorry the last one I missed a repopick and I didn't test it as I was super busy with work...

LineageOS for rtwo - Browse /lineage-20/lineage-20.0-20230926-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 should say that i've not experienced any of the issues that Drasner is describing. Freezes, random restarts, and black borders on apps (as he described on page 7)? None of that was observed by other users, and while daily driving neither me or The_MarD have seen it, all we see is a smooth, very stable experience. To add to that, battery life is pretty good here and better than stock, as i said before it got improved by recent changes.

Not to say it shouldn't be followed up on, but that it could be something funky on @Drasner's device, or something went wrong while setting it up initially (flashing stage). One peculiar thing i noticed is that for each build uploaded at SourceForge, the main ROM zip download count never matches up, i.e is much higher than, any of the other IMG files required and uploaded to the same directory. I think a bunch of non intuitive users are doing bad flashes..

Also my results on the new build (Sept patch) : it feels even a little better, i guess the LineageOS sources being synced as well contained something good.
[Motorola Edge 40 Pro  / Moto X40 (China)] jimmie32:
My experience is that a clean flash of the latest RETUS base, booting it (this step is very important), then going to fastboot and flashing LOS gives me a much better time.

I haven't had the chance to rerun benchmarks on the SELinux-enforcing builds to see if performance issues remain for me. But I'll do it tonight to see if everything works better.
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
The black borders on apps only happens in desktop mode.
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
I can confirm the problem with sound in desktop mode, has to do with a problem in audio through hdmi.

I have tested and if I connect a Bluetooth speaker the sound works fine, even in desktop mode. The moment I try to route the sound through the HDMI, it does not work.

It was working fine with the original Motorola software.

Can anyone else test if they can play sounds through HDMI with this ROM?

EDIT: After dirty flashing the last update, same situation, audio through HDMI is not working.
[Motorola Edge 40 Pro  / Moto X40 (China)] ronnz98:
Are the vendor files for this device available somewhere?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@ronnz98 if you check the developer resources in post one and on the local manifest it shows where all the repos are

I'll add audio via HDMI doesn't work to bugs
[Motorola Edge 40 Pro  / Moto X40 (China)] ronnz98:
I did look. However the vendor files are not anymore here:

<!-- vendor -->

<project name="moto-sm8550/proprietary_vendor_motorola_sm8550-common" path="vendor/motorola/sm8550-common" remote="gitlab" revision="lineage-20"/>

<project name="moto-sm8550/proprietary_vendor_motorola_rtwo" path="vendor/motorola/rtwo" remote="gitlab" revision="lineage-20"/>
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@ronnz98 All the information is there. The remote says Gitlab, so it isn't on GitHub
[Motorola Edge 40 Pro  / Moto X40 (China)] ronnz98:
Thanks for your swift reply. I overlooked this!
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
Great, but ideally someone else should check if they get audio through HDMI with this ROM or not for confirmation.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Marc is preparing the next build, that brings a newer kernel codebase with latest ASB on top of latest CLO tags
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
A new test build is going up! It'll be ready in 30 mins or so. lineage-20.0-20231002-UNOFFICIAL-rtwo has a kernel rebased on the LOS qcom sm8550 repos and some minor display/graphics cflag and props tweaks (unfortunately it didn't fix the laggy boot animation though, oof). Please test every function! This will resolve the IPACM/libipanat issue that will get us LOS team approval to fork our trees onto the LOS GitHub org so it's very important that we are stable. Bruno mentioned that USB tethering might be broken on this setup though so definitely need someone to test that, please!

update! Had to take this build down fml... my build machine acted up... I did a repo sync and did my repopicks and then started a build and it spat out some weird out of memory error and I resumed the build and it completed but it seems to have skipped some kernel modules like camera.ko so I'll do another clean build and check it
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Nice to see we managed to get to upstream Linux with that as well ( Linux kernel 5.15.131 is from this month ) and on top of that, the latest Qualcomm sources are actively being merged in.

I can't ask for much more of what i like to see: the latest hardware and chipset, and latest software, on top of that the cleanest ROM that harnesses it all. I see a bright future of LineageOS on rtwo, maybe it's even gearing up to be one of the most well-supported devices in development scene, similar to how it was with the OnePlus 6T for years. That it's currently the best bang for buck on the €550 Moto X40 contributes to its appeal, if only all buyers discover how early we got this extensive custom ROM support, so that they can choose the most bloat-free, lightweight and privacy/security friendly way, elevating this device to peak performance over stock ROM.

In fact, LineageOS makes this phone the absolute #1 performing flagship of 2023, Geekbench multi-core is still at 5400+ for me, in contrast to other Snapdragon 8 Gen 2 flagships scoring 4800-5000
[Motorola Edge 40 Pro  / Moto X40 (China)] jimmie32:
This is awesome to hear that we are using the upstream Linux kernels and the latest patches now. Thanks so much for the hard work. I'll test this out :)

A quick question, is there any scenario where a dirty flash would not be recommended? Since I'm not using this daily (yet) I've been always reinstalling the base RETUS ROM + flashing LOS clean on top of it, but if dirty flashes work well and there's no bad things that are known to happen for doing so I'll probably do that as the updates are really frequent and I'd like to start using my Edge+ as a daily driver.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Dirty flashing really is no problem, we do it all the time

First feedback from myself: it looks like the new test build with kernel update is very stable

Edit: camera doesn't seem to work in my case, i forwarded logs (main feature is crash in /apex/com.android.runtime/lib64/bionic/libc.so and Motorola Camera error code 73400001). I also noticed overall instability after a few hours, but think that got traced back to a bugged Android WebView Canary install (due to which play services/gms crashed and triggered domino effect), so i won't scrutinize this LOS build on this unless it re-occurs with standard webview which so far it hasn't

Main part of camera logs:

Spoiler content hidden.
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@jimmie32 you won't need to worry about which stock ROM was installed last as we are including the proper device firmware to match the vendor blobs we use so it'll always have the correct stuff (y)

If it's a fresh install coming from say stock ROM? You will still need to first do the copy-partitions zip to ensure the inactive slot is populated before you can flash the lineage zip to it is all.

@mxz55 I took the build down oof, my build PC seems to have hit a weird out of memory error and then when I resumed the build it skipped a bunch of kernel modules like camera.ko as you'll see in logcat if you capture it from boot... I rebooted my PC and started a clean build so it should finish without errors meow and I'll double-check that the modules are there

I modprobe: Failed to load module camera.ko: No such file or directory
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Ok! Let's try again lol... It's uploading meow so it might take 30 minutes or so. lineage-20.0-20231003-UNOFFICIAL-rtwo definitely has a camera.ko and lots of other kernel modules. This build has a kernel rebased on the LOS qcom sm8550 repos and some minor display/graphics cflag and props tweaks (unfortunately it didn't fix the laggy boot animation though, oof). Please test every function! This will resolve the IPACM/libipanat issue that will get us LOS team approval to fork our trees onto the LOS GitHub org so it's very important that we are stable. Bruno mentioned that USB tethering might be broken on this setup... but I just tested it on my Windows 11 PC and my Chromebook and USB tethering definitely works for us! So that's a good sign I guess heh

LineageOS for rtwo - Browse /lineage-20/lineage-20.0-20231003-UNOFFICIAL-rtwo at SourceForge.net

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

sourceforge.net

It seems like the camera bugs for taking a picture during video recording is still there and same with pictures on Telegram and other apps so those probably aren't kernel related...
[Motorola Edge 40 Pro  / Moto X40 (China)] jimmie32:
On latest build camera works now and everything feels smooth. Going to give it a factory reset and start setting it up. Thanks for the hard work!

Update: It feels like in recent releases that Wi-Fi 6 is very slow and leading to dropped connections. I'm not sure if it's my router or something else - is there anything I can do to debug this or it would show up somewhere in the logcat?
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Two builds in one day! lol... This one's a small but significant change. It's uploading so give it 30 minutes or so. lineage-20.0-20231003-2-UNOFFICIAL-rtwo contains a swap of thermal-engine configs from rtwo.conf to rtwo-game-perf.conf as the default rtwo.conf throttles the SoC very agressively and really limits the performance. rtwo-game-perf.conf has a much better balance of performance while still not heating the phone too much so it'll be a better overall experience, especially for users playing 3D games.

LineageOS for rtwo - Browse /lineage-20/lineage-20.0-20231003-2-UNOFFICIAL-rtwo at SourceForge.net

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

sourceforge.net

From today's previous build: This build has a kernel rebased on the LOS qcom sm8550 repos and some minor display/graphics cflag and props tweaks (unfortunately it didn't fix the laggy boot animation though, oof). Please test every function! This will resolve the IPACM/libipanat issue that will get us LOS team approval to fork our trees onto the LOS GitHub org so it's very important that we are stable. I just tested it on my Windows 11 PC and my Chromebook and USB tethering definitely works for us! So that's a good sign I guess heh. I also tested mobile hotspot and it works fine too. The camera crashes when you take a photo while recording videos and photos using apps like Telegram are unfortunately still there so that might not be kernel related...

@jimmie32 this build will feel even more smooth heh! (y)

As for WiFi 6? Tbh I can't test it myself so maybe check the bandwidth of it and see what that looks like? I'm not too sure what we can do for that issue as annoyingly even my Edge 30 has WiFi bandwidth issues (and even on stock ROM too lol oof!!!)... it could be config related but so far I have no ideas... You could check logcat and see if maybe it spits out some errors I guess too???
[Motorola Edge 40 Pro  / Moto X40 (China)] jimmie32:
Thanks @ThE_MarD, I'll try to figure out what's going on with the WiFi.

The camera issue maybe is coming from upstream? Even users on the stock ROM report issues with the camera, which I'm not sure if it's related or not. Maybe the quality of the blobs from Moto are just garbage... https://xdaforums.com/t/motorola-ed...agram-stock-camera-bug.4633063/#post-89073167
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
I have dirty flashed the new build in my Moto X40.

- DP alt mode not working at all, confirmed in the chat. Previously video was working, sound was not. With this last build nothing works.

- I reported a few builds ago that I was getting sporadic 5-10 second freezes and sometimes reboots after the freezes. With the previous build I was getting freezes but no reboots. With this last one I have not gotten any freezes or reboots. It has only been 24 hours, so I'm not 100% sure it is fixed. I'll report back if it happens again.

- One weird thing I have noticed is, when I'm calling someone, if I put the call on speakers before the other side has pick up the call, I'll get no sound during the call. I have to hang up and call again. If I wait to put the call on speakers after the other person has picked up, everything works fine. This is new from this build.
[Motorola Edge 40 Pro  / Moto X40 (China)] lanbui:
Hi @ThE_MarD , I flashed the latest version(lineage-20.0-20231003-2-UNOFFICIAL-rtwo) from the latest RETUS firmware last night, most of bugs I met in early version have been fixed (GPS, fingerprint, lockscreen works fine), thanks for the work!

But I still find the same issue that I've found at the early version, I have to use telegram by vpn in my country, in usual, I can simply use telegram after I turned on some VPN apps (http proxy), but at LOS I have to set proxy (socks5) at telegram, I don't know if this is an known issue, it doesn't matter but I feel weird because I never met this issue at other ROM before, I hope this issue can be fixed.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
Since the very beginning, i experienced screen mishaps like random taps, interference from the curved screen edges (like: unintended holds, zooms, especially when you're scrolling and using the device one-handed in a way that slightly touches the sides)

Today i discovered that the "High touch polling rate" in Display settings is to blame for all that, i enabled it on day one and that it was worth testing without it didn't come to mind. So, this LineageOS specific feature isn't working properly on rtwo, i advise to not use it for now, and who also experienced this can review their settings.

Btw, i never experienced any issues like Drasner repeatedly described, i guess his freezes/reboots are the result of a bad flash, misconfiguration etc (which can explain why it resolved after he updated to latest build; whatever went wrong on his device was corrected). From my perspective, the ROM is extremely smooth and stable at the moment
[Motorola Edge 40 Pro  / Moto X40 (China)] luki2411:
How is the battery life compared to stock rom?
[Motorola Edge 40 Pro  / Moto X40 (China)] Drasner:
Or it could be that my device is a X40 and uses a slightly different firmware that was interacting differently with the ROM.

A bad flash is 100% a possibility, although the problems persisted through a couple of dirty flashes, but not sure why assume it has to be a bad flash.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
In recent builds it's really good, i think just a little better than stock

In other news, a new build with October ASB is being prepared and i would expect it to be uploaded in the next 48 hours. I like how it's been going with all recent updates; by being right on the spot with everything, even during unofficial status, we can give off a good sign for the solidity of support and what's to come.

Also, another status update on when we can apply for official status: at the very least camera-in-3rd-party apps bug has to be fixed, and preferably also DP alt mode (SGCMarkus is about to start working on it).. everything other than these 2 is stable, really.
[Motorola Edge 40 Pro  / Moto X40 (China)] jimmie32:
Firmware with moto devices is weird. I've had wildly different results even when just running different variants of the stock firmware. So it could be just device peculiarities. Even whether or not you boot the stock firmware before flashing LOS could matter...
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
Heyyo, new test build is up! lineage-20.0-20231009-UNOFFICIAL-rtwo contains October security patch

LineageOS for rtwo - Browse /lineage-20/lineage-20.0-20231009-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)] luki2411:
Any other changes in the new update?
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
I just want to post a bit of advise for the Magisk Rooted users under us: don't run Magisk Debug builds on your Edge 40 Pro / Moto X40 / Edge+ (2023). I could reproduce a nasty effect that does happen on rtwo but not on dubai for example, where all Chromium-based apps such as Chrome, Cromite, WebView (if you changed webview provider to your own) will malfunction.. fail loading pages, render blank content if it eventually loads, etc. Details on this and the advise in general, see my write up @ https://github.com/topjohnwu/Magisk/issues/7408#issuecomment-1756892351

Magisk Debug releases may feel like they are suitable for daily use, it's not sluggish or anything, but clearly for rtwo it tampers/interferes with some system level stuff.
[Motorola Edge 40 Pro  / Moto X40 (China)] mxz55:
No.

When it comes to the update policy of a brand like Motorola, the main subject is fear of not receiving enough security patches in a timely fashion. By doing it in LineageOS whenever the Android Security Bulletin with patches gets released, even if we don't bring other updates to the table, we are already favoured by users. I'm just saying, nothing wrong with intermediary builds that only sync with LineageOS sources and bring a security patch, as this one did.
[Motorola Edge 40 Pro  / Moto X40 (China)] clubwagon:
Im following close this threat waiting for the official release 😀, i has a question, when the official build come out , this will have the original motorola camera? Thanks
[Motorola Edge 40 Pro  / Moto X40 (China)] ThE_MarD:
@clubwagon yes it will

update: Added that the offline charging animation doesn't work to bug lists as I just noticed it... oof
[Touch Diamond, MDA Compact IV ROM Development] krussa:
Where to buy htc touch diamond motherboard
[Touch Diamond, MDA Compact IV ROM Development] charli:
Think thats difficult man
[Touch Diamond, MDA Compact IV ROM Development] charli:
But look in ebay, maybe you find something
[Touch Diamond, MDA Compact IV ROM Development] xam.co:
Hi ,i have 1 motherboard for sell .Please contact me if you needed at morenomassimo@libero.it
[Touch Diamond, MDA Compact IV ROM Development] ibrahim.hamdy:
I need on too

if any one got please contact me asap

ibrahim.hamdy @ hotmail.com
[Touch Diamond, MDA Compact IV ROM Development] Usemyass:
Need a Motherboard HTC Diamond

I need a motherboard for HTC Diamond : willingass@wanadoo.nl
[Touch Diamond, MDA Compact IV ROM Development] ibrahim.hamdy:
sent u message
[Touch Diamond, MDA Compact IV ROM Development] ibrahim.hamdy:
am still want the board.. if anyone got....
[Touch Diamond, MDA Compact IV ROM Development] Dimitris09:
in need for diamond mainboard :(

if there is any spare please contact me I need one asap couse I destroyed the lcd connector of my sisters diamond... (jsofian@hotmail.com) Thanks!!
[Touch Diamond, MDA Compact IV ROM Development] Mr.Humble:
hi i need mainboard HTC touch diamond...please contact me by email or YM at Feriadi7@yahoo.com
[Touch Diamond, MDA Compact IV ROM Development] cheetozz:
Wrong forum.
[Touch Diamond, MDA Compact IV ROM Development] norgan:
maybe wrong forum but i need one too lol my diamond just died :( nath@norgan.net
[Touch Diamond, MDA Compact IV ROM Development] barbapappa_86:
I need one to for my diam100. Bricked it :D. Barbapappa_86@hotmail.com