Sometimes it fails to load for some reason and then it is “off” after reboot. It is hard to get it working again. Another reboot usually helps
If it loads correctly and if stayed “on” before reboot then after it will be “on” too.
I can confirm this Bluetooth behavior with my 10 V. Better to leave Bluetooth on.
What is your experience with screen brightness?
My 10 V can only be used inside, screen brightness is not sufficient for outdoor use with Sailfish OS. This is in contrast to
- 10 V screen usable outdoor with Android
- 10 iii screen usable outdoor with Sailfish and Android
According to specifications, 10 V screen is much brighter than 10 iii. With non Sailfish OS I can confirm this. But with Sailfish 4.6.15 beta even in max brightness settings screen is unusable dim on 10V for outdoir use.
Since my 10 V does not suffer dim screen under Android, I guess my hardware is OK, but Sailfish beta and the non-optimized OS is the reason.
But why then is nobody else reporting this dim screen issue.
What are your experiences?
Can anyone please test 10 V screen brightness in bright light against 10 iii screen brightness? Or a similar comparison?
The Xperia 10V screen gets more brighter if you turn of auto brightnes and turn the brightnes to max.
(No Comparison)
Interesting, in my device auto or non-auto makes no difference;
unfortunately,
… maybe my device has slightly different hardware??? I am just speculating, but slightly different hardware might also explain why some people experience the audio loss (after GPS) with the 10 iii and others do nor.
Dunno about configuration management in smartphone industry, but I worked in medical device sector many years, in this highly regulated environment, such silently available different hardware modifications within a single product line but not properly specified are NOT possible. So I am skeptical about that, but faulty hardware appears unlikely since an Android everything is fine.
Strange, very strange my 10 V unit.
The reason I choose the X10 V for Sailfish was the bright screen in the specs 
There are only two variants that I know of. 6GB or 8GB RAM, otherwise the same. I’m not sure about your specific case but as you know different things may affect things that are not obvious right of the way.
This is still deep beta release, some people reported this some said i didn’t affected thier device. I’m sure Jolla knows about it already
I suppose it’s due to bluetooth In SFOS 4.6.0.15 In Xperia 10 V, that no info file is found In /var/lib/bluetooth/ when Amazfit Stratos 3 is paired with Amazfish App of Xperia 10 V.
Thus, I can not add Appearance=0x0192
In info file like In Refs. [1-2].
I found the server side pairing code (UUID, 32 characters long) from the log file of Zepp (in Android) by Windows 11 with command ‘adb logcat > full_log.txt’.
Pairing between Amazfish and Stratos 3 happens very slowly as early reported. I have now repeated that pairing several times with that server side pairing code.
Looking forward to SFOS 5 commercial update.
Curious, Stratos appears in the list of watches of Amazfish?
Yes, there is also support In App *) for Amazfit Stratos 3. But there are also limitations In Bluez In this SFOS 4.6.0.15 beta so far.
*) Amazfish 2.5.0 (2024-11-24) Chum.
1 Like
Are there any news, any progress with 10V commercial image that somebody knows of?
This is the latest news as far as i know.
4 Likes
Was hoping for something I don’t know already. 
So, I’ll go back to waiting 
You probably saw this already?
3 Likes
That is very disappointing. I was under the impression that the updated blobs were the solution to all the problems, and all Jolla had to do was flip a few booleans, push an OTA update, and everything would be working.
Between the lack of a camera and especially being forced to use the speakerphone for all calls, it’s sometimes quite difficult to use my 10 IV.
Has anyone had success resizing the root directory?
I’m following the guide linked here and when I input
fastboot boot hybris-recovery.img
on step 3.3.1, I get
FAILED (remote: ‘not supported’)
1 Like
yes, ít is very disappointing.
Of course, it may be way more difficult than we think it is, yet at least some progress update on this topic would be nice after the weeks the new blob is now out there. But that’s the same old story.
I bought my Xperia 10 V 8GB RAM last summer. It was the last new device on ebay with a shipment to Germany. The last months the device will be not used or very occasionally (my second sim card). Something is going wrong. When Sony can not publish valid kernel modules, should Jolla prefer an another vendor - a lot of smartphones will be supported by the community and LineageOS.
Or the company has no knowledge to develop SFOS for Sony.
I like SFOS and Xperia 10 V DualSIM is a nice device but that waiting is like wasting our time and hope.
It’s very disappointing.
For example: Spring 2025 - Jolla will publish official comercial version of SFOS for both “new” Xperias. Nobody will can get a new device because it is EndOfLife - no new manufactured devices this year. It’s a joke and not a right customer marketing
5 Likes
Maybe in case of the 10 IV and V they should have sticked with Android 13 blobs, much more polished/finished. In such case, quite possibly we could have had a fully working 10 IV / V SFOS release for months. I’m not sure what benefits result from using Android 14 instead if even the kernel version seems to be the same.
4 Likes
There is a Lineage 20 port for the 10 IV (stock aosp 13 based, not sodp) which faces none of the issues we’re dealing with aside from fast charging being unavailable. If SFOS was based on A13 it stands to reason it would manage the same functionality, no?
1 Like
if I have installed SFOS on Xperia 10 V with given Android blobs should I have to re-flash everything from scratch when official support comes in and there are newer Android files or it could update itself?
The one on XDA or you know about some newer port for 10 IV?