I think I fund solution. I have problem with MMS after switching SIM cards between XA2 and 10III. Chat GPT told me to log in to another network provider. Of course login failed but i try to do this to all visible providers. After that I log in to my provider and then my Volte was marked as “registered”. MMS wasn’t work, but filling proxy adres and port fix this. At one time I have two problems solved ![]()
That’s only a solution to your MMS issue, not VoLTE and 5G ![]()
But Volte work now. Earlier doesn’t. Flashed on Android 13 and Jolla recommended binaries for 11
Wladi, Which provider?
Play Poland. Work after reboot, so looks like problem solved.
AFAICT, @andyestmoi, when looking at the SEA firmware 5G is disabled for Vietnam (I assume because Sony don’t support the Xperia 10 III there). This was taken using the QPST EFS Explorer which tells the system to disable the 5G bands when on a Vietnam network:
</rf_band_list>
<rf_band_list ns="global" name="apac_452_b">
<gw_bands base="hardware"/>
<lte_bands base="none">
<include>0 2 6</include>
</lte_bands>
<tds_bands base="none"/>
<nr5g_sa_bands base="none" />
<!--Because Sagami don't have a plan to support RID012137 at RTL/MR timing before S-OSV. Lena need to follow Sagami. -->
<nr5g_nsa_bands base="none"/>
</rf_band_list>
This is what the global setup looks like (though no countries are set to it):
<rf_band_list ns="global" name="default_b">
<gw_bands base="hardware"/>
<lte_bands base="none">
<!-- A2 Support LTE band 1,3,4,5,7,8,20,28,38,39,40,41 -->
<include>0 2 3 4 6 7 19 27 37 38 39 40</include>
</lte_bands>
<tds_bands base="none"/>
<nr5g_sa_bands base="none" />
<nr5g_nsa_bands base ="none">
<!-- A2 Support 5G band n1,n3,n7,n8,n28,n77,n78 -->
<include>0 2 6 7 27 76 77</include>
</nr5g_nsa_bands>
</rf_band_list>
You can see in the Vietnam rf_band_list (apac_452_b) that there aren’t any included bands for 5G (nr5g).
Based on this information, my assumption is that 5G didn’t work when your Xperia 10 III was running Android, is that correct? I’d be really surprised if it was! Sorry to bring the bad news.
Side note - I have managed to resolve this 5G issue in NZ where the 5G bands are also disabled (get it working), but I can only do it in Android, not sailfish.
No, not at all, from the previous time I reflashed sailfishos, 5G signal worked fine on android, but this status somehow disappeared on sailfish.
Interesting! That’s makes this all so much more painful to understand. I wonder why 5G was working for you when the modem suggests otherwise. I’d be curious to know what variant it is (if you happen to know), such as SEA, HK, EEA etc.
I believe that it is SEA variant.
I had another look and you’re right (not that I need to tell you that, haha). Here is a dump from the Android 13 SEA modem (Band 78 is supported):
<!--viettel_vn_p vinaphone_vn_p lte: 1 3 5g: n78-->
<rf_band_list ns="global" name="viettel_vinaphone_vn_b">
<gw_bands base="hardware"/>
<lte_bands base="none">
<include>0 2</include>
</lte_bands>
<tds_bands base="none"/>
<nr5g_sa_bands base="none"/>
<nr5g_nsa_bands base ="none">
<include>77</include>
</nr5g_nsa_bands>
</rf_band_list>
While this may not help you, it was mentioned that, after Sailfish 5.0.0.58, 5G stopped working: [Xperia 10 III][5.1.0.11] oFono SEGV crash and 5G NSA attach failure with Iliad (regression)
I can’t tell you where you could find a 5.0.0.58 image to test it. I’d be curious if this is your issue with 5G