Has anyone else had problems sending SMS while roaming on the 10V? I recall it working fine with my XA2 Ultra. Considering filing a bug report but want to hold off in case it’s a me problem.
I am able to receive messages as usual.
Has anyone else had problems sending SMS while roaming on the 10V? I recall it working fine with my XA2 Ultra. Considering filing a bug report but want to hold off in case it’s a me problem.
I am able to receive messages as usual.
Music And Film Industry Association does not do that ![]()
Yes but that is very different than Sony AOSP. Adapting for a lineage-like distro still keeps too many vendor blobs
Some funny issue;
I upgraded the Xperial 10 V to Android 14 before flashing it (according to instrucitons it should be fine);
however, android support only shows Android 13 (which btw makes the Microsoft Authenticator non-functional).
EDIT : ok @explit above mentioned this, so I guess it’s expected. Assuming this will stay on Android 13 for now.
On Xperia 10 lll, when flashed from android 13, Sailfish shows android 11.
As I understand it, they’re two different things. The base Android version (13 in your case) over which you flash gets mostly replaced with Sailfish apart from some low level hardware drivers. The version of Android Sailfish quotes is that of AppSupport, a new self contained (but integrated) Android environment within which you run your Android apps under SFOS. The AppSupport version for Xperia 10 iii is currently stuck on Version 11, whilst that for the iv, v and Jolla C2 is at version 14.
I think the Android version within SFOS is independent from the Android version that was on the device before SFOS flashing…
Ok so one more reason to wait for the fixes
I just ordered Sony Xperia 10 V, so I hope this port advances soon to proper state! Happy to run Sailfish on newish hardware again.
Welcome to the club.
I’m waiting for a long time and got a Sony Xperia 10 III, in the meantime to have a device, that can function as a daily driver.
Unless you don’t expect to actually use that phone with Sailfish OS running on it, I recommend you return it.
I have done the same thing as you and it is pretty clear to me at this point that this phone will never be usable with Sailfish OS on it.
Or at least not in the next 5 years or so, at which point it will not be newish hardware anymore.
But I never expected to daily drive Sailfish OS anyway, so it’s not that big of a deal for me.
I’m just slightly disappointed, mostly in myself for believing Jolla’s lies.
So, unless you actually want a useless toy, I recommend you return the phone.
I’m daily driving the phone for more than three months and the only things that bother me sometimes are the missing camera and torch. I have to grab my wife’s or my work phone when I want to take a picture. Since Jolla stated that they got the camera already working with the new blobs, I’m pretty convinced that I’ll have a (beside all other known SF bugs) fully working phone within this year.
Advantages in comparison to the III are the much quicker GPS fix and nearly not existing audio loss in calls.
Same here; tho the lack of camera is surprisingly irrelevant in everyday s life (I use a nikon). The biggest pain for me is still the authenticator from ms not working properly (due to the android 13 in aas) and the lack of qr reading (due to lack of camera, really the only use case at the moment). Otherwise the phone is great, fast, and browser works alot better than on xperia 10 ii (even with ads)
Thanks for the warning, and I do understand what you say.
But I decided to now take the risk as getting these phones is harder and harder. I decided to take the risk and trust that Jolla will finish this port, because there’s been so many people who have bought already these phones on the expectation that Sailfish will work on them “soon”.
So it’s a risk, but I have enough faith that Jolla will go through with it as many people are waiting for it and have put money to it.
This highly depends on personal demand with phone. I rarely take pictures and I have daily drived xperia V for about 2 month. It is definitely acceptable to me.
The most annoying thing actually to me is no battery info. There is an app but I have to open it every reboot and unlock my phone to see it.
Never had any issues with the battery indication. You just have to use the right blobs version. You can find the info here in the forum…
That is true, I do not remember which it is, but with one of the older blobs battery indicator works flawless and accurate on the 10 V, easy try fastboot flash only the blobs
Maybe someone out there wants to use wired headphones already after some years of waiting for the Jolla release for the 10 V
and might therefore, find this info useful…
To my awareness there is still no support of the headphone jack currently on the 10V. For me a major drawback when I want to use wired headphones.
But for those who have a USB DAC, it might be interesting to know that I got audio on my beloved wired headphones via my FIIO KA11 USB-C to 3.5mm adaptor on the 10 V today.
I did it more or less according to this:
Beware of typos in the text, e.g. section 3:
‘pactrl load-module module-udev-detect’ is incorrect
‘pactl load-module module-udev-detect’ without r is correct.
I having a hard time deducing the right information from this (and other) threads.
Given the right blobs what are the remaining issues for the Xperia 10 V?
Is there a “right set of blobs” that has all the working features that are plaguing other blobs or does it differ per blob? My main issue is the battery indicator (not having that is just annoying) and being able to make and receive calls on the level of the Xperia 10 III (which is still not perfect btw).
Battery indicator works on v4b blobs for me
Funnily, it works for me as well (Android 14 base + latest blobs).
However, i have noticed the phone sometimes having troubles realizing it’s not out of battery.
Meaning; the phone runs low on battery (say 20%); but at some point decides to reboot (with still 20%). After this, even the boot loader has issues recognizing the actual power threshold.
In fact, it might not charge at all. What helps in this case, is a full reboot.
Could there be some services deep in the SoC that are not restarted properly?