yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 20 Pro] npjohnson:
/shrug I can no longer recreate the BSOD on 20 or 21 - going to consider it closed unless someone else pops up.
[Motorola Edge 20 Pro] Eric_Close:
So sad. The freeze issue persists in the LineageOS 21 unofficial build version 20240205.

* issue tracker
[Motorola Edge 20 Pro] :
I can confirm the freeze issue occurs in lineage20 20240205 build. It was okay for the entire first day (yesterday) but screen freezed today. I was tethering when the freeze happened which may or may not be related. Sorry, I am unable to reliably reproduce the issue since it seems to occur at random.
[Motorola Edge 20 Pro] npjohnson:
bad (but really good) news - only the panel fix made it in for the 0205 build.

The _next_ build will have the modem crash fix - which should stop the black screen/freeze issue.

The black screen had two issues.

One where it would just BSOD randomly (panel fix), and one where onscreen items freeze then BSOD - that's the modem issue.
[Motorola Edge 20 Pro] zpunout:
On version 20-20240205 I seem to get a freeze about twice a day when hotspot tethering. If I have fingerprints registered to unlock the phone, the freezing occurs more frequently. On two occasions, I suspect the tethering freeze happened when the device being tethered became out of range from the Moto Edge 20 Pro (no fingerprints registered). I only discover the freeze upon unlocking the phone or a few seconds afterwards, not during prolonged screentime usage. I hope this info helps with reproducing the issue. When I'm home again next week, I'll try capturing a logcat.

[Edit: It's been 24 hours since my previous feedback and the phone hasn't frozen once in that time. Such an elusive bug to reproduce ]
[Motorola Edge 20 Pro] raulillo88:
I've never done tether but in my experience, occurs often when I'm doing exercise and have more devices connected to the bluetooth (headphones and smart band). Maybe could also be related with modem problems
[Motorola Edge 20 Pro] zpunout:
Ok, so I'm home again and my phone had a bsod after nearly 3 days without a problem. It occurred while hotspot tethering (2 devices connected). The connected device lost internet connectivity, so I toggled the hotspot icon in the quick settings. The hotspot icon animated endlessly and the phone became unstable and eventually unresponsive. After another minute, the screen went black. Unfortunately, I was unable to capture a logcat as adb devices reported the device as offline.

After a forced reboot, I ran:

adb root
adb remount
adb bugreport

Is there anything in the 7MiB bugreport file which could be useful to find the issue?

[edit: I just installed LogFox from F-Droid with root permissions granted. Am recording logs now and hope to capture a crash]
[Motorola Edge 20 Pro] npjohnson:
Not really sadly.

But again, I think it's related to the modem/comms crash.

Which I've fixed in the next build on the 12th
[Motorola Edge 20 Pro] raulillo88:
Could you check for fix NFC payment too? Regards
[Motorola Edge 20 Pro] npjohnson:
Not something I can or will fix. NFC itself is fixed, payments are safety net related - I can't do anything about it.

My workaround for it was patched.
[Motorola Edge 20 Pro] raulillo88:
I've had another freeze one hour after last build installation.

Seems related with modem again, because appears no data signal exclamation. This time have been different, because I can awake the screen and even unlock phone one time (does not respond to anything with phone unlocked). Then I've locked the screen, and after that, only awakes screen but can't unlock.

Regards
[Motorola Edge 20 Pro] zpunout:
I've been trying to catch this with the LogFox app for a couple of days but haven't had an issue yet. Murphys Law. Are you willing to install Magisk and record logs with LogFox or similar as well?
[Motorola Edge 20 Pro] npjohnson:
FWIW I was able to hit the BSOD at one point.

The issue here is there appear to be a few different ways things can crash, and the one that I could recreate no longer happens after the SSR ram dump fix from last week.

I've solved another one this week (for the next build), but yeah a log would be vital!
[Motorola Edge 20 Pro] :
I had 2 automatic reboots in lineage-20.0-20240212. The screen didn't freeze in this build but the mobile just rebooted itself. FYI, I was tethering when the reboots happened.
[Motorola Edge 20 Pro] Eric_Close:
Same here. My device encountered an automatic restart issue around 04:00 AM GMT+8 on 20240214 while I was asleep..

I'm uncertain if it experienced freeze or black screen problems before this.

I captured the logs approximately 5 hours after the restart, unsure if they are still relevant.

If necessary, I will attempt to capture logs the next time the device experiences an automatic restart.
[Motorola Edge 20 Pro] npjohnson:
we really need logs of the crash - not of the afterwards.
[Motorola Edge 20 Pro] npjohnson:
good news - this crash we can confirm is fixed in the next build, https://github.com/LineageOS/androi...mmit/9104484a77e9631ec0de309b9f939fff9864b5f4
[Motorola Edge 20 Pro] raulillo88:
I must say, after first reboot, I haven't another freeze. But if this fixes any possible of any freeze it is good news.

Regards
[Motorola Edge 20 Pro] tohigh:
China variant camera failed.
[Motorola Edge 20 Pro] npjohnson:
Mmmmm. Okay, I'll mark the chinese variant as unsupported for now, but I anticipate that it's something missing from the kernel.
[Motorola Edge 20 Pro] tohigh:
logcat
[Motorola Edge 20 Pro] npjohnson:
while the file might be helpful, all you've done is said "logcat" lol
[Motorola Edge 20 Pro] Eric_Close:
Edge S Pro (SKU: XT2153-1 & codename: pstar, same with other variants) China variant.

There may be slight hardware differences between variants.

But I converted it into a RETEU (Retail Europe) software channel. And then flash the full RETEU firmware, everything works fine. After that, I was using LineageOS 19.1 and almost everything worked fine too.
[Motorola Edge 20 Pro] MrZZZ123:
this full log file
[Motorola Edge 20 Pro] npjohnson:
Well, I have RETEU and camera works fine so there's defs a difference here.

Can you try formattting data and seeing if it works then?

So, is your device also retcn that you converted to retail?
[Motorola Edge 20 Pro] MrZZZ123:
CHINA VERSION (XT2153-1_PSTAR_CMCC_12_S1RAA32.54-37-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ) UPDATE TO RETAIL VERSION (PSTAR_RETAIL_12_S1RAS32.41-20-16-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) , AND I INTO bootloader mode , run fastboot -w command , and fastboot flash dtbo dtbot.img && fastboot flash vendor_boot vendor_boot.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot reboot recovery,AND adb sideload lineage***.zip flashed the LineageOS20.0, just the LineageOS20 have the bug , LineageOS19.1 it worke , not the bug .
[Motorola Edge 20 Pro] Eric_Close:
By the way, the LineageOS 20 unofficial build by Markus (another LineageOS maintainer), does not have the above mentioned problems on Chinese variant (except the same MTP issue).

Both the built-in camera (Aperture), and other apps that needs camera permission can access the camera normally. The flashlight works fine too.

I'd like to know what the difference is that's causing this.
[Motorola Edge 20 Pro] npjohnson:
retcn people - please try the 0621 unofficial and lmk if it works - I made a small change that bring us closer to markus's build.
[Motorola Edge 20 Pro] Eric_Close:
Where can we download the 0621 unofficial build from?
[Motorola Edge 20 Pro] npjohnson:
the link to the unofficial in the OP
[Motorola Edge 20 Pro] Eric_Close:
I'm sorry, I couldn't find the link that I can download the 0621 unofficial build. If you mean this, page not found now 🤣.
[Motorola Edge 20 Pro] npjohnson:
I'll fix that link: https://github.com/ods-releases/pst...ar/lineage-20.0-20230621-UNOFFICIAL-pstar.zip
[Motorola Edge 20 Pro] npjohnson:
nothing in the reply - did it work?
[Motorola Edge 20 Pro] npjohnson:
sorry, failed to reply to you message
[Motorola Edge 20 Pro] Eric_Close:
Well done! There aren't any issue that I mentioned (except the MTP issue) right now.

When USB debugging is enabled, run 'adb logcat', then turn on the file transfer, adb logcat will interrupt immediately.

And another problem I found is that the screen flickers when the minimum and peak refresh rates are below 90Hz (even the Anti flicker option is on).

Finally, thank you for your work and if there is anything I can do, I will cooperate when I am free.
[Motorola Edge 20 Pro] npjohnson:
fix merged, next official build will fix it.

As for MTP, unsure, I'll look into it, but it works here for me
[Motorola Edge 20 Pro] Eric_Close:
MTP logcat
[Motorola Edge 20 Pro] summer9:
Hi, my pstar is using the goodix fingerprint module, can I merge it in the next build? markus fixed it for me in his build.

https://review.lineageos.org/c/LineageOS/android_device_motorola_sm8250-common/+/357800
[Motorola Edge 20 Pro] summer9:
I can always test unofficial builds.
[Motorola Edge 20 Pro] Eric_Close:
I found some problems after installing Magisk with your unofficial 20230621 build but not present in the official build.

The boot up will be slow. Mobile data is not available, it will prompt no signal when calling, IMEI shows unknown. And device may reboots automatically after a while. adb logcat does not work at all even USB debugging is on.
[Motorola Edge 20 Pro] pandr-moto:
Hi npjohnson

Thanks for developing this rom for moto edge 20 pro users like myself, appreciate the time and effort involved.

Followed the upgrade 19.1 to 20 instructions on the device's wiki page and everything running sweet as...except for camera not functioning "camera keeps stopping error" (not critical for my usage at this time and forum notes suggest you might be exploring that for the next build)..install to OS 20 was quick and smooth, previous settings were unaffected, thanks again
[Motorola Edge 20 Pro] deepmean:
I tested unofficial build and got dead screentouch ，how can I back to official one？ Im suffering bootloop after flashed back. Please help me out.
[Motorola Edge 20 Pro] npjohnson:
merged - next build will have it - thanks for the reminder.

Makes no sense - They are build from the same source - sounds like you installed a magisk patched image of the official ROM and not the unofficial? The mismatch would kill modules which would break a lot of things.

Camera is fixed in next build for retcon users

Makes no sense, built from same source - sounds like you flashed a funky boot or vendor_boot image - just follow the wiki and you'll have a fine experience.
[Motorola Edge 20 Pro] Eric_Close:
So weird. I installed a magisk patched image of the boot.img that extracted from payload.bin in your unofficial build (instead of the boot.img from Stock ROM).

Then I reverted it to the original boot.img of your build and tried to install Magisk using adb sideload Magisk.apk, experiencing the same problems too.

Install magisk in the same way, without these problems in the official build.
[Motorola Edge 20 Pro] npjohnson:
That's really weird. Not sure what magisk is doing to break that stuff.

Maybe some selinux stuff that they stub out.
[Motorola Edge 20 Pro] summer9:
Do you need me to perform the relevant tests? I can always test.
[Motorola Edge 20 Pro] npjohnson:
Nope, appreciate it tho.
[Motorola Edge 20 Pro] summer9:
Okay, message me if you need any other tests.
[Motorola Edge 20 Pro] Eric_Close:
I found the random black screen problem in the LineageOS 20 official build.

This was fixed by electimon earlier with this commit, but I found that it was not merged into the 20 branch.

Can we merge it into the next build?
[Motorola Edge 20 Pro] tohigh:
I found 2 bugs:

1. an old bug come back, can't wake up screen.

2. the notification sound such as unlock screen is delayed.

@npjohnson
[Motorola Edge 20 Pro] npjohnson:
Merged.
[Motorola Edge 20 Pro] pandr-moto:
Since upgrade to OS20, others cannot hear me on phone calls although i can hear them.. also calling and texting function are working, contacts and call history migrated over in tact .. mic appears to be on, not muted .. still checking if its a setting on my device but unable to rectify with couple days checking and researching. As a newbie I unsuccessfully tried to revert back to 19.1(which didnt have the sound issue), but was able to upgrade back to OS20 .. I'm hesitant to consider reverting back to stock as the moto rescue tool doesnt seem to support the edge 20 pro anymore .. posted in case anyone else experiencing the audio issue so it can be looked into for a fix.
[Motorola Edge 20 Pro] npjohnson:
what carrier and what variant?

And what firmware did you start on stock wise?
[Motorola Edge 20 Pro] pandr-moto:
Carrier is Optus (australia) .. and this is where my newbieness comes in when answering about the variant .. model is XT2153-1 made in china but sold in Australia for use here.. was shipped with android 11 and upgraded to 12 once activated ... however not long after purchasing i switched to lineage OS 19.1 .. have been very stable with no issues for many months .. even random black screen wasn't an issue after a few of the weekly updates ..if there's more info to better answer the variant question please let me know.. just no sound on me calling out has me baffled, sure i have permissions correct
[Motorola Edge 20 Pro] Eric_Close:
You can figure it out with this command (when your device is in fastboot mode):

fastboot oem config carrier

Or if you are using the Stock ROM, you can find it in Settings → About phone → Software Channel.
[Motorola Edge 20 Pro] pandr-moto:
Microsoft Windows [Version 10.0.22621.1848]

(c) Microsoft Corporation. All rights reserved.

C:\platform-tools\platform-tools>fastboot oem config carrier

(bootloader) <UTAG name="carrier" protected="FALSE">

(bootloader) <value>

(bootloader) </value>

(bootloader) <description>

(bootloader) Carrier IDs, see http://goo.gl/lojLh3

(bootloader) </description>

(bootloader) </UTAG>

OKAY [ 0.011s]

Finished. Total time: 0.012s

hmmm doesnt show the ret value?

only other info in fastboot mode was:

product/variant: pstar XT2153-1 256GB PVT
[Motorola Edge 20 Pro] Eric_Close:
Well... Try this command instead.

fastboot getvar radio

Or maybe you need to go back to the stock rom, and then find the software channel of your device.

By the way, I installed the official LineageOS 20 for a while, and then go back to the stock rom after I found the camera issue. Didn't test the phone call yet, I will try until the next Lineage build arrives.
[Motorola Edge 20 Pro] Eric_Close:
After testing, same problem here.

The built-in recorder app can work normally, however, the voice cannot be heard on the other side during the phone call. A bit like the previous camera issue, which was not present in the markus's unofficial 0601 build too. 🤣

And in the telegram group, there is an Indian bro who have also reported the same problem.
[Motorola Edge 20 Pro] pandr-moto:
Thanks Eric_Close for testing/confirming that it isn't just me re: the phone..

On the variant, result of getvar command was:

Fastboot Flash Mode is 'Secure' and Tools Mode Config 'disabled' if this is affecting expected results? Also, can you point me in direction of a decent guide to revert to stock? guessing i can't just factory reset, and would need to know variant details? Otherwise i can just see what happens with next build. Appreciate the advice.
[Motorola Edge 20 Pro] npjohnson:
So, this Markus used my trees for that build lol.

So, are you sure it works on markuses?
[Motorola Edge 20 Pro] npjohnson:
LSMA rescue tool from Lenovo will do it all for ya.
[Motorola Edge 20 Pro] pandr-moto:
I wish LSMA tool would do it all for me lol .. however i get this message:

using the IMEI1 info off the box
[Motorola Edge 20 Pro] Eric_Close:
Yes. I’m sure it works on markus’s unofficial build, lol. 😂
[Motorola Edge 20 Pro] npjohnson:
which dated build?
[Motorola Edge 20 Pro] Eric_Close:
lineage-20.0-20230601-UNOFFICIAL-pstar.zip from Google Drive.
[Motorola Edge 20 Pro] summer9:
I'm using your unofficial build and there is no sound issue on the phone call, the other can hear my voice, the version is this

But this version doesn't work with Magisk, I'm using 19.1 kernelsu.
[Motorola Edge 20 Pro] npjohnson:
So, he built directly from our trees... sooooo that doesn't make a ton of sense.

This confuses me more, as I also have no issues on normal or VoLTE calls. So, Eric, what type of carrier are you on, and does it use VoLTE?
[Motorola Edge 20 Pro] Eric_Close:
I'm confused too, my carrier is CTC (China Telecom) and I only tried the VoLTE call.

The phone comes with a dual SIM slot, not sure if it's the same as other variants.
[Motorola Edge 20 Pro] Eric_Close:
You can flash the stock rom via TinyFastbootScript, and read the usage in the website.

Download the firmware that matches your software channel:

* firmware download link
[Motorola Edge 20 Pro] npjohnson:
Can you try the opposite sim slot?

Volte on sim2 can be... Funny.
[Motorola Edge 20 Pro] Eric_Close:
I tried it just now. It didn’t work, even though I tried another carrier sim card CMCC (China Mobile, I inserted 2 sim cards there). Then I tried Google phone instead of aosp dialer, not working too.

And the Indian bro tell me his carrier is Jio, Volte too.

I think it’s not carrier releated, official 19.1 and unofficial 20 would be normal with it. Don’t really know what’s difference between them.
[Motorola Edge 20 Pro] pandr-moto:
thanks again eric_close..might await the next build to see if corrects the situation then i'll explore stock maybe, appreciate the links.. also tried downloading google phone dialer and same result as above
[Motorola Edge 20 Pro] Maxi693:
Has anyone tried the new update?

Could you tell me if it still has errors?

Please
[Motorola Edge 20 Pro] Maxi693:
great job by the way

I'm still sticking with 19.1 until 20.0 is more stable
[Motorola Edge 20 Pro] summer9:
I tested 0627 official and I encountered fingerprints not working (my fingerprint module is goodix) and camera not working.

I used in turn the markus build unofficial (no above problems), the npjohnson build unofficial no above problems), and the 0627 official.

I think it might be a problem with the official build tool.
[Motorola Edge 20 Pro] Maxi693:
I have no idea, maybe

Maybe I'll try it tomorrow anyway
[Motorola Edge 20 Pro] fZkom2dj:
Hi npjohnson,

Thank you for LOS 20.

I just updated from last week's build to LOS 20-20230627-NIGHTLY-pstar and am still having camera issues as others have reported earlier in the thread.

My torch is also still not working, in the quick settings tiles it is greyed out and says "Camera in use". I have tried third party camera apps without success.

I upgraded from LOS 19.1 (Android 12).

Otherwise, everything else (fingerprint and phonecalls) work as expected.

Thank you again
[Motorola Edge 20 Pro] Eric_Close:
Bad news:

A couple of friends and I found that the camera issue is still present in the official build 20230627. And one friend who uses Goodix fingerprint scanner, told me that the fingerprint is still not working. I guess there is a conflict between electimon and Markus' goodix related commits, I'm not sure.

And I started trying to follow the official wiki to build it myself, everything was fine at first, no errors reported, until this section [Extracting proprietary blobs from payload-based OTAs].

The following errors were reported, you can check the attachment for details.

I'm not sure if these errors are related to the camera and fingerprint issues, I hope it will helps you to troubleshoot the problem.
[Motorola Edge 20 Pro] fesdonomist:
Seconding this, I have the same issues. I also upgraded from LineageOS 19.1. The app WO Mic doesn't work for me (nothing comes through), but I don't know about phone calls. Haven't tried.
[Motorola Edge 20 Pro] npjohnson:
getprop | grep date

please.

Sounds like a partition isn't flashing.
[Motorola Edge 20 Pro] Eric_Close:
[init.svc.update_engine]: [running] [init.svc.update_verifier_nonencrypted]: [stopped] [ro.boot.vbmeta.invalidate_on_error]: [yes] [ro.bootimage.build.date]: [Wed Mar 8 09:55:29 CST 2023] [ro.bootimage.build.date.utc]: [1678290929] [ro.build.ab_update]: [true] [ro.build.date]: [Wed Mar 8 08:46:08 CST 2023] [ro.build.date.utc]: [1678286768] [ro.odm.build.date]: [Wed Mar 8 09:55:29 CST 2023] [ro.odm.build.date.utc]: [1678290929] [ro.product.build.date]: [Wed Mar 8 08:46:08 CST 2023] [ro.product.build.date.utc]: [1678286768] [ro.system.build.date]: [Wed Mar 8 08:46:08 CST 2023] [ro.system.build.date.utc]: [1678286768] [ro.system_ext.build.date]: [Wed Mar 8 08:46:08 CST 2023] [ro.system_ext.build.date.utc]: [1678286768] [ro.vendor.build.date]: [Wed Mar 8 09:55:29 CST 2023] [ro.vendor.build.date.utc]: [1678290929]
[Motorola Edge 20 Pro] npjohnson:
.... What build are you even running?

March 8th?

It looks to me like your device isn't flashing things at all lol.

Id flash stock, then return to the latest lineage build.
[Motorola Edge 20 Pro] Eric_Close:
Sorry. I am running the Stock Android 12 now. I'll resend the output after flashing the official LineageOS build.
[Motorola Edge 20 Pro] Eric_Close:
The official lineage build output:
[Motorola Edge 20 Pro] npjohnson:
we are looking into this now.
[Motorola Edge 20 Pro] summer9:
May I ask what was updated in 0702?
[Motorola Edge 20 Pro] fZkom2dj:
There might be another place, but I've always checked changes here:

LineageOS Downloads

download.lineageos.org
[Motorola Edge 20 Pro] summer9:
I used the build of 0702, but the bug still exists.
[Motorola Edge 20 Pro] fesdonomist:
Same for me. Camera and torch still not working.

I've discovered another issue, and that's Bluetooth audio not working with my headphones. I get no output, and then when I try to select and reselect them when playing music, I just get it coming out of the phone speakers.
[Motorola Edge 20 Pro] npjohnson:
We figured out all of these issues - hint: It was a really dumb reason.

New build will have _all_ of this fixed.

New builds rolling tmrw.
[Motorola Edge 20 Pro] npjohnson:
We fixed the issues - tomorrow's build will work.
[Motorola Edge 20 Pro] summer9:
ll我们

thank you
[Motorola Edge 20 Pro] fZkom2dj:
Thanks team. Can confirm the latest build resolved my camera and torch issues.
[Motorola Edge 20 Pro] Maxi693:
Amazing

I can't wait to try it
[Motorola Edge 20 Pro] summer9:
Thanks team.

I have discovered a bug where enabling USB debugging in Developer options prevents file transfer functionality. The file transfer only works when USB debugging is disabled.

But other users have reported that using Magisk can cause issues with SIM card functionality, so currently I am using KernelSU.

But this bug does not affect my use.
[Motorola Edge 20 Pro] fesdonomist:
What was the issue? You guys forgot a line or something?
[Motorola Edge 20 Pro] npjohnson:
The manifest that tracks vendor repos lacked a pstar entry, so common proprietary files were being included but not pstar specific ones.

My unofficials included it but not officials.

Normally because those are inherit product entries it would have failed to build BUT it was a legacy case of if product exists lol
[Motorola Edge 20 Pro] fesdonomist:
Nice work on fixing it. Magisk is completely and utterly broken with this new build (phone freezes then restarts after a few minutes, camera is garbled, and mobile data doesn't work), but you guys don't support that anyway so I'll look into other options, what matters to me more is that the basic functionality works, which you guys have got down now! Nice job.
[Motorola Edge 20 Pro] fesdonomist:
I'm still experiencing the Bluetooth audio issue I mentioned earlier. My xm4s connect, but I get nothing out from them, and when I switch the output to phone and back to the headphones it says it's playing through the headphones but it's coming out of the speakers. For some reason, the Google assistant chime plays through the headphones but nothing else plays.