Community work on Xperia 10 V camera support

Hello guys!

Recently I bought xperia 10 V - XQ-DC72 and flashed Sailfish OS onto it (used v4b version of blob)
I knew about camera issue on this phone and started investigation
I was able to run telephoto lens (2.0x). Selfie camera and flash also works.
Currently working on resolving the OIS subdev issue on the main 1.0x sensor

35 Likes

Oh thats quite cool!
Thanks for your work!
Next you can investigate audio :wink::flexed_biceps:

4 Likes

Wow!
Did you get CameraAPIv2 working? Or did you use v1?

3 Likes

Yep
CameraAPIv2 is working
just run in terminal
/vendor/bin/hw/android.hardware.camera.provider@2.5-service_64 &
it will be enough for selfie camera at least
The main camera has an issue with stabilization interface.

15 Likes

Wow, that works! Thx so much. Now for the front camera (I hope).

You’re certain it’s running the camera2 branch of droidmedia? Do both photographs and video work?

I wonder why Jolla did not start the camera service to begin with. Surely some camera is better than no camera.

Apparently, according to another thread here, Jolla (Mal) said that they got the camera to work months ago back in 2025.

I’ve often wondered why they never released any update. Working cameras would go a long way to making the phone usable as a daily driver for many in my opinion.

Maybe there was some other issue.

1 Like

Working cameras, the reboot every morning when I unplugged the charger, and an inability to take a private phone call were the reasons I stopped using the Jolla port. I don’t know how I managed to put up with it for so long now!

That sounds like an Xperia 10 iv (which I also have, and which has the exact same issues as on yours).

I’m talking about the Xperia 10 v, which is able to use both the loud speaker and ear speaker without issue. It also doesn’t randomly reboot itself either.

With the v4b blobs (which make the battery percentage display and mobile networking functional) and a fix for the cameras, the 10 v would be a good daily driver for me.

1 Like

I understand that I own an Xperia 10 IV. I’m just saying that no camera was a bit part of why I ported Sailfish to it with a Lineage base. If it had a camera, possibly even still with the other little complaints I also had, I might still be using the Jolla port. I was just wondering aloud why the 10V still had a disabled camera if enabling at least partial camera support is as easy as starting a service.

1 Like

Yep, me too. Especially because Jolla commented that they got the cameras working back in 2025.

Maybe they are not interested in the 10 iv & v any more…

This produce Segmentation fault

edit: i reverted back to 14_5.4_v3a some time ago, that is maybe the difference, because on v4b phone randomly starts heating after day or two and draining battery so daily charging was necessary. back on v3a the battery indicator does not work (using my batinfo again) but charging once per 3 days or more.

also noticed that /vendor/bin/hw/android.hardware.camera.provider@2.5-service is running with low pid so it looks like it is starting after boot under user camerasomething. (can’t check it now as it is gf phone and she is away)

well @jolla should be interested due to reputation because they announced full support years ago and people spent money by purchasing devices… i personally purchased two pieces of 10V… if i knew how it will be i would better go and pay some bitchez or purchase new corals :smiley: lets hope they will return to work on 10 V / IV after J2 , now they have nice money from selling J2 so they can pay more developers, right @rainemak :wink:

3 Likes

Of course they are not. Properly working 10 IV and 10 V would negatively affect JP2 (and previously C2) sales. So they became disinterested in making the new Xperias work properly the very day they decided to start selling phones themselves. As for ‘reputation’, they care about it just as much as in case of the tablet f***up, or the Mind2 soap opera (and more) - zero communication.

2 Likes

Please, lets not slide into what could be considered as conspiracy theories…
Plus communication is always complicated when you are a company, you should always mesure every word you say cause you gona be taken accountable for each one of them. All big firm’s communications have to be filtered by teams of lawyers for a reason.
One could even argue that luckily they didnt communicate more since then an army of posts would confront them if results wouldn’t deliver as planned…

Anyhow all what we can do is to cross fingers and hope @jolla will get us nicely working 10 IV and V at some point!

Also this initiative to tinker and help crack bugs is so cool, love it!
Then Jolla can profit the warm hearted community work and merge the commits!

7 Likes

I’ve tried that with you command:

where selfie (front) camera started to work, unfortunately I can’t get this one:

From your photo, I’m unable to switch to lens 2.0 in any mode.. :-/

Kindly refrain from instructing me what to say or not. It’s not the first time and it’s getting annoying.

1 Like

Hello Tom
Try to run
dconf write /apps/jolla-camera/position 3
dconf write /apps/jolla-camera/deviceId “‘3’”

Also please try to record some video - I had some issue with jolla-camera app.

4 Likes

Hello Steve

Thank you for your note
Could you share a link on that thread

Cool.. that commands works for taking pictures :stuck_out_tongue:
Video hangs and then crashes the camera app..

Also 2nd command works without quotes and double quotes:

dconf write /apps/jolla-camera/deviceId 3

1 Like