Oops. Oneplus 7 Pro. Flashed through latest Magisk. After I uninstall it in Magisk and reboot I get service back with 1 sim.
This Module not working on Androis 10 Stable
After install no Baseband and no IMEI
After install no Baseband and no IMEI
Yeah from Pie to Q official release. Uninstalled and tried again. I actually had this same issue on the 2 betas they released also.
It actually works fine (for me at least) on the OP7 Q stable. I had the same issue with the no service thing, solution was to disable the module, reboot, uninstall the module, reboot, reinstall the module, reboot. Should be fine, other than sim and network settings crashing when you try to open it. Can confirm on the global rom for GM1900 that the call recording settings work, and the recording itself works fine.
Common issue to not uninstall/disable magisk modules before rom update...
No guides I've ever seen mention uninstalling modules, and for your information I did disable all of my modules and reenabled them one at a time after the update, it was still broken.
You should read the first post carefully, especially the Read-me section :good:
Yeah great buddy I was talking about upgrade guides. Guess what? Most people don't go to xda look for read me's for a module that isn't even written by the dev of said module.
OK.... So besides the weird argument, if the OP or Mod have any ideas please share. I know JOnePlus Tools app has an option in it that does work without any issues. Either way this module was working and I would like to see it working again.
As you wrote here https://forum.xda-developers.com/on...ble-call-recording-boot-t3634292/post80304165 I had no issues on both OB1 and OB2 when I disable all magisk modules and install them after the update(from 9.5.8 to OB1 or OB1 to OB2).
There's also a try with the other variants like Tasker, but I can't imagine why it should not work for you.
Have you tried to dirty flash the stable android 10 again(before uninstall all magisk modules) then install call rec mod again?
In the case of this module specifically, an uninstall and resinstall would be required after updating OOS. A simple disable/enable will not work (unless OnePlus make no changes in the apk being modified by the module in the updated OOS being flashed) and will most probably lead to issues.
I will be adding this imporant piece of information alongwith the changelog and other stuff that is displayed when installing this module from Magisk Repo. Hopefully that should avoid people running into an issue because of not reading the OP.
The module is still working for almost everyone. If it doesn't, I suggest you try the other methods listed in the OP. Good luck!
Including the sim & network settings crash? Still happening for me, even with a fresh install of Q and the module on OP7 non-pro.The module is still working for almost everyone. If it doesn't, I suggest you try the other methods listed in the OP. Good luck!
The ADB non-root method (stock device) works fine in oneplus7 OOS 10.0.GM57AA
I did not believe it before I try, but it works properly
many thanks!
I did not believe it before I try, but it works properly
many thanks!
Yep, same problem here.
It will break the modem and phone capabilities if installed on OxygenOs 10 with Oneplus 7 pro, EU version.
Edit. And I tried again and suddenly it works, wtf.
Last edited:
Works fine for me on official Q/oneplus7 (non-pro). For callrecording, all it does is flip an adb setting (which you can also do manually if you wanna);
adb shell settings put global op_voice_recording_supported_by_mcc 1
adb shell settings put global op_voice_recording_supported_by_mcc 1
Thanks for this! In case of an update if we uninstall the module will the directory it saves the recordings too also be erased? Speaking of which where is the location?
Nope, location of phone recordings will not be removed: /storage/emulated/0/Record/PhoneRecord
There's definitely something wonky going on with the module, not sure if OP can look into it at all but on Q the module sometimes breaks the phone seeing your sim card, sim & network settings crash immediately (and cause the phone to lose service temporarily), and occasionally the phone will just lose connection to LTE (toggling airplane mode or tapping the sim & network settings causing a crash in telephony fixes it for a while). If you use the tasker profile everything works perfectly, settings don't crash, no sim issues, no data loss issues. Seems like there must be more to the module than flipping the adb string, why else would it have such drastic differences compared to the tasker method?