yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series Questions & Answers] jihoo125:
How to DOWNGRADE Android to Nougat because apps AREN'T working properly I need Android 7.1.1 on my device, BACK! But I don't want to SPEND money. I can connect to a PC! HOW do I do it?
[Motorola Edge 20 Pro] npjohnson:
moto edge 20 pro

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 20 thread for the moto edge 20 pro .

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

pstar - Official builds​

pstar - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.​

Find any? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​

Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sm8250
[Motorola Edge 20 Pro] npjohnson:
Official builds rolls on Tuesday.
[Motorola Edge 20 Pro] MrZZZ123:
Wow, nice job!!!

thanks you , bro !:D
[Motorola Edge 20 Pro] summer9:
Hey,bro.

The build task failed，Please check the task，thx.

android #55602 · LineageOS

pstar 20230613

buildkite.com
[Motorola Edge 20 Pro] npjohnson:
aware, trying to get it requeded but may need to wait for next week.
[Motorola Edge 20 Pro] summer9:
Thank you and look forward to it.
[Motorola Edge 20 Pro] tohigh:
Need upgrade to stock rom 13? I'm using lineage os official 19.
[Motorola Edge 20 Pro] npjohnson:
Nope.
[Motorola Edge 20 Pro] jdavidoa91:
No Lineage 20 version is available for download
[Motorola Edge 20 Pro] npjohnson:
literally read the last few posts it builds tomorrow
[Motorola Edge 20 Pro] jdavidoa91:
My bad, sorry for not reading the whole post.

Thanks!
[Motorola Edge 20 Pro] Eric_Close:
Thank you very much for your hard work.

I installed LineageOS 20 from the Stock ROM Android 13. Yep, I did a clean flash. However, I found many problems here:

[Bug Report]

1. Camera keeps stopping. I can't use the camera at all, either the built-in 'Aperture' camera or any other third-party app (e.g. Google Camera, Simple Camera, Telegram, etc). And the torch is not working, the Torch tiles keeps showing 'Camera in use'.

2. The tiles in the Quick Settings panel (Notification panel) are frequently unresponsive or slow to respond, whether you click or long press on them. Here is the attached video:

View attachment 5936687

3. When using the Bitwarden (password manager), there is a significant delay both when switching to the Bitwarden app and when clicking to Auto-fill the password. Here is the attached video:

View attachment 5936685

4. File transfer is not available when USB debugging is on.

Finally, I hope this will help you to fix these problems.

Update: All issues are resolved in lineage-20.0-20230704 official build, except the 4th issue: MTP not working when USB debugging is on.
[Motorola Edge 20 Pro] npjohnson:
Your issues are that you started from 13, I was a bit worried some issues would pop up but some people were telling me things were fine, I will go add 12 as a requirement to the wiki, that is likely going to be your camera issue, potentially as well as your USB issue.
[Motorola Edge 20 Pro] Eric_Close:
I tried to downgrade completely to Android 12 Stock ROM, and then flash to LineageOS 20 agian. But no luck, the above problem remains. 😂
[Motorola Edge 20 Pro] npjohnson:
So weird, I just took 10 photos and 2 video on the camera via the Aperture app - do you use Magisk or anything funny?

Flashlight toggle works for me.

And MTP works fine - I just tried - what host OS do you use?
[Motorola Edge 20 Pro] Eric_Close:
Yes, it's very strange. Not using Magisk yet, and I only have MindTheGapps installed. The host OS is Windows 11 Pro v22621.1848.

Then I tried not installing MindTheGapps and the problem was the same too.
[Motorola Edge 20 Pro] npjohnson:
what variant of pstar do you have? EU? US?
[Motorola Edge 20 Pro] Eric_Close:
Same here. This is the log I provided, and I have identified some instances of repetitive content.

01-16 11:18:35.458 0 0 I [drm:dsi_panel_send_param_cmd] [msm-dsi-info]: (0) is setting new value 0
01-16 11:18:35.458 0 0 I [drm:dsi_panel_set_backlight] [msm-dsi-info]: backlight type:2 lvl:0
01-16 11:18:35.458 0 0 E : [drm:dsi_ctrl_set_cmd_engine_state] *ERROR* [msm-dsi-error]: dsi-ctrl-0: State error: op=1: 1, 0
01-16 11:18:35.458 0 0 E : [drm:dsi_ctrl_set_cmd_engine_state] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Controller state check failed, rc=-22
01-16 11:18:35.458 0 0 E : [drm:dsi_display_cmd_engine_enable] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable cmd engine, rc=-22
01-16 11:18:35.458 0 0 E : [drm:dsi_host_transfer] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable cmd engine, rc=-22
01-16 11:18:35.458 0 0 W [drm] [msm-dsi-warn]: DSI_0: Turning OFF PHY while PLL is on

..................

01-16 11:18:35.462 0 0 E : [drm:dsi_panel_set_backlight] *ERROR* [msm-dsi-error]: failed to update dcs backlight:0

01-16 11:20:58.526 0 0 I [drm:dsi_panel_post_unprepare] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
01-16 11:20:58.541 0 0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
01-16 11:20:58.541 0 0 E dsi_pll_enable: PLL(0) lock failed
01-16 11:20:58.541 0 0 E vco_7nm_prepare: pll(0) enable failed, rc=-110
01-16 11:20:58.541 0 0 E : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
01-16 11:20:58.541 0 0 E : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
01-16 11:20:58.541 0 0 E : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
01-16 11:20:58.541 0 0 E : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
01-16 11:20:58.541 0 0 E : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
01-16 11:20:58.541 0 0 E : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
01-16 11:20:58.541 0 0 E : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
01-16 11:20:58.541 0 0 E : [drm:dsi_host_transfer] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable all DSI clocks, rc=-110
01-16 11:20:58.541 0 0 E : [drm:dsi_panel_send_param_cmd] *ERROR* [msm-dsi-error]: failed to set cmds, rc=-110
01-16 11:20:58.541 0 0 E : [drm:dsi_panel_set_param] *ERROR* [msm-dsi-error]: dsi_panel_set_hbm: failed to send param cmds. ret=-110
......
01-16 11:21:05.204 0 0 E : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
[Motorola Edge 20 Pro] npjohnson:
We figured this out by the way, I think at least, please try the build that went up tonight.
[Motorola Edge 20 Pro] jrzhao:
Do you mean

lineage-20.0-20240116-nightly-pstar-signed.zip?
[Motorola Edge 20 Pro] npjohnson:
yes
[Motorola Edge 20 Pro] Eric_Close:
Ok, I have upgraded the device to the 20240116 build just now. I will observe in the coming days to make sure whether the issue of screen freezing followed by a black screen still persists or not.

Additionally, I would like to mention that I have identified the issue of NFC not being able to enable , which was previously reported by others. This problem persists in the 20240116 build, and I have attached the relevant logs.
[Motorola Edge 20 Pro] npjohnson:
pls file the ticket on the official tracker that way it ends up in my todo.

Wiki has details.

Thx.
[Motorola Edge 20 Pro] mikib1:
Same here I also have freeze and reboots 3 - 4 daily now, that is less than before last update, but still. I hope it can be fixed... Anyway thank you for building LoS for our devices.
[Motorola Edge 20 Pro] mikib1:
Yes and most stable ROM was since 20240101 till this update 20240108 😭😭
[Motorola Edge 20 Pro] npjohnson:
0116 fixes it all
[Motorola Edge 20 Pro] Maxi693:
I accidentally just installed the latest version of magisk and it works perfectly

I didn't have the reboot or network problem.
[Motorola Edge 20 Pro] Maxi693:
What I did realize is that it won't let me activate NFC
[Motorola Edge 20 Pro] npjohnson:
Working on it.
[Motorola Edge 20 Pro] Maxi693:
Cool

Good luck
[Motorola Edge 20 Pro] npjohnson:
If that's the case, it now works on 20 too.

The issue was Magisk patching made our ramdisk too large.
[Motorola Edge 20 Pro] Maxi693:
oh lol

I don't know about this but how crazy that something as simple as that can cause so many problems. 😅😅
[Motorola Edge 20 Pro] raulillo88:
New version, new problems.

This morning I've wake up the screen, but couldn't unlock. It didn't detect fingerprint or swipe up to introduce manually my pin. I've tried to turn on wifi or bluetooth because the upper panel swipes down, but didn't turn on neither.

Finally I've had to reboot manually.

Please, recompile 01/01 version and upload it here for people who wants an stable version. I use the phone for work, and yesterday I had a reboot during a conference call.

Regards
[Motorola Edge 20 Pro] npjohnson:
We fixed that issue, the next build will have all that fixed.
[Motorola Edge 20 Pro] Eric_Close:
I tried a voice call on Telegram and and encountered the same issue. I captured the logs and you can see the details in this issue.

I hope the log will help. Feel free to reach out if further testing is required.
[Motorola Edge 20 Pro] zpunout:
Update about my issue of VoLTE not working with my carrier. I now have VoLTE working using root. I updated my previous post #166 with the steps I took.
[Motorola Edge 20 Pro] mikib1:
About "BTW" , the same in my edge 20 pro, update from 2024.01.16 did not fix problems of this ROM
[Motorola Edge 20 Pro] Maxi693:
Hello sir

Is there a way to put apps that are not old in the option to force apps to full screen?

For example, the geometry dash app that shows a black stripe on one side
[Motorola Edge 20 Pro] npjohnson:
It's in settings as "Full-Screren apps" or something like that. You have to enable it per app.
[Motorola Edge 20 Pro] Maxi693:
There is an option in the settings/display tab but no apps appear there
[Motorola Edge 20 Pro] npjohnson:
Then that app can't be resolved. It only allows doing to for apps which use older ask targets as that's how we handle it.
[Motorola Edge 20 Pro] Maxi693:
Ohh I understand
[Motorola Edge 20 Pro] mikib1:
You are right... all work as it should work. Sorry for my complaint of ROM. Problem was caused by root that I need...
[Motorola Edge 20 Pro] raulillo88:
No. Neither root is the problem, because I'm not rooted and have the same problems, neither is solved all problems in 16/01. I have same problems like previous versions. I can't wait for next update to see if at least is all fixed. Finger cross
[Motorola Edge 20 Pro] mikib1:
You are also right... my first thinking was that root is the problem, because after I removed root and Magisk problem back but after much longer period of work without reboot and "bsod" . Any way... I use this OS since my First Motorola Defi and Cyanogenmod... so like you "....I can't wait for next update to see if at least is all fixed. Finger cross..." And I hope this also be fixed in LoS 21 for our phones. Unfortunatli I'm not good enofugh in IT to suport this OS to build it up
[Motorola Edge 20 Pro] Eric_Close:
Confirmed that the black screen issue still exists in version 20240116. The issue does not appear to be related to root methods.

I will wait for the next version to arrive and in the meantime keep the log for reference.
[Motorola Edge 20 Pro] Eric_Close:
Unfortunate news: According to the feedback from several friends who updated to 20240122, the black screen issue persists.

Currently, no one has captured the logs. 😂
[Motorola Edge 20 Pro] raulillo88:
NFC is not working either. So I assume other issues should be present too.

Please, recompile last working version to have a bugless free rom until all problems are gone.

Regards
[Motorola Edge 20 Pro] npjohnson:
Okay, we know what's up.

HBM is messing with things. Next build should have it remediated. I'll push an unofficial people can try in the mean time to verify.
[Motorola Edge 20 Pro] npjohnson:
That's not how this works.
[Motorola Edge 20 Pro] npjohnson:
Good news, thinks we have that solved, please try today's unofficial build.

As for NFC we know what is wrong, fixing it for next week, but the unofficial I'm about to post in an hour should have both issues fixed.
[Motorola Edge 20 Pro] Eric_Close:
Where can I download it, I see the latest version on your site is lineage-21.0-20240114-UNOFFICIAL-pstar.zip.
[Motorola Edge 20 Pro] npjohnson:
It is building right now. Still.

Sorry, been a long day of builds lol.
[Motorola Edge 20 Pro] Eric_Close:
Understood, I will patiently await until it releases.
[Motorola Edge 20 Pro] npjohnson:
So, you can wait for next week's official, or try this https://download.ods.ninja/Android/lineage/pstar/lineage-21.0-20240122-UNOFFICIAL-pstar.zip 21 unofficial.

It should resolve all these issues and the fixes have been backported to 20
[Motorola Edge 20 Pro] Eric_Close:
Which one should I try, 20240122 or 20240123?

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

download.ods.ninja

Update: I will test the build version 20240123.
[Motorola Edge 20 Pro] npjohnson:
0123 please.

Note you won't be able to go back to 20 without wiping
[Motorola Edge 20 Pro] Eric_Close:
I have encountered an issue on the LineageOS unofficial build where during the initial setup wizard, it is impossible to set a PIN or password as the keyboard fails to appear. (I am stupid, I forgot to perform a factory reset)

Update:

* NFC is working in Los 21 now.

* Nevertheless, it necessitates further time to verify the existence of the black screen issue.
[Motorola Edge 20 Pro] npjohnson:
Gboard issue sounds like it wasn't from fresh format?

Sounds like conflicting app data.

But yeah, I'm fairly confident that the issue is remediated.
[Motorola Edge 20 Pro] Eric_Close:
Gboard is working following the reset.

Initially, I performed a factory reset in the LineageOS 20 from system settings (to avoid triggering FRP), then it rebooted.

Subsequently, I flashed Los21 and I just forgot to do a factory reset. Lol
[Motorola Edge 20 Pro] npjohnson:
mmm yeah migrations are still a work in progress, hence the "unofficial" part.

But yeah good to hear - if you hit the black screen issue let me know but I doubt you will - for the rest - those on officials, next weeks build (or if we can bribe someone into firing one off earlier) will have all this fixed.
[Motorola Edge 20 Pro] Eric_Close:
😂 The black screen issue persists in LineageOS 21 unofficial 21.0-20240123-UNOFFICIAL-pstar.

Here is the log.
[Motorola Edge 20 Pro] npjohnson:
ugh, digging into it. Thx for testing quickly.
[Motorola Edge 20 Pro] Eric_Close:
Though the blackscreen issue still exists, and I can't wake up the screen through power button.

I found an interesting situation:

The screen can be awakened by scrcpy, and although it encounters an error and exits after a while. Then the screen won't stay unresponsive and go black.

D:\Program Files\scrcpy-win64-v2.3.1\scrcpy-server: 1 file pushed, 0 skipped. 27.4 MB/s (66007 bytes in 0.002s)
[server] INFO: Device: [motorola] motorola motorola edge 20 pro (Android 14)
INFO: Renderer: direct3d
INFO: Texture: 1080x2400
ERROR: Could not open audio device: WASAPI can't find requested audio endpoint: 鎵句笉鍒板厓绱犮€
ERROR: Demuxer error
[Motorola Edge 20 Pro] mikib1:
Yes I confirm, black screen a random often reboots in LoS21-UNNOFFICIAL, unfortunatli I have no logfile.
[Motorola Edge 20 Pro] Eric_Close:
I reverted to the official lineage version, specifically 20.0-20240123, without using any custom root.

Unfortunately, it has encountered a freeze once more. I patiently waited for several minutes, there was no automatic reboot.

Efforts to capture the log through logcat proved unfruitful as it failed to generate any output. An I find myself unable to access the shell.

* Issue Tracker
[Motorola Edge 20 Pro] raulillo88:
Sorry for my post, but I was upset to see another update without fixing previous problems. To me since yesterday's version evertything is working fine. I'll test and report.

About wifi auto-connect that is not working, could be fixed?

Thanks for your effort
[Motorola Edge 20 Pro] raulillo88:
I've had another BSOD. I've tried to export the logcat, but apparently when it is in that state, computer does not detect phone
[Motorola Edge 20 Pro] mikib1:
Till now I could not grab the logfile because of this. I wrote also post in LoS 21 thread, in new unofficial build are the same issues.
[Motorola Edge 20 Pro] raulillo88:
Yesterday, I was using whatsapp I press in a conversation and phone freeze. This was my first time that freezes with screen on
[Motorola Edge 20 Pro] mikib1:
I get back to LoS 20, also clean install, all wipes, complete fresh, with no MAGISK and today also freezes when I press one of programs that working normally. Still problems occur.

Additionally, LoS 21 Mindthegapps 14 can't be flashed because of not enough space for them in partition
[Motorola Edge 20 Pro] npjohnson:
Not sure why you're flashing Google apps on top of 21, the unofficial 21 builds come with gapps.
[Motorola Edge 20 Pro] mikib1:
Yeah... you right... i forgot that... during crazy digging what can be wrong and crash the LoS build and phone... automatically I loaded the Gapps after few reflashes I got freakout... and load them🤦‍♂️🤦‍♂️

Sorry.
[Motorola Edge 20 Pro] zpunout:
Try lowering the screen maximum refresh rate to 90Hz in the display settings. Seems to have worked for me after a day of testing.
[Motorola Edge 20 Pro] raulillo88:
No, that is not a solution either.

I really don't understand a stable rom with same bug for one month. Yesterday I missed an important call, because phone does not ring.

I think is not screen related, because I've had several freezings with screen on too. Maybe related with voltage?

At last, I'm going to try again. Please recompile 01/01 version to manually flash to have a stable version. We cannot have an stable rom that seems more like an alpha rom
[Motorola Edge 20 Pro] Eric_Close:
However, the freezing issue persists even though I have configured both the minimum and peak refresh rates to be 90 Hz from the outset.
[Motorola Edge 20 Pro] zpunout:
Funny, mine stopped freezing 3 days ago. My maximum refresh is set to 90Hz, minimum at 48Hz. I'm using the latest RETAPAC Android 13 firmware from here: https://mirrors.lolinet.com/firmware/lenomola/pstar/official/

I also deleted all my fingerprints and left just one fingerprint. Not sure if that is relevant though.

[Edit: It seems that it may indeed be the fingerprint unlock being one cause for the freezing screen. I registered my fingerprints again and am occasionally having what I call a "partial unlock". The home screen appears but opening apps is not responsive. Swiping across on the home page works for a few seconds before the screen freezes completely. If I can reproduce this when at home, I'll try to capture a logcat ]
[Motorola Edge 20 Pro] raulillo88:
Nothing fixed in last rom either.

Keep freezing like before.

NFC is working, but connot pay anymore. When try to pay in a POS, gives an error something like Card not recognized.

I will try to get a logcat if phone does not freeze before.

BTW in OP you should warn about these bugs. Because this rom is not bugless and people could try to use this rom as stable version, which is not anymore.

Regards
[Motorola Edge 20 Pro] npjohnson:
Can someone please give me a reliable case to reproduce this BSOD? I can't hit it.

I just used pstar all day.
[Motorola Edge 20 Pro] npjohnson:
Blindly trying to solve it here, try the February 5 build located at https://download.ods.ninja/Android/lineage/pstar/ (note this will require wiping data to try, then wiping to come back to officials)
[Motorola Edge 20 Pro] raulillo88:
This is my NFC error for today.

02-05 22:54:18.351 1751 1799 W BroadcastQueue: Background execution not allowed: receiving Intent { act=es.redsys.hce_library.ACTION_PAY_SERVICE_NULL flg=0x10 (has extras) } to es.evobanco.bancamovil/es.redsys.movilidad.hcems.wcm.components.ReceiverNFCC

02-05 22:54:18.351 1751 1799 W BroadcastQueue: Permission Denial: broadcasting Intent { act=es.redsys.hce_library.ACTION_PAY_SERVICE_NULL flg=0x10 (has extras) } from es.evobanco.bancamovil (pid=4483, uid=10206) to es.openbank.mobile/es.redsys.movilidad.hcems.wcm.components.ReceiverNFCC is not exported from uid 10222

Regards
[Motorola Edge 20 Pro] npjohnson:
that doesn't look related - are you sure you're not just failing safety net/play integrity?

That build is trying to solve the BSOD, not the NFC issue.

I think BSOD is solved.
[Motorola Edge 20 Pro] raulillo88:
Before 08/01 I could pay without any problem with my phone through my bank application (not Google wallet)

About BSOD like we have said before, you can only take log after reboot. During freezing, phone does not connect to the PC.

Regards
[Motorola Edge 20 Pro] npjohnson:
Did you read what I said?

I'm not asking for logs - I am saying I think I've fixed the BSOD - please try the build.

And yeah, around August/October is when my safety net patch was patched by google. so makes sense that stopped working - unless you use magisk and spoofing stuff it won't work anymore.
[Motorola Edge 20 Pro] raulillo88:
Yes, I've read, but like I said previously, I can't format phone every time because I have a lot of stuff that I don't want to lose because is my everyday/professional phone.

If I could wipe it I would be already in 01/01 build.

Are there any chance to upload fix in an official build?

Regards
[Motorola Edge 20 Pro] npjohnson:
All - I strongly believe that we've solved the BSOD issue - please try the 0205 20.0 build and let me know
[Motorola Edge 20 Pro] npjohnson:
^ done
[Motorola Edge 20 Pro] Eric_Close:
I will attempt to flash the unofficial build version 0205, waiting me a few days to test whether the freeze issue persists. Regardless of whether I encounter the freeze issue again, I will let you know.

Before flashing Lineage each time, I always reflash the official firmware (version: T1RAS33.55-15-16-5) and perform a data wipe before installing LineageOS. I am uncertain about the reliable reproduction steps for this issue, but in previous build versions, I have made the following modifications:

Disabled Dark theme

Disabled Ambient display

Disabled Notification light

Set Peak refresh rate: 90 Hz

Set Minimum refresh rate: 90 Hz

All other settings remain at default, without any additional modifications (such as Magisk). Subsequently, I leave the device idle for several hours, sometimes charging, sometimes not. When I attempt to wake the screen, it completely freezes or sometimes it partitial freezes.
[Motorola Edge 20 Pro] npjohnson:
You are welcome to use the unofficial if you like but the official build that rolled today also contains the fixes. If you'd prefer that route.

Thank you.
[Motorola Edge 20 Pro] zpunout:
My post might be irrelevant now since the new build release but here's my feedback for 20240129 build:

I'm not 100% sure yet, but on build 20240129 I've been testing my Moto Edge 20 Pro with and without fingerprint unlock registered. It seems to me that using only pattern unlock I have stability whereas if I have fingerprints registered, I have semi freezing and sometimes bsod, even if I press the power button with my fingernail to avoid fingerprint recognition and unlock with the pattern. I'm still testing this build to narrow it down as I haven't ruled out if hotspot tethering is a contributing factor. Once I figure out how to reproduce the issue reliably, I'll report back and also start testing the next build.