Related

[Bug] No call sound until hitting volume up or down

Seensoul
25 days ago

After entering running or walking activity, and after trying to call somebody from watch or answer a call, there's no incoming sound. The interlocutor hears me, but I can't hear him.

A temporary solution is to select the phone app on the watch and enter the volume, click volume up or down, then you can hear the sound from the call

What may be cause this is that I have voice information about heart rate zones turned on during activities. 

Also, when calling somebody and when voice message about HR zone starts, the watch microphone is automatically disabled for a time of voice message,but it's not so important for me as the problem above with no sound until pressing volume up or down of the call application screen

Update

Unfortunately, not only during a run, but also during inactivity, simply when I call someone on the watch or answer a call, I simply have no sound, only pressing the phone app and pressing the volume down or volume up key causes the sound from the phone to appear in the watch speaker, so this is not a bug related to running activity or walking activity

FW 13.19

  • 0 9 days ago

    I have the same problem. Unfortunately garmin support doesn't respond about this bugs. They write prepared templates in response.

  • 0 8 days ago

    I also have this problem, though I have not associated it with any activity.  The caller hears me but I do not hear them.  While going to the phone app to correct this can work, I can get the incoming voice to be heard by swiping up after answering the call and changing the volume up and down.  This seems to turn on the speaker.  This is the fastest correction so I do not lose the caller.   I've had to use this routine several times before and after ver 13.19

  • 0 7 days ago in reply to JeffsV3

    The funny thing is that when you contact tech support to resolve this issue, they say they don't know about this problem and think it's an isolated incident. They offer the standard solutions of resetting the clock and reinstalling the app on the phone, but it doesn't help.  I have done this 3 times. For some reason, instead of helping to solve the problem, the support team tries to shut down at any moment. It's 100% a firmware problem and they don't want to admit it. Unfortunately there are a lot of such cases and we are not alone.