Help: IPv4 on mobile data Sony Xperia 10 III 4.4.0.68 Vanha Rauma

General
#1

Update 2022-08-15: Please read this bug report:

My experience, for the record (I first thought this was only about my VPNs not working):

Migrating from Sony Xperia 10 4.4.0.68 (Vanha Rauma) Device adaptation 0.0.6.3.0 installed 2020-08-04, updated with each new SFOS version since, to :

Sony Xperia 10 III 4.4.0.68 (Vanha Rauma) Device adaptation 1.0.0.142 installed 2022-08-12 following strictly the Jolla procedure (this includes checks w/ Android 11 and downloading Sony image SW_binaries_for_Xperia_Android_11_4.19.v9_lena). After the installation, backup from SD card was restored.

On Sony Xperia 10 III, VPN supplier provided .udp.ovpn files are installing without (visible) warnings.

The VPNs are not connecting on mobile data on Sony Xperia 10 III. They have been and are still working fine on Sony Xperia 10 (w/ same SIM), Sony Xperia 10 III has only one SIM and a SD card.

The VPNs are connecting OK on WiFi on both phones.

Settings → Cellular Network → Data access point → Protocol = Dual on both phones. I have tried IP and IPv6 alone. No effect in this problem but they give new connectivity problems. Set back to defaults on both phones.

I do not have other ISP’s SIM cards available for testing.

An observation - perhaps related - in application jolla-mediaplayer 1.3.1.1-1.6.1.jolla on Sony Xperia 10 III :

My playlist have streaming radio stations. Those with URL is http://77.86… do not work, those with https://stream… do work when on mobile data; On Sony Xperia 10 both do work on mobile data with the same media player version. On both phones the radio stations are all streaming fine when connected with WiFi. Common with the .udp.ovpn files is the usage of IP-addresses, not FQNs when failure occurs.

#2

The common nominator is IPv4 IP-addresses. Looks that IPv4 is missing on Xperia 10 III when on mobile data:

On Xperia 10:

  [nemo@Xperia10 ~]$ ip -4 route
    default via 10.45.xxx.94 dev rmnet_data0
    10.45.xxx.92/30 dev rmnet_data0  proto kernel  scope link  src
    10.45.xxx.93
    10.45.xxx.94 dev rmnet_data0  scope link
    192.168.10.110 via 10.45.xxx.94 dev rmnet_data0
    [nemo@Xperia10 ~]$ ip -6 route
    fe80::/64 dev rmnet_data0  proto kernel  metric 256

On Xperia 10 III:

    root@Jolla10III defaultuser]# ip -4 route
    [root@Jolla10III defaultuser]# ip -6 route
    ::1 dev lo  proto kernel  metric 256
    2a01:cb16:xx:9f04::/64 dev rmnet_data1  proto kernel  metric 256
    2a01:cdxx:7fff:0:192:168:10:110 via fe80::c80:76xx:49d9:c73e dev rmnet_data1  metric 1 onlink
    fe80::c80:76xx:4xx9:c73e dev rmnet_data1  metric 1 onlink
    fe80::/64 dev rmnet_data0  proto kernel  metric 256
    fe80::/64 dev rmnet_data1  proto kernel  metric 256
    default via fe80::c80:76xx:4xx9:c73e dev rmnet_data1  metric 1024

Dual port for Protocol is activated (see above). Is this a “feature” or a bug? How to get IPv4 on Xperia 10 III?

#3

I just tested ip v4 with my Xperia 10III, 4.4.0.68, Vodafone Germany.

Bildschirmfoto_20220814_001

VPN over ip v4 also works.

Maybe there is an issue with your provider?

#4

And welcome to the show:

#5

Thanks WT.Sane for the valuable feedback: Indeed it is depending of your service provider as we can observe from the link in the above message.

#6

Thanks @miau for the link. I did not find it since I thought the problem was only with VPN originally. Sorry for a double ticket, I’ll link back.

Looks quite frightening, with reflashing etc. :cold_face:

Being done this regularly since the Jolla First One, I guess that from now on I will spend my Sundays more wisely and continue to use Xperia 10 until the III receives a bug fix for mobile IPv4 :pray: .