Answered call - can't hear caller, caller can't hear me (fixed but why?)

PaulQ

Well-known member
Jan 6, 2011
1,984
29
48
I answered a valid call today and heard nothing. I assume they heard nothing from me. I checked if it was going to my watch, it wasn't. Tried speakerphone, nothing. It was like the earpiece and speaker were dead. Had someone else call me, same thing.

I rebooted and it's working now (or for now). It's P7P.

I haven't done anything to keep it from happening again because I don't know if there's anything to do or just a random glitch.

It was on WiFi calling but the signal is strong.

Anyone know why this might have happened or had it happen to you?

Thanks!
 
Do you use Pixel Buds? There's a persistent bug with my Pixel Buds 2 where sometimes they'll connect to my phone, even when still in the case. That can be annoying, because if I get a call in that situation, no one can hear anything (since the audio is going through the buds in the case).
 
I too have experienced that problem with my pixel buds. My solution is to reboot the phone and the problem goes away.

Sent from my Pixel 7 Pro using AC Forums mobile app
 
Do you use Pixel Buds? There's a persistent bug with my Pixel Buds 2 where sometimes they'll connect to my phone, even when still in the case. That can be annoying, because if I get a call in that situation, no one can hear anything (since the audio is going through the buds in the case).

That's an annoying bug. I have Pixel Buds A in my backpack. Nearby. Are they also experiencing that bug?

Can you switch the input/output source on the call screen from the buds to the phone?

I just hope I don't have to reboot often. I missed a call that was kind of hard to return. Then it was several minutes rebooting and getting going. I did call back and jumped through all the hoops to get to the right person. It worked out this time.

Still love this phone. You should see the sea of SPAM calls it deflects.
 
You can switch it in the in-call UI -- but now that I think of it, since you said you already tried switching to Speakerphone, I'm guessing this isn't your problem. If it were connected to your Pixel Buds, you'd see it on the screen (in place of the toggle for Speaker).
 
Don't stress yourself out about this, it's something that just happens from time to time. I have had it happen on iphones, galaxy phones and pixel phones.

There are reasons why it is suggested to restart your phone on a weekly basis. Software is not and never will be free of little glitches and bugs. Which are commonly fixed by the universal first trouble shooting step, turn the device off then back on.

Sent from my Pixel 7 Pro using AC Forums mobile app
 
Don't stress yourself out about this, it's something that just happens from time to time. I have had it happen on iphones, galaxy phones and pixel phones.

There are reasons why it is suggested to restart your phone on a weekly basis. Software is not and never will be free of little glitches and bugs. Which are commonly fixed by the universal first trouble shooting step, turn the device off then back on.

I'm not stressed about it but it was a very bad time for it to happen. This was a glitch I had never experienced in all my phone years. I reboot my phone occasionally but I'll do it weekly now as suggested. Too bad the Pixels don't have the automatic scheduled reboots like Samsung.

Thanks all!
 

Members online

Forum statistics

Threads
954,016
Messages
6,960,259
Members
3,162,899
Latest member
dkpiper