As someone us complaining about the double-tap-to-wake being unreliable, in principle it should support it, I guess: https://forum.fairphone.com/t/fp5-double-tap-to-wake-not-always-working/100558
Few opinions on the matter:
- Be wary of how HyperOS is connected to bootloader unlocking; there are many unknowns whether Xoxomi plans to completely cut unlocking off. I can only recall horror stories of current unlock times.
- Fairphones are, IMO, overpriced for what they offer, but it is a good candidate nonetheless.
- The Xperia 5 IV, from reviews, seems to have overheating issues, so I would avoid it.
This is actually a good suggestion and am vouching for it! Do note that porting the 5 means that 95% of the port for the 1 is done, in case you would like to support them both.
Personal tip: consider having the port stock-based if you want to take full advantage of the camera.
It would take me some time to make a decision though, but feedback noted:) - notice the period between the first post and me buying the one of the Zenfone 8 for example.
Agreed! But IV makes the list because it’s in my reach (literally, it just needs to yield ownership).
Thanks, that sounds promising! (considering we won’t have AoD)
- I am aware of HyperOS changes… I think I posted the same above. I am including that device because it is not yet Hyper but upgradable to HyperOS.
Also, as history shows (Huawei, ASUS), any company can pull the plug (or just go bankrupt) and no tethered bootloader unlocking is safe… not even Fairphone or Sony.
But yes, I now see the horror 3 days to 15 days to 2 months stories
- Agreed. But until now they Fairphone was not even desirable for me. So I think its only… fair to note the advancement in this area.
- That is some serious issue, especially if there are some android services responsible to throttle and may not run in the AOSP or hybris adaptation. Hopefully it can be nailed down to video recording or something and hopefully that doesn’t include flashlight usage. But you never know before trying what’s the next blocker bug (:ahem: Zenfone wifi)
Yes, I am aware of that. Am at least a little bit aware of the way rinigus built multiple device configs.
Nothing happens quickly so…
As I said before, there’s a delay between me thinking this throughly and posting it here till actually making a decision. You folks help me somewhat steer, but even then there are always non-rational instincts to overcome (hey, did you know Xiaomi still has an IR blaster??) even though for this exact reason I try to give marks in what I call an objective score that is still personal
1 Like
I currently use a 5 iv. The overheating is mostly when recording video, charging while doing something cpu heavy, or anything else of that sort. The vast majority of the time the phone is fine, as there were a series of software updates to address it. From my understanding it can’t be completely fixed in software since it’s just SOC itself has overheating issues even in other phones. I also have no idea how well the bug fixes would work with libhybris.
2 Likes
Nice info! Which Android version? There is a kernel version change between Android 13 and 14.
1 Like
I have the US version so we are still on 13, unfortunately. I can’t report on how 14 may or may not reflect power management. When the update hits I can update you if I see changes in either direction?
1 Like
If you only look at the bang-per-money factor, the FP can only lose, of course. From my point of view, I would say that most other phones are overpriced for what they pay the workers and for the environmental impact they have. And for the fact that they don’t offer a long warranty like the FP and may have to be replaced sooner.
But the discussion is probably going nowhere at this point. Unless Vlad would be willing to add a broader point to the list, which he/she could perhaps call “karma factor” 
Even though Fairphone may be lame or unreliable in many ways (as a company) they would probably be the last of the whole list to intentionally pull the plug on unlocking.
5 Likes
Yes! real usage info would be useful for me/us. Starting a port with a kernel or another would be a very early decision to make.
I have 8: The manufacturer is company I would like to support
And could expand this to be like 0 (Xiaomi), 0.5 (Google), 1(Sony) and give Fairphone an edge at 1.5 points. This would not give the same weight as one Fairphone supporter would consider, but it at least shows a different value.
I’m going to now play with inserting a table for the more recent posts that I can still edit, but first a new data point:
Pixel 6 and 7
Both have large enough cameras (1: 1pt), OLED screens with some tap to wake (2: 1pt), no jack, under display fingerprint reader (unknown if it can be adapted), no IR, largish battery (6: 1pt), probably real proximity sensor (7: 1pt), a company I am not sure if I want to support (8: 0.5pt), possibly popular model (9: 1pt) and notch is centered (10: 0.5 pt because centered is still better than left:).
This gives these pixels a 6pt score.
| Criteria | Pixel 6/7 |
|---|---|
| 1. Camera at least 1/1.7" | 1pt |
| 2. OLED screen with double tap to wake. | 1pt |
| 3. Headphone jack | - |
| 4. Fingerprint reader - side-mounted sensor | 0pt |
| 5. Infrared port. | - |
| 6. Largish battery - 4000+ mAh | 1pt |
| 7. Real proximity sensor (not virtual) | 1pt |
| 8. Manufacturer is company I would like to support | 0.5pt |
| 9. Model is popular enough so it helps Sailfish | 1pt |
| 10. Screen not notched / centered notch for 0.5 | 0.5pt |
| TOTAL | 6pt |
The differences between the two are probably just down to chipset/size and both chipsets are uncharted territory. The 7 is slightly smaller and has a brighter display.
3 Likes
I have a feeling it might be helpful if someone sat on your left shoulder as an angel and whispered “FP5, FP5, FP5, …” in your ear all the time to drown out your inner diabolical “Xiaomi” voice and the equally diabolical “Sony” voices of the others here, right?
I’m happy to take over: “FP5, FP5, FP5, …”
You could also break new ground for yourself (what an adventure!) by trying out the Halium route: https://forum.sailfishos.org/t/what-would-be-required-for-a-port-to-fairphone-5/17870/5
Sounds tempting, doesn’t it?
1 Like
And if you want to go on an even bigger adventure, CalyxOS is apparently as good as done with Android 14, as far as I understand it:
I bought Fairphone 5 and hope that there will be a port to sailfish :-))))
Will that be before or after universal peace on earth and trains arriving in time?
1 Like
After the Russians attacked NATO 
1 Like
Since there is Lineage 20 for Unihertz Titan, Pocket and Slim, maybe for someone would be interesting to have a Blackberry-like device with keyboard and port SailfishOS to it.
1 Like
That is a very interesting device, I see contrasting pros and cons to it.
First, it seems this is really untethered unlocking, no need to ask for a code to a remote service (on simple initial scrutinity). Second, it has keyboard, and front facing fingerprint sensor inside, and at least the Slim I looked at has scrolling behaviour on that keyboard too. And last, at least the Slim seems to have infrared port. Great job!
But there are some negatives I see… the build quality and the device thickness would be one, the LCD panel and the lack of brightness another, performance (usually not a problem in SFOS per se) of the Helio chipset (this might be a problem with some codepaths assuming qcom - but again, there are other Mediatek ports so maybe that’s not a worry).
Also, as much as I enjoy hardware keyboards (I had a BB Passport once, so with tactile keys too), there is little info on the cameras - and I don’t count megapixels, I only look at sensor size, and that is not available info. Probably 2020’s 1/2.55" equivalent as they are all over the place (Actually I’m wrong, it’s 1/2" according to techradar there’s a S5KGM1). Back to keyboard, it would have been nice to have a keyboard directly usable in Terminal app… but that’s the curse of mobile devices, not enough symbols on the kayboard:))
| Criteria | Uniherz Titan Slim |
|---|---|
| 1. Camera at least 1/1.7" | - |
| 2. OLED screen with double tap to wake. | - |
| 3. Headphone jack | - |
| 4. Fingerprint reader - front-mounted sensor | 1pt |
| 5. Infrared port. | 1pt |
| 6. Largish battery - 4000+ mAh | 1pt |
| 7. Real proximity sensor (not virtual ) | 1pt |
| 8. Manufacturer is company I would like to support | 1pt |
| 9. Model is popular enough so it helps Sailfish | - |
| 10. Screen not notched / centered notch for 0.5 | 1pt |
| TOTAL | 6pt |
This is the same as Pixel 6/7 but for surprising reasons.
One of the not visible things is that the displays are even smaller than the smallest full touch screen devices so I may stay clear from these… also, IPS.
@Kuba77 do you have a such device, can you comment on build quality, screen, camera vs a known sfos phone for the community?
1 Like
No, I don’t have. I just randomly found Unihertz devices and searched if Lineage is available for them.
I just received the Andrdoid 14 update on my 5iv. I ran multiple successive Geekbench runs of both CPU & GPU. I took it out of my case. It was a bit warm to the touch, but it wasn’t anything so warm it would prevent me from using it. The biggest issue, from my understanding was 4k video recording whilst plugged in. I did a test recording while on the charger for about 10 minutes. I didn’t feel it being unreasonably warm still, but it was warmer than just running the benchmarks. Naturally, mileage may vary, but I am not seeing a huge issue with the heat. I don’t have anything installed to track temperature, so this would be an entirely subjective take on it. I hope that helps you regardless.
1 Like
@dreimeterfeldweg I enjoyed your reply very much. There are two things that hold me from doing this port, and one is owning the device (solvable) and the other one is time (negotiable).
Also, as you notice, I do not yet have what I call “1st world itches”, but living in a close neighborhood makes me sympathetic to that.
So, my plan is to get the device through a NLnet grant. I have written a draft of the application here - you need a codeberg account to comment and suggest.
I also know from the other thread that mal already has the device, but from experience he is one with the less amount of time…
So, if you can help shape up the NLNet application and it is approved, then I would only need that time negotiation part (and a bit of 
) to deliver a port.
LE: application posted
3 Likes
Thanks @twzorek for the detailed testing! As you can see the actual device is not yet set in stone, it depends…
Very nice, I’ll have a look tomorrow!