The Fairphone 3+ is a repairable dream that takes beautiful photos
gizmodo.com
gizmodo.com
https://en.wikipedia.org/wiki/Android_One
Nokia is the only manufacturer that seems to have a whole range on it, and even they are messing with Android.
I totally agree with your assessment. So does Fairphone. That's why we trying to address both issues with a modular design for ease of repairs and long lasting software updates.
Have a look at our current effort to bring continued software updates to our five year old predecessor Fairphone 2: https://www.fairphone.com/en/2020/06/18/fairphone-2-gets-and...
I suspect that the outdated downstream 3.4 kernel isn't even getting security fixes, so the QualPwn root takeover vulnerability (among many others) would be unpatched.
A big step in the right direction would be to work with Linaro, postmarketOS, and other parties actively involved in mainlining Qualcomm chipsets to forward-port the old SoC to a mainline kernel, or at least to a newer downstream Qualcomm kernel version. It's not trivial, but it's possible; I've ported my Pixel 2 XL with a Snapdragon 835 (kernel 4.4) to the 855's kernel version (4.14) with most features working. I never got around to finishing it and polishing it for daily use, but an actual company like Fairphone should have the resources to do so. In fact, there is already a WIP port of the FP2 to pmOS with a mainline kernel [2], and there's more mainlining work for it that has a decent amount of features working [3].
While this doesn't solve the firmware problems (which really can't be dealt with as even OEMs don't get a lot of the source code for the firmware), it still improves security (and performance!) by a lot since most severe vulnerabilities that users are most likely to be hit by are in the kernel. I think this is ultimately going to be the right way to go if Fairphone wants to keep updating devices for so long and patching as many security issues as possible.
Perhaps Fairphone could also negotiate a long-term support contract with Qualcomm? I noticed that the mid-range Snapdragon 660 that started on kernel 4.4 was officially forward-ported to kernel 4.14, probably due to some vendor requesting it.
Don't get me wrong: it's already much better than other manufacturers, and the BSP support problem is out of Fairphone's control, but it's still possible to make the best of the situation on the software side without relying on Qualcomm as much.
[1] https://blade.tencent.com/en/advisories/qualpwn/
[2] https://wiki.postmarketos.org/wiki/Fairphone_2_(fairphone-fp...
[3] https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_800/8...
We did indeed talk to other interested parties and attempted forward ports of the Qualcomm specific kernel features to LTS versions. I am not directly involved in that team anymore and sadly cannot tell you the exact reasons, but this failed to yield a usable kernel.
I do like your suggestion of long-term support from Qualcomm which was unfortunately not possible for the Snapdragon 801. For Fairphone 3, this is hopefully on the table again (especially, if — as you are saying — other customers also show interest in LTS support).
In summary, you make many great suggestions most of which we also attempted at some point. Unfortunately, the devil is often in the details.
[1] https://www.clove.co.uk/collections/smartphones/products/fai...
> At present, Fairphone doesn’t support 4G connectivity in the U.S.
FP3/FP3+ Network specifications
In case you need it for your specific situation, the network specifications for the FP3/FP3+:
Configuration Dual-SIM, Dual-Standby (DSDS)
SIM Sockets 2 x Nano-SIM (4FF)
Network Technology 2G / 3G / 4G LTE - Advanced
GSM/GPRS/EDGE Quad-band: 850, 900, 1800, 1900 MHz
UMTS: Band 1 (2100 MHz); Band 2 (900 MHz); Band 5 (850MHz); Band 8 (900 MHz)
3G Max Downlink Speed - 42 Mbps
3G Max Uplink - 11 Mbps
4G / LTE Advanced Band 1 / 2 / 3 / 4 / 5 / 7 / 13 / 20 / 26
4G Max Downlink Speed - 300 Mbps
4G Max Uplink Speed - 75 Mbps
Source: https://support.fairphone.com/hc/en-us/articles/360047326452Nowadays the barrier for entry is much higher. Most things are soldered on, there's adhesive and sealing gaskets EVERYWHERE (fancy heating machines help, but cost $$), and even if you get it back together you can no longer count on the device being waterproof -- which is surprisingly a big deal for a lot of people, even though waterproof phones are a recent thing.
Prepare the substrate, use the right silicone for your materials, use gap-preventing technique, and you can make it happen with high reliability even if you don't have an ultrasound to check your work. Your grandpa didn't have an ultrasound and his automotive gaskets had to put up with a lot more abuse than your phone ever will. There was no magic then and there's no magic now. You can do it too.
And don't even get me started on iPads, the screens never go back on right. I flatly refuse to work on them anymore.
Waterproof phones might be a real thing, but dropping phones in water isn't. It used to be that certain clumsy friends of mine would write off a phone by dropping it in the toilet every few months. Most phones will survive this now.
Though this new batch of tinker friendly devices like Fairphone or Pinephone is something I track with interest. Main issue with phones getting obsolete is not hardware though as it is software. That keeps me hopeful especially regarding Pinephone, but Fairphone keeps updates significantly longer than run of the mill Android phones.
They are all too big for my taste, but that's a different subject altogether. I would like to see something in Unihertz Jelly 2 format. But for now I will stick to beat down phones.
But the number and complexity of tools has increased a lot. Used to take 2 screwdrivers to fix a phone or a laptop. Now you need special screwdrivers, a heat gun, pry tools, glue, small tweezers at least.
And a whole BGA rework station if you want to replace components with a decent quality of work.
Sure, but can you reassemble it after the disassembly? There are certainly products for which that is essentially impossible: https://www.ifixit.com/Teardown/AirPods+2+Teardown/121471
It's the same in that loads of people say it's impossible when it actually just requires a new bag of tricks.
[1]https://www.extremetech.com/computing/280501-apple-confirms-...
I had a hell of a time trying to get someone to fix my Blackberry (long story) a few years ago (longer story) even though every store said they could handle it. They could not.
> The problem, an Apple repair representative explained, is that an open-for-business repair partner might still have to send the device into Apple anyway, a process that could have left me without a phone for well over a week and possibly longer.
Much like the apple stores, Apple forces AASPs to declare everything a mainboard repair and ship the devices in, forbidding them from doing simple port swaps and such.
https://www.youtube.com/watch?v=g_Dkzj10jeA
The officially refurbed mainboards have exceedingly low quality to boot. That same youtuber has run into official refurbs with rubber pads to push intermittent connections into position, boards that were clearly left in the oven over lunch break, and so on. Someone wrote in from the refurb center, which is apparently run like a sweatshop with competitive quotas that make shoddy refurbishing and "run it on the test bench again, it might work" nonsense inevitable. It's bad.
Apple Authorized repair doesn't exist to repair your device, it exists to persuade you to buy a new device.
The mic and camera repeatedly failed. Wiggling and cleaning the contacts worked occasionally. We also bought new mic and camera modules. Ironically the repairabiilty compromised the reliability.
The last time it broke we bought a refurbished iPhone.
It's unfortunate but I think they had to go through each iteration to make it work better, I think they've found a sweet spot now. It's too low spec for my taste, but good enough for any other member of my family
I'd buy a Fairphone again if they'd fixed those issues.
I assumed that the issues with pogo pins were likely to do with corrosion (tarnishing) on the PCB pads affecting the contact. And that I have't let the experience affect my view of Fairphone enough to prevent me buying one in future.
> Fairphone hopes that its phones can stretch that length of time to between five and seven years, in part by making phones that aren’t disposable by design.
Does anyone have a 5 year old Fairphone? How are they able to keep software updates coming while every other Android maker is making a huge deal out of 3 years of support?
For details read https://www.fairphone.com/en/2020/06/18/fairphone-2-gets-and...
> Qualcomm is no longer supporting the chipset in the Fairphone 2, we have to make Android 9 comply with all of Google’s requirements ourselves
That's why it took longer and why it's not android 10.
I went for a Fairphone 3 because I could afford it, because I support its values, and because its spec is more than enough for me. Six months in and I've no doubts about whether it was the right decision. I'd very much recommend it.
I'd love to see stats on device longevity versus the iPhone. In 3-5 years. I do get frustrated with having to replace devices every few years, but I don't think I'd make the same choice you did. Paying a premium for a device which is tied to a 2 year old version of Android with 3G is a tough pill to swallow.
The SE 2 won't be found on the second hand market anytime soon.
Ask me in 2025 how well they've held up.
EDIT: Oh, and the phone HAS 4G, just not in the US.
I don't need 5G, but 3G is a bit too slow. I mean that's going back in time a decade (literally).
When my X Play died, I did look into getting a Fairphone, but they weren't selling at the time, and I needed a new phone that wasn't be another 2-3 months away.
Hopefully it will be a long time before I buy another phone, but I am keeping an eye on Fairphone, Pinepone and the Purism phone. Especially Fairphone has really come a long way and have a really compelling product now.
I do need some apps from the Play Store, most can be worked around in a decent web browser with somewhat reduced comfort (FB Messenger for instance), but others demand the app (mobile payments and short-term car rental/sharing here in Denmark), so for the moment I have to stick with the Android ecosystem.
Maybe I just need to cold turkey the whole thing.
Is it the case that Fairphone 2 is only on Android 7.1? I understand it's modified, but I don't think we can consider that really supported with updates with an OS that old.
* Major version upgrades ("cookie upgrades") and * Security updates
Fairphone 2 still receives security updates for Android 7 and Android 9 for Fairphone 2 is in beta.
The hardware support was EOL'd due to supply chain issues: https://www.fairphone.com/en/2017/07/20/why-we-had-to-stop-s...
For subsequent devices (FP2 and FP3) the situation has improved a bit but frankly, long term support from Qualcomm is also non-existent. We are still struggling to bring updates to the old platform of FP2.
The thing I wanted to bring attention to is the author said the phone's memory was 64GB, expandable to 400GB with a MicroSD card. He should be using the word storage. Phone adverts should be using the word storage. The technical specs pages on the phone manufacturer should be using the word storage. Phone reviewers should be using the word storage and not memory, because they aren't talking about Random Access Memory (RAM).
Amount of RAM is the only spec for phones sold today that indicate whether or not it can be responsive while running both Chrome, Facebook, and GPS simultaneously. If every mobile phone sold on earth was like the Fairphone, then this would be the one deciding factor for me - and it's a detail, that for some absurd reason, is ommited from the article.
Sorry to go off on this tangent, but yeah, probably. I've been trying to use Firefox for Android recently and it's just been pretty bad. Social media sites (Twitter, Reddit) all seem almost unusably bad in it, frequently becoming unresponsive. Certain features like text highlighting not working in form fields on some sites is common. And I get they're bloated, and in Reddit's case deliberately annoying, but Chrome for Android at least produces a reasonable experience.
Edit: having tried the site in both browsers - the site itself is pretty anti-user in both browsers, but in chrome seems to be more or less okay-ish after giving it a little while to load.
sadly yes. firefox on android is unusable. really, really unusable.
Mozilla is continuing the war against its own mobile users. The problem is, it's winning.