Bandwidth Limit not working
Closed this issue · 7 comments
First i would like to thank you for this great app.
The issue is when I'm using the Bandwidth Limit at 2 MB . the connected device doesn't seem to be affected, because when I'm using speed tests like Fast.com , the speed is not limited and I'm getting above 10MB/s ( my max Data speed ).
I'm very new at reporting issues , please let me know what else is needed from me to help you diagnose this issue.
I will see about the inaccurate bandwidth limit. When not using the limit, do you also hit 10 on fast.com?
Either turning it on or off has no effect , 4G LTE internet always goes between 7 MB/s - 12 MB/s .. So if the function ever gets functioning : a 2 MB/s should be a very distinguishable/obvious change.
Regarding my other closed topic, it is actually a serious one as without internet access to the essential apps , the whole purpose of tethering is in vain.
BTW , enabling or disabling the bandwidth limiter has no effect on internet access to these apps :
Telegram
WhatsApp
Facebook
Instagram
Threads
Speedtest by Ookla
Hi
Chat apps like Telegram are unsupported currently as they use websocket which can not be proxied by the Android OS
All the Facebook and Speed test related apps use websocket as well. Particularly apps owned by Meta do not like proxies and will explicitly block proxy connections. For these, there is nothing I can do as a third party developer without becoming a system VPN option, which this project explicitly does not want to do, sorry.
Okay , Is there any workaround for making them work , If i use VPN connection by another app maybe ?
Regarding the Bandwidth limiter , If you need any log or anything to help you diagnose it , let me know.
I unfortunately do not know. I know other apps that perform a similar function to this one exist, like Net share for example. You are welcome to try those to see if they have managed to solve the problem somehow.
Hello
Just an update, I have noticed that the bandwidth limit is incorrectly applied per-socket instead of per-client. As a result, it leads to wildly different numbers than expected. I have a new dev build in the works that I am testing with that gives much closer numbers on fast.com
A limit will never be perfect, but the old code was very far off and this is considerably closer. I hope to release this in the next version. Thank you for your patience. I will update again as release gets closer.