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.
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.
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.
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.
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.
I know about that. Again postponing official release to a time after next AOSP images is slightly annoying. It was once postponed to that and we all have been patiently waiting. Then the new images have been there but still no official license.
I’m waiting for that for almost half a year now, carrying two devices with me, because only the older xperia 10 II provides app support.
I can live without camera and fingerprint. I also adapted to the battery problem. But why can’t I pay Jolla the money to get exchange, android and predictive input functionality?
Would have done that 6 months ago. Probably even used the subscription model despite missing hardware features. But why can’t I?
It doesn’t work at moment, otherwise Jolla would have released it. The big question is: are you willing to pay for a license even if you’re not getting exchange, android and predictive input functionality? Probably not, that’s why you can’t buy a license.
Actually I would buy a license if in exchange I get a clear commitment to when they’ll be able to release it and stick to that plan. They announced a working version for approx. Sept. '24. We have March '25 by now.
And concerning “not working”: AFAIK they only have issues with HW things like battery status, fingerprint sensor or camera with pre November images and other HW issues (wifi, cellphone) with November images.
I doubt that MS exchange, android app support or predictive text input has any issues with SFOS on either of those base images (please correct me, if I’m wrong here).
November images seem to be a show stopper for a mobile device, but as already said: I’m using Xperia 10 V with SFOS on pre November images as my daily driver despite not having fingerprint or camera. I miss the 3 other features mentioned above and would immidiately pay for it.
I would have paid for it on community ports of SFOS as well. Don’t know why app support is only avaible as bundle with OS itself. I always thought it should be possible to just install it on a community port as well.
At the most recent community meeting it was mentioned that a couple of sailors are on leave for the next fortnight, but then on return they would get Appsupport out the door relatively quickly for 10IV and 10V. So hopefully only a few more weeks for those people hanging or for Appsupport. See the IRC logs for the real wording.
I would pay them for the adroid functionality and the promise to work on the rest - with one requirement, weekley status updates here in the forum by the team working on it.
I can confirm that on my V phone headphone jack produces no audio output, neither with Android 14 nor with Android 15 before SFOS flashing, netiher with v3 nor v5 binaries, neither with 4.6 SFOS nor with SFOS 5. I can confirm, it never worked with SFOS
