Hello,
I just update to AOSP Extended ROM (Android 7.1.2 not Touchwiz) and apart from the normal bugs everything was working fine but this morning for some reason none of my call will connect the just say dialing for 2-5 mins then end and when someone calls me it doesn't ring and just goes to voicemail. I can text and receive texts perfectly fine.
I thought it was the ROM at first so I switched back to the original one I had which is King of Nougat (Android 7.0 Touchwiz) but I still have the same problem I'am not sure how to fix it and nothing I try seems to work.
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 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.
On having installed the some roms they work well but there is a problem, does not leave me to send notes of voice for whatssap or sometimes they are cut, practically it notices them of voice they do not work (the microphone this one good) it happens to me with cm 12 or roms verision 5.1 pls me:good:
If I'm understanding correctly none of the current roms work on Sprint's network. Is that correct?
I've tried lineageOS and couldn't hold a signal so if there's one that works please point me in that direction.
Thanks.
I hadn't had any luck with ROMs on Sprint either until today. I decided to restore my TWRP backup of LineageOS 14.1 official, then I re-flashed the bootloader and radio from the most recent stock build (I had been on 4.4.3 to test something). The device was not active on my account at the time, but when it booted up, I got an alert from Signal Check Pro that it had an LTE signal, and the LTE indicator was on. So then I signed on and swapped devices to try to reactivate it, and immediately went into carrier settings and tapped update network settings. I got an alert shortly after saying com.android.phone had stopped, but it appeared to work, and I had a signal and LTE indicator. There was a Lineage update showing (May 17), so I downloaded it (over LTE) and installed it. Everything has been working so far, both before and after the update: voice, LTE (all bands), SMS, MMS, and RCS. So I really didn't do anything different, it's just working now.
Note, I have had SMS problems on every stock build starting with the first 6.0.1 build, and all security releases after it. I haven't had any problems on any older Android version. What happens is it works fine for a while, but at least once a day. SMS stops working until I reboot or update network settings. That's why I installed Lineage, trying to determine if it's a bug in Android or the radio. So far, no problems, but it has only been a few hours.
Sent from my Nexus 5 using Tapatalk
LOL it course the SMS bug struck after about 24 hours.. except this time it took a couple of tries to get data working again, and SMS wouldn't work again.. I knew better.. back to stock again..
Sent from my Nexus 5 using Tapatalk
I have a G920F currently running rooted stock 7.0 and there seems to be some sort of a problem with call audio. The other side sometimes can't hear me. It's not microphone's fault. When I record the call I can hear myself and the other person but during the call my voice is choppy or non-existent.
With a headset everything works fine.
I also tested it on custom roms and on NexusOS 8.1 it works like nothing ever happened. The problem occurs on stock based roms.