Attah:
Why ‘sorry’?
After Jolla 1 I bought four Sony’s. James Noori flashed the X for me. The other three are flashed by myself. That’s five devices. Currently I have no Sailfish device that functions well enough for using as daily driver… If the new rules would have been applied earlier, I would have done at least 25 years with these five devices.
My daughters still use their iphone 6s. To be honest.
@Attah The sustainability of phones not only depends on software. And even Fairphone depends on Telecom that decides ae need 5G. Just as smartphones seemed to be fully developed Big Tech came with AI features, luring us to buy new devices. We watched the ads of the duopoly at ITV ad nauseam. Why Fairphone and Gigasets are better: it’s easy to replace the battery. The repairshop refused to change the battery of my XA2. The card slot of my XA2 plus is broken. Can’t be repaired. They don’t repair Sony phones. So yes, something has to change in the tech world.
It is polite-speak for “you are very wrong”. A very common rhetorical construct.
You say all of this like we would be able to mind-read why your phones broke, and that is a well-established fact. Requirements of VoLTE had lots of Xperia X and XA2 users posting, so evidently people can keep their phones for long. And even though i have switched maybe every 18 months before now - nothing has forced me to do so in the slightest.
The 5-year of software update rules? What do they matter when SFOS has never done under 7 even before? As far as i have seen it has no bearing on parts availability.
Other shops would have accepted.
I can’t see any relevant spares for that for Fairphone either.
@Attah,
I don’t blame you or Jolla if a Sony with Sailfish needs a repair. That would be ridiculous, so there is no need for defense on that point. By the way, I am not the only one here who experienced a refusal at an official repair shop. Someone else said this too.
I am also not the only one with five Sailfish devices in a drawer in about ten years. Concerning the software: on the XA2 and the XA2 plus GPS and video calling never worked. The 10 III that I bought and flashed has an irritating echo. You know very well that there were many bugs each time when Sailfish was ported to a new Sony . Afterwards several were solved but not all of them. So it’s not so weird saying that it could benefit Sailfish if the OS could be developed on the same device over more years.
I just wish Sailfish a future.
Could - maybe. But it is so far from guaranteed. And you are not making any particular arguments for it apart from that you think it “seems probable”.
A new port would have to make up for the changes all those intermediary Android versions for which there is no official port. Making a port for every version is optimal from that point of view, if you can at all manage. Android versions come out every year.
There is also nothing that says that more time spent will solve every type of issue. What’s more, people are already complaining about Xperias being old - imagine the average user showing up and the latest version is a 3+ year old Fairphone? I don’t think that would go down too well. You also would have to mostly subtract the age of the model of phone from how long you expect it to be supported.
No, i think the key here is better quality hardware, vendor kernels and binaries. Ideally mainline. Maybe Fairphone is it - maybe it isn’t.
Hi @mal
Thanks for your hard work on getting this to work on FP devices.
I’m considering acquiring a FP5 as my next phone and I’m curious if the source for this port are public?
Hi, @mal I was wondering if this condition persists? I was looking at getting an FP4 since I’m not able to use video reliably on the volla phones and have happily used your FP2 ports in the past.
Did compiling a kernel with these changes, or anything else, get it going for you?
if those kernel config changes are really needed I can make the changes to kernel.
Hello!
I didn’t compile the kernel, so I can’t say whether those changes are needed or not.
Which repo are you using to compile your FP4 kernel, @mal? Is it public on GitHub or somewhere similar?
I have a problem with the camera on my FP5: I manually adjusted the exposure of a picture one time. Now I always get an extremely dark picture when i open the app, just like in other apps like Fotokopierer or barcode readers. The only thing that can be seen are lights or so.
Neither a manual change of exposure nor a reboot fixes this. Furthermore, even the front camera is dark.
Try
dconf reset -f /apps/jolla-camera/
Unfortunately that didn’t change anything ![]()
I can confirm this. Just after SailfishOS installation my pictures were absolut awesome (comparing to Xperia 10 III), now they got much darker and not so crisp.
Another bug i found so far: Sometimes when the battery is low and i connect the charger the FP5 doesn’t charge. It shows the charging symbol, but the battery percentage doesn’t increase. I need to reboot the FP5 to charge.
In my case it isn’t just a little but darker or not so crisp. The photo is of my foot in a well illuminated office with flash. Without flash, nothing would be on the photo ![]()
wow, for me its not so extreme, but the quality is much better than yours, but much worse, than it was before…
I’ll have to investigate the camera issue.
Found one weird bug on FP5, don’t know if its already known: When the battery is low (under 10%) and you connect the charger - charging symbol appears, but the battery is not charged. Only after restart charging works normal.
I managed to get video recording working on both fp4 and fp5. I’ll see what is the best way the handle the needed changes and mention here when the changes have been integrated, hopefully that happens soon. I’ll also try to figure out the video playback issue on fp5.
I tried to reproduce the exposure issue but only managed to make it temporarily broken, it gets back to normal after moving manual exposure from minimum to maximum a couple of times. For me triggering the issue happens if changing picture/video mode or camera when exposure value is low.
