-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Android app will go to low bandwith mode whenever on mobile network (LTE) #14686
Comments
It doesn't look like a low bandwidth problem but rather a connectivity issue when youa re using LTE. Can you reproduce the problem if you start on LTE directly? Do you observe the same when using meet.jit.si rather than your own server? |
Hello, |
In your tests, where the server and the mobile part of the same network? |
Uff I did just test with WiFi outside the office network and it is the same issue. I have also tried joining with my PC using the LTE hotspot (doesn't work). So my guess is now that there is something not correctly configured either with port forwarding or with Nginx reverse proxy manager on the server. |
Looks like the media port (10000 UDP by default) might not be properly forwarded to the JVB server. |
Description:
Mobile app (Android) will go to low bandwidth mode and disable video whenever I would switch from WiFi to mobile network LTE. If I run speed test on mobile, it shows about 130Mbps down and 40Mbps up with 24ms ping. So I think the connection should be more than enough to support 2 people on call. Also when there is no video, there is no audio too, so not sure if this is related or a separate issue. I have checked in the mobile app if there is any setting to disable this "saving bandwidth" mode, but didn't found any.
Steps to reproduce:
Expected behavior:
Video and audio should continue working on LTE given a sufficient bandwidth (130/40).
Actual behavior:
Application displays message "Video has been turned off to save bandwidth".
Video and audio stop working.
Server information:
Client information:
Additional information:
/
The text was updated successfully, but these errors were encountered: