search

sailfishos-sony-tama / main

Documentation, releases, and issues
MIT License
36 stars 7 forks source link

internet problems since update to last version in xz2c #199

Open Dracks opened 1 year ago

Dracks commented 1 year ago

Hello,

Last weekend I updated to the last version. (I did a big jump, maybe thats the cause, from 4.4 to 4.5.0.19) I've got problems with internet.

the problems seems to come from wiki and mobile.

About the mobile: It say is connected to 4G, but there is no internet at all. I tried to restart and didn't work, once what worked was to simply put it in airplane mode and leave it. But not always.

About the wifi: This is more stable, but seems that sometimes is disconected from the wifi, and also when I arrive home, it doesn't connect automatically, If I connect it manually then it works.

What logs I can check and retrieve/share here?

Since this update, it was amaizingly well.

Thanks! Jaume.

rinigus commented 1 year ago

going from 4.4 to 4.5 should be OK. As 4G/Wifi issues, don't know where to start. On XZ2, I don't have any of these - so it is possible to have it stable. Try to check the logs and see if something is obviously wrong.

Dracks commented 1 year ago

Sorry I was not able to debug it, usually when I realize the problem I'm far of the computer... What I realize is that only happens when waydroid is up and runing, when it's not runing, seems that the problem is not there anymore.

rinigus commented 1 year ago

It could be related then just to RAM pressure and some processes being killed when you have Waydroid running.

Dracks commented 1 year ago

Yesterday I tried, I had only half of the ram usage with waydroid and the internet connection went down, I stop waydroid (I'm using waydroid-runner) and inmediatly the wifi was connected again. Now that I know how to replicate it, I will try to get time and replicate and get logs. (In any case, seems more a problem from the waydroid than the sailfish, but until I've got more info, is ok to keep this issue open?)

Dracks commented 1 year ago

I can confirm that most of the times that this happens is having the waydroid runing. There is complettly 0 comunication of the device in that case. But I think is not only when the waydroid is runing. There were some cases that I didn't had the waydroid runing and when I leaved my house I realise the phone didn't had any internet.

rinigus commented 1 year ago

Then it s probably just OOM killer doing its job and killing something useful. I would expect it is a generic problem and not related to the port as such. Closing?

Dracks commented 1 year ago

Not sure... the apps are still runing, is not the apps killed... I don't have any other phone to test it with details.

Dracks commented 11 months ago

hi, I investigated a little bit, this past week, seems the problem is like linux doesn't wish to request an ip for the wifi/mobile data when waydroid is up and runing. While the ip keeps the same, everything works fine (for example, this night I had the waydroid runing all night, and no problem, is still connected, but at the moment that I put the flight mode, and disable, is not able to connect until I stop waydroid)

Is it possible that the priorities of the network interfaces are wrong and when he detects the ip for the virtual network of waydroid ignores the rest?

Thanks for the help.

Dracks commented 7 months ago

Hi,

I investigated more, and I think the problem maybe comes from waydroid, I can create a ticket there if you wish. But what I discover is that waydroid creates two network interfaces waydroid0 and veth3xk8AE while the first one doesn't seem to do anything, if I set it down it, waydroid internet continues to work, and the problem of sailfish persists, the second one, seems to handle all the networking of the waydroid, and when this one is "down" the problem dissapear, of course, letting the waydroid VM without internet.

I also commented it in the sailfish forum

Thanks!