Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iTeamtalk fails to transmit voice after connection lost and reconnected #1974

Open
2 of 10 tasks
hejiadong0608 opened this issue Aug 7, 2023 · 2 comments
Open
2 of 10 tasks

Comments

@hejiadong0608
Copy link
Contributor

Description

When the network is poor and the connection is lost, and after reconnecting to the server, voice transmission is no longer possible. Toggling the transmission function also has no effect. The connection must be manually disconnected and then reconnected to the server.

Application

  • qtTeamTalk
  • TeamTalkAndroid
  • iTeamTalk
  • TeamTalkClassic
  • TeamTalkServer

Platform

  • Windows
  • macOS
  • Android
  • iOS
  • Linux

Expected behavior

When itreconnected to the server, voice transmission is available.

Actual behavior

Voice is no longer transmitted after reconnection

Steps to reproduce problem

  1. connect to a server
  2. start to transmit voice
  3. cause the connection to be lost, such as switching networks or restarting the server
  4. Waiting for automatic reconnection
@Simon818
Copy link

I have been noticing this on unstable networks as well. It only happens if the TeamTalk app is out of focus. I wonder if TeamTalk is letting go of the microphone when it disconnects but is then unable to reinitialize it when the app is running in the background. Once TeamTalk is in this state, there's no way to fix it besides disconnecting and reconnecting. So if I'm in a car and switching cell towers, I just have to keep the app open in case the connection times out.

@stickbear2015
Copy link

this issue is still a problem, @bear101 and like @Simon818 I am able to get around it by leaving the app open, but I'm not going to sit their with the app open, it hogs batteries enough in the background, to get my transmission to stick around on a network switch. I also note, that if the connection drops, and reconnects, in some cases, I even lose inbound audio from others on the server, I mostly find this is happening when my vpn drops, when I am coming back onto my home wifi or a wifi network I've purposely configured to not use my VPN. It's sad to see issues like this go stale, and issues like #444 being left for years. I understand you do this for free for most users, but you are making money off the pro licenses, if you want to make money from users that might purchase a pro license, how about you show the average user your actually paying attention and listening to the issues being raised instead of just adding a label and then falling off the face of the earth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants