[C2] Wifi strange issue

Bug Reports
1

REPRODUCIBILITY: ~ one per week
OS VERSION: 5.0.0.70
HARDWARE: Jolla C2
UI LANGUAGE: Français
REGRESSION:

DESCRIPTION:

After sometimes, randomly, wifi stop Working : I cannot ssh to my phone or go to internet etc.

C2 connect to routers (2 tested) well. C2 have ip and I can see C2 on my routers.

[root@JollaC2 defaultuser]# connmanctl state
  State = ready
  OfflineMode = False
  SessionMode = False
  InputRequestTimeout = 300000
  Ipv4StatusUrl = http://ipv4.jolla.com/return_204
  Ipv6StatusUrl = http://ipv6.jolla.com/return_204
[root@JollaC2 defaultuser]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
[...]
27: wlan0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether dc:79:d5:e9:ed:9c brd ff:ff:ff:ff:ff:ff
28: usb0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 66:8f:43:0f:68:9d brd ff:ff:ff:ff:ff:ff
[root@JollaC2 defaultuser]# ip a
[...]
27: wlan0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether dc:79:d5:e9:ed:9c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.33/24 brd 192.168.1.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::de79:d5ff:fee9:ed9c/64 scope link 
       valid_lft forever preferred_lft forever
28: usb0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 66:8f:43:0f:68:9d brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.15/24 brd 192.168.2.255 scope global usb0
       valid_lft forever preferred_lft forever
    inet6 fe80::648f:43ff:fe0f:689d/64 scope link 
       valid_lft forever preferred_lft forever
root@JollaC2 defaultuser]# ip neigh show dev wlan0
192.168.1.1 lladdr 8c:f8:13:3c:8b:86 REACHABLE 
[root@JollaC2 defaultuser]# ping -c 3 192.168.1.101
PING 192.168.1.101 (192.168.1.101): 56 data bytes

--- 192.168.1.101 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
[root@JollaC2 defaultuser]# arping -I wlan0 192.168.1.101
ARPING 192.168.1.101 from 192.168.1.33 wlan0
Unicast reply from 192.168.1.101 [50:eb:f6:64:a3:58] 4.877ms
[root@JollaC2 defaultuser]# arping -I wlan0 192.168.1.1
ARPING 192.168.1.1 from 192.168.1.33 wlan0
Unicast reply from 192.168.1.1 [8c:f8:13:3c:8b:86] 12.324ms
[root@JollaC2 defaultuser]# tcpdump -i wlan0 -n icmp
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:21:01.353008 IP 192.168.1.34 > 192.168.1.33: ICMP echo request, id 19, seq 1, length 64
19:21:01.353274 IP 192.168.1.33 > 192.168.1.34: ICMP echo reply, id 19, seq 1, length 64
19:21:02.171933 IP 192.168.1.34 > 192.168.1.33: ICMP echo request, id 19, seq 2, length 64
19:21:02.172184 IP 192.168.1.33 > 192.168.1.34: ICMP echo reply, id 19, seq 2, length 64
19:21:03.196574 IP 192.168.1.34 > 192.168.1.33: ICMP echo request, id 19, seq 3, length 64
19:21:03.196819 IP 192.168.1.33 > 192.168.1.34: ICMP echo reply, id 19, seq 3, length 64
19:21:04.220402 IP 192.168.1.34 > 192.168.1.33: ICMP echo request, id 19, seq 4, length 64
19:21:04.220618 IP 192.168.1.33 > 192.168.1.34: ICMP echo reply, id 19, seq 4, length 64
19:21:50.716653 IP 192.168.1.33 > 192.168.1.101: ICMP echo request, id 10990, seq 0, length 64
19:21:51.717251 IP 192.168.1.33 > 192.168.1.101: ICMP echo request, id 10990, seq 1, length 64
19:21:52.717889 IP 192.168.1.33 > 192.168.1.101: ICMP echo request, id 10990, seq 2, length 64
19:21:53.718500 IP 192.168.1.33 > 192.168.1.101: ICMP echo request, id 10990, seq 3, length 64

arping -I wlan0 IP_router works

ping IP_router don’t work

ip neigh show dev wlan0 show router as RECHABLE

tcpdump -i wlan0 -n icmp show request echo for ping coming from C2 and show request and reply echo for ping coming from another PC. But no response in both cases.

I try to disable firewall :

iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
for t in filter nat mangle raw security; do iptables -t  $t -X;done

but no effect… I try some other thing too

Restart the phone restore the wifi.

PRECONDITIONS:

none

STEPS TO REPRODUCE:

  1. Connect to Wifi

  2. Wait problem appear

EXPECTED RESULT:

Wifi works

ACTUAL RESULT:

Wifi stop working

MODIFICATIONS:

Chum, storeman, aptoide. A lot of package.

ADDITIONAL INFORMATION:

1 Like
2

For me this happens when moving out of the Wifi reception area and when moving back, it doesn’t reconnect. One solution I found was to shortly enable flight-mode and disable it again. After that it will reconnect.

3

It don’t work for me… :frowning:

4

Restart network from settings might help also as a workaround.

5

I tried : rfkill, flight-mode (same as rfkill, probably), on/off WLAN, restart connman. Arping working suggest that hardware is ok. tcpdump receive echo, suggest that receive is OK. tcpdump sending echo request (but never received) suggest that blocking mechanism is somewhere between tcpdump layer and hardware. And just for emit. But what it is ?

6

I guess this can be linked to [C2]Phone falsely claims being on Wifi

2 Likes
7

Maybe linked. But a difference : My routers see the phone. I had again the problem 3 days ago. And none since.

Next time, i’ll test to remove driver from kernel and modprobe again.

8

This problem is known with all sailfish supported devices. On some more than others. I wonder how this could not be resolved for years and instead going from device to device…

9

I have this issue also with xz2 compact community-port. It seems it was introduced since a major connman update, somewhere after 4.5!?

10

I have this issue but also others. From time to time, my C2:

  • loses wifi connection
  • runs hot
  • discharges the battery very quickly.

From advice at Mainline Linux kernel for the Jolla C2 , I can fix this by charging the battery to full, shutting down (power button then icon), wait, start up without Android support, start my usual non-Android apps, wait, start Android support, wait, then start Meecast and Whatsapp. And hope that this is a good restart and the phone will run for more than a day.

This has been happening since late March when the phone was returned to me after reflashing. I’ve installed all the updates. The longest it’s run without these issues is 12 days; more often it fails after 7 days or less. I keep hoping the next software update will fix it…

Even when the battery is ok, I see the wifi issues noted above. On earlier phones, I used to toggle Flight mode to restore access. On this C2, flight mode never seems to return from ‘on’; instead, when I see there’s no connection (for instance, Meecast can’t update), I toggle WLAN off and on. But the heat-up battery-down occurs when I’m not using the phone. It can drop from around 90% to around 30% in an hour or two (2% overnight), very disconcerting.

Am I the only one seeing this? What can I do?

11

I have a remarkably similar problem with my Xperia 10 II. After first setting up the phone, everything is fine. But after a while (I don’t know what the exact prerequisites to trigger this fault) it does not connect at all anymore, or very slowly. The problem also exists on LTE. I tried to restart networking and restarting the phone. This also does not work. It has made the phone unusable for me in this state and I will try to reinstall the operating system next. Any help is very welcome!

12

Just about a blueprint copy from my experience. Yesterday I had the exact same experience during the night and my C2 where totally drained and switch off and hence no wake up alarm.

13

I have a C2 and a XPeria 10 II and the second one is not having this particular issue (it is sometimes a bit slow though but this is RAM-related and some optimisation not ….optimised); for the moment I am actually using the Xperia instead of the C2 as the wifi issue is bothering me too much (battery drain and no connection at times). So I think you could reflash your phone if you can as the problem described here seems to be restricted to C2

14

Sometimes, restart don’t work. But poweroff and on, works. It seems that reboot don’t make the same things that completely off. (Maybe cut power off wifi module ?).

Or maybe it’s just luck.

15

Similar issues reported at Are there still connectivity issues with C2?

which mentions ‘Jolla told in one of the community meetings that they have found solution for connectivity problems with C2‘. I do hope this is true

16

I should have edited that comment earlier… I miss remembered details about discussion and it was AAS related discussion