That’s been a problem for many years, both for Exchange and Office365 accounts. I’ve had it on my XA2, Xperia 10iii and v.
Strange, had never heard of this being a problem prior to getting my 10 V. Surely that’d be a pretty important thing to fix especially if it’s occurring on devices with a paid licence? Not in doubt that you’re correct, just slightly confused now.
The More You Know™, as they say.
I can confirm the chronology of Steve_Everett. It’s a reason why I’m selling my 10V. After 18 months of waiting time I have an unused device in my drawer.
I will maybe give it till the end of the year now as I’m still playing with my latest toy (Xp’ 5 Droidian), which although it has the odd qwerk is no where near as buggy as the SF 10v. If it doesn’t happen with the 10v I might just stick with the Droidian 5 and keep the SF XA2 as a standby. The 10v I bought has an unlocked bootloader (hence the reason I got it so cheep), so android custom ROM install might just get me my money back I’m thinking.
Well here is a bug report I raised on this nearly three years ago at the beginning of 2023 …
Anybody got any experience with the v7b blobs on the 10 V?
That doesn’t sound all too convincing…
Thanks dude, I won’t try the 7b yet for sure under these conditions.
But the 4b blobs work perfectly as far as I know. I’ve reflashed with the 4b blobs and I have found no problems so far.
Only the v4b blobs work for me, the others don’t even get me working WiFi.
But I’m flashing them on Linux on top of the latest Android (15) images from Sony since I do not have a Windows machine anymore and thus no Emma to flash an earlier Android.
I can confirm that v4b blobs are the best atm..
I was running a lot of months on v5a and cellular internet connections hangs due to switching between 4G and 5G network.. BT is still hanging sometimes on both blobs, but restart of the phone helps.
Also, v5a had issue with stuck cellular network have been disconnected, nobody could call me back. I think, it happens with re-connection between wifi and 4/5G network ..
And a few more:
- High power consumption, even higher than the 10 III (which is already quite high). Even on standby, without SIM card (i.e. no mobile network connectivity at all), BT/NFC off, WiFi off, display off, and everything else off, it eats 50-80 mA, compared to 10 III’s 30-50 mA with 4G network and mobile data enabled.
- Stereo speakers on 10V don’t work correctly - left channel is not played at all, right channel is played via both speakers
bluebinderprocess regularly crashing and utilizing nearly 100% of one CPU core, boosting power consumption to even 700-1000 mA, needs to be stopped withsystemctl- call recording doesn’t seem to work - there is no button shown to start recording, even if the corresponding option is enabled in settings
- there is no bootloader charging mode - the phone always boots the full OS once you connect the charger when it is switched off
and there’s some more I’ve forgotten atm.
The bluebinder bug is more annoying than not having a working camera to me. Forgot to stop its service? Oh, look, 10% battery.
Disabling it (to stop it coming back after a reboot) used to work but now doesn’t, for whatever reason. So you have to be very careful about stopping the service every time you reboot; I leave the terminal app open as a reminder that I’ve done it.
I hadn’t noticed the non-functional stereo audio until now but that’s definitely going to bug me lol.
I’d say that a working camera and fixing that bluebinder bug could make the 10V somehow usable as a secondary / backup phone. But power consumption is also a big problem. As I wrote earlier, 50-80 mA when 100% idle and with everything switched off is already twice the idling 10 III power drain, but even just enabling WiFi on the 10 V makes it start to draw not less than 120-140 mA, all the time. Which is horrible…
My 10 III with its high power drain ate its battery in 3 years - its actual capacity is now reported as ~3500 mAh, i.e. around 1/3rd is gone. So the 10V will probably ruin its battery twice faster.
The snag list is just too long for me. I like devices that just work, don’t mind a little snagging but I have to draw a line on this one. Might try loading up LMODroid on mine. Its one I’ve never had and could be interesting if the long promised linux container for android project comes to fruition.
Last news from the community-meeting: @attah states, that he sees work in the repos. @mal said he is testing fixes against new blobs and also he has done some work on sensorfw and die AIDL-VoLTE-Implementation.
I really would love to have a camera again…
So, in December 2025, is flashing to Sailfish OS from Android 14 with using v4b blobs the route to the ~most viable Xperia V installation?
Currently this is the best, though some work has been happening at Jolla, so hopefully soonish this changes.
Darn, the installation script insists on using the Android 14 version of v4a blobs. So the v4b blobs should be flashed manually afterwards?