We’re working on getting RAWFish working on the community port, it should translate back to the official port as the hardware is identical.
6 Likes
I flashed it a few days ago. My battery life has stayed the same—so it’s still great! (SONY Xperia 10IV).
Thanks again. 
I do not remember the android version but the binaries are v4b since the beginning.
1 Like
Next update: I got the video recording working, now I’m experimenting with the tele lens
8 Likes
So coooool!
You plan to make ‘commits’ to @jolla 's github so that they could be mainstreamed in the next SFOS update?
2 Likes
Right now I’ve made changes to the kernel, droidmedia, gst-droid and some changes to config files. I plan to create pull requests for Jolla and also provide a flashable boot image with the kernel, rpm files for droidmedia and gst-droid and a guide for the rest.
But as Jolla has hinted a 5.2 for the 10 V in the near future I will rebase the work on that and make it public afterwards to avoid duplicate work or even update issues.
Disclaimer: I have not tested if the same changes could also work on the 10 IV, this has to be done by someone owning the device and who knows how to compile these components for that device.
7 Likes
Cool! Maybe @jolla and @mal could even make a small ‘hotfix’ 5.2.x update just for the 10 V after merging your work!!
2 Likes
You know ‘near futureTM’ is not always as near as we may project 
…
At least if your commit is simple, it may always be considered for the 5.2 release, in case 5.2 for the Xperias would not be coming as soon as we think.
Quite likely that after Jolla Phone, 5.2 will come secondly only to the C2…
I do not think Jolla will integrate a kernel update this short before a release, I’m not even sure they will integrate it in 5.3 yet as it seems 5.3 is already in internal testing if I understood the last community meeting correctly.
1 Like
As long as it isn’t in cbeta, there is still a good chance to get changes into the next release.
Next small update: I got tele working, but the focus is not working here. But at least that way the camera is not crashing anymore if I accidentally press on 0.6. The tele lens seems to be the hardest problem.
3 Likes
Your work is such a game changer for usablility of the 10 V…
Tbh the 0.6 is likely the less important of all lenses… 1.0 being such a treat if it now works.
3 Likes
Please - share the recipe of your way to make video recording to work (I beleive that files are saved as well) - I have reached similar situation with BigPickle model - Files were just did not save back then. I have reflashed back to Android to use the phone. If you share that roadmap - I’ll try to reproduce that also for Xperia 10 IV. I wish someone makes Camera 2 API fully working on Sailfish OS to finelly end this mess.
2 Likes
I hope I have time at the weekend to publish everything, I hope for 5.2 if Jolla publishes it, if not for 5.1. And I hope I get the tele working completely then too. But as multiple components are involved it is not just a simple rpm to install, you should know how to use fastboot and the shell.
As a teaser, this
is an image I took with the main camera, the low noise level even in darker areas is quite good for that price range. And brighter images are even better. Both images are taken with the Jolla camera, so I’m curious about RAWFish and camera2 in the future.
8 Likes
@balta — great work, this is exactly what the 10 IV needs too. I’m the guy with the murray (XQ-CC54, official Sailfish 5.1.0.11), I posted the camera fix earlier in this thread.
Current state on my 10 IV:
- Flashed Android 13 v3a murray blobs → provider runs fine, all 4 cameras (main, ultrawide, tele, front) work with photos in the Jolla Camera app. Video is the blocker: pressing record freezes the app and produces a 0-byte file (also on the selfie camera, so it’s unrelated to lens mapping).
- I already dug into the encoding path and traced it to the same place your changes touch: QtMultimedia → gstcamerabin →
encodebincan’t select a video encoder. On 5.1.0.11droidvenc(gst-droid → MediaCodec) never gets picked, andv4l2h264enc(Venus) fails to register its elements — so the branch silently dies and no AVC encoder is created. Your kernel + droidmedia + gst-droid recipe sounds like the missing piece.
I can compile for murray (kernel, droidmedia, gst-droid) and I’m happy to volunteer as the 10 IV tester: when you publish at the weekend (boot image + rpms + guide), I’ll rebase and verify on the 10 IV, including the tele focus behavior over here. Also happy to test any PRs you want checked on murray before they go to Jolla.
One thing I can contribute: on the 10 IV the tele/ultrawide labels were swapped in Jolla Camera (fixed via dconf write /apps/jolla-camera/backCameraLabels "['1.0', '2.0', '0.6']"), and I’ve confirmed the HAL ID permutation behind it — can share the CAMX log evidence if useful for your lens work.
Just ping me when the files are up (or let me know if you need anything from the 10 IV side beforehand).
2 Likes
Thanks, this dconf command fixes the lense labels. For my current state: I got the focus of the tele lense completely working, but it involves manipulating files from Sony (the v4b binaries). Right now I’m checking how I can distribute such changes without license issues, I will not provide a flashable image here as I’m pretty sure not allowed to do so. I also do not know howJolla could handle something like this so I don’t know how easily the fix can be included into an official release. I will post anything needed as soon as I know how to do that.
Cool. Anyhow maybe a fix of the main camera,without the tele lense, is already great, if that’s easier to release.
1 Like