You do know that MLS is not available anymore?
And tried more solutions documented here and on doc website?
Yes, but the devices are equipped with the “Global Positioning System”, and the software claims to support “Location” services.
So, I do find it strange that even when using:
a) fully functional devices
b) with the latest SFOS software
c) the latest and most highly regarded Mapping software
d) with every conceivable location service configured
That I have never in the history of four SFOS devices (X, 10ii (sons travel toys), XA2Plus, 10iii (my daily drivers), have I managed to get useful device tracking in mapping software working. Across ~six years of use.
Updating C2 went without a hitch. Thank you, Jolla, and Happy Easter!
That was my mistake (to put it short). As can be seen from the changelog, the same fixes went in both to AppSupport11 and AppSupport13. There were also audio-specific fixes in files common for both AppSupport generations.
Please test thew audio fixes with Xperia 10 III (AppSupport11).
I can’t comment on that but I used navigation with XA2, X, X 10 and C2. Yeah, I had to be patient sometimes. But lately it’s great for me.
I’m pretty sure I not the only one.
The OTA update on the C2 doesnt work. After reboiting it says uodate failed try agsin later.
What should I do? Afaik there is no factory reset button on the C2.
The file
/var/log/systemupdate.log
may contain a hint on what went wrong with the update.
Thank you very much @duvi
I took me only one second attempt since you posted your solution before. Have a great Eastern.
And thanks to Jolla for another update. Great to see you still going strong after all these years.
You mention the 10 III, that’s the phone I use too, I’ve never had GPS issues with that; Pure Maps, Sygic, GPSinfo and anything else using the location chip works flawlessly.
Because Puremaps is slow for me to search a destination, I often already set it up before I leave, put it in the car holder, and within minute (usually within 30 seconds) it will have a fix.
I got back on SFOS since 4.5, upgraded through every (pre)release and it’s always worked.
Years back on the Fairphone 2 it’s always worked as well.
I have no sources for this but I remember Jolla’s “promises” about updating App Support for Xperia X.
Seems like 5.0.0.62 vil be a “stop release” for my 10III … until an useful version for my 10V has been made, so it can be my private phone. Here after I can install the latest sfos on my 10III from scratch.
The 5.0.0.67 the latest version does not correct the bug with audio via the usb port for the Xperia 10 iii
Sony Xperia 10 v updated to .67 fine, but my 10 iii (on .62) would not update. Tried 3 times, waiting for 10 mins before entering the security code, but no luck. Guess I’m stuck on .62 on this phone if I don’t want to do a painful reflash and reload of everything.
Update went swimmingly on Xperia 10 II. Confirmed that Wireguard connection now works when using FQDN. Thanks for your hard work & happy easter!
What phone do you have?seems like on the xa2 wireguard make my phone reboot…
The same here. Only on Jolla 1 I could use satnav Here flawlessly.
5.0.0.67: since updating Thu late night, in 2 days I’ve seen AppSupport itself disappear at least twice, of which one resulted in an unrecoverable AppSupport restart-loop until a reboot.
This rarely if ever happened in earlier releases: individual apps would get killed, but never AppSupport itself.
Quoting LMK because it’s my primary hypothesis for what might be involved. Anyone else seeing weirdness with Android behavior now?
I do get a ring tone even though people are already answering my call.