Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Google Voice dial pad and latest Firefox 135.0.1 64-bit

  • 1 resposta
  • 0 tem este problema
  • 3 visualizações
  • Última resposta de markwarner22

more options

Can no longer use Google Voice in second half of a normal 8-5 work day, it appears. No amount of rebooting/restarting, closing browser, clearing caches, removing temp files, etc. appears to affect the issue. Turning off Enhanced Protection doesn't help. Issue is that I can dial a number, call connects, I can hang a call up, but the dial pad becomes unresponsive during the call. Using keyboard numbers vs. clicking the dial pad numbers makes no difference; no response either way. This happens with normal local calls, MS Teams calls from New York & other places for work, all of them. But, again, seems to happen after noon/lunch time. Very odd. The latter was why I thought it was more than 1 tab open, system resources, temp files, RAM allocation, etc. Happens whether I have only Google Voice open in 1 tab, have multiple tabs running alongside it, doesn't seem to matter.

Very perplexed. I shifted away from Brave to use FF for Google Voice & now the situation is reversed. Now, I can normally open Brave when this happens & get a responsive dial pad in Google Voice.

Using Windows 10 Professional, 64-bit on a big powerful workstation replacement category notebook.

Can no longer use Google Voice in second half of a normal 8-5 work day, it appears. No amount of rebooting/restarting, closing browser, clearing caches, removing temp files, etc. appears to affect the issue. Turning off Enhanced Protection doesn't help. Issue is that I can dial a number, call connects, I can hang a call up, but the dial pad becomes unresponsive during the call. Using keyboard numbers vs. clicking the dial pad numbers makes no difference; no response either way. This happens with normal local calls, MS Teams calls from New York & other places for work, all of them. But, again, seems to happen after noon/lunch time. Very odd. The latter was why I thought it was more than 1 tab open, system resources, temp files, RAM allocation, etc. Happens whether I have only Google Voice open in 1 tab, have multiple tabs running alongside it, doesn't seem to matter. Very perplexed. I shifted away from Brave to use FF for Google Voice & now the situation is reversed. Now, I can normally open Brave when this happens & get a responsive dial pad in Google Voice. Using Windows 10 Professional, 64-bit on a big powerful workstation replacement category notebook.

Todas as respostas (1)

more options

What happens when you Chrome for this progam?

Útil?

Faça uma pergunta

É necessário entrar na sua conta para responder a publicações. Faça uma nova pergunta, se ainda não tiver uma conta.