Yes I experienced the same thing. It has to do with the Oneplus Dolby sound that was added. I tried messing with the settings for it and i just couldn't reduce the output gain so I disabled it.
That's what I figured although I turned Dolby off and it's still loud so I guess I'll stick with vibrate for the time being.
Would someone please post the. Patched 221007 boot image. I cannot seem to get magisk to patch anymore. Thank you in advance.
Thank you! I updated today and lost root. Patching the latest boot image with Magisk and flashing it to my device sent me to crashdump mode. Flashing this sorted it and gave me root access back in MagiskIt worked fine for me. Here's a copy that I uploaded for you.
Same thing to me. I had 5 crash dump error now since update.
Should happen if you have Gapps installed (setup wizard for nikgapps). If you do have Gapps installed, try a factory reset. You'll get the crdroid setup first, the the Google setup.OK you guys I've been around for a very long time but I'm no expert. Not by any means! I accidentally bricked my phone and was able to recover but had to do a wipe when reinstalling CRDroid. It went through the CRDroid setup but not the Google setup. How does one get the Google install instead? I'm also having a storage issue but that is for next time. I Iike CRDroid but like the setup that reinstalls all my apps and settings.
You can use the LineageOS instructions as a guide. Just make sure you use latest OOS 11 and the CrDroid recovery (instead of OOS 12 and the Lineage recovery that are mentioned in the guide).
Bro no way, crdroid 8.10 uses the 184.108.40.206 oos firmware. Not oos12, it doesn't matter if crdroid 8.10 is android 12 it still uses android 11 oos firmware. And oos 11 != android 12, its android 11 like in the name.Alright. I was doubtful that firmware was the issue. When I was addressing our device maintainer I was doing so respectfully.
It's been a long 3 days, but I backed up my data, did a MSMTOOL flash of both slots with an Android 12 OOS rom. I also tried our fancy firmware updater from gwulf to Android 12/crDroid 8, both slots.
I am currently on crDroid 8.10 (and in both slots).
I had the Qualcomm crash dump, again. It happens when trying to play videos.
I'd like to know how I can help track this down. There must have been a merge request in late August or early September that introduced this problem.
So the original question is: does this problem rely on our device maintainer or the main project devs?
*** Disclaimer I am not responsible for any damage you made to your device You have been warned
fastboot flash boot boot.img
adb sideload crDroid.zip
adb sideload crDroid.zip