Closed Programmerino closed 7 months ago
Hi, use a lower port number instead of 65000. Try the default of 8228?
Please also attach a screenshot of your Hotspot screen, thanks!
I was testing the issue with a range of ports to see if it changed anything, here's the issue with default settings:
Ok cool thanks. Something seems to be causing problems for the ktor socket we use. I wonder if they know anything. Thsnks for the report, I'll dig around
Hi, I've looked into this and it seems like an IOException is unique to a device given a specific situation.
Basically its a tough bug. That being said, it looks like our ktor library can handle this by just "ignoring" the error and continuing to try again and again.
The next version will have a new experimental tweak called "Stubborn Proxy" which will ignore the error and keep trying, as well as some other tweaks to how we establish the server.
While I don't have a release date in mind yet, I hope when this new release comes out it may be able to help the problem, or further isolate the cause. Hopefully in the next few weeks.
Thanks!
Hello
Version 40 is recently released on the play store. Please download it when you have the chance and try enabling the "Stubborn Proxy" tweak. Thanks!
When I initially tested this change, it didn't seem to be working, but when I was trying to collect logs to submit here now everything seems to be working as expected! I'll keep you updated if anything changes. Thank you!
Device: Pixel 6a on Android 14 Issue: Regardless of the port, name, or password chosen, the following error occurs after any device attempts to connect to the hotspot. I've also noticed that the NetShare application which appears to use the same WiFi Direct legacy group + proxy strategy also mysteriously stops after starting. Logs: