Did you forget the tablet fiasco?
5 Likes
Oh, right. I did forget about that scam, indeed. So this is actually the second biggest fu**up in their history.
Anyway, back to the current state of 10 IV/V support, their only response to the question asked about it by one of the participants of yesterday’s community meeting was: “the new blobs also introduce issues with suspending which has been a bit problematic to solve”. And that’s it, not a single word more, and not a single word about those “completely different approaches by enabling 10 IV/V through an officially supported community port” they allegedly “have been thinking about” for over 3 months now, obviously without any perceptible outcome.
So this miserable soap opera will never end.
3 Likes
IMHO, scam is a bit much as my effected coworker got his money back together with every one else. But you’re right it was a fu**up indeed.
I have my 10 V in my backpack besides me ATM and it’s so sad that it’s nearly usable but probable stuck in this state for ever and tempting me to switch from SailfishOS to one of the open Android distributions.
I will resist for the moment but if my 10 III breaks I will be severely tempted again.
3 Likes
So, if no one starts to make a communtiyport (I dont have the skills…) than their thinking wont help either. So a community port is usually something the community builds. If you complain about that, please step in and start the port. Or explain, how a port that is done by Jolla can be a community port, perhaps I miss an information.
Missing communication and thus information is exactly the point.
2 Likes
Someone might be much more encouraged and interested in making such a community port if they at least bothered to say whether they would “officially support” it (like they speculated in November), or at least whether they would officially enable Android App support (AAS) for such a port (obviously at a regular, commercial price), about which they were asked dozens of times (not only in case of this community port but also many existing ones) but never gave any response other than that “they’d think about it”. As long as they keep trying to do some fixes and workarounds in those shitty Sony blobs, they actually make a (false?) impression that they still make some progress with their own official 10 IV/V ports, and this way they quite possibly actually DISCOURAGE people from making a community port, because who would want to invest quite a lot of work, time and effort into it if maybe not much later Jolla would come up with an official release. And this is how we already wasted 1,5 years. The 10 III case clearly shows that if something’s broken in Sony blobs, then Jolla can actually do sh*t about it and only Sony can actually fix it. Problems like 10 III’s echo in calls, display tint and color banding, etc. were actually fixed by Sony, not by Jolla. And 10 III’s high power drain remained unfixed until today because Sony no longer updates 10 III’s blobs. So expecting that Jolla alone would ever fix what’s broken in 10 IV / V Sony blobs, knowing how it looked like with the 10 III, is like waiting for Godot.
Note that this case is much different than other community ports, because those two phone models were officially announced almost 2 years ago as to be officially supported within a few months (which made quite a lot of people buy those devices specifically for that purpose), which then never materialized. So there is a special obligation in this case, to make it finally happen, at least if we assume that this is a serious company responsible for their words and actions. Or if they don’t intend to finally do something about it because they have other priorities and interests, they should at least ultimately clearly state it.
3 Likes
While I agree with everything you have said thus far, maybe this whole discussion is better in its own topic? Perhaps a mod can split the thread? I know @pherjung is the Split-meister
Maybe you’re right. On the other hand, I think it was worth pointing out that they don’t even care to mention this topic, knowing well how all the misled 10 IV and V users have been waiting for it for 1,5 years.
2 Likes
But at least, they answer and don’t ignore totally.
2 Likes
Awesome, indeed.
1 Like
But what’s the use and any real outcome of it? The 10 III case teaches us that Jolla wasn’t able to fix literally any 10 III issues originating from Sony blobs: in-call echo, display tint and banding, high power drain, GPS issues (e.g. taking ages to get fix), the whole audio system getting mute after GPS usage, fingerprint sensor acting up every now and then, and more. The first two were fixed by Sony in A12 blobs, not by Jolla, who didn’t even bother to test and start recommending those very much improved A12 blobs to be used with SFOS. On the contrary, they kept recommending A11 blobs heavily affected by those issues. As for power drain, GPS issues, etc., they remained unfixed until today and no one ever gave a **** about it.
So what kind of optimist (or sucker / pigeon) it takes to be to believe that with the 10 IV / V it’s going to look any better? The only real improvement so far was that the battery indicator started working in v4b blobs, but that - again - only because it was Sony who fixed it, not Jolla. Jolla so far (i.e. during almost 1,5 years) didn’t actually fix a thing. See e.g. that nasty bluebinder issue - suddenly starting to eat 100% of one CPU core and emptying battery within an hour or two - no one seems to care.
It looks that the plan is to keep us waiting so long that we’ll all eventually give up on the 10 IV and V. Problem solved.
9 Likes
I don’t know that Jolla is intentionally ignoring problems, but I have definitely long since given up on the 10 IV/V. I have zero hope it’s actually going anywhere. It pains me to say it but it’s clear that the phones as a whole are a tough nut to crack, not just the fingerprint sensor on the V.
Bluebinder issue is a good example and I don’t think there has been a single word from Jolla with regards to it. systemctl stopping bluebinder every time you log in after a reboot is not sustainable and really shouldn’t be necessary. I’m also 90% sure it’s the cause of the extended boot time which weirdly nobody is talking about at all, I’ve been saying it for at least a few months now.
3 Likes
Proper bug report often helps.
Well…I can serve with a list of bug reports of mine, confirmed by other users, then not even touched by Jolla for several years…
1 Like
I can easily imagine that you’re frustrated. I am too.
OTOH you gave strong examples in your text but one less strong bug report.
I optimistically bought a 10V on eBay in summer 2024, thinking I wouldn’t be waiting too long (my 10 I ‘s battery was rapidly dying). Last June I gave up and reflashed it to Android and it’s been my daily driver ever since. SFOS is never going to be usable on this phone. Lack of fingerprint unlock is a complete deal breaker, never mind the other problems.
The new Jolla phone looks nice, but I’m not going to drop €600 on a phone which will never be able to do banking or many other everyday tasks. My bank (or any other bank here) will never allow their app to run on a rooted Android never mind app support on Sailfish. So after ten years (starting with J1) for me it was a reluctant goodbye. The UI on SFOS still can’t be beat. I avoid all Google apps and use FOSS apps wherever possible, but our government and every other EU government is going down the route of making online life more or less impossible without an Android or iPhone.
3 Likes
Firstly, I am not frustrated. I am tired and annoyed by such an attitude and literally zero informative communication.
As for bug reports, I submitted like a dozen or more. Please, look up for them yourself (or at least ask for other examples in a little bit more polite way) if it is of your further personal interest. Otherwise, I do not feel the need to prove anything to you individually.
Anyway, the point was that they were never able to fix any problems originating from Sony blobs, simply because they can’t and only Sony could do. But it is less and less likely in case of 3-4 generations old models. So bug reports of such issues won’t do much, anyway.
3 Likes
Just came here to say that android apps don’t know if the bootloader is unlocked on the phone or not… Can’t get that information from native side as they run inside the container. Unfortunate to hear that in your country banks are so tied to Google. In Finland all bank apps work with AAS, so truly hit or miss by your location unfortunately. But shitty situation for you, don’t meant to downplay that. The situation with IV & V has been challenging say to least… Maybe one day….
4 Likes
Dude, chill.
Some people like the convenience that every other device can give them, it’s not a bad thing or something unheard of.
No one will point fingers to someone that is using a washing machine for example just because you are happy bashing your clothes with a bat by the river.
There are banking apps that use verification apps to compete a transaction as an example and you can’t do anything about it.
1 Like
They said at that meeting that the microphone and camera can work. Why not let flash package out where the microphone and camera can work? The official download link or the flash package, the sailfish system whose microphone and camera don’t work properly?
1 Like