I've noticed that on CM12, CM12.1 and OxygenOS that the call command ("call *******") for Google Now does not place a call, it simply enters the number into the dialler and leaves it at that. Does anyone else have the same problem? I'm trying to find out what is causing it but I haven't been able to so far. I have a Nexus 4 and a Nexus 5 that work flawlessly but it won't work on my OPO.
Related
This happens only on outgoing calls on bluetooth (car audio): I can hear the person on other side talking, but that person cannot hear me. I switchover to handset or speakerphone and switch back to bluetooth, and the problem goes away. Both parties can hear each other and call proceeds without a problem.
This problem does not occur on incoming calls at all. I pick up using the button on car audio and the conversation happens without an issue.
The exact same issue occurs on all the builds I have tried: CM10.1 (both stable and nightly), Slimrom 4.2, Slimrom 4.3 nightly, Aditya's CM11 (tried at least 3 builds, currently running his build 12).
I did not see any mention of this by anybody else. Am I alone in facing this issue?
I have used both an android phone and a windows phone earlier on this car audio and this issue did not show up on those.
Thanks, folks. I would really love to fix this and continue to use this wonderful phone for a few more years!
It gets crazier
I just got my hands on a Sprint Galaxy Nexus (toroplus):
Weird: This exact issue (bluetooth outgoing call does not grab my side of the conversation until I switch the call to speaker/handset and back to bluetooth) happens on all the builds of CM10.2, CM11 and Slimkat.
Weirder: This DOES NOT happen on 4.3 stock rom (JWR67B) version of the software. I am unable to try and load stock rom to NS4G, so haven't tried this trick with that.
Weirdest: Now that I have isolated the problem to the CM (or its derivates in slim version), how is it even POSSIBLE that I am the only one experiencing this? I cannot find any mention of this issue anywhere in the net. Unfortunately, both my bluetooth receivers are the exact same model: pioneer DEH-4500BT. However, the fact that Galaxy nexus stock rom (and earlier phones, like Samsung Prevail or Lumia 521) work flawlessly deflects any suspicition on the DEH-4500BT's part.
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Roy2208 said:
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Click to expand...
Click to collapse
Unfortunately this is a known issue that hundreds, if not thousands of people have been experiencing and reporting ever since the phone was released a year ago. So yes ever since 4.4, before even 4.4.2. Even more unfortunately it is a known issue that neither Google nor any carriers admit to own up to. Anyways to my knowledge no one knows if it is a software or hardware issue, but it is most likely not a carrier issue since it is reproduced on multiple different carriers. Anyways I will link you to the Google Forums thread that started on this issue a year ago and has hundreds of people posting and reporting it in that thread. You can find that post if you click right here.
The only solution is a work around, not a permanent solution. If you find out that someone called you, and the phone did not ring, restart the phone. It seems to have resolved the issue temporarily. I always restart mine every 2 to 3 days anyways to try to prevent it as little as possible, so that is what I would suggest. Also maybe state on your voice mail if you did not pick up to leave you a voice mail or send you a text so you know they called, because you been having issues with calls on your phone. That way you know someone called, because you will still get the text message or voice mail notification.
I had the problem mentioned in the second post (which may not be what OP was describing) and I solved it by trying out different radios. Latest one with Lollipop is fine, but the two before that weren't good.
The stock CM 11s allowed me to use a Bluetooth device and set the phone to auto answer on incoming calls using one of the few apps for "Auto Answer" in Play Store.
It looks like CM12 and Roms for OPO running Android 5 and above this doesn't work. Anyone tried this and got it to work?
Calls auto answer on bluetooth
Still no fix for this issue ? Since it's quite important for me to get automatic answers while working, I decided not to upgrade my OPO to CM12. Has anyone found another solution ?
Hello, I have a Gear S3 Classic BT with a Oneplus 3 (LineageOs, last nightly).
Everything works except for making/receiving calls, it just says something like "check device" when I rotate the bezel to accept a call and does nothing when I try to start a new one.
Is there a way to fix it?
For OP3 users on OOS: does it all work with stock rom?
I had exact same problem.I was using Lg g2 with custom cm 14 rom, when i tried to call someone or answering incoming calls gear just says "check device" and nothing happens.I tried many things but none of them have worked.Solution for me is going back to stock based rom.
Gone back to OOS, calls work. Not fine (bluetooth connection issues, it disconnects randomly), but at least it works.
Hi guys,
I enjoyed the native call recording feature of my OnePlus 7 Pro (still official OOS without mod), activated only by using Magisk and jOnePlus Tools via ADB command.
In previous versions of OxygenOS it worked flawlessly, but after my official upgrade to OOS 12 it produces this echo sound, which the second person hears during call (he hears his own voice).
I tried to reinstall/reactivate it many times, but still this issue persists. My friend's OnePlus 7 Pro has got the very same issue after upgrading to OOS 12 and is not able to do anything against it either.
Does anyone of you face the same issue, please? Did anybody succeed to solve this, please?
Thanks for any comments!
Hey
Did you ever find a solution? Just got the OOS12 update now and having same problem.
Maybe will try another dialer (I couldn't get OnePlus dialer to work after downloading from somewhere).