I just had the opportunity to test 5.1.0.11 in very poor network conditions. Once 4G was lost it mostly did not help to restart cell phone services, network or just turn flight mode on and off. I had to reboot the phone completely some times to get reconnected to 4G. Once the phone got offline it even had problems to connect to WiFi.
btw Cisco WPA3 did not seem to work.
Edit 20260704: In urban conditions everything is an was fine.
Iâve adapted the same patches as the merge-request above:
I just upgraded to 5.1.0.11, but now my Xperia XA2 single SIM wonât connect to the cellular network anymore. The ofono service keeps crashing.
From journalctl:
Jul 03 07:28:11 XperiaXA2 systemd[1]: Started Telephony service.
Jul 03 07:28:11 XperiaXA2 ofonod[4283]: [gbinder-radio] Connected to android.hardware.radio@1.1::IRadio/slo
t1
Jul 03 07:28:11 XperiaXA2 ofonod[4283]: slot1 version 101
Jul 03 07:28:11 XperiaXA2 ofonod[4283]: SIM card OK
Jul 03 07:28:11 XperiaXA2 ofonod[4283]: Requested file structure differs from SIM: 6fb7
Jul 03 07:28:11 XperiaXA2 ofonod[4283]: Open logical channel failure: MISSING_RESOURCE
Jul 03 07:28:11 XperiaXA2 systemd[1]: ofono.service: Main process exited, code=killed, status=11/SEGV
I had trouble with crashing ofono in the 5.0 version too, but it would eventually start and stay stable, but now it crashes immediately 100% of the time.
Any advice?
It might help if you disable SIM PIN.
Thanks, but I donât have it enabled. At least, I donât get asked for anything other then my decryption code for the OS.
Restarting ofono helps?
No unfortunately not. Itâs always the same error. I tried multiple times from the settings but also from the terminal with systemctl restart ofono. I rebooted my phone at least five times too for good measure.
Huh, it seems to have worked on the 56th (or thereabouts) restart of ofono. Hope it sticks!
Buetooth poroblem, XA2+ dualsim. After updating to Pispala 5.1.0.11, my good old BMW e61 connects with the phone but can not enter the phonebook (phoneâs contacts) any more. Seems like its trying when showing on the screen âUpdating phonebookâ and the spinning wheel for about half a minute. Before it worked fine. A call from the car system can be done only by selecting numbers using carâs selector. I removed pairing and did the pairing again but no help. Has anybody else faced similar?
I suppose you did but in doubt:
Did you allow contact sharing in AAS settings?
Perhaps this help you:
systemctl --user restart obex
That solved the problem! Thank you so much @haf-med, you made my day!!!
@ric9k thank you for respose. Contact sharing is allowed in AAS, This car is that much old that I donât think the phone system has anything to do with android. The carâs my bluetooth connection history sofar: Nokia N9, J1, XPERIA X, XA2+. All worked fine. till update 5.1.0.11.
Can confirm the work around: Press Power Button helps to get Xperia XA2 to switch from flight modus on to off.
on a different topic: I am totally missing Android support after installing freshly purchased new license for Pispala 5.1 on new Xperia III device. Also Android support is unavailable from the store.jolla.com when I try. what is going on with missing support? what is the point of selling 5.1 at all if android support is not there?
It is there.
It will be in the Jolla Store after you registered your phone.
thanks for reply, do you know how do I check that my phone got registered with jolla correctly? I never had to register any phone and this is 5th one (license) which I purchase for the 5th device. I have over the years 4 jolla devices and never had to deal with manual registration of the phone.
He means login to the phone with your Jolla account (Settings- Account). Note that one license is usually tied to one phone.
Go to: Jolla | Login
Check if thereâs your Xperia 10iii is listed
in the left Model column there should bexqbt52 and in the IMEI column there should be the exact one from your phone (use the Settings app, on the System pane, in the last section info click on About product, IMEI are listed here, the first one should be also in the devices page).
thank you for the answer. Yes, the new phone IMEI is properly registered with yestarayâs activation date. there must be something else going on. I have opened a support ticket with jolla.zendesk.com hopefully they come up with the answer. Interesting that during ticket opening, there was a question about OS version and drop down list of SFOS doesnât have 5.1 version, it ends with 5.0.78. So does it mean that Jolla is not supporting 5.1 on the Xperia 10iii? If so that would explain the missing android support, but that would still raise the question, why do they sell the license for it and allow the 5.1 download for X10iii at all?