[Xperia 10 III][5.1.0.11] oFono SEGV crash and 5G NSA attach failure with Iliad (regression)

[zioamer]

REPRODUCIBILITY: 100% in single‑SIM mode, 100% NSA failure in dual‑SIM mode
OS VERSION: 5.1.0.11
HARDWARE: Xperia 10 III (XQ‑BT52)
UI LANGUAGE: Italian
REGRESSION: Yes, 5G NSA worked correctly on 5.0.0.58

DESCRIPTION:

On Xperia 10 III running Sailfish OS 5.1.0.11, using only one SIM (Iliad Italy) and enabling “Prefer 5G” causes oFono to crash with SEGV and restart.
After the crash, the device registers only in LTE and never completes a 5G NSA attach.
In dual‑SIM mode, oFono does not crash, but 5G NSA still fails (continuous 4G/5G fallback loop).
This behaviour is a regression: on Sailfish OS 5.0.0.58, 5G NSA with Iliad worked correctly and no oFono crashes occurred.

PRECONDITIONS:

• Device flashed starting from Android 11 (recommended base)
• Only one SIM inserted (Iliad Italy)
• Network mode set to “Prefer 5G”
• Device freshly booted and PIN entered

STEPS TO REPRODUCE:

1. Power off the device

2. Insert only one SIM (Iliad Italy)

3. Boot the device

4. Enter SIM PIN

5. Set network mode to “Prefer 5G”

6. Observe network behaviour

7. Run:
   journalctl -u ofono -f

8. (Optional) Restart oFono to trigger the crash immediately:
   systemctl restart ofono

EXPECTED RESULT:

• oFono should not crash
• Device should remain registered
• 5G NSA attach should succeed (as in 5.0.0.58)
• No fallback loops
• Single‑SIM and dual‑SIM modes should behave consistently

ACTUAL RESULT:

Single‑SIM mode (Iliad only):

• oFono crashes with segmentation fault:
  ofono.service: Main process exited, code=killed, status=11/SEGV
• Service restarts automatically
• LTE registration succeeds
• 5G NSA attach is never completed
  Dual‑SIM mode:
• No SEGV crash observed
• 5G NSA attach still fails
• Device repeatedly falls back from 5G to 4G (blinking behaviour)

MODIFICATIONS:

No patches, no custom repositories, no Waydroid.
Clean installation of Sailfish OS 5.1.0.11 over Android 11 base.

ADDITIONAL INFORMATION:

Relevant log excerpt:
ofono.service: Main process exited, code=killed, status=11/SEGV
ofono.service: Failed with result ‘signal’.
Starting Telephony service…
ofonod[14871]: oFono version 1.29
data reg changed 2 → 1 (registered), attached 0
Activating context: 1
setting up data call

• Issue appears only with Iliad Italy (5G NSA EN‑DC configuration)
• Other operators with simpler NSA profiles may not trigger the crash
• Regression likely related to oFono 1.29 + Xperia 10 III radio HAL + single‑SIM initialization
• Dual‑SIM mode avoids the crash but still fails NSA attach
• 5G NSA worked correctly on Sailfish OS 5.0.0.58

[zioamer]

Additional details (Xperia 10 III + Iliad Italy):
I tested the issue by reflashing different Android bases and reinstalling Sailfish OS 5.0.0.71 each time:

-Android 11 - Sailfish 5.0 - 5G NSA still fails (5G icon blinks, fallback to LTE).

-Android 12 - Sailfish 5.0 - same behaviour.

-Android 13 (clean flash) - 5G NSA works perfectly in all tested Iliad locations (Milan city centre).

After flashing Android 13 - Sailfish 5.0 again -
LTE/4G+ and dual‑SIM behaviour are now fully stable, but 5G NSA still never attaches.

This confirms:

-The modem firmware and SIM are working correctly (Android 13 proves it).

-The issue is not related to Android base version.

-The problem appears only on Sailfish OS, both 5.0 and 5.1.

-The device sees the 5G carrier, but NSA attach never completes.

Context:
Iliad Italy updated its 5G network (NSA/SA core upgrade) at the end of April 2026:

https://tariffe.segugio.it/news-tariffe/5g-standalone-anche-per-iliad-cosa-cambia-per-nuovi-e-gia-clienti-00046395.aspx

Since this network update:

-Android 13 attaches to 5G NSA immediately

-Sailfish OS fails NSA attach consistently

-The 5G icon blinks but never completes ENDC setup

-LTE/4G+ works perfectly

Conclusion:
This suggests that oFono’s NSA attach parameters need to be updated to match Iliad’s new NSA configuration.

[crun]

So are you the only one using 5G, and the the only one who knows/thinks that A13 is needed?
Are you having any other issues with using A13 as the base for SF? (e.g. camera, bt, echo ?)

[crun]

Can you clarify:
In the bug report you imply it is working using A11 base, SF 5.0.0.58.
In the most recent post, you specify that 5G only works using A13 base, SF 5.0 (using 5.0.0.71)

[zioamer]

Thanks crun, here are the clarifications for both of your questions:

Before Iliad’s 5G NSA/SA core upgrade (end of April 2026), NSA attach worked on Android 11 and Sailfish 5.0.0.58.

After the upgrade, the behaviour changed even on Android:

A11 base:
-SIM1 sometimes saw 5G but NSA attach always failed
-SIM2 had major issues (no data, unstable registration)
-dual‑SIM behaviour broken
Android 11 is no longer usable with Iliad’s current NSA configuration.

A12 base
-Same issues as Android 11
-NR sometimes appeared but NSA attach never completed
-SIM2 unusable, data unstable

A13 base
-5G NSA attaches immediately and works perfectly
-dual‑SIM works normally
-data stable
This proves the modem fw + Iliad’s new NSA configuration are fully compatible.

Sailfish inherits the modem state from the Android base:

On Android 11 and 12 bases, Sailfish also had:
-unstable data
-SIM2 issues
-NR appearing briefly but NSA attach failing
-dual‑SIM instability

Only Android 13 and Sailfish 5.0 gives:
-stable LTE/4G
-stable dual‑SIM
-regular NSA attach attempts (NR appears briefly)
-but NSA attach still fails inside Sailfish/oFono

Android 13 is not required by Sailfish, but it is the only base that restores correct modem behaviour after Iliad’s network upgrade.

Other issues with Android 13 base:
-Camera: mostly fine, only minor issue: night flash photos sometimes have a slight blue tint.

Bluetooth: works normally.

Echo: sometimes present, sometimes not, same behaviour as Android 11/12 bases.

Dual‑SIM: now perfect after Android 13, Sailfish reinstall.

The modem sees the 5G NR cell (NR appears briefly)

ENDC attach is attempted but rejected by the network

Sailfish/ofono never completes NSA attach

A13 attaches immediately in the same location

This suggests that ofono’s NSA attach parameters need to be updated for Iliad’s new NSA configuration.

[zioamer]

Quick update.

I decided to test Sailfish 5.1.0.11, and unfortunately the same LTE issue came back immediately (signal stuck at one bar, unstable behaviour). After over five years of using this Xperia 10 III, first with Android and then with Sailfish, the hardware is no longer in good condition (display ghosting, etc.). For now I’ve decided to keep it on the last stable version that works for me (5.0.0.71) and wait for future updates. I’m also considering moving to a new device soon, maybe the Xperia 10 IV or the 10 V once it becomes more stable.I’ll leave this thread here in case the information helps other users or future ofono updates.

LTE signal stuck at one bar on 5.1.0.11

[miau]

The LTE signal stuck at one bar was introduced in one of the 5 0.x updates, when they changed the behavior of the bar. For me ts always one bar and everything is fine.

Really low signal strength on 5.0.0.73

REPRODUCIBILITY: 100 OS VERSION: 5.0.0.73 HARDWARE: X10 III UI LANGUAGE: EN REGRESSION: Yes DESCRIPTION: Phone reports really weak 4G signal strength compared to the previous version 5.0.0.72 Now at working place Espoo keilaranta, using Elisa 4G reports RSSI 2% and Cell RSSI 59%. Speed is fine, speed test gives something like 90/40Mbps so I suspect that reported values are not correct. Home at Helsinki reported value is better ~75% but it used to be almost maximum before update. PRECONDI…

[zioamer]

Thanks! In my case it wasn’t only the cosmetic one‑bar issue. Even outside the modem stayed locked on Band 7 with just one bar, when it normally shows full signal on 5.0.0.71. And in the Milan underground the signal went up, but it still remained stuck on Band 7. So it seems to be a different issue.