Database Users

[Q] Phone restarts when answering/rejecting/making phone calls

Hey, so when ever I make a call (I can dial but when I hit call) my phone will lock up, then the screen goes black, shuts off and turns back on. It happens when I answer or reject incoming calls as well. This only started happening when I updated my S5 to lolipop, I unrooted, and when back to the S5 stock kitkat ROM, full factory reset before going to lolipop, phone calls worked fine rooted and unrooted in KitKat, so it makes me think it's a lolipop issue. Since running into the problem I've tried, going back to kitkat and upgrading again, factory resetting from within lolipop, wiped caches, and such, and I just can't get it to work. Any ideas would be greatly appreciated. It can't be hardware related since calls work fine on kitkat right?

OEM_NV_Backup BT_MAC_MISSING notification after every reboot

We been having this issue with our Malaysian OPT with OOS 2.1.0 and later OOS 2.1.1.
Every time it reboots, the error message OEM_NV_Backup BT_MAC_MISSING will pops up. It can be swipe off. No other error on the phone, everything else works fine. Not a big issue but just annoying.
This happens on both stock recovery, stock kernel, locked bootloader and unlock bootloader with AK Kernel, TWRP recovery.
Btw, the Bluetooth works in case you're wondering if BT_MAC_MISSING notification screws up the BT. And we have try factory resets and clean install.
Anyone has any ideas on this. Thanks.

Unable to receive calls and SMS after root

After rooting, I cannot receive phone calls or SMS messages. Even after making a call and changing "Searching for Service" to "Verizon Wireless", I still can't.
Does anyone know a fix for this? I really want to keep root, but there's no point of having a phone if you cannot receive phone calls.

I would suggest download the STOCK firmware, install it go thru the setup process. Then flash what ever firmware you are wanting to root a d you should be fine. The important part let it boot up on stock and check everything out before you root.

Same thing happened to me today after the pe1 root. I tried everything to get my text to receive. Only would recieve texts the First two minutes. Ended reverting to stock pe1 and got all my texts from this morning to now

ironbesterer said:
After rooting, I cannot receive phone calls or SMS messages. Even after making a call and changing "Searching for Service" to "Verizon Wireless", I still can't.
Does anyone know a fix for this? I really want to keep root, but there's no point of having a phone if you cannot receive phone calls.
Click to expand...
Click to collapse
I believe I have found the issue. I have returned to stock after the same thing happened to me. Re-rooted and after I set everything back up it happened again. It says "searching for service" in the status bar and lockscreen. Phone status in settings shows out of service.
-- I ended up reflashing the v15 fix for a second time, first was right after I rooted and wiped the cache partition. I am now able to send/recieve texts and phone calls now. Hope this helps

Reflash v15 fix
Do what Kole said – reflash the v15 zip. I had the same problem. I reflashed stock and it worked for about a day before I had the same problem again. Anyways, in order to find the cause, I used my wife’s phone to call mine every time I made a substantial change, for example, after rooting, after flashing one of the fixes, after flashing Xposed… I even did it every time I activated a single module. Long story short, it came back but didn’t seem to be directly caused by anything. After going to safe mode, uninstalling xposed, even calling Verizon to reset my connection with them, nothing worked… until I reflashed the v15 zip. I’ve been going strong for about a month now without any problems.

Same issue but still not working after flash
Zram5678 said:
Do what Kole said – reflash the v15 zip. I had the same problem. I reflashed stock and it worked for about a day before I had the same problem again. Anyways, in order to find the cause, I used my wife’s phone to call mine every time I made a substantial change, for example, after rooting, after flashing one of the fixes, after flashing Xposed… I even did it every time I activated a single module. Long story short, it came back but didn’t seem to be directly caused by anything. After going to safe mode, uninstalling xposed, even calling Verizon to reset my connection with them, nothing worked… until I reflashed the v15 zip. I’ve been going strong for about a month now without any problems.
Click to expand...
Click to collapse
So I'm in a similar boat, but my sms/calling issues have returned after about a day of flashing the v15 zip. So far I've probably reflashed it like 5 times in the last 5 days. It works without fail so far, but this is not a permanent solution. Could it be some setting configuration? Any feedback is appreciated.

elan5 said:
So I'm in a similar boat, but my sms/calling issues have returned after about a day of flashing the v15 zip. So far I've probably reflashed it like 5 times in the last 5 days. It works without fail so far, but this is not a permanent solution. Could it be some setting configuration? Any feedback is appreciated.
Click to expand...
Click to collapse
What build are you on?

TWRP Randomly started freezing and crashing when attempting to wipe anything...

Hello,
I have an odd problem I need to iron out. . . Recently I installed the NeculaROM mostly without a hitch, however I was having issues not being able to make outgoing calls, so I wanted to switch back to my old Rom. Normally this wouldn't be an issue however when attempting to wipe anything on the phone, it starts vibrating and shuts off in TWRP. I can flash things fine still, back things up, yada yada. I tried reflashing TWRP, and that didn't help either.
So now I am stuck on this rom, and I can't do anything in TWRP. Is there any way to fix this? I can't seem to find much information on this particular issue. Any help would be great.
Thanks!

I believe this is caused by f2fs changes with rebasing this device to nougat.
Have you tried using the TWRP linked to the OP of the NucleaROM thread? You might have to format internal storage to get things working right again.
If that doesn't work out for you I'd recommend searching around more recent discussions in the TWRP thread and LineageOS thread. These issues with wiping and differences between unofficial TWRP, official TWRP, and what works with what ROM/firmware combinations have been covered in both.
Sorry I'm not more help on exactly what to do. I've just stuck with marshmallow firmware and custom roms based on it. I'm waiting for the dust to settle on this nougat rebase business.

Had same issue. I ended up just reflashing all the firmware images. Fixed my problem (for the most part.)

Finally on A11, and it bootloops 2x now in 1 week. Anyone else?

So I've finally got to upgrade from A10 to A11. I was unable to follow the guides for doing local upgrades, because of my previously mentioned "No changelog" and "System Update Installation Failed" message the moment you selected the upgrade package. I tried multiple downloads and verified hashes, this wasn't a corrupted download. So I ended up having to Wipe data to get to a stock A10 and then upgrade using local upgrade. That was Sunday. Since then, I've rooted, restored my apps, lived happily on A11....for about 1-2days before I'd wake up a bootloop. The phone would just be sitting on the spinning Oneplus logo without me knowing why we got here. Even stranger, I had NoLimits installed, so I should be seeing that instead of Oneplus.
Attempting to fastboot boot any of my boot images still keeps me in a boot loop, not much to do other than to wipe and try again....So wipe, on A11 stock, root, restore apps and go on my way....Worked great yesterday. again all apps were restored, things were working, no issues. And then I woke up this morning to find issues with Facebook app (images not loading). Okay, whatever, something may be corrupt, just wait for an update from them. Multiple apps in Playstore need an update, great...do those. But then Oneplus Gallery refuses to update...hmmm. Catlog/Logcat refuse to open with insta-crashes. Facebook nolonger has the corrupt image issue, it just insta-crashes.......uh oh......maybe a reboot?.....rebooted and then stuck on NoLimits bootscreen for about 2 minutes....after 2 minutes it reboots and I'm back to being stuck on Oneplus boot image.
So I'm out of ideas now. about to wipe and go back to A10, because I can't for the life of me find a connection to all of this and its getting tedious to restore apps (especially 2fa apps).
Any help would be appreciated.

Hi!
I have had annoying bootloops when making a call.
It connects to a call and then boom, goes dark and reboots by its self. Very annoying.
I have 2 SIM cards on use, dont know If that matters.
Iam suspecting the network connection change during call -setting has something to do with it...
Hope there is an update coming soon to fix this.

Yea I have 2 sims as well (TMo and GoogleFi) so that's an interesting point. We finally now have dual-sim (US/Glo).
I'm currently testing out how long i can go with my current setup: Just A11 + Root + NoLimits....wait about 2-3days, then try LuckyPatcher (best way I know to remove ads), 2-3days, and then continue testing other ideas).