I'm seeing this everywhere, in scattered threads, so I wanted to make a centralized post for this issue and any potential remedies. Feel free to add to this list as well.
Problem #1:
Inbound Verizon iPhone calls are failing immediately upon answering.
Problem #2:
Inbound Verizon iPhone calls are not coming through at all.
Problem #3:
VZW iPhone users are reporting poor sound quality from the OnePlus user during the call.
Problem #4:
Inbound calls from non-contacts show as restricted at time of calling, but number shows in call history.
Related
I haven't found a thread on this, but then again I didn't do that great a job on searching.
Does anyone else have this issue? I am getting an average 50 Mbps download and about 7 Mbps upload but still get a 1 second lag between hearing the other person and them receiving my end of the conversation. Without wifi calling everything is fine.
If so, anyone have any tips on rectifying or point me in the right direction of the thread containing the info?
I can't even use Wi-Fi calling at all. Incoming calls don't even ring. I just get a voice mail notification.
Sent from my HTC One using XDA
I get an invalid sim error when set to cellular preferred, but I haven't had any trouble when set to wifi only or wifi preferred. I'm very light on voice usage though. I think there are several server locations, so issues could be regional, or (obviously) device specific. As of a couple days ago there was discussion of a widespread wifi calling outage (on tmobiles support forums I think, google it).
I've got some lag. Hoping it will get better if we ever get that update. It's really annoying since I'll say something...not hear a response... say something else...then accidentally cut into the other persons sentence. Then it turns into a sick game of who can finish the sentence first.
I've noticed the lag as well on wifi calls. I also hear my voice echo in the background when I'm talking to the person. They hear this echo which is delayed by a second or two. And I get crackling sounds pretty often, but I can usually understand the person ok.
I hope the next update TM pushes out fixes this and I hope it comes soon.
My wifi calling was not working at all as of a week ago (I was getting SIM errors) but now it seems to be working fine. No echo or delays here.
The person I am calling sees my wife's name in the caller ID (I guess because she's the primary person on our account?) but that's the only quibble I have.
I've also submitted two bug reports to google! Can't be the only one. Two separate issues, both are related to phantom digits getting input into the dialer with no visual record of them being input (i.e. it's happening somewhere on the backend).
After dialing into a conference call, when I go to put the conference number in. I.E. conference code 651582503, one of the digits is DUPLICATED.
So. I typed 651582503, and the conference line will say "Incorrect conference number, check the # and try again 6511582503
If you noticed, I typed an extra 1 for what the conference system reads back because it detects a phantom number. Now mind you, this issue has been occurring for about a year, and I dial into conference calls on this line at least 5 times a day.
The solution is to hangup, force quit dialer, and dial back into the conference. Only when doing this will it accept the number without adding duplicates.
Now, I initially thought this might be a bug with the samsung dialer. So I disabled google voice when dialing into this number and the issue completely went away.
I also upgraded from the Galaxy S6 to the Galaxy S8+ and the issue is persistent only when using google voice.
Separately, my phone will initiate call recording without me pushing #4 on the dialer.
I thought it was my Galaxy S6 causing the problem, but I just upgraded to a galaxy s8+ and the issue is still persistent.
Seriously, go into my last 20 call recordings and each time it's me apologizing to an executive or a client for recording them and that it was not intentionally initiated.
Anyone else having these issues? Is it a samsung issue or google voice!
Curious is anyone else can replicate this issue I am having. When I receive a phone call, the person on the other end of the line hears a really bad echo . It seems to only happen on incoming calls. If I hang up and call the person back, the echo goes away. I'm on Project Fi. I have weak cell signal so I stay connected to WiFi at home mostly. I'm not using hangouts or anything, just the regular dialer.
To produce the problem:
Receive incoming call over WiFi
Ask the person on the other end if they hear an echo?
If so, hang up call the person back (over same WiFi connection). Does echo go away?
Seems software related since calling the person back makes the echo go away. Thinking about factory reset unless others can verify it happens to them. I am on the most recent November security patch.
In case anyone cares, I contacted Fi support and they believe it is very likely to be a bug. I submitted a couple bug reports after making and receiving calls. Engineers are supposed to contact me back within 48 hours.
The same has happened to me when I call my friend with Discord. I haven't tried calling the person myself, that might fix the problem. I'm using unlocked with Verizon.
@bballjohn32 The same exact problem on first gen pixel (project fi).
Only when someone is calling me over wifi do they hear an echo. Also to note, when either making or receiving a call over wifi the phone says call via "unknown ssid". prior to Oreo 8.1 it used to name my wifi network name. I spent two hours with support and ended by performing a hard reset, that did not fix it either. They are issuing me a refurbished phone which I'm not too happy about...
Hey everyone,
For anyone experiencing this issue, I found a temporary fix until Google releases a patch.
First of all, you need a rooted phone for this to work. I'm NOT going to cover the details here on how to obtain root, but a quick Google search will certainly help you out on this one. If your phone is still under warranty, then this procedure is maybe not for you.
1 - Have a rooted phone that experiences the sound issue where an inbound caller hears himself in an echo.
2 - Install a free app called DeFluence from Google Play.
3 - Open DeFluence and grant Superuser rights to the app.
4 - Tap "Disable Fluency". If it was successful, you will see the message "DeFluence was granted Superuser rights".
5 - Reboot the phone and enjoy inbound calls without the echo issue.
The only drawback I can see from this is that the other person might hear some background noise of wherever you are located, but I think it's still a great temporary solution.
So all in all, this most probably means this is a software issue that slipped into Android Oreo, and hopefully Google will be able to find a solution soon.
What I believe is happening is that the mic used for noise cancellation is picking up the voice of the caller and echoing it back into the call, when it should really just act as a noise cancelling microphone and not a regular mic.
If you have any questions, feel free to ask.
HI all,
My gf's phone behaves in a really strange way...
During an audio call using common communicators, say skype, whatsapp, messenger, if a new incoming gsm/lte connection is coming, then it automatically takes priority over communicator call. Communicator call is put on hold.
What is most annoying, is that you are not able to inform the person on other side of the line that there is a new incoming connection - no, the second incoming connection is appearing on screen, current connection is put on hold. To clarify, user can chose whether to accept or cancel new incoming call, but the 'communicator' call is already on hold;(
I find this most annoying coming from iphone environment, where I have full control on all live and incoming connections and where no connection is prioritised. When im on a whatsapp audio call and a regular gsm connection is coming, I can let other person know that I have incoming connection and decide to answer, cancel or put current call on call. I find this rather normal behaviour. Unfortunately this is not the case on my gf's phone which drives me nuts
Please let me know if this is case of specific ROM, or android os in general? I hope you could guide me toward an easy solution, hopefully not requiring reinstalling new rom. Many thanks!
Phone is running MIUI Global 10.2.1.0, Android 8.0.0.
All incoming calls from people not in the contact list show caller ID name as "Restricted", despite the phone number being available. Sometimes the incoming number is displayed, sometimes it's not, depending on where the incoming call is shown. The number is always available in call history, and the caller's location is displayed. This is a huge headache, since some of us don't care for answering blocked callers.
This is not a carrier issue, but a glitch in the way the phone interprets the caller ID information.
Has anyone come up with a workaround or fix yet?
Same issue here. Quite frustrating.
geekasso said:
Same issue here. Quite frustrating.
Click to expand...
Click to collapse
I thought it was related to me having the google dialer framework installed.
Now I know I'm not alone. Yeah, pain in the butt.
X3