No internet connection in Waydroid (OnePlus 5T)
-
Since I've updated Waydroid to the latest version (Waydroid 1.51, Android 13) in most cases there is no internet connection in Waydroid. The log says “unable to connect to 192.168.240.112: 5555: No route to host”.
I’ve tried everything I found on the internet.
The strange thing is: From time-to-time Waydroid DOES connect to the phone and everything works fine. But I’m not able to reproduce this behavior. Although I repeat all the steps that seem to have led to a working system before, like rebooting, restarting, reinstalling, resetting internet connections on the phone and in Waydroid in a special order, it usually fails.
Updating Waydroid and Ubuntu touch doesn’t change anything.
On another OnePlus 5T everything is the same.
There seems to be any random mechanism working, when Waydroid tries to get an ethernet connection to the host ...
Any ideas?
Or anyone facing such problems on similar or other devices? -
@Phil87 Sounds similar to the (fixed) issue: https://forums.ubports.com/topic/11133/waydroid-no-internet-inside
-
@sven Thank you! Unfortunately installing yesterday’s new Waydroid version didn‘t help.
This is the only procedure that works – sometimes:
- Switching WLAN and mobile data off,
- restarting phone,
- starting Waydroid, resetting internet connection in Waydroid,
- resetting internet connection in Waydroid again – and switching on WLAN on the phone, while the search for an internet connection within Waydroid is running.
- Success: Waydroid has internet!
- Stopping Waydroid session and container and restarting it – the connection is lost again
The moment to switch on WLAN seems to be critical. It must not be two seconds too early nor two seconds too late.
-
Sorry to hear that it does not work for the OnePlus 5T. Maybe the files for this device are not ready yet? You could use the issue on github to get some more help https://github.com/waydroid/waydroid/issues/1958
or (maybe better) ask in the telegram group "WayDroid on Ubuntu Touch". -
@sven Okay, thanks! I posted the problem on github too, hoping for a patched vendor image – and ordered a Fairphone 4 which should be maintained more intensively.