Ask / Submit

[Help] Xperia X losing WLAN connection

Tracked by Jolla

asked 2019-01-04 23:06:19 +0300

Piece_Maker gravatar image

updated 2019-07-26 10:39:59 +0300

Giacomo Di Giacomo gravatar image

Hi everyone,

I've noticed an odd problem this past couple of weeks, and I'm not really sure how to pinpoint what's causing the problem. I've not changed anything on my home network such as router settings.

I have the phone connected to my home WiFi network, and all is well - however after a random time period (Sometimes it lasts a few hours, sometimes as little as 15 minutes), I'll lose the ability to connect to anything from my device. This not only includes websites, but also things running on my internal network such as my IRC bouncer and Syncthing nodes. The WiFi indicator on Sailfish OS still shows I'm connected to the WiFi, however the web browser simply won't load a website up. Usually I'll try to disconnect and re-connect to the WiFi at which point it'll fail, or tell me that the connectivity is limited.

I have to go into the 'Utilities' part of the settings app and restart the networking subsystems to fix it, although sometimes I'll even have to reboot the device before it'll work again.

As far as I'm aware no other device on my network is dropping connection, although there are various other phones/tablets and it's not always possible to check them all. My home network is just the generic ISP router, no custom DHCP or DNS servers running such as Pi Hole. I have already tried setting the DNS servers on my phone to use as well as just to make sure it's not a problem with the default DNS setup but this doesn't seem to help.

Can anyone help me track down the source of this issue? I'm not even sure where to start! Thanks a lot!

Edit 24 July 2019: The issue, who had almost disappeared, is now happening repeatedly since the device was upgraded to 3.1.0.

Edit 26 July 2019: The issue has got catastrophically worse since the update to 3.1. I need to reboot the phone about 10 times a day when I am at work. This appears to be related either to loss of mobile network signal, or to wifi networks with multiple access points.

edit retag flag offensive close delete



After reading your description, I think I am suffering from the same problem with a Sony Xperia X and Sailfish OS First I thought only Android apps were affected, but the native apps are also missing a connection. Unfortunately, as you described, you do not notice the problem until you are using an app that complains about missing connectivity. There is no sign in the Sailfish OS GUI at all. Concerning debugging: Did you have a look into the logs (devel-su and journalctl)?

Benjamin ( 2019-01-06 12:45:06 +0300 )edit

Hey there!

I don't really use Android apps very much so I haven't noticed any problems on that front, presumably it'd be exactly the same though.

My journalctl for the past half hour is pretty huge, but I'm not sure which parts are relevant, pastebinned here:

Another pastebin that may or may not actually have the relevant bits (It has things about networking/connman so I assume so?)

It was around 12:20 that I noticed the network being off so this would make sense.

And yes, the odd part is that the network indicator on the GUI seems to always show a 100% maxed signal rather than it going up and down as normal as I wander around the house.

Piece_Maker ( 2019-01-06 14:43:06 +0300 )edit I landed at Austin, TX airport y-day, and Xperia X wifi went completely crazy on me. Browser couldn't connect to anything, it was not possible to turn wifi off (it would automatically reconnect to AP), and after a few minutes, phone would completely freeze. After reboot, same thing. Interestingly, just like notes today, SSID could not be deleted from the list to forget the network.

Only way to get the phone stable was to post-reboot skip SIM pin code entry, and really quickly try to disable wifi adapter.

At my hotel, everything works fine again. Hypothesis: there's quite certainly some types of AP setups out there that are able to drive current SFOS wifi stack completely nuts.

lkraav ( 2019-01-07 02:18:54 +0300 )edit

Hi, I went to Boston a couple a weeks ago and experienced the same thing as described by @lkraav but with hotel wifi AP. I am on Xperia X and Sailfish

DNG ( 2019-01-07 20:11:47 +0300 )edit

After having tested this a little further, the BYOD WiFi at my workplace seems to not suffer from this issue at all. That even requires me to login, which works first time every time in the WiFi GUI menu, so presumably is a more 'complicated' setup than the one at my house.

This only started with the last ( update, it worked fine before then and is still present in the update.

I'm considering a clean flash, though in reality I can't really be bothered with that, especially without knowing if it'll actually help.

Piece_Maker ( 2019-02-02 23:57:40 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-01-06 19:29:06 +0300

Benjamin gravatar image

I see the following disconnect in your first log. It is also contained in the second log.

Jan 06 12:19:24 Sailfish kernel: CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3
Jan 06 12:19:24 Sailfish kernel: CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK
Jan 06 12:19:24 Sailfish kernel: CFG80211-ERROR) wl_notify_connect_status : link down if wlan0 may call cfg80211_disconnected. event : 16, reason=2 from 48:d3:43:7a:03:bf
Jan 06 12:19:24 Sailfish wpa_supplicant[2376]: wlan0: CTRL-EVENT-DISCONNECTED bssid=48:d3:43:7a:03:bf reason=3 locally_generated=1
Jan 06 12:19:24 Sailfish statefs[677]: Network manager is "ready"
Jan 06 12:19:24 Sailfish kernel: cfg80211: Calling CRDA to update world regulatory domain
Jan 06 12:19:24 Sailfish kernel: CFG80211-ERROR) wl_cfg80211_reg_notifier : reg_notifier for intiator:0 not supported : set default
Jan 06 12:19:24 Sailfish kernel: CFG80211-ERROR) wl_cfg80211_reg_notifier : Set country code 00 from User
Jan 06 12:19:24 Sailfish kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

And as far as I can tell the connection is established again here:

Jan 06 12:26:19 Sailfish wpa_supplicant[2376]: wlan0: Trying to associate with SSID 'VM8004106'
Jan 06 12:26:19 Sailfish kernel: CFG80211-ERROR) wl_cfg80211_connect : Connecting to ff:ff:ff:ff:ff:ff with channel (1, 44) ssid VM8004106
Jan 06 12:26:20 Sailfish kernel: wl_bss_connect_done succeeded with 48:d3:43:7a:03:bf
Jan 06 12:26:20 Sailfish kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

A little bit later it seems that you restarted the network in the settings:

Jan 06 12:26:47 Sailfish estart[7365]: [D] executeAction:48 - Start Restart
Jan 06 12:26:47 Sailfish systemd[1]: Stopping ConnMan VPN service...
Jan 06 12:26:47 Sailfish connman-vpnd[2369]: Exit
Jan 06 12:26:47 Sailfish systemd[1]: Stopped ConnMan VPN service.
Jan 06 12:26:47 Sailfish com.jolla.settings[2132]: invoker: Invoking execution: '/usr/bin/jolla-settings'
Jan 06 12:26:47 Sailfish systemd[1]: Stopping Connection service...
Jan 06 12:26:47 Sailfish kernel: CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3

I have found an issue that seems to be similar. But it mentions an log entry “CFG80211-ERROR wl_scan_timeout: timer expired” that I cannot find in your logs.

I did a web search for “wl_is_linkdown WLC_E_LINK” and found a question. A comment there suggests that it might be a power management issue with the wifi device.

edit flag offensive delete publish link more


I did restart the network, because although the connection is apparently re-established, I still end up with no actual networking.

I've heard of power management issues with WiFi on Linux before, but it does seem a bit odd that this problem has only started occuring for me recently, considering I've been running the Sailfish X since release. The difference is though, that my WiFi doesn't actually drop - the indicator stays up like everything's fine.

Thanks for the links! I'll see if I can glean anything further from them!

Piece_Maker ( 2019-01-06 19:36:22 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2019-01-04 23:06:19 +0300

Seen: 410 times

Last updated: Jul 26