A list is here: Supported Devices
Looks like they have tested with / want users to have Android 13 on the 10 IV and the 10 V.
A list is here: Supported Devices
Looks like they have tested with / want users to have Android 13 on the 10 IV and the 10 V.
Am I correct in assuming that Android versions starting 68.0 equal to Android 13 and those starting 68.1 equal to Android 14?
My device (bought from Elisa/Finland this spring) seems to be old stock with 68.0.A.0.768. Probably the smart move is to not update to anything even if it started with 68.0. It’s offering me the 68.0.A.0.797update now.
Usually the first number is tied to the device and the second one is tied to the Android version, so, if the device came first out with Android 13, that will be 68.0 and 68.1 will be Android 14.
Is it possible to update to exactly 65.1.A.5.113 which is the newest Android 13 even though newer versions (Android 14) exist?
If we only knew firmware version corresponded to which Android version
For example, this update to version 68.0.A.0.797 is what my Xperia 10 V wants to do out of the box. I assume that I could let it do it, but I’d prefer to know the exact “safe” versions from Jolla so we don’t have to guess and deduce things, and possibly mess around with Emma which is prone to your-phone-is-now-a-brick errors (and also requires Windows, which I don’t legally have)?
Here is the overview for:
As pointed out by @emva in post below yours 68.0.A.0.829 is the last available Android 13 version.
You stay put and don’t do a thing. Revision .768 is good for us. The only winning move is not to Google Play.
One can safely accept each consecutive OTA update that has a version number starting with 68.0. Up to (and including) 68.0.A.0.829, which is the highest available Android 13-based version for the 10 V. Then, when you are offered to download an update starting with version number 68.1., simply shut down the device, unlock its bootloader, and you’ll never be offered any OTA updates again.
I have bought a Xperia V and waiting for the SFOS. Right now I have prepared the phone with the latest android 13 using EMMA.
Did you know that working with iphone or android is like working with Win 8.0, where as SFOS is like e.g. Win 11. In Win 8.0 the overview with whats apps was open were very poor and closing an app not that easy.
I’m sorry but If you can’t click a button or swipe up, sounds to me more like a skill issue
Correct, thats why Win 8.0 was not a success.
My bank has. There is not even a www application now.
I can imagine they may not even be aware that alternatives to Android/iOS exist on smartphones, but why on earth do banks think everyone would want to do their banking on a tiny screen in the first place?
It is not about what people want. Some bankers want to control our identity — that is the reason for the mobile banking innovation.
I was told randomly that “fraud” is now the largest crime - true? Don’t know.
Banks have been on the bleeding edge of the internet since the start and have embraced mobile (phone) apps fully as well. They are facing a cost/fraud issue, and fewer faces for the fraudsters is a decision they’re happy to make.
I’ll happily name SCB (Siam Commercial Bank) as the sinner in my case.
It rarely is. It is invariably about what the corporation/government want - no matter what the negative user experience is.
Please, let’s steer the discussion over here.