Thanks. Yes, Bluetooth audio works once Bluetooth works. I now just never turn it off, but sometimes it is turned off by itself? Rebooting also doesn’t seem to be a reliable fix for me.
I didn’t see that about the audio routing, and that unfortunately didn’t make it to the release notes.
Turning off is something I have NOT experienced until now. Once established, the bluetooth connection was rock solid.
Yes, unfortunatly this info was not in the release notes, but hey, we have a vibrant community to get informed 
For me cable routing audio signals is important for listening flac files with high quality headphones
On my Xperis 10iii bt does not work after a restart. The workaround is to enable bluetooth and while the icon is blinking restart bt via Sailfish Utilities. If the restart process takes mote than 5 seconds, bluetooth works as expected until a reboot. Maybe this works on 10v too?
Yes i have a similar workaround on the 10v
Installed without problem thanks once I realised that the “blue” / “green” light is on the left not right as in previous Xperia and is a screen “star” display item rather than an LED light on the right hand side (duh). Some comments / feedback
I have a UK SIM from SMARTY (a brand of Three.co.uk) The Data Access Point shown on installation referred to Three.co.uk rather than SMARTY and the access point was that of three.co.uk rather than the SMARTY access point of mob.asm.net The setting can be edited manually however. (does the file with access point data / network settings need updating?)
I also notice that sometimes on a restart, the handset /seems/ to boot more successfully with power connected.
Overall the Xperia 10 V seems to perform OK accepting the notified issues. (I confirm that the flashlite doesn’t work)
NB Storeman App now shows a Network error but this seems to be a server side certificate issue with Openrepos.net not the Xperia 10 V.
That is true. Storeman and openrepos certificate issue is independent from the device and discussed here: Openrepos down, or certificate expired?
I have three two problems so far:
Furthermore I encountered once a breakdown of audio? I was called and did not hear the caller. Neither did he hear me. I restarted the phone and it worked again. Don’t know if restarting audio subsystem would have been sufficient. Didn’t think of it, as I never had that issue before on my Xperia II.
What experiences do you V Sailors have with screen brightness?
Reason I am asking is that I today used my Sailfish driven Xperia 10 V in bright sunlight and the screem was barely readable, because dim.
When I checked the Xperia 10 V device with Android in bright sunlight for getting familiar with the hardware a few weeks ago, the brightness of the same screen was much more similar to the brightness of a Galaxy S22 Ultra. This is why I expected the brightness of the Xperia 10 V in direct sunlight to be closer to Samsungs upper class than the Xperia 10 iii, which is known for less brighter screen than the V.
I was very surprised today by the mising brightness under Sailfish with Xperia 10 V and being on Xperia 10 iii level when used in direct sunshine
What are your observations?
Can this be related to 4.6.0 15 being beta release quality?
I have been roaming around and also lost mobile for some 12h or so. Based on initial results, I’d not be surprised if there an issue in lower layers somewhere. Managed to get my mobile connected with a bit of hacking. Hopefully, my findings would eventually help you as well.
So what kind of hacking are you talking about?
For direct sunlight i use the bright ambiences glacial and the purple i forgot the name of. This gives a higher contrast
You do have enabled automatic brightness, right?
But I do remember it as not great in Andy too 
.
Yes, that is what I did as well
Yes, it was on Auto Brightness.
I have no hard numbers at hand, but I think it was GSM Arena that published some numbers that I found reasonable by my non-scientific eye judging. Those were approximatly
So the V is relatively close to the current Samsungs in terms of max brightness. My quick test in June in bright sun with Amdroid confirmed this more or less (non-scientifically)
Yesterday, the Xperia 10 V appered as dim as I know my Xperia 10 iii to be.
This led me to wondering, if some hardware resources in terms of screen brightness are currently unused by the current OS, especially taking into account the current beta status.
And starting from this, the question if some settings changes can tweak it and increase max brightness, came to my mind.
Please don’t get me wrong, no complaint; question is coming from technical curiosity perspective (from an obvious noob)
Today I received the substitute of a broken SIM tray of my Xperia 10 iii, so I can continue to use it.
According to GSM Arena review, the Xperia 10 iii has an expected screen brightness of 345 and 559 nits depending on manual ot auto brightness with Android.
In contrast, acoording to GSM review, the V has 629 and 947 nits.
When I place both devices in direct sunlight with manual max brightness settings, my V is DARKER than the iii. So the other wasy around than expected.
With dark ambience, see picture (in blue silikon is the V)
Here repeared with light ambience
Can this be OS and software related?
Is it reasonable to expect that the V in future stable Sailfish OS releases will improve the screen brightness and bring it to full flavour?
the brightness you set is just the base brightness. so even if you enable auto brightness and set it to the lowest brightness it will not reach maximum brightness, so you still have to higher the brightness if you want to have the display more bright, even though you enabled autobrightness
I indeed used the base brightness under settings - display.
Are there additional ways to influence screen brightness? If so, then I missed something fundamental.
My Xperia 10 III is with android and my Xperia 10 V with SailfishOS.
Brightness is better on my 10 V than on my 10 III.
Interesting,
Brightness on V with Android was much BETTER than iii on Sailfish
After flashing Sailfish it is the other way around:
Brightness on V with Sailfish is much WORSE than iii.
So I guess it is not hardware related (no faulty screen), but controllable by software.
The proof would probably be to
But that would be time consuming
Next question is how is brightess in AOSP on which SFOS is based…
