This is certainly true, but to ensure optimism is kept in check, let me add that I think making what Jolla have available for use on a community port is probably what Jolla meant - rather than fixing bugs and making it work. I am just speculating though. Let’s see how the next couple of community meetings go.
1 Like
Well, the Nagara port (for the 1 IV and 5 IV) is actually fully mature (and AAS works very well on it ‘out of the box’), but so what…
@wetab73 , the nagara port is based on Lineage21, these murray and zambezi ports are based on Lineage 22.2. These are quite different beasts. And it seems it is this difference that is the show stopper for AAS currently. Not saying it cannot be solved. Just it is not working currently.
2 Likes
@juz, I know, I meant something different. I meant that if a nearly perfectly working AAS (that doesn’t need any modifications as it just works out of box - there is only some not yet solved issue with some video codecs but other than that it is literally 100% functional) on as mature port as the Nagara port is, doesn’t seem to be of any noticeable interest to Jolla, then chances that they would do anything in case of the 10 IV or V are very poor. Yes, they said (a year or so ago) that they ‘might think about’ supporting AAS on community ports, but that was both the first and the last time they mentioned it.
2 Likes
Oh, yes, I understand now. I probably agree, though will hold onto a bit of hope, but clearly their priorities are elsewhere.
2 Likes
It’s very easy to ask them again. In that case we avoid speculation.
4 Likes
I’m not speculating, I’ve only stated some facts. It is a fact that as mature port as Nagara (quite possibly surpassing quality-wise all official Xperia X ports) and AAS working great on it, so far haven’t triggered any attention from Jolla, and it is a fact that when they said nearly a year ago that they might think about supporting community ports was the last time this subject was ever mentioned by them. But, of course, it’d be great to ask them again and see what they say this time.
I didn’t know, that these two community ports have AAS. How was this achieved?
I think I’ve said this in the 10 IV thread, but my understanding is that the HIDL vs AIDL differences between Android 14 and 15 bases make AppSupport difficult at present. Same goes for fingerprint, though I think I have a reasonable chance at being able to fix that one given enough time.
These are not concerns on Nagara because they use an Android 14 base. I did not want to go to the effort of porting Lineage21 to Murray or Zambezi, so I used the pre-existing Lineage22 builds.
Happy to be proven wrong about the above.
Similarly for bluetooth phone calls, Rinigus wrote a handy little script called droid-bthelper on Nagara to fix that problem, but again because he ported Lineage21 himself, he was able to use android.hardware.audio@7.0. The prebuilt Lineage22 I’m using only ships android.hardware.audio@6.0, so I need to learn how to modify droid-bthelper to talk to that interface instead.
Finally, cameras - some great discoveries have been found by @denissius and co at Community work on Xperia 10 V camera support regarding cameras in the Jolla port on 10V and 10IV. It would appear that the Jolla port uses the Camera2 API, which is interesting. I have used the Camera1 API, which limits us to a single lens front and rear. We could switch to Camera2 and likely have all three rear lenses, but we’d lose video recording functionality. I suppose if the people using these ports would prefer that, I will look into it. But we can only have one or the other. Nagara uses Camera1 to my knowledge, but due to the way Sony wrote their proprietary camera blobs for Nagara, they have access to both standard and telephoto lenses where we only have standard.
The other outstanding issues of dual sim and fussy youtube playback I’m not quite sure how to tackle yet, I haven’t really looked too closely. Usb-moded can be fixed I’m sure, I just need to put the time aside to do it as well. Same for dual-sim, though it is not a priority of mine. As always, if you are willing and able to help in any way, please do. Sources are here. I’m only one person and I have many other things to do of an evening / weekend!
5 Likes
Jolla did comment on AAS support for Nagara at one stage (at 16:57):
2 Likes
Yeah, that ‘they’ve been thinking about it’ (as always), that ‘it’s unlikely for that community port to get support as the first one’ (well, then it’s hard to imagine any other port to get it considering that the Nagara port is the most advanced and polished one and AAS runs on it out of box and therefore doesn’t require any work from Jolla but to simply start selling licences), and that ‘more on that later’ (and then not a word since December 2025). Also, I wasn’t incorrect saying that the Nagara port didn’t trigger any attention of theirs - it wasn’t their initiative to talk about it, they only (vaguely, as always) responded to someone’s question. That person even tried to further ask what they mean by ‘later’ and whether it might mean January or February 2026, so they told him that it’ll be ‘not too far in the future’, which clearly in Jollan language means more than 9 months which have already passed since then without any further reference to that matter anymore. So while I truly admire and understand many people’s optimism, I rather prefer to be realistic, having observed Jolla since 2012 or so and how ‘they had been thinking’ about so many important things not to be heard about ever again. Of which the 10 IV & V have also been a good example, including how a random guy made the cameras work with a single line edit of a config file whereas they’ve been - allegedly - struggling to make it work since 2024. My ass 
Anyway, you’ve done a fabulous work! Kudos for it! All 10 IV & V users (myself being one) owe you eternal respect and gratitude. Thank you, @Sharks.
1 Like
After all, there is a certain difference between X1, X5, and X10 IV/V. Jolla has promised official support for the latter. That’s why I think there’s a chance to get AAS on X10 IV/V.
1 Like
Yet to be seen. Or actually not. When was the last time they talked about it? 1,5 or 2 years ago?
I’m afraid it’s the same kind of promise as above… Though I will be very happy if they prove me wrong.
1 Like
Is it not possible to have both as separate excluding services that you could potentially toggle? I don’t know much about the lower level workings of the camera APIs, just wondering if it would not be possible to have two of those android.hardware.camera.provider executables that you could switch between depending on your needs.
The port has arrived!
Again, I cannot thank @juz enough for helping me test this thing and get it to the stage that it is now.
Please note that as @Keto is away currently, Jolla Store access is yet to be granted. When it is granted, the store should show all apps as normal, but for now it will only show a limited selection. Openrepos and Chum work fine though. Update 18/08/26 Jolla Store access granted!
For those of you who wish to install the port, please find what you need at my GitHub repo: sailfish-on-zambezi/INSTALLING.md at main · sharks-dev/sailfish-on-zambezi · GitHub
Note that I have not replicated the entire installation instructions, as the procedure is largely identical to murray. Again, like murray, this port was developed and tested on the XQ-xC72 variant, but it should be just as functional on the XQ-xC54 variant. If someone could please report back their experiences on that variant I would be grateful.
Thanks all for your patience. Any feedback or queries please post them here and I’ll get back to you as soon as I can. Enjoy!
14 Likes
Not easily to my knowledge, because you need to have different builds of droidmedia for each version.
Thank you very much! I will try it out as soon as I get a grip on everything else around me. It’s busy times, like never before. 
2 Likes
Will try to test today after work.
2 Likes
Sometimes it is easier/faster for the porters to take the initiative.
If the mountain will not come to Muhammad, then Muhammad must go to the mountain.
Besides, how would Jolla even know the Nagara-port users want AAS, if they don’t specifically ask for it? After all, in the past they were only thinking this in the context of 10 IV and 10 V, so wouldn’t hurt asking this again with the Nagara-port in mind.
Edit: Okay, I first read just a couple of replies after the message I quoted to see, if this topic had been discussed further, and then wrote my reply, but I see in later messages it was mentioned, that Jolla had been asked about the topic specifically regarding the Nagara port.
2 Likes
I had seen Jolla being requested multiple times over the past 10 years to consider making AAS available for community ports. So that matter certainly isn’t new to them.
Definitely not true. It was already discussed and requested in case of several older community ports, like e.g. Tama, which has been around for years. But they never gave any meaningful answer other than they “would think about it”, with zero outcome after that.
Anyway, it is actually irrelevant if they’ve been explicitly requested or not. As a small company that’s been - allegedly - permanently starving for funds, why not simply make easy money on just selling licences, at least for ports on which it works out of box and doesn’t require any time or labour of theirs? It has always been beyond me, just like their unwillingness to start supporting commercial applications in their store and make money on it, too.
Anyway, let’s not spoil this thread and leave it for the port related discussion. Hopefully someone asks them and gets some more meaningful answer than that they’ll ‘think about it’. Let’s wait and see.
1 Like