The ip associated to the mobile data can sometime be seen in Aida64, but in general stay up for less than 10 minutes, then I am not connected anymore (but the phone can receive calls, and sms works too). It is quite hard to stop the network device, but I can make it work with random actions like stopping the mobile data in the settings, then from the quick settings, then restart the network from the tools menu.
But again, it will works for a very short time.
The Sony is a test phone, as I am waiting for the third batch for the J2, if this is a know issue of this sony but it won’t be for the J2, then, for me, it’s fine. But if this is a know issue for all the phones using SFOS, then what can be done ?
I don’t remember that in any of my three diffrent SFOS phones.
I did notice strange issues back then before my mobile network provider did enable VoLTE.
So you also need to provide more details if you have 4G prefered and if VoLTE is and stays registered.
I have the same problem with my Xperia 10 IV, but only here on my home network in Austria (A1) after a restart. When I restart the smartphone while abroad, there’s no problem—until I cross the border, at which point it takes about 10 minutes before I go offline.
Other than disconnecting and reconnecting the data connection, I don’t know of any workaround.
I tried all kind of different settings: Prefered 5G, or Prefered 4G. Today I thought that maybe disabling VoLTE solved the issue, but it is not the case, disabled or enabled don’t change the issue. When enabled it stays registered.
Right now : VoLTE is enabled and reported as registered, I am in “Prefer 5G”, and the mobile data is reported as connected. But there is no ip reported in AIDA.
The ip a s command return that :
defaultuser@Xperia10IV ~]$ ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN gro
up default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qle
n 1000
link/ipip 0.0.0.0 brd 0.0.0.0
3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen
1000
link/gre 0.0.0.0 brd 0.0.0.0
4: gretap0@NONE: <BROADCAST,MULTICAST,DYNAMIC> mtu 1462 qdisc noop stat
e DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
5: erspan0@NONE: <BROADCAST,MULTICAST,DYNAMIC> mtu 1450 qdisc noop stat
e DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default q
len 1000
link/ipip 0.0.0.0 brd 0.0.0.0
7: ip6_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN group default
qlen 1000
link/tunnel6 :: brd ::
8: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen
1000
link/sit 0.0.0.0 brd 0.0.0.0
9: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default q
len 1000
link/tunnel6 :: brd ::
10: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop state DOWN group default
qlen 1000
link/gre6 :: brd ::
11: rmnet_ipa0: <UP,LOWER_UP> mtu 9216 qdisc pfifo_fast state UNKNOWN g
roup default qlen 1000
link/[519]
12: rmnet_data0@rmnet_ipa0: <> mtu 1500 qdisc mq state DOWN group defau
lt qlen 1000
link/[519]
13: rmnet_data1@rmnet_ipa0: <> mtu 1500 qdisc mq state DOWN group defau
lt qlen 1000
link/[519]
14: rmnet_data2@rmnet_ipa0: <> mtu 1500 qdisc mq state DOWN group defau
lt qlen 1000
link/[519]
15: rmnet_data3@rmnet_ipa0: <> mtu 1500 qdisc mq state DOWN group defau
lt qlen 1000
link/[519]
16: rmnet_data4@rmnet_ipa0: <> mtu 1500 qdisc noop state DOWN group def
ault qlen 1000
link/[519]
17: rmnet_data5@rmnet_ipa0: <> mtu 1500 qdisc noop state DOWN group def
ault qlen 1000
link/[519]
18: r_rmnet_data0@rmnet_ipa0: <> mtu 1500 qdisc noop state DOWN group d
efault qlen 1000
link/[519]
19: r_rmnet_data1@rmnet_ipa0: <> mtu 1500 qdisc noop state DOWN group d
efault qlen 1000
link/[519]
20: r_rmnet_data2@rmnet_ipa0: <> mtu 1500 qdisc noop state DOWN group d
efault qlen 1000
link/[519]
21: r_rmnet_data3@rmnet_ipa0: <> mtu 1500 qdisc noop state DOWN group d
efault qlen 1000
link/[519]
22: wlan0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc mq state DOWN g
roup default qlen 3000
link/ether 3c:38:f4:99:28:de brd ff:ff:ff:ff:ff:ff
23: p2p0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group de
fault qlen 3000
link/ether 3e:38:f4:99:28:de brd ff:ff:ff:ff:ff:ff
[defaultuser@Xperia10IV ~]$
Might be you need a reboot after setting the setting. I seem to recall sometimes it moves back. @mal, I seem to recall we once had a chat about this to get some parts reset correctly, with a whole bunch of reboots, and I’m quite sure your memory is better than mine on this topic.
Here is what I think : the network is “lost” after some times the screen is locked. If I make it work, and use the phone, then the network works fine, until I lock it and stop using it for a while.
I have noticed something, and maybe this is an issue with my provider, but :
it seems I can’t receive calls if VoLTE is not enabled (SMS works)
if VoLTE is registered, and I have an ip, then no issue
if VoLTE is registered, but I lost the IP, I can’t receive calls
As right now, I am using the Sony to check if I can using Sailfish as my main phone, and these are quite critical, can I assume this won’t be there on the J2 ? Or should I consider this could be an issue on any phone that can run Sailfish ?
Low level fumction of VoLTE is very device specific. I’m pretty sure that this part will be fine in J2. Operators VoLTE config are common. So it make sense to solved it if that is the problem. Did you already report a bug?
