I used sailfish on 10 IV for less than a day due to bugs not mentioned anywhere. Outside of what you’ve said the issues I had were: no cellular after turning off screen, fingerprint not working at random, loudspeaker being used as call speaker during calls and echo in calls.
I used latest android 14 as base with V3 binaries.
I do hope new binaries will help to fix those issues.
Weird question, I guess bug reporting counts? Would you want jolla employees to waste time on fixing Sony employees screwups? Company sizes are absurd to compare and lack of access to sources for sailors makes it even more dumb, should they spend all their workpower to reverse engineer the blobs to help poor small company called Sony?
Were those issues also present in Android 13 binaries, that Jolla originally intended to use? If not, what was the reasoning behind switching to Android 14, which resulted in months of delays and all those issues not solved until today?
@throwaway69
All of this doesn’t matter. From customer perspective you have not working phone and no finger pointing on the world will help the customer.
So yes, the customer expects from the company delivering the software to do something, or just stop pretending. So the company could analyze the issue and provide a work around or quick fix until the other company providing the blobs solves the problem.
While this game goes on and on, the customer does not have a working phone, has broken promises and disappointments.
If you ask me the issue is 100% with Jolla and I have stated this many many times. Jolla should do extensive testing and whould not adopt such devices that do not work.
Since day one the customer is the beta tester for Jolla and is paying the price.
So @yusssufff , you are beta tester as all we are. If you want to have a kind of working phone, just buy and configure one that most report is working.
For me it is Xperia 10 II with 4.4.0.72. As far as I can see nothing after this that is working well and the new C2 with SFOS 5.x doesn’t seem to be much better.
btw. somebody wrote on this forum that aosp is non-profit so we can not push or expect that sony will do better job but it is far away from the truth, aosp and its ability to install SFOS or another OS is the key feature and the reason why purchase Sony and not samsung or other brands… what about to send some public letter to sony?
Look if release notes tell me - this thing is not working, it doesn’t actually matter any more.
If I have to reboot once a week for example or sound stops working … yes it is not in the release notes, because no one know why it is like this.
So … what should I say … stick the release notes in … and do something meaningful.
Please, I am not so dumb.
I have to reboot SFOS because it stops working - for example sound, calendar or people app stops working.
Actually the way you people answer seems you believe you are very smart and when some one asks questions that challenge your believe you act like narcissists. This is very sad observation.
But we did it only long after the date on which the final / commercial images were said to be released (to no avail). As of March 18th, 2025, it’s been now whopping 10 months since the Jolla Love Day 2 where the release of SFOS 5 for the 10 IV / V was announced as “within 1-2 months, followed by AppSupport and commercial licences in August” (but hey, they did not say which August, though ).
I keep asking what was the true reasoning behind dropping Android 13 base (that, IIRC, was free of those nasty issues present in Android 14 blobs, which now are being blamed for perpetually delaying everything) and going Android 14 instead, and if A13 blobs were indeed free of those issues then was it really worth having lost already almost a year, with undoubtedly even more to lose while still waiting for Godot… ehm… Sony to release fixed A14 blobs, which they may just as well never do now that they already tinker with Android 15, but Jolla guys somehow don’t seem to be noticing my questions.
It’s kind of intriguing why was it so important to use Android 14 rather than 13 on the 10 IV / V (while it doesn’t even ofer a newer kernel), whereas the 10 III is kept on Android 11 and they don’t care to even just test Android 12 or 13 base and blobs with it (which have been available for years) even though it has been reported that it brings some quite useful fixes, e.g. in the echo cancellation or display tint / banding department. But no. While in case of the 10 IV / V it was so important to switch to Android 14, which - clearly - only caused issues and delays, with no perceptible benefits.
Jolla should test it and if 13 blobs are better than 14 blobs they should release SFOS for xperia 10 V / IV for 13 blobs so we can finally use these phones as daily drivers. and then they will get plenty of time to wait for 14 blobs… i believe that many from us would purchase licence even not needed android support or exchange just as the reward for the work…
Actually, battery status indicator is updating for me using SW_binaries_for_Xperia_Android_13_5.4_v4b_zambezi on Xperia 10 V.
The device was running Android 15 when I installed Sailfish.
Camera, flash and fingerprint doesn’t work.
Wifi and mobile internet works, both in Android apps and Sailfish apps.
VoLTE works.
).