Feedback on Xperia 10 V

Devices
#218

I looked up replacement batteries for the 10 V and the text on it indicates that the charge cutoff voltage is 4.48V. It’s not uncommon for high-quality Lipo batteries to be rated for higher than 4.2V charge voltage to “get more capacity” out of an otherwise smaller battery (sometimes at the expense of longevity).

Now, if only there was a way to replace the battery indicator with a raw voltage reading, I’d totally survive with that - that’s how I fly my drones, after all, start at 4.2V and expect to land around 3.5V.

Actually, is there a way to replace the battery indicator with a voltage reading?

2 Likes
#219

could be changed but instead i made simple app what also trigger notification about battery low, so you can hear the sound and plug the charger
otherwise system runs until batt is completely discharged around 3V and that is not good for battery life…

1 Like
#220

it seems the developer of this app already commented, but i would recommend his app: battInfo for Xperia 10V | OpenRepos.net — Community Repository System

#221

And now Android 15 has just arrived to my Xperia 10V.
Wondering how it’s going to work together with Sailfish once I decide to flash…

1 Like
#222

Soon we get new blobs for the next android version and Jolla can develop again Sailfish for this device

I think it could be a problem because of the file structure between Sailfish with blobs for Android 14 and new base on your device.

1 Like
#223

The new android version can add some extra steps to flashing sfos, but nothing irreversible. Usually you can always reset Android to earlier versions using Sony’s Emma tool

#224

Or for Linux users via Xperifirm and newflasher

8 Likes
#225

Just upgraded OTA to 5.0.0.55 (Tampella), seeing no difference so far. Any hidden improvements?

#226

Aside from a few more screens allowing auto rotate and some extra ambiences, I see no real changes on my 10 IV either, though I already had ESR91. To be fair, it was noted:

etc etc…

So as expected, there is no progress on the new Sony blobs.

I suppose I shouldn’t complain as nothing new is broken, but what exactly was supposed to be added with the big 5.0 release? Is it just screen rotating on the homescreen, an extra wallpaper or three, and the community developed ESR91? What has Jolla been doing? Do I expect too much? Heck, even if they’d just release AppSupport for us that would be a nice QoL improvement. Surely the issues with the Sony blobs can’t be the reason that’s still being held back.

3 Likes
#227

In the Tampella 5.0.0.55 thread Jolla say they’ve been fully occupied with the C2 and Jolla Mind, so I guess other things have been de-emphasised for now.

I also thought the 5.0.0.55 release was more like a small bugfix point release (i.e 4.6 → 4.7) rather than a major OS upgrade release, as aside from the new browser engine (done by a community member, no longer a Jolla employee), landscape mode for some of the existing Jolla apps, and a call blocking feature added to the settings of the phone app, there appears to be little different from before in terms of new functionality of SFOS.

1 Like
#228

If Jolla is using semantic versioning (or something like it https://semver.org) there is a reason why they did not go 4.6 → 4.7.

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes
  2. MINOR version when you add functionality in a backward compatible manner
  3. PATCH version when you make backward compatible bug fixes

Or it could be something “funny” like the reason the Linux kernel is using:

Does the major version number (4.x vs 5.x) mean anything?

No. The major version number is incremented when the number after the dot starts looking “too big.”
There is literally no other reason.

2 Likes
#229

If Jolla is using Pride Versioning, they are probably just really proud to pass a major milestone they are proud to see … such as the many-month upgrade of the browser, & getting new devices.

2 Likes
#230

their versioning has something to do with this:

versioning
versioning1231×582 34.1 KB

2 Likes
#231

The lack of headphone jack is pretty irritating—one of the primary motivators for going this route was going to be keeping the headphone jack on my phone. pactl list cards seems to show only a Card #0 with nothing related to headphones or hi-fi. Is the jack on some sort of daughter board with a DAC that the kernel isn’t exposing?

Bluetooth worked with a bit of fiddling but was stuck on SBC codec. I much prefer my wired setup.

1 Like
#232

They do not, as you can tell by the four field version numbers and the fact that “incompatible API changes” are introduced with every “minor” version.

#233

Hello, is it possible to install sailfishos on xperia 10 V with android 15? or only 13/14?
Thank you

#234

It is possible with 15: Fastboot flashing of Xperia 10 IV and 10 V - #5 by aerique

3 Likes
#235

Thank you @aerique I will follow on that post.

#236

Are there any new ETA for officially supported images with app support and maybe even working camera?

#237

Current AOSP blobs released by Sony back in November '24 have issues. The assumption of course is that the new blobs released by Sony (at some point) will be fixing some (hopefully all) of the underlying issues. The webpage to look at is here: https://developer.sony.com/open-source/aosp-on-xperia-open-devices/downloads/software-binaries I keep checking every now and then to see when a new image gets released. After the new blob gets released - Jolla needs to work on integrating it with SFOS and once the bugs are fixed / functionality is confirmed we can have an Early Access Release. After the Early Access release assuming no major blockers a General Availabliity release will happen and then licenses would be purchasable etc. So there’s still some work ahead with dependencies coming in from Sony’s AOSP blob.