I will try to flash back to version 4.4.0.64 tomorrow.
If the IPv4 mobile data connection works in SFOS 4.4.0.64, there is probably a new bug in version 4.4.0.68.
Had with 4.4.0.64 the same issue.
1 Like
Have you tried flashing from Android 62.0.A.3.109 to SFOS 4.4.0.64?
The first two times I flashed SFOS 4.4.0.64 I was on Android 62.0.A.9.11. Both times the IPv4 mobile data connection under SFOS did not work.
Only when I flashed to Android 62.0.A.3.109 and then to SFOS 4.4.0.64 did the IPv4 mobile data connection work.
After today’s update to 4.4.0.68, the IPv4 mobile data connection no longer works.
Maybe just a coincidence, but I’ll test it again tomorrow with SFOS 4.4.0.64.
Yes and try the same with 4.4.0.68
Weird, I had the opposite experience:
- installed Sailfish ontop of which ever Android 11 / 62.0.A.3.xx was out-of-the-box, and got troubles with connection, mostly when roaming abroad (stuck at “2G” level, and unreachable network)
- flashing Android 11 / 62.0.A.9.11, running the checklist (including testing internet connection), then reflashing Sailfish OS from a
ddbackup, solved the problem for me.
I still needed to systemctl restart ofono.service every now and then when losing the connection, but eventually it’s stable now (some OTA update downloaded by the modem’s firwmare or the SIM itself and stored on one of the zillion Android partitions?).
Temporarily the same here.
I don’t remember if it was the “keep the 2nd SIM slot turned on” tick or simply forcing connection with systemctl restart ofono (or even more trivially: the SIM or modem firmware doing their own thing and fetching some OTA update for themselves).
But eventually it resolved, I have 4G connectino while roaming abroad again.
I flashed SFOS version 4.4.0.64 and also version 4.4.0.68 several times without flashing back to Android.
I could not get the mobile IPv4 internet connection to work.
Interestingly, there were different behaviors.
Sometimes I didn’t get an IPv4 address at all.
ofono: 0x93c22e0 DUAL no IPv4 address set
(see log in bug report)
After the next flashing, I got an IPv4 address and the route was entered correctly, but no internet connection was possible.
[root@Xperia10III defaultuser]# ifconfig
...
rmnet_data0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.28.99.243 Mask:255.255.255.248
inet6 addr: fe80::f972:149c:9c45:5c3a/64 Scope:Link
inet6 addr: 2a01:59f:918b:7360:f972:149c:9c45:5c3a/64 Scope:Global
...
[root@Xperia10III defaultuser]# ip -4 route | grep default & ip -6 route | grep default
default via fe80::2091:ad45:2f36:5d45 dev rmnet_data0 proto ra metric 1024 expires 65509sec
default via 10.28.99.244 dev rmnet_data0
[root@Xperia10III defaultuser]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
--- 8.8.8.8 ping statistics ---
24 packets transmitted, 0 packets received, 100% packet loss
I also tried the SIM switch, but in slot 2 my SIM card doesn’t work at all at first.
The SIM was recognized and the PIN was requested, but no connection could be established.
Neither telephony nor data (network search runs forever).
After further flash attempts, the card worked in Slot 2, but also without an IPv4 connection.
Also I tried restarting ofono but that didn’t change anything.
Only after I flashed Android 62.0.A.3.109 again with Emma, tested the IPv4 connection and flashed SFOS 4.4.0.64 from there did I have an IPv4 internet connection again.
[root@Xperia10III defaultuser]# ifconfig
...
rmnet_data1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.46.151.212 Mask:255.255.255.248
inet6 addr: 2a01:598:a902:10bb:40e1:52ba:9bdc:36bc/64 Scope:Global
inet6 addr: fe80::40e1:52ba:9bdc:36bc/64 Scope:Link
...
[root@Xperia10III defaultuser]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=112 time=198.151 ms
64 bytes from 8.8.8.8: seq=1 ttl=112 time=37.438 ms
64 bytes from 8.8.8.8: seq=2 ttl=112 time=27.022 ms
64 bytes from 8.8.8.8: seq=3 ttl=112 time=27.786 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 27.022/72.599/198.151 ms
Then I made an update to SFOS 4.4.0.68 via the GUI and after that no IPv4 connection is possible anymore.
ofono: 0x9a07b70 DUAL no IPv4 address set
(see log in bug report)
Maybe i have to Flash Android 62.0.A.3.109 again with Emma and then directly SFOS 4.4.0.68?
Maybe i need another Android Baseband Version for SFOS 4.4.0.68?
Maybe there is a bug in SFOS 4.4.0.68?
Does anyone have a hint?
I gave it one more try and it worked for me as follows:
I flashed Android 62.0.A.3.109 again with Emma,
tested the IPv4 connection on Android,
flashed directly to SFOS 4.4.0.68.
[root@Xperia10III defaultuser]# version
Sailfish OS 4.4.0.68 (Vanha Rauma)
[root@Xperia10III defaultuser]# ip -4 route | grep default & ip -6 route | grep default
default via 10.120.51.105 dev rmnet_data2
default via fe80::998d:4125:59b0:fe29 dev rmnet_data2 proto ra metric 1024 expires 65174sec hoplimit 255
[root@Xperia10III defaultuser]# ping -4 dns.google.com
PING dns.google.com (8.8.4.4): 56 data bytes
64 bytes from 8.8.4.4: seq=0 ttl=112 time=26.221 ms
64 bytes from 8.8.4.4: seq=1 ttl=112 time=25.940 ms
64 bytes from 8.8.4.4: seq=2 ttl=112 time=30.579 ms
^C
--- dns.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 25.940/27.580/30.579 ms
Maybe just until the next update?
On my phone it doesn’t work with flashing Android 11, testing ip4 and than flashing SFOS
I followed exactly the described procedure but it doesn’t work for me neither! In consequence no telegram usage is possible over mobile network because telegram seems to rely on IPV4. Android app firefox instead works.
Edit: This thread could(!) be a double post / duplicate to Unable to use mobile data on Sony Xperia 10 III 4.4.0.64 - #49 by akikyo
Edit: … or [4.4.0.64][Xperia 10 III}VoLTE conflicts with mobile data
After a few days with no IPv4 issues, I decided to turn on VOLTE.
But VOLTE could not be registered. I knew it had worked on 4.4.0.64 so I rebooted the phone.
After restart, VOLTE was successfully registered, but since then IPv4 mobile connection again, is no longer possible.
Jul 24 16:17:39 Xperia10III connmand[5336]: ofono: 0x6a0b370 DUAL no IPv4 address set
I switched the SIM to Slot 2 and there i have my ipv4 back again.
But no matter what I try in slot 2, VOLTE cannot register.
I also need the SD card and who knows how long it will work in slot 2.
Therefore, it is not a permanent solution for me to occupy slot 2 with the SIM card.
Since this doesn’t work for others either, I no longer believe that flashing to Android 62.0.A.3.109 is really the solution.
The fact that it worked for me twice can’t be a coincidence either.
But I’m slowly running out of ideas and would be grateful for any hints as to what else I could try.
PS: Could someone with proper rights please remove the ‘fixed’ tag
I’ve the same problem. Updated to 4.4.0.68 and my IPv4 adress is gone when using mobile data. Sim Slot 2 only asks for PIN but never connects.
Seems i have to reflash again…
I also think it is not relate to the flashed Android base. I never got an ipv4 adress with .109. It worked with an even older Android version once, but after updating to 4.4.0.68 ipv4 was one an also hotspot functionality. Now im tired of reflashing until it works. hopefully Jolla fixes this in the next update.
1 Like
I’m also tired of re-flashing over and over again just to get it working for a short time.
At least I’m not the only one with this problem.
I think it affects far more users, but unless they rely on pure IPv4 services, they usually won’t even notice the problem.
However, I am afraid that as long as only a few users notice and report this problem, it will not be taken seriously enough.
When using sim slot2 i’ll get an IPv4 adress, but VoLTE is failing and i can’t connect to the net.
Have the same problem now.
After i deactivated SIM slot 1, only limited connection with mobile data on slot 2.
IPv4 and IPv6 address is assigned, but no internet connection possible.
[root@Xperia10III defaultuser]# ifconfig
...
rmnet_data1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.25.152.250 Mask:255.255.255.252
inet6 addr: fe80::b05d:a509:8007:1ea/64 Scope:Link
inet6 addr: 2a01:59f:a810:a080:b05d:a509:8007:1ea/64 Scope:Global
UP RUNNING MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1272 (1.2 KiB) TX bytes:15956 (15.5 KiB)
...
[root@Xperia10III defaultuser]# ip -4 route | grep default & ip -6 route | grep default
default via 10.25.152.249 dev rmnet_data1
default via fe80::bd9e:6812:c963:e4cb dev rmnet_data1 proto ra metric 1024 expires 65487sec
[root@Xperia10III defaultuser]# ping -4 dns.google.com
ping: bad address 'dns.google.com'
[root@Xperia10III defaultuser]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
--- 8.8.8.8 ping statistics ---
27 packets transmitted, 0 packets received, 100% packet loss
[root@Xperia10III defaultuser]# ping -6 dns.google.com
ping: bad address 'dns.google.com'
[root@Xperia10III defaultuser]# ping 2001:4860:4860::8888
PING 2001:4860:4860::8888 (2001:4860:4860::8888): 56 data bytes
--- 2001:4860:4860::8888 ping statistics ---
21 packets transmitted, 0 packets received, 100% packet loss
Unfortunately, reactivating slot 1 doesn’t help.
After hours of testing, the only certain result is that sooner or later the mobile data connection will stop working properly or break off completely.
The mobile internet is currently not working at all for me when using SIM slot 2.
Although an IPv4 and an IPv6 address have been assigned, “limited connectivity” is displayed under “Mobile network” and the mobile Internet does not work. See above
I experimented a bit more and found the following workaround for using mobile internet with SIM slot 2:
By switching the network mode to “2G only”, the connection is re-established and “Connected” is now displayed under “Mobile network”.
If you then switch back to the “4G preferred” network mode, the mobile data connection remains “Connected” and the mobile Internet connection works correctly with 4G.
When connecting to a WLAN, the mobile data connection is disconnected as expected. After logging out of the WLAN, the mobile data connection is correctly established again.
So far so good, but unfortunately after restarting the phone or after toggling the flight mode, the previous problem reoccurs and the above process has to be repeated.
And of course VOLTE still doesn’t work with SIM slot 2.
But better than nothing and finally a reproducible behavior.
However, this trick does not help with the actual problem with SIM slot 1 (no IPv4 mobile data connection).
Thanks, @senders for the interesting reporting and for the suggestion for a procedure IPv4 mobile data connection not possible - #2 by senders which I attempted to execute, but with 4.4.0.68, not with 4.4.0.64. While it did not work for me on SFOS I managed to make IPv4 work on Android 11 / Xperia 10 III, albeit it did not work out of the box on Android, either, with my operator’s SIM.
The default APN (Access Point Name) settings on Sony’s Android 11 were :
- APN Protocol = IPv6
- APN Roaming Protocol = IPv4
I am not sure has my operator communicated to these values to Sony or to Google, or both but these values are not the same as my operator promotes on their configuration help pages.
Interestingly, the default set of parameters is not editable in Sony Android 11’s Network & internet → Mobile network → Advanced → Access Point Names. There was another ASN profile, for the professional clients of the operators, in which the above settings were:
- APN Protocol = IPv4
- APN Roaming Protocol = IPv4
(For good reason, since in professional usage VPN connection is often requested and the VPNs - that I know - use IPv4. Even a dual protocol IPv4/IPv6 support that SFOS suggests by default, would just create a leak of IPv6 in case the VPN software cannot turn it off.)
In the contrary to the SFOS, Sony Android 11 allows to create a new APN profile in the above menu, and it was possible for me to set a new profile using the values from the help pages of my operators. Not surprisingly, the values on the self-help page are, for APN:
- APN Protocol = IPv4
- APN Roaming Protocol = IPv4
After activating the newly created profile, Sony Android 11 installation started to work as I expected, also with the VPN and with the sites with non-public, fixed IPv4 IP-addresses.
After a couple of reboot and re-testing of this Emma flashed Sony Android 11 62.0.A.3.109 all remains good and I attempted to flash (again, yes, it is tiresome to spend one’s life doing this).SFOS 4.4.0.68.
Of course, it did not work, and even it was still claiming the APN Protocol being “Dual” (i.e. IPv4/IPv6): no change in this parameter changed anything: ip -4 route remains, desperately empty.
There is no mention about the APN Roaming Protocol in SFOS.
I can understand that Jolla is interested in recovering Google/Android/Sony knowledge about different operator’s settings, bur frankly, the sheer idea of having dependency for this on an underlaying Android installation is on a quite slippery surface what comes to the configuration control:
At least, Jolla should provide a full power APN profile viewer and editor/creator like Sony Android 11 is providing. Now we are shooting in the dark.
You are also right, @senders that probably not enough interest is generated to highlight this issue, since for most people the IPv6-only works and it may go unnoticed for the majority of people that they do not have IPv4 on mobile data, only on WiFi.
But if Jolla is claiming that they are strictly security oriented, they should make IPv4 APN protocol working for all and provide a way to suppress IPv6 altogether.
Unless they can make all the VPN providers to switch to IPv6 tomorrow.
2 Likes
Yesterday i reflashed Android12 and SFOS about a dozen times, with no luck. I only once got my IPv4 address back and this was gone after a reboot.
Maybe Jolla get this fixed.
2 Likes
Thanks to @PeegeeTips, various mobile data issues will be addressed at the next community meeting.
This bug report is also mentioned in the topic description.
Hopefully this helps draw more attention to this issue.
PS: Could someone with the appropriate rights please remove the ‘fixed’ tag which I sadly set prematurely.
Or forward the request accordingly? Maybe @pherjung
4 Likes
Are all Xperias concerned? I can confirm this bug for a Congstar SIM in both, a Xperia ii and Xperia iii, both running 4.4.0.68. Both do not have any connection problems with a Vodafone SIM. I have not tried the XA2 yet, but will do so tonight.
1 Like