I had to use X10V before C2. Not once I saw LED in Andy.
Missing notification LED is one thing, but they removed the extra camera button, which I cannot understand. This was one of the important reasons for me to use Sony smartphones, as it made them unique. Finally even Apple added this feature to their inferior iPhones.
I read between these lines that Raine already knew about the upcoming news on the Sony Front
3 Likes
… and as a leading media company Sony really knows how to hold the tension high. At least they didn’t spoiler what we can expect like
- battery level updates
- camera(s)
- more robust connectivity
- fingerprint sensor
- magnetic lid sensor
Anything I missed?
Working flashlight aka torch
Edit: and screen brightness is still crippled and way below if what the hardware is capable to deliver
1 Like
I tested the X10V binaries already, and while battery percentage now updates, other things need more work before they can function. For example; modem, WLAN and Bluetooth don’t currently seem to work at all, and camera needs to be re-enabled anyway.
So, stay tuned for updates 
20 Likes
I tried yesterday with the same result like you
Is it enough to use fastboot flash SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img for newer Sony blobs on 10 V?
fastboot flash oem SW…img
is to be used to try the new blobs
╰─➤ $ fastboot devices -l 1 ↵
HQ63BJ0498 fastboot
usb:1-2 /0.5s
--------------------------------------------
╭─ ~/Downloads/SAIL
╰─➤ $ fastboot flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
Warning: skip copying oem image avb footer (oem partition size: 0, oem image size: 432464996).
Sending 'oem' (422329 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed /0.9s
--------------------------------------------
shouldn’t be there oem_a ?
No, I did not specify a or b.
Only fastboot flash oem did work flawlessly with A13 or A14 blobs for me every time
There isn’t more information about this error? Strange
Hmm… verbose mode is not so verbose 
╰─➤ $ fastboot -v flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
fastboot: verbose: Do flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
fastboot: verbose: target didn't report max-download-size
Warning: skip copying oem image avb footer (oem partition size: 0, oem image size: 432464996).
Sending 'oem' (422329 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
Neither this works :-/
That’s funny, because oem only without -a was sufficient and worked on my device.
Just double checked from my terminal history
??
Sorry, just reflashed my oem partition on my X10V, and ‘fastboot flash oem SW…ing’ works with new and old blobs.
Sorry, I cannot reproduce your error.
Your verbose claims partition size zero??
Sounds unusual to me
if i understand correctly that with new blob, modem, Wland and Bluetooth does not work but with SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img it is working fine here (except camera of course)
5G is working fine having speedtest around 230d/95u
I can confirm that modem, WLAN and Bluetooth are inactive with the new November zambei blobs, while with the ones recommended by Jolla in the beta 4.6 15 release all three work
1 Like
It worked for me after the first boot but then soon drained the battery and now it’s stuck between airplane mode and not detecting the SIM. At least data worked as I didn’t made a call. WLAN and Bluetooth look like they would work but I haven’t tested yet.
Edit: I double checked and I have the problems above with SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img.
1 Like
As the target did not report the maximum chunk size it supports one may set it manually by the fastboot option -S 256M to 256 MByte.
But this should only become an issue for files one flashes which are larger than 512 MBytes, and this file is slightly below that (422329 KB).