I think my project is finally mature enough to bring into the daylight. Before saying anything further - thanks @mal for all the work you do and thanks to you and @elros34 and all the other gurus on #sailfishos-porters for your help getting me this far.
In light of the disappointing announcement from Jolla at the 04/06/2026 Community meeting, I have decided to take matters into my own hands.
So, for the last month and a bit I have been working on a Lineage22.2 based SFOS 5.1.0.11 port for the Xperia 10 IV (pdx225). Note that my phone is a XQ-CC72. YMMV if you have an XQ-CC54 but it should still work the same. Update: @mettska was successful installing on their XQ-CC54.
Camera (just main rear camera for now, I was so happy with that I havenāt bothered looking into getting the rest going. Photo + video works)
Charging / Battery (incl. charge limit & much faster charging than Jolla port)
Speaker (and earpiece speaker, and 3.5mm jack)
Sensors (sensorfwd seems to require restarting after first boot, you can just reboot the device or run devel-su systemctl restart sensorfwd)
GPS
NFC (theoretically, I donāt use it)
CPU sleep
Vibration motor
Notification LED
Local video playback
SD card
What doesnāt work?
Rejecting a phone call (you have to let it ring out, miami had the same issue but it was solved so I can probably fix it if I look into it)
Fingerprint (I think AIDL fingerprint driver is the cause, community fpd looks for HIDL only)
CPU sleep when connected to wifi doesnāt work. ~3%/hr drain. With wifi off we have ~80% sleep and ~0.6%/hr drain or less.
usb-moded (usb networking & MTP transfer & OTG, also was broken on Jollaās port IIRC but probably fixable here if I / someone else can be bothered)
Dual-sim (breaks mobile data for me, I only use 1 sim so I just disabled it, would probably cause problems with XQ-CC54 anyway)
Youtube playback in the browser (seems intermittent / related to resolution)
Calls only take place using phone speakers, not bluetooth (this should be fixable using a modified version of @rinigusās droid-bthelper from nagara, but I need to spend some time to wrap my head around that or get help).
As reported by @mettska, 5G VoNR calls may not have working sound.
Disregarding the above issues, from my testing the port is really stable. I have had my primary SIM card in it for a week now (as Iāve been trying to debug VoLTE & call audio) and it has been trustworthy as my alarm clock, navigation, browser, etc. no worries. And now, finally, it even works as a phone! If you are daily driving a 10 IV on the Jolla port like I had been doing since October 2024, this is a great improvement over that experience and I would highly recommend it.
FAQ:
Will you do the same for the 10V?
No. I donāt own one and I donāt have the money to buy one. But people say the 10V and 10IV are quite similar architecturally so presumably someone could copy much of my work to make a 10V port? I would most likely be willing to donate some time to help someone else do the work.
Yes! See top of this post for a link.
Does Android App Support work?
No idea, Jolla said at one point if someone went to the effort of making a Lineage based port for X10IV they would consider allowing AAS on it. But I donāt know if I need to do anything on my end to make that a reality, and they have not endorsed this port specifically yet. Once I have SailfishOS working and in the hands of users Iāll consider looking into what needs to change to get Waydroid happy if thatās possible.
Not at this stage, the Android 15 base (ie. AIDL) might be too much for it.
Do you promise to spend the rest of your life maintaining this port?
Eh, I will most likely continue to maintain this port while I personally use this phone, but I will not promise anything beyond that at this stage. I will work on it when I have time, which might only mean a few hours per month going forward. I have sunk way too many hours into it over the last month and I need to cut back so I can maintain my own health / relationships / other priorities.
Where do I get it?
Today, this post is just an announcement. Soonā¢, I will release a build. Hold your horses until I have the port registered to use the Jolla store and so on, will take another day or maybe a few. That said, the sources are here and the image probably will be too within the week.
Can I help?
Abso-freakin-lutely. Iām more comfortable elbow deep in gear oil working on a tractor than I am sitting in front of a computer screen. If Iāve got things this far (admittedly with a lot of help), surely there are smarter people who can do better software hacking than I can. Youāre probably one of them. Please set up a build environment, download the sources, and contribute any fixes you can.
So please, have a crack at using this port when it comes out and see if I was at all successful. And then dive into the sources and see if you can be any successful-er.
This is exciting stuff, @Sharks ! I will definitely try it when itās available.
Iād thought about trying to do this port every time I looked at my 10 IV sitting on the shelf, flashed back to Android because the official Jolla port is essentially useless. But it was more work than I had time for. Very impressive that youāve got it working this well.
Itās going to be a tough choice if I have both a functional 10 IV and a new J2 a month from now. Especially if the 10 IV now has a working headphone jack.
Thank you so much. I cant wait, till your port is available and will definitly test it!
I was also working on this port, but had other priorities in the last weeks, so I couldnāt finish it.
As I have said in the wrong thread, this is an amazing amount of work that will go on to benefit so many people. Thank you for taking the time and effort to do this. It is an incredible leap forward to to 10IV and 10V becoming usable.
I hope to perhaps slowly replicate what you have done for the 10V, but it is surely not something I have experience in.
Only if one is referring to the single silly instance, in which the religious institution decided to give their deity the common noun āgodā as a pet name.
This is only my second port, the first one I got to the homescreen but not much further, and I must say this time around it was much much easier. I think mal and friends have done a power of work getting the later Android bases as painless as possible to port to.
I was concerned it would be difficult to port a hybris-22 base but aside from a few catches where the latest versions of a couple of packages are incompatible and I had to roll back, most things were relatively straightforward to get working. It just took time to trawl through the logs and the documentation to find what needed doing, or else ask in the chat and get some pointers. Iām sure if you have an X10V in your drawer, youāll get the same result I did in the same amount of time.
FYI quick update, I am aiming for a release by the start of next week - no promises - Iāve been asked to shift from a ācommunity-styleā image to an LVM based one and Iāve only just got OBS sorted out last night, so I need to work out what needs doing there. Iām out this evening so will be tomorrow before I get to have another play. All going well Iāll manage to tidy everything up over the weekend and get something out for people to begin testing.
It is with great pride that I announce the release of my first published SailfishOS port
I must once again thank everyone who helped me get this far. There were a couple of points especially in the last few days where I was struggling a bit - perhaps it was a mistake to announce things so early and put pressure on myself. But it is done now.
As I have said, I will continue to maintain this port for the foreseeable future. If I get particularly bored I will work on fingerprint, and Iād like to get bluetooth calling fixed, along with the other small bugs Iāve noted in the first post of this thread. But unless there are any showstoppers right away that I donāt yet know about, I plan on taking a few weeks off from this project to focus on other things in my life that I have been neglecting. I strongly encourage others to give feedback here and/or submit their own improvements in pull requests, etc. - I would be thrilled to have that kind of engagement and help. And Iāll still be around to answer questions if required.
That said, right now I am off to bed now for it is nearing 2AM. Hopefully I wake up to read that everything has gone swimmingly and there are a few people on the other side of the planet enjoying what Iāve managed to pull off. Hopefully there wonāt be too many teething issues.
Thanks so much for all the work you have done, and especially for the fantastic documentation you gave taken the effort to publish here on the forum and on your Github. The extra effort you have put into documentation is fantastic, and it is great for the community for you to share so much of what you have learnt
I am sorry if my mentioning your work in the audio thread put pressure on you. I was just excited to see all the effort that was happening, and thought it relevant. Sorry
Thanks again for this great contribution to the community.
Donāt be sorry, @juz, I meant this thread! When I first posted it I intended to have an image a day or two later at most. It took longer than Iād hoped, but Iām keen now to hear peopleās feedback and I hope it works as well for everyone else as it does for me. Iāve spent almost every waking moment outside of work for over a month trying to get it to this stage - mostly because I was learning a lot as I was going - so Iām keen to reap the benefits now.
I think my documentation is lacking a bit, but I tried to remember to capture the important things that caught me out. As Iāve said before, feel free to get in touch and ask me silly questions if yourself or anyone else is planning on taking a brave pill and doing the same for a 10V. Iād be happy to help if I can.
If I follow your link to the first web-archive, I can donwload all necessary .img-files, but the download of the lineage-22.2ā¦zip fails. Any idea how to solve that? Can you provide the files in your github or is there some copyleft-issue?
