Network connection freezes in WLAN with FritzBox

matebovate · 29 September 2021 07:27

REPRODUCIBILITY (% or how often): nearly every day, but not in predictable time
BUILD ID = OS VERSION (Settings > About product): 4.2.0.21
HARDWARE (XA2, X10, X10 II, …): Xperia X
UI LANGUAGE: En
REGRESSION: (compared to previous public release: Yes, No, ?):

DESCRIPTION:

Since half about half a year my XperiaX freezes it’s network connections when I’m in my home-WLAN. All other WIFI-Connections seem to work fine - e.g. at work I have no problems.
When the connection is frozen there is no more network activity possible:
* I cannot turn on/off WIFI, Mobile Internet, Bluetooth or FlightMode
* The Connection-Icon shows a Wifi-Connection is active
* Even if I leave the house it still shows a wifi-connection.

To get a new connection I need to restart the phone.
The timing of this seems to be random. Sometimes it’s nearly instantly broken and some rare days it works without interruption.

Receiving an SMS or Phone-Call seems to interrupt the connection instantly.

Are there any useful logfiles I could take a look at?
Is there any way to reset my network connections without rebooting the whole device.

ADDITIONAL INFORMATION:

My home-Wifi is powered by a FritzBox 7490. No other device seems to be affected. In any other WIFI there are no problems.

Thank you.

lukas_jolla2015 · 29 September 2021 12:01

I can confirm exact the same problem with Fritzbox 7530 AX. I have a X10 with current OS 4.2.0.21, too.
Would also be very interested in how I could investigate the problem.

WT.Sane · 30 September 2021 22:41

No problems here with Fritz!Box 6591, 6490, 7170, 7560, 7590 and some more.
Maybe it is some configuration issue?

senders · 2 October 2021 11:19

I can confirm exactly the same behavior on my Xperia-X (F5121, SFOS 4.2.0.21)
Unfortunately, the complete loss of network connections is not indicated.
Usually I only notice when I open the Sailfish-Browser and see that most of the favorites icons are no longer displayed.
Then only a soft reset (Power+Vol.Up) helps until the next crash.
But this is not a new bug, it was already reported in the old Jolla-Forum.
https://together.jolla.com/question/205934/sailfishx-wifi-firmware-crash/
https://together.jolla.com/question/225927/xperia-x-complete-connectivity-freeze-with-accesspoint-steering/
Unfortunately without a practical solution.
It has been suggested that it has to do with AP-Steering (802.11v/k)
This assumption could be correct.
I use an AVM 7560 as access point and an AVM 2400 repeater with mesh steering.
Since I cannot deactivate the AP-Steering because of the other WLAN users, I only have the option of not using the WLAN with my Xperia-X
Therefore I would be very interested in a solution or at least in a workaround.

WT.Sane · 2 October 2021 12:38

My setup here: XA2, Verla and Fritz!Box 6591 with two meshed 2400 repeaters. 2.4 and 5 GHz Network, WPA2 (CCMP), canal auto selection, about 70 2.4 GHz Networks and about 14 in 5 GHz range nearby. Normally 3-6 active devices.

This worked similarly well with my Xperia X when I had a 6490 and only one repeater.

lukas_jolla2015 · 6 October 2021 13:03

I have these problems since I started to play with the configuration of the router. To be sure, that all problems concerning this are gone, I have reseted the router to production settings.
Where are the configfiles of the different known wifis stored on the phone. Maybe not everything is deleted by using the “forget” function. Due to the fact, that all other devices work fine with the router and my phone works fine with every other router, the problem must be in the configuration of the wifi of the fritz router.

ChMe · 6 October 2021 16:42

I started having the same problem since the very moment I added two Fritz-repeaters and established a mesh-network into my home-network. So for me its obvious that it’s a problem with the mesh: my wifi freezes on the phone when it seems to change the access points. Before that, without a mesh-network, everything went fine for years.

WT.Sane · 6 October 2021 20:22

I have a mesh network with two repeaters here. Works.
But we throw a lot of wireless bandwidth in our 85 square meters apparent.

petervandeninseln · 7 October 2021 04:19

I have the same problem with my Xperia X Compact, seems to be caused when i’m moving in the house between access points of the mesh network (fritz box router, fritz powerline network)

lukas_jolla2015 · 7 October 2021 06:07

Maybe we have got two issues here. I am thinking so, because my problem does not deal with the mesh function; I am just using the router without any APs.
So my situation is, that I had a working setup, “played” with the router, problems ocured and because of that I made a factory reset of the router. I expected a working setup again.
Does anyone know, where the wifi network configs are stored? To my mind in my case the problem has to be there. I do not want to flash by phone due to this problem…

peterleinchen · 7 October 2021 06:25

Take a look under (SFOS 3.2)
/home/.system/var/lib/connman
But it might have been relocated to
/home/$USER/.local/share/system/…
on newer SFOS version, not sure and cannot check ATM.

lukas_jolla2015 · 7 October 2021 07:57

Thank you very much for that info, I found the folder using find -name connman in /, forgot, that we have linux here
“Unfortunately” the forget function of a wifi network seems to work fine. When I use it, the config file disappears…
I tried now, to forget all networks, reboot the phone, and add network again. Right now it works, the question is, how long; I will inform here.
Really strange behavior.
@chris.adams: maybe you could give us a hint, where to look for the root of the problem?

lukas_jolla2015 · 7 October 2021 08:20

Changed nothing. After a few minutes the freeze is back. No Internet, not possible to switch off wlan, only vol up + power helps…

petervandeninseln · 8 October 2021 13:29

just a guess: does your fritz router switch automatically between different bandwidth? (like 2,4 / 5 ghz)? Maybe this could cause the same problem than changing access points.

matebovate · 12 October 2021 06:38

@petervandeninseln That was a good hint.
I’ve deselected some settings in my Wi-FI Channels Settings in my Router-Configuration:

Previously the four checkboxes where active. And now it seems to work (at least for the last four days).

Thanks a lot.

senders · 12 October 2021 17:39

After several days of functioning without any problems, the network connections crashed again.
Before, my Xperia-X had been out of WiFi range and had a cellular data connection.
After WiFi was available, it had successfully connected to the repeater,
but 15 seconds later the network connections crashed.

In the access point logs I can see that the frequency band and the access points were successfully switched several times during the days before.
At the time of the crash, no band- or AP-steering took place.
So I can’t see any direct connection between the AP- or band-steering and the crashes.

The Wi-fi channel settings of the Mesh Master were previously set to automatic.
Now I have adopted the setting which matebovate describes, with the exception of Checkbox 2 (switch automatically between 2.4GHz and 5GHz). Because the deactivation makes the mesh function useless for me.

Furthermore, I have adjusted the sailfish system logs to persistent, to hopefully get more information from the Journal next time. Does anyone have any idea what to look for in it?

Let’s see if this lasts longer, I’ll report here again.

lukas_jolla2015 · 13 October 2021 05:43

@petervandeninseln, @senders : Thank You very much for the hint! These settings work for me, too.
Is the switching between 2,4 and 5 GHz described in the wifi standard? I am asking, because that would simply meen, that SFOS currently just do not support the latest standard. If not, it is an implementation bug.
Thank you again and best regards,
Lukas

paulvt · 8 November 2021 19:51

For me the whole kernel network stacks seems stuck, even running ip a on the terminal blocks.
I found the following (kernel) journal messages in my log when it happened:

Nov 08 20:24:41 tension kernel: INTERNAL ERROR: FIRMWARE HALTED : set BUS DOWN
Nov 08 20:24:41 tension kernel: CONSOLE: _rrm_abort: state upd to 1
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.101 wlc_rrm_abort: state upd to 0
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.101 wlc_rrm_abort: return to the home channel
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.102 wlc_rrm_bcnreq_scancb: state: 0, status: 4
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 
Nov 08 20:24:41 tension kernel: CONSOLE: FWID 01-75cc3c71
Nov 08 20:24:41 tension kernel: CONSOLE: flags 1
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 
Nov 08 20:24:41 tension kernel: CONSOLE: TRAP 4(25f828): pc 7a094, lr 7a093, sp 25f880, cpsr 6000019f, spsr 600001bf
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103   dfsr 80d, dfar 218
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103   r0 36, r1 5, r2 0, r3 1, r4 24a5cc, r5 0, r6 24a55c
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103   r7 4, r8 259e38, r9 4, r10 24a5cc, r11 f, r12 0
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 
Nov 08 20:24:41 tension kernel: CONSOLE:    sp+0 00256bf4 00259e38 0007a079 00000000
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103   sp+10 0021dbec 001e5f1d 00256bf4 00256bc4
Nov 08 20:24:41 tension kernel: CONSOLE: 
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+8 0007a079
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+14 001e5f1d
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+34 001e682b
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+3c 00079dff
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+64 00029c91
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+7c 00031793
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+a8 00029c91
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+d8 0000640b
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+fc 00023f3b
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+128 00029c91
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+150 00020023
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+19c 0002ffff
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+1b0 00020023
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+1dc 0002c4af
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+1f8 0000018b
Nov 08 20:24:41 tension kernel: CONSOLE: 048801.103 sp+1fc 00036a71
Nov 08 20:24:41 tension kernel: dhdsdio_checkdied: msgtrace address : 0x00000000
                                console address  : 0x0025DEBC
                                Assrt not built in dongle
                                Dongle trap type 0x4 @ epc 0x7a094, cpsr 0x6000019f, spsr 0x600001bf, sp 0x25f880,lp 0x7a093, rpc 0x7a094 Trap offset 0x25f828, r0 0x36, r1 0x5, r2 0x0, r3 0x1, r4 0x24a5cc, r5 0x0, r6 0x24a55c, r7 0x4
Nov 08 20:24:51 tension kernel: CFG80211-ERROR) wl_scan_timeout : timer expired
Nov 08 20:26:00 tension kernel: i2c-msm-v2 7af6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
Nov 08 20:33:52 tension kernel: i2c-msm-v2 7af6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090

This seems… not good!

chris.adams · 7 December 2021 09:33

Unfortunately I do not know. I will ask Jussi.

13497422 · 8 December 2021 05:12

Same problem on my X. I am struggling with that problem since i have it. It is a sad defect in a base function - network is supposed to work. Period. I tried to prevent the device from going to sleep mode. I don’t know perfect that worked, at least it works some days, but at the end it fails too. That is a fundamental problem, i am really fed up with this. I also can see kernel module crashes on dmesg output, this occurs on every boot. This is embarrassing.