Nobody with this problem? Or nobody any idea? This problem is making me crazy.I have the Oneplus 9 Pro LE 2120 (CN). I have a massive problem with the connection quality when making a call with Bluetooth (in the car). The quality is so bad that a normal phone call is not possible. Direct phone calls without Bluetooth are normal. I didn't have the problem with the Oneplus 7 Pro with Android 11 (crDroid 7.13). I also reinstalled the original software (C63 with Android 12) as a test, I had no problems. I couldn't find anything about this problem here in the forum either (I hope I haven't overlooked anything). Maybe someone has a tip for me?
The problem is also present in LineageOS 19.1, on which crDroid 8.x is based. It is very annoying, and as you said, it only happens on phone calls, not media playback. Lots of people noticing the problem, but no indications that it's being worked on.
OnePlus9Pro_EEA-user 12 RKQ1.211119.001 R.GDPR.202208171117 release-keys
It's in the order that it appears in. After crDroid and gapps have been installed you may choose to root your device. Sideloading the apk seems to work but that method is not officially supported anymore so I prefer patching the boot.img file and then booting into it from fastboot then using direct install from the magisk app to root.First time rooting / installing custom rom on Oneplus 9 Pro Global LE2125 (coming from oneplus 6t & twrp).
I'm a little confused on this statement in the guide to achieve root:
Can anyone help dumb this down for me step by step?
Where does this step fit in the 'First time installation (clean flash)' ?
I was able to locate/download the latest boot.img (boot-20220923.img) via download page. I've also downloaded the latest magisk (v25.2) apk.
Is magisk.apk sideloaded via adb? Or do I have to manually create a patched boot.img?
Thanks for the input!!It's in the order that it appears in. After crDroid and gapps have been installed you may choose to root your device. Sideloading the apk seems to work but that method is not officially supported anymore so I prefer patching the boot.img file and then booting into it from fastboot then using direct install from the magisk app to root.
So basically, after crDroid is installed and you are able to boot normally, patch the boot.img with magisk app
reboot to bootloader
fastboot boot magisk-patched-boot.img
Open magisk app and direct install.
That's my preferred method anyway.
Great to hear that I'm not alone.
It does make me wonder if other Android 12 ROMs for the 9 Pro have this problem. I'd try others myself but my 9 Pro is my daily driver and I don't want to mess up what's working (and LOS/crDroid recovery wipes out everything when you select the factory reset option, and I don't feel like reloading files in storage on my phone every single time; makes me long for a working TWRP that can wipe data without wiping all storage). If other ROMs have this problem, I'd say it's a driver/binaries issue; if they don't, it's almost certainly an LOS issue.Great to hear that I'm not alone.
The opposite is very bad to hear and audio is like there is a buffer or encoding error. Like a broken MP3.
I can confirm:
- The issue exists also on pure LineageOS 19.1
- It does not depend on any firmware. Tried c62 and c63
- The new Android 13 ROMs do also have the issue
- Changing bluetooth settings in developer options does not help
- A OnePlus 7 Pro with latest crDroid / Android 12 works without any issues
For the future, you can always recover from a bricked state even if you can't boot into bootloader or anything else at all with MSM tool. As long as you can get it to detect EDL even if for only an instant.
guys, i guess i bricked my phone. i wanted to flash, but it seems that i was not on Android 12 firmware, but Android 12.1.
Now my phone is stuck on boot Screen (Cannot, recovery, or bootloader anymore)
Can someone help? Is it rescueable?
EDIT: i can boot fastboot mode....i guess i have to reply everything with C.63 Firmware
EDIT2: Everything went well. Gonna test the rom now
*** Disclaimer I am not responsible for any damage you made to your device You have been warned
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot boot.img
adb sideload crDroid.zip
adb sideload crDroid.zip