Happy FairPhone 4 user here. Running 3+ years, only replaced the battery once. Aim to keep it 7-10 years, barring unforeseen events like theft. Not going to replace it just because a newer model is released.
That's a lot, I usually use old phones from family members, most of them have 4 years of use by the time I get them and I get a whole day of usage from the battery.
Many important security updates will end much earlier. The table is based on how long Fairphone will provide incomplete security updates, not how long the device will truly receive security support.
Fairphone 5 and earlier have end-of-life Linux kernel branches without security support. Fairphone's more recent devices are headed to the same situation. In practice, the same thing happens with other components beyond the Linux kernel.
GrapheneOS is like a veteran and war zone expert: for them, not only the external environment is considered extremely hostile that you should leave your house only wearing an armor and with bodyguards, but also the internal environment is hostile: your bodyguards could be bribed and work against you, that's why you need to somehow be protected against that as well.
Just as physical security, digital security most of the time not as radical, and tradeoffs are usually accepted, especially when they are "invisible": hardware and software security features are usually not mentioned in the specs and the regular and even power user just don't know most of them and what do they do.
When GrapheneOS says "private" and "secure", they mean top-of-the-line security features, updates as soon as possible, all available mitigations against zero-days and insecure code which will limit the impact before the patch, etc. Security as in a killdozer.
When other say "private" and "secure", most of the time it means: "we've followed all the recommendations applicable to our development budget, device price point, and support life time". Graphene does not like that definition of these words.
For smartphone, chip manufacturer goal is not to protect the user at all costs, but to provide reasonable security features for the price.
BUT the goal of chip manufacturer to protect the device at all costs is for… game consoles! That's why Xbox, PlayStation, Switch all run on a custom silicon and not an ordinary chips!
> That's why Xbox, PlayStation, Switch all run on a custom silicon and not an ordinary chips!
Not really. Xbox and PlayStation both run on pretty standard AMD Zen 2 chips. Somewhat customized, but standard enough that people by binned playstation 5 motherboards to use as computers with normal OS'es (lookup BC-250). The last gen with more customized chips was the PS3/Xbox360 era, when both went with a variant of PowerPC, same as Gamecube/Wii/WiiU.
Switch runs on basically the same Nvidia Tegra CPU/GPU as multiple android tablets.
It is a foundational reality that software (especially in unsafe languages) will invariably have vulnerabilities. Defense in depth and least privilege have compounding effects by forcing attackers to chain multiple exploits to achieve a compromised device, rather than a single vulnerability.
GrapheneOS shows how much can be accomplished on top of relatively secure platforms to begin with (AOSP, Pixel Stock OS, etc.) without sacrificing nearly any usability to the end user (barring manufactured hurdles like Play Integrity). It makes it more damning that many "privacy" OSes and devices cannot even meet the baseline level of privacy and security that AOSP provides, but degrade it.
Firmware and driver neglect and the lack of secure element utilization is not "reasonble security for the price".
>GrapheneOS is like a veteran and war zone expert: for them, not only the external environment is considered extremely hostile that you should leave your house only wearing an armor and with bodyguards, but also the internal environment is hostile: your bodyguards could be bribed and work against you, that's why you need to somehow be protected against that as well.
Yeah, iPhoens are made that way as well. It's just caring about the privacy of your users.
> When GrapheneOS says "private" and "secure", they mean top-of-the-line security features, updates as soon as possible, all available mitigations against zero-days and insecure code which will limit the impact before the patch, etc. Security as in a killdozer.
I think it's deceptive because people think they will get better privacy/security with a /e/ fairphone when it's actually much worse than an iPhone.
Fairphone makes their fair share of blunders. Software updates are a big issue, especially around the times that critical vulnerabilities need to be patched.
With the hardware I'm not impressed, and on their own forum I've seen plenty of people reporting issues with overheating on the Gen 6. Hopefully kinks have been ironed out on their 6+.
The current CEO also has a persona that would stir up any community (read a few of his AI-gened posts on their blog, if interested of context).
Still holding on to my FP4, but they are not of consideration on my future phone purchase, unless there is some kind of reality check over there and improvements materialize beyond words.
Ultimately, a lot of the “fairness”
of the Fairphone is offered by “just buy a really popular manufacturer.”
Everyone and their dog can repair an iPhone because it’s the most popular phone on the planet. Are those repairs accessible to the consumer at home with amateur skills? No, not really. However, newer iPhone models are significantly easier to repair and come along with lower repair costs direct from the manufacturer compared to previous models.
You want years of software updates? Yeah, an iPhone has you covered there, too.
And of course, fairphone’s hardware and OS are nothing to write home about. For the freedom and security nerds they’re better off with GrapheneOS on Pixel or whatever upcoming Motorola phones will support it.
Who is the Fairphone for exactly? Who is buying it and why?
I think the fairbuds are their best product, but I also imagine AirPods Pro 3 are on a whole different level of sound quality, noise cancelation, voice quality/voice isolation, and firmware/software polish.
And let’s be honest about repairability with tiny earbuds: being able to replace the battery is has such a tiny impact on their footprint. If I have to throw out my
AirPods Pro 3 every 5 years due to battery degradation, that’s such an insignificant quantity of material being wasted, so it’s probably worth it to get a better product. I could offset my environmental impact by eating a little less beef or riding my bike instead of driving a few times. You drive 30 miles and that’s an entire gallon of refined petroleum product, how much material and energy is used to make one pair of AirPods? I can’t imagine it’s a lot.
I don’t say any of this to be a big corporate or Apple shill. I am rooting for the little guys. But the little guys need to be realistic. You look at products like the Framework 13 Pro and you can actually say, okay, here’s a product with really legitimate benefits over its incumbent competition. There is a reason to buy this product for a certain buyer. I just don’t see that with Fairphone. I can’t think of a customer profile where that person is getting a better ownership experience with Fairphone products.
The GOS people really spend a lot of time of energy showing the worst sides of FairPhone to the world. I think it is because the conscientious technology user is really interested in the combination of ethically sourced, repairable hardware and a security and privacy (from big tech) focussed OS. Tbh I also like that sliders to switch to a simple mode. A well, we can’t have it all. I do prefer de-googled + freedom to do what I want over security (to a degree). So… I’m on the fence. As many vocal people are. A second hand pixel 10 is also a “green” choice.
I do have the feeling that many non-nerds can express the difference between all mentioned attributes, many just like FairPhone as an ethical phone. It’s not that simple, I agree.
So I have been on /e/OS on a Fairphone 3+ for 4.5 years. I was really into /e/OS when I got my Fairphone. When it stopped being usable (not because the hardware was not working anymore, just that the apps I want on my phone were lagging so much they were unusable), I looked into alternatives, including GrapheneOS.
And at that point I got quite disappointed by /e/OS, because I felt like their marketing had been abusing me for years. For instance, my Fairphone 3+ was 4 years behind the Fairphone Stock Android on some updates. /e/OS just wasn't forwarding them, they seemingly were just not maintaining the FP3. Though I bought it to /e/OS, under the promise that it would be supported!
Then I realised that all this time, not only my bootloader was unlocked (so the Android security model had been broken from the first day I powered the phone), but the system was signed with the Google test keys! When you are encouraged to install apps "from the internet" instead of the Play Store, on a phone that disabled the security model so that you're not protected against malware as on any Stock Android, would you say it's being a security nerd?
The thing that GrapheneOS keeps repeating and I realised is true is that many times, if you run a deGoogled alternative that is not GrapheneOS, you get worse security than if you were running Stock Android. It's not about "getting the best possible security", it's about getting the baseline. The truth with /e/OS (or LineageOS, which is pretty much what /e/OS ships, I believe?) is that it depends a lot on the phone. And with many phones, you get worse than the baseline you would get with Stock Android.
> I do prefer de-googled + freedom to do what I want over security (to a degree).
So I switched to GrapheneOS on a Pixel, and I feel like I get the best of both worlds: I get the privacy benefits of the sandboxed Play Services, and the better security. And it's not a "weird" system at all: I asked my family to use it and they didn't realise it was not a "normal Android". It is very different from running something like a Linux on mobile, which would be very very different.
> many just like FairPhone as an ethical phone
Yes, why not. If I was to get a Fairphone again, though, I would use the Stock Android.
And I wish Fairphone could get to the level where they can be supported by GrapheneOS. But it feels like my next phone will probably be a Motorola with GrapheneOS rather than a Fairphone.
Fairphones are closed source hardware with closed source firmware and closed source userspace drivers. Fairphones are less open than Pixels, not more open.
It isn't truly known how a Fairphone compares to an iPhone or Pixel when it comes to environmental impact or fairness to workers. Fairphones are designed and built by T2Mobile since the Fairphone 4. T2Mobile barely has any public information available about it. There isn't information on the working conditions, pay and other aspects of of it. The same applies to the rest of the supply chain. Fairphone provides a list of companies involved in the supply chain without details.
I really would like to mention that many times, using /e/OS or LineageOS (or the likes) means that you get worse security than Stock Android.
It would be fine to run /e/OS or LineageOS on a Pixel, assuming those Android systems are not too slow with updates (my experience with my /e/OS phone was that they were 4 years behind as compared to Stock Android).
But really, if you have a Pixel, it doesn't really make sense to use something other than GrapheneOS IMO.
> It's not like any other device meets their ridiculous standards either
I don't think it's ridiculous to want the ability to relock the bootloader, for instance? Do you realise that if you cannot do that, you just break the whole Android security model right away?
There are devices meeting these basic standards right now, and the entire family of them, no less.
GOS are vocal about safety and security of all the devices, not just seriously insecure Fairphones, and this article is about something different altogether, that's misinformation they've been hit with several times.
Fair criticism is fair, but yours is fabrications.
Android Open Source Project userspace code runs on any devices with Treble. That means it runs on any certified Android devices with the ability to install another OS. Updates and security features for the Linux kernel, drivers, firmware and hardware are still needed.
Fairphone 5 and earlier have end-of-life Linux kernel branches without security support. Those lag multiple years behind on providing full Android security updates. The 1-2 month delays for partial security backports is compared to the Android security bulletins and is actually a much longer delay compared to when the patches are made available to ship by OEMs.
> they also compare the security to the "Android Open Source Project" as if it's a real thing
It is very much a real thing. You can build AOSP from sources and install it on a phone. Many Android devices run that (e.g. drone controllers).
> Is certainly much better than my Samsung flagship
Oh yeah, that's for sure. To share my experience, in terms of updates for me it has been GrapheneOS >>> Stock Android > /e/OS. I was running LineageOS/Cyanogen a decade ago but I don't remember and it was a different time anyway.
I suppose it's a testament to their success, but, I have a fairphone 3 from almost 6 years now, and I'm a bit annoyed that they're basically "sunsetting it" (no more software updates, no more spare parts.)
My fairphone 2 had lasted 5 years, but was completely unusable at the end. My current phone works very well (again, huge kudos to the team if anyone is reading this), and I would not mind trying to reach the decade with it - but in a few months, someone (my bank, a shop, a 2FA, whatever) will ask for an unsupported android feature.
I know people will give me names of exotic non-android distros, but will they run my bank's app :/ ?
I had a similar experience but with the Fairphone 2. I never swapped out any parts because performance hardware upgrades never became available and it was superseded by the Fairphone 3. I've not invested again in a Fairphone since. I've no interest in paying extra for repairability I'm never going to use since they have the same obsolescence/replacement model as any other phone.
Fairphone 5 are already in a similar situation due to the kernels no longer having security support with no plan to take it over or move to a newer branch. Fairphone's more recent devices are headed to the same situation. The same thing happens with other components beyond the Linux kernel. People are using the devices with the belief they're receiving security support that's not being provided.
The recently released Fairphone 6+ runs on Android 16. I had to look that up on Wikipedia, their website doesn't even clearly state that. Android 16 is 14 months old at the moment. Android 17 was released to manufacturers 6 months ago and had a general release 2 months ago.
So why does a brand new phone run an operating system from over a year ago? Does it really take over 6 months to update a phone to a new version of Android?
How am I supposed to believe a company is committing to supporting a phone for a long time when at release it already runs outdated software?
Getting security updates for issues that are not marked high/critical. These are not your typical RCE, but they are used in exploit chains.
For those not aware, Android Security Bulletins only cover high/critical vulnerabilities. There are also rumors that Google will soon stop fixing vulnerabilities in not-actual versions that were discovered by Google in LLM-driven vulnerability discovery. There was recently a GrapheneOS thread about it.
Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that's decreasing. Android 17 is also required for the latest and greatest privacy/security protections which are not backported. There have been massive privacy and security improvements in each yearly Android release.
I belive you are mistaken. Android 17 final was "released" 6-7 weeks ago.
But Google being Google, this release is pretty much useless until Samsung et al deal with all bugs and performance issues, which will take 2-4 months.
As a Linux, macOS and Windows user it’s really strange to me that you can’t just install the latest OS on your device. Even my iPhone updates to the latest version as soon as it’s released.
Certification takes time and probably overlaped with the phone development. Fairephone is small compared to e.g. samsung and they describe themself more "stable" and long-term support than bleeding edge.
Fairphone 5 and earlier also have end-of-life Linux kernel branches without security support. Fairphone's more recent devices are headed to the same situation. In practice, the same thing happens with other components beyond the Linux kernel.
Fairphones have 1-2 months of delay for partial security backports to older releases from the beginning and much longer delays for full updates. Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that subset is decreasing.
Android 17 is also required for the latest and greatest privacy/security protections which are not backported. There have been massive privacy and security improvements in each yearly Android release.
Even worse: Google actually does four releases releases per year (major and QPRs), of which QPR2 is also provided to OEMs. Only Samsung and GrapheneOS roll out QPR2 releases.
If this were genuinely 100% a Qualcomm limitation, I'd expect every Snapdragon 7s Gen 4 phone to be similarly stuck. But Motorola's Edge 70 Fusion uses the same SoC and was already in Android 17 beta testing in February, and Nothing's Phone (4a) and OnePlus Nord CE 6 are also slated for Android 17. So it seems the SoC isn't inherently preventing Android 17.
Great what they are doing - yet I found Shiftphone to be also fair, equally or better repairable and even more open for alternative Operating Systems. I think Fairphone supports 2 OSes officially, Shiftphone has a whole custom ROM list of ~10.
Ten? So like Android and Linux flavors? I'm not sure I even know of ten: e/OS, Calyx, Lineage, Ubuntu Touch, eh is there like Mobian or something still alive... how do they get to ten?? Do they also all fully work? Camera and calling (and not only on 2G) for example?
I'd be interested in the list, the website you've linked is super sparse (the full menu is like shop, some feel-good pages about device deposit and impact, blog, and contact us - no knowledge base, documentation, or somewhere where you'd expect to find OS info or even downloads)
Anyone have any updates on why this device can’t support or get behind Graphene OS? A repairable and secure phone is my desired option for a phone that’s truely mine and I’m sure this is true for many others also.
From my understanding it’s not there as the Graphene team says that fairphone haven’t taken security hardware seriously and there’s key hardware security features missing that means they are not even interested to look at supporting the device.
Keen for latest updates on this, happy to be corrected.
While yes I am on GrapheneOS' side on these issues, I'm surprised nobody clones the GrapheneOS repo and simply disables the minimal handful of features which block it from working on devices. Maybe calling the clone CarbonOS? If MTE is required to boot GrapheneOS and Fairphones don't have MTE, then Fairphone clones GrapheneOS and disables MTE for its images. Graphene has so many features beyond just hardware security that other Androids lack, that it would be worthwhile to do this and it would still be higher security than the others (even if it's below GrapheneOS' own full security). Sensor & network permissions, storage & contact scopes, autoreboot, scrambled pin, radio auto-off, MAC address randomization, and more, I'm sure don't require MTE or Titan etc. Just follow GrapheneOS as upstream, making sure that the minimal set of changes needed to get it working on other/older devices transfers with the new updates.
MTE is not the only blocker here. Pixel 7 series do not have it and are currently supported by GrapheneOS. There are other concerns regarding things like a proper secure element implementation and timely firmware/binary blob updates.
That's highly inaccurate information. MTE is included on a large number of smartphones beyond Pixels. It's heavily integrated into iOS on the iPhone 17 as their Memory Integration Enforcement feature. MTE enables massive security improvements against exploits and Pixels have had it since the Pixel 8 in October 2023.
Traditional desktop computers have atrocious privacy and security throughout hardware, firmware and software. That isn't a relevant comparison for GrapheneOS. Recent Mac hardware does support MTE and so will non-Mac devices using Snapdragon chips. Qualcomm has added MTE support for their latest flagship mobile SoC platform and will bring it elsewhere. MediaTek and Exynos have also added MTE support.
MTE does not have the substantial performance or battery life impact you're portraying it as having. It's also far more useful than you're portraying it as being. Apple would not have extensively integrated MTE if they had to give up significant performance or battery life. iPhones have a lot of focus on security but aren't willing to make significant sacrifices in those areas for it, at least for the default settings. Their Memory Integrity Enforcement entirely based on MTE is always enabled in the kernel and the large portion of userspace where they deployed it. It's not only used for Lockdown Mode.
I've always been a bit curious about Fairphone, but as I only get phones that cost less than $200 (and use them until they physically break), I'll probably never get one.
Still only on my second smartphone, so I'm not worried about producing more e-waste.
Are ya'll really repairing your phones? I replace mine when it can't run Google Maps smoothly anymore.
After 4-5 years, on every phone I've ever had, user interactions begin to lag noticeably. Apps launch much more slowly. Intense graphical apps like maps become frustrating to use. At some point I can't take it anymore and replace the phone, long before its physical parts or battery have worn out.
I've bought new a Google Pixel 7a two years ago, paid for it 400 euros. After 1 year I've dropped it, landed on a corner, screen completely broken, replacement costed screen costed me nearly 120 euros (and was not an original screen, otherwise I would have spent more). Just costs much money because of the fucking fingerprint reader under the screen that why couldn't put it in the back of the phone as they did for many years. Broken it again, fuck it I will not repair it again, with the cost of the repair I may as well buy a new phone.
Then I've decided that is worth either spending money on phones whose replacement parts doesn't cost half of the phone itself, or just buying the cheapest Xiaomi or similar chineese brand phone and when it breaks buy a new one or repair it (funny enough cheap phones are more repairable than expensive ones, so I usually repair them).
I've replaced batteries on Pixel 3 XL and Pixel 6 Pro, both having run GrapheneOS. I use OSMAnd~ with no network permission (except during maps/POI updates). OSMAnd~ shows me where ALPRs are, so I can plan my routes around Flock. :^)
My family's Pixels have all lasted physically long enough for Google to stop supporting them. My wife was annoyed when I told her she needed a new one because from her perspective there was nothing wrong with her existing one ( lack of security updates is not on her radar.)
Genuinely, how do you make your phone so slow? I've been using my s10 for 7 years, and besides the minor crack in the corner of the screen from being dropped, and constantly juggling storage because I hoard media, it works as well as it did when it was new.
I had the same experience. Repeatedly. IMO it's the software, not the hardware. The issues always start/get worse with a big update to Android or the main Google apps.
The Fairphone 6+ looks really interesting but I'm not seeing it having the ability to wirelessly charge. I exclusively charge my Pixel 10 XL Pro (25w+) phone on a wireless charger now in the car and at my house and really like it, I don't want to go back to plugging in a USBC cable anymore unless it's an emergency. Am I missing something? Does it support Qi 2?
Was really happy with my FP3 until it died: "sudden death". No power, nothing. According to their own forum, it's a very common problem after a while. Of course there is no warranty and replacing the mainboard is not possible...
You always have the right to a minimum 2-year guarantee from the moment you received the goods. However, national rules in your country may give you extra protection.[1]
Would be neat if Fairphone would build a real compact smartphone, something with 4" or 5" screen. Current device is too large for human pockets and all those protruding camera bumps and buttons are really uncomfortable.
Fairphone issue an annual director's report, has financial audits and list the titles of each director. You can easily find the name of and information about the CEO. They have an Impressum section on their site along with many other legal documents.
This is more than can be said about other projects in this space
I would love a Fairphone, but no headphone jack is a nonstarter for me. Still blows me away that a company saying they are focused on longevity would get rid of a universal audio interface that we've had for decades. In the article they claim it's to fit other features in, but frankly that's not a believable claim. Other manufacturers manage to get a headphone jack in just fine, without any noticeable downside.
The headphone jack is inside USB-C connector. You can use USB-C-to-3.5mm passive (!) cable to connect your 3.5mm headphones, or you can buy 3.5mm headphones with USB-C audio connection.
There's no additional DAC involved, the analog audio is already on a USB-C pins.
I can't find anything about that in the article or the Fairphone 6 manual. Do you have a source for this?
My main problem with USB-C headphones on my Android phone is how unreliable they are. But if the USB-C port can just pass through an analog audio connection, that should work much better, I expect.
At this point headphones with an usb-c connection have become nearly as common as 3.5mm trs ones. Additionally you can permamently hook a small usb-c dac with 3.5mm trs output to the headphones of your choice.
Only issue is some very cheap ones are actually bluetooth headphones in disguise where the usb-c connection only exist to power the bt recepter inside the headphone. I find this completely stupid.
> If there are tradeoffs, if would be nice if the customers can decide what to have, in a modular product.
A "modular product" has tradeoffs in and of itself (such as size, price, water resistance, …), which presumably would not fly for a majority of customers.
Given how severely that hard requirement restricts your available options, I'd suggest adapting to the USB-C audio world. No, it's not as nice as a headphone jack. But it is a relatively small con to just stick an adapter onto the ends of your 3.5mm devices and replace it a few times a year when it breaks. And yes, you can get a "charge and listen at the same time" adapter.
Linux is a kernel. Embedded, server and mobile Linux distributions without glibc, gcc, GNU coreutils, systemd, D-Bus, Wayland, Pipewire, etc. are Linux too. Linux is not a specific desktop software stack that's largely used on FreeBSD and elsewhere too. Android Open Source Project and GrapheneOS are Linux distributions.
It’s both superior engineering-wise and morally. The moral framing is probably more popular with folks that don’t care about engineering superiority, too.
Surely it's morally superior to limit resource use by using things for longer and repairing them when broken. I often use a weak Kantian Imperative that I couch as "if everyone did what you do would it be good, sustainable?" as a _guide_ to moral choice, it's a starting point really, but from that I think moral superiority of more repairable goods follows.
There’s a get-out clause in the law that allows your battery not to be required to be user replaceable if it can last 1,000 cycles while remaining at 80+%. Apple’s phones certainly meet that these days, and I imagine Samsung’s will as well (though I’m not sure if silicon carbide changes that at all).
Parts for the Fairphone 2 (2015) and Fairphone 3 (2019) aren't available anymore, but I suppose that's not all that surprising after 11 respective 7 years.
Afair, they started running out of some Fairphone 3 spare parts around 2024 and kept the ones they still had for warranty repairs. Source: I own one (and switched to the Fairphone 6 early this year).
Reminds me of the cold steel throwing axe that I bought that specifically has replaceable handles in case you break one. No one actually sells the handles though!
I bought a fair phone 2 when I lived in Germany in 2016. Got a software update when I moved back to Australia. Bricked it. The kernel debug interface has no standard header, and required a fine pitch soldering iron header. I rented a German post box to send it to, as you need a European address for support. I tried to send it twice, and it was refused by German customs. I gave up and now I just buy cheap second hand Motorolas and unlock the bootloader, put lineageos on them. I think giving new life to discarded devices is more ethical anyway.
Didn't they launch only their first device (considering this is the sixth generation) in the USA a few months ago? Hopefully the replacement parts are yet to come. I'm not sure why it's so difficult, perhaps it's that they're stretched too thin and barely managed to get the base device to market there at all
I bought one a few years ago. Good device, too big for my hands (back then, there were still smaller options so I bought one of those smaller ones in second-hand). Not having spare parts available would make me hesitate since that's like 50% of the point (fair sourcing being the other half), but besides that it's a (big) phone like any other
When I had a Fairphone 4, regulars on the community forum repeatedly reminded everyone that repairability was not a primary goal of Fairphone, ethical consumerism was, and any longevity and repairability was secondary or coincidental.
Yes, that goes against most of Fairphone's own advertising, but it was consistent with my experience of the phone and discussions on the forum: security updates frequently so far out of date that some software could not be run, flimsy components inconsistent with advertising (yes, the battery was nominally swappable, but the snaps on the back would break easily, and support would claim that it was not intended to be removed regularly), parts that were frequently out of stock, and of course, whole new phone designs every generation rather than Framework-like component upgrades.
It seems like they may have improved since then, but those problems, along with the atrocious security (FP4 used AOSP's public test signing keys, with publicly-available private keys, for its firmware) and sketchiness around specs, standards and openness (especially for the camera), generally turned me off the company.
Happy FairPhone 4 user here. Running 3+ years, only replaced the battery once. Aim to keep it 7-10 years, barring unforeseen events like theft. Not going to replace it just because a newer model is released.
Someone stole my fairphone 4, then threw it on the ground. So it seems like i'll keep it a while longer
I've been running mine for ~4ish I think, on my third battery and might run out my fourth because it's feeling a _little_ sluggish at times.
I am waiting for the next FP model where I can use a USB-C/dp external display and then I'm all over it.
That's a lot, I usually use old phones from family members, most of them have 4 years of use by the time I get them and I get a whole day of usage from the battery.
1 reply →
What is happening to your batteries? I'm on something like year 6 on my Redmi and my battery is fine. Am I simply lucky?
1 reply →
> Aim to keep it 7-10 years
Security updates will end 01 Sep 2028.
https://endoflife.date/fairphone
Many important security updates will end much earlier. The table is based on how long Fairphone will provide incomplete security updates, not how long the device will truly receive security support.
Fairphone 5 and earlier have end-of-life Linux kernel branches without security support. Fairphone's more recent devices are headed to the same situation. In practice, the same thing happens with other components beyond the Linux kernel.
4 replies →
Not an expert, but I recently heard that apparently not everything is perfect in fairphone land: https://discuss.grapheneos.org/d/24134-devices-lacking-stand...
GrapheneOS is like a veteran and war zone expert: for them, not only the external environment is considered extremely hostile that you should leave your house only wearing an armor and with bodyguards, but also the internal environment is hostile: your bodyguards could be bribed and work against you, that's why you need to somehow be protected against that as well.
Just as physical security, digital security most of the time not as radical, and tradeoffs are usually accepted, especially when they are "invisible": hardware and software security features are usually not mentioned in the specs and the regular and even power user just don't know most of them and what do they do.
When GrapheneOS says "private" and "secure", they mean top-of-the-line security features, updates as soon as possible, all available mitigations against zero-days and insecure code which will limit the impact before the patch, etc. Security as in a killdozer.
When other say "private" and "secure", most of the time it means: "we've followed all the recommendations applicable to our development budget, device price point, and support life time". Graphene does not like that definition of these words.
For smartphone, chip manufacturer goal is not to protect the user at all costs, but to provide reasonable security features for the price.
BUT the goal of chip manufacturer to protect the device at all costs is for… game consoles! That's why Xbox, PlayStation, Switch all run on a custom silicon and not an ordinary chips!
> That's why Xbox, PlayStation, Switch all run on a custom silicon and not an ordinary chips!
Not really. Xbox and PlayStation both run on pretty standard AMD Zen 2 chips. Somewhat customized, but standard enough that people by binned playstation 5 motherboards to use as computers with normal OS'es (lookup BC-250). The last gen with more customized chips was the PS3/Xbox360 era, when both went with a variant of PowerPC, same as Gamecube/Wii/WiiU.
Switch runs on basically the same Nvidia Tegra CPU/GPU as multiple android tablets.
7 replies →
This is not an apt analogy.
A couple of the tenets of computing security are:
- Defense in depth - Principle of least privilege
It is a foundational reality that software (especially in unsafe languages) will invariably have vulnerabilities. Defense in depth and least privilege have compounding effects by forcing attackers to chain multiple exploits to achieve a compromised device, rather than a single vulnerability.
GrapheneOS shows how much can be accomplished on top of relatively secure platforms to begin with (AOSP, Pixel Stock OS, etc.) without sacrificing nearly any usability to the end user (barring manufactured hurdles like Play Integrity). It makes it more damning that many "privacy" OSes and devices cannot even meet the baseline level of privacy and security that AOSP provides, but degrade it.
Firmware and driver neglect and the lack of secure element utilization is not "reasonble security for the price".
On the other hand, my experience with /e/OS on a Fairphone was that it was 4 years behind in updates as compared to Stock Android on that Fairphone.
I don't think that expecting security updates it being an extremist, or is it?
>GrapheneOS is like a veteran and war zone expert: for them, not only the external environment is considered extremely hostile that you should leave your house only wearing an armor and with bodyguards, but also the internal environment is hostile: your bodyguards could be bribed and work against you, that's why you need to somehow be protected against that as well.
Yeah, iPhoens are made that way as well. It's just caring about the privacy of your users.
> When GrapheneOS says "private" and "secure", they mean top-of-the-line security features, updates as soon as possible, all available mitigations against zero-days and insecure code which will limit the impact before the patch, etc. Security as in a killdozer.
I think it's deceptive because people think they will get better privacy/security with a /e/ fairphone when it's actually much worse than an iPhone.
5 replies →
Fairphone makes their fair share of blunders. Software updates are a big issue, especially around the times that critical vulnerabilities need to be patched.
With the hardware I'm not impressed, and on their own forum I've seen plenty of people reporting issues with overheating on the Gen 6. Hopefully kinks have been ironed out on their 6+.
The current CEO also has a persona that would stir up any community (read a few of his AI-gened posts on their blog, if interested of context).
Still holding on to my FP4, but they are not of consideration on my future phone purchase, unless there is some kind of reality check over there and improvements materialize beyond words.
Ultimately, a lot of the “fairness” of the Fairphone is offered by “just buy a really popular manufacturer.”
Everyone and their dog can repair an iPhone because it’s the most popular phone on the planet. Are those repairs accessible to the consumer at home with amateur skills? No, not really. However, newer iPhone models are significantly easier to repair and come along with lower repair costs direct from the manufacturer compared to previous models.
You want years of software updates? Yeah, an iPhone has you covered there, too.
And of course, fairphone’s hardware and OS are nothing to write home about. For the freedom and security nerds they’re better off with GrapheneOS on Pixel or whatever upcoming Motorola phones will support it.
Who is the Fairphone for exactly? Who is buying it and why?
I think the fairbuds are their best product, but I also imagine AirPods Pro 3 are on a whole different level of sound quality, noise cancelation, voice quality/voice isolation, and firmware/software polish.
And let’s be honest about repairability with tiny earbuds: being able to replace the battery is has such a tiny impact on their footprint. If I have to throw out my AirPods Pro 3 every 5 years due to battery degradation, that’s such an insignificant quantity of material being wasted, so it’s probably worth it to get a better product. I could offset my environmental impact by eating a little less beef or riding my bike instead of driving a few times. You drive 30 miles and that’s an entire gallon of refined petroleum product, how much material and energy is used to make one pair of AirPods? I can’t imagine it’s a lot.
I don’t say any of this to be a big corporate or Apple shill. I am rooting for the little guys. But the little guys need to be realistic. You look at products like the Framework 13 Pro and you can actually say, okay, here’s a product with really legitimate benefits over its incumbent competition. There is a reason to buy this product for a certain buyer. I just don’t see that with Fairphone. I can’t think of a customer profile where that person is getting a better ownership experience with Fairphone products.
19 replies →
I have an FP4, and when it'll die, I will just buy an iphone. Security updates are slow, and after the bullshit of the android upgrade, yeah but no.
1 reply →
The GOS people really spend a lot of time of energy showing the worst sides of FairPhone to the world. I think it is because the conscientious technology user is really interested in the combination of ethically sourced, repairable hardware and a security and privacy (from big tech) focussed OS. Tbh I also like that sliders to switch to a simple mode. A well, we can’t have it all. I do prefer de-googled + freedom to do what I want over security (to a degree). So… I’m on the fence. As many vocal people are. A second hand pixel 10 is also a “green” choice.
I do have the feeling that many non-nerds can express the difference between all mentioned attributes, many just like FairPhone as an ethical phone. It’s not that simple, I agree.
So I have been on /e/OS on a Fairphone 3+ for 4.5 years. I was really into /e/OS when I got my Fairphone. When it stopped being usable (not because the hardware was not working anymore, just that the apps I want on my phone were lagging so much they were unusable), I looked into alternatives, including GrapheneOS.
And at that point I got quite disappointed by /e/OS, because I felt like their marketing had been abusing me for years. For instance, my Fairphone 3+ was 4 years behind the Fairphone Stock Android on some updates. /e/OS just wasn't forwarding them, they seemingly were just not maintaining the FP3. Though I bought it to /e/OS, under the promise that it would be supported!
Then I realised that all this time, not only my bootloader was unlocked (so the Android security model had been broken from the first day I powered the phone), but the system was signed with the Google test keys! When you are encouraged to install apps "from the internet" instead of the Play Store, on a phone that disabled the security model so that you're not protected against malware as on any Stock Android, would you say it's being a security nerd?
The thing that GrapheneOS keeps repeating and I realised is true is that many times, if you run a deGoogled alternative that is not GrapheneOS, you get worse security than if you were running Stock Android. It's not about "getting the best possible security", it's about getting the baseline. The truth with /e/OS (or LineageOS, which is pretty much what /e/OS ships, I believe?) is that it depends a lot on the phone. And with many phones, you get worse than the baseline you would get with Stock Android.
> I do prefer de-googled + freedom to do what I want over security (to a degree).
So I switched to GrapheneOS on a Pixel, and I feel like I get the best of both worlds: I get the privacy benefits of the sandboxed Play Services, and the better security. And it's not a "weird" system at all: I asked my family to use it and they didn't realise it was not a "normal Android". It is very different from running something like a Linux on mobile, which would be very very different.
> many just like FairPhone as an ethical phone
Yes, why not. If I was to get a Fairphone again, though, I would use the Stock Android.
And I wish Fairphone could get to the level where they can be supported by GrapheneOS. But it feels like my next phone will probably be a Motorola with GrapheneOS rather than a Fairphone.
1 reply →
Seems you have to compromise on HW openness and ethics vs paranoia.
It's paranoia to want ≥ security than an iPhone or stock Pixel?
7 replies →
Fairphones are closed source hardware with closed source firmware and closed source userspace drivers. Fairphones are less open than Pixels, not more open.
It isn't truly known how a Fairphone compares to an iPhone or Pixel when it comes to environmental impact or fairness to workers. Fairphones are designed and built by T2Mobile since the Fairphone 4. T2Mobile barely has any public information available about it. There isn't information on the working conditions, pay and other aspects of of it. The same applies to the rest of the supply chain. Fairphone provides a list of companies involved in the supply chain without details.
1 reply →
> vs paranoia
I really would like to mention that many times, using /e/OS or LineageOS (or the likes) means that you get worse security than Stock Android.
It would be fine to run /e/OS or LineageOS on a Pixel, assuming those Android systems are not too slow with updates (my experience with my /e/OS phone was that they were 4 years behind as compared to Stock Android).
But really, if you have a Pixel, it doesn't really make sense to use something other than GrapheneOS IMO.
So to me it's really:
- GrapheneOS if you can
- Stock Android vs an alternative otherwise
2 replies →
[flagged]
> It's not like any other device meets their ridiculous standards either
I don't think it's ridiculous to want the ability to relock the bootloader, for instance? Do you realise that if you cannot do that, you just break the whole Android security model right away?
> neither will their own Motorola whenever they get around to actually making it
Source: You made it up
A quick search would basically disprove everything after your first sentence.
2 replies →
There are devices meeting these basic standards right now, and the entire family of them, no less.
GOS are vocal about safety and security of all the devices, not just seriously insecure Fairphones, and this article is about something different altogether, that's misinformation they've been hit with several times.
Fair criticism is fair, but yours is fabrications.
8 replies →
[flagged]
Android Open Source Project userspace code runs on any devices with Treble. That means it runs on any certified Android devices with the ability to install another OS. Updates and security features for the Linux kernel, drivers, firmware and hardware are still needed.
Fairphone 5 and earlier have end-of-life Linux kernel branches without security support. Those lag multiple years behind on providing full Android security updates. The 1-2 month delays for partial security backports is compared to the Android security bulletins and is actually a much longer delay compared to when the patches are made available to ship by OEMs.
1 reply →
> they also compare the security to the "Android Open Source Project" as if it's a real thing
It is very much a real thing. You can build AOSP from sources and install it on a phone. Many Android devices run that (e.g. drone controllers).
> Is certainly much better than my Samsung flagship
Oh yeah, that's for sure. To share my experience, in terms of updates for me it has been GrapheneOS >>> Stock Android > /e/OS. I was running LineageOS/Cyanogen a decade ago but I don't remember and it was a different time anyway.
4 replies →
I suppose it's a testament to their success, but, I have a fairphone 3 from almost 6 years now, and I'm a bit annoyed that they're basically "sunsetting it" (no more software updates, no more spare parts.)
My fairphone 2 had lasted 5 years, but was completely unusable at the end. My current phone works very well (again, huge kudos to the team if anyone is reading this), and I would not mind trying to reach the decade with it - but in a few months, someone (my bank, a shop, a 2FA, whatever) will ask for an unsupported android feature.
I know people will give me names of exotic non-android distros, but will they run my bank's app :/ ?
I had a similar experience but with the Fairphone 2. I never swapped out any parts because performance hardware upgrades never became available and it was superseded by the Fairphone 3. I've not invested again in a Fairphone since. I've no interest in paying extra for repairability I'm never going to use since they have the same obsolescence/replacement model as any other phone.
Fairphone 5 are already in a similar situation due to the kernels no longer having security support with no plan to take it over or move to a newer branch. Fairphone's more recent devices are headed to the same situation. The same thing happens with other components beyond the Linux kernel. People are using the devices with the belief they're receiving security support that's not being provided.
My previous phone was an OPPO Find X3 Pro phone. Incredible phone. I only changed it because it has no zoom on the cameras. But I used it for 5 years.
OTOH my OnePlus 5T is more than 9 year old now, and still perfectly usable (I changed the battery once).
The recently released Fairphone 6+ runs on Android 16. I had to look that up on Wikipedia, their website doesn't even clearly state that. Android 16 is 14 months old at the moment. Android 17 was released to manufacturers 6 months ago and had a general release 2 months ago.
So why does a brand new phone run an operating system from over a year ago? Does it really take over 6 months to update a phone to a new version of Android?
How am I supposed to believe a company is committing to supporting a phone for a long time when at release it already runs outdated software?
I am a user. What does Android 17 do for me that 16 doesn't?
Since about 12 or so, it's been a series of cosmetic changes, bugfixes, and "AI" features.
3 replies →
Getting security updates for issues that are not marked high/critical. These are not your typical RCE, but they are used in exploit chains.
For those not aware, Android Security Bulletins only cover high/critical vulnerabilities. There are also rumors that Google will soon stop fixing vulnerabilities in not-actual versions that were discovered by Google in LLM-driven vulnerability discovery. There was recently a GrapheneOS thread about it.
4 replies →
Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that's decreasing. Android 17 is also required for the latest and greatest privacy/security protections which are not backported. There have been massive privacy and security improvements in each yearly Android release.
16 is fine if you don’t connect your phone to rhe internet, or use sms.
[flagged]
1 reply →
I belive you are mistaken. Android 17 final was "released" 6-7 weeks ago.
But Google being Google, this release is pretty much useless until Samsung et al deal with all bugs and performance issues, which will take 2-4 months.
As a Linux, macOS and Windows user it’s really strange to me that you can’t just install the latest OS on your device. Even my iPhone updates to the latest version as soon as it’s released.
5 replies →
Certification takes time and probably overlaped with the phone development. Fairephone is small compared to e.g. samsung and they describe themself more "stable" and long-term support than bleeding edge.
Fairphone 5 and earlier also have end-of-life Linux kernel branches without security support. Fairphone's more recent devices are headed to the same situation. In practice, the same thing happens with other components beyond the Linux kernel.
Fairphones have 1-2 months of delay for partial security backports to older releases from the beginning and much longer delays for full updates. Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that subset is decreasing.
Android 17 is also required for the latest and greatest privacy/security protections which are not backported. There have been massive privacy and security improvements in each yearly Android release.
Even worse: Google actually does four releases releases per year (major and QPRs), of which QPR2 is also provided to OEMs. Only Samsung and GrapheneOS roll out QPR2 releases.
The Android version is clearly displayed in the article.
[flagged]
If this were genuinely 100% a Qualcomm limitation, I'd expect every Snapdragon 7s Gen 4 phone to be similarly stuck. But Motorola's Edge 70 Fusion uses the same SoC and was already in Android 17 beta testing in February, and Nothing's Phone (4a) and OnePlus Nord CE 6 are also slated for Android 17. So it seems the SoC isn't inherently preventing Android 17.
7 replies →
Great what they are doing - yet I found Shiftphone to be also fair, equally or better repairable and even more open for alternative Operating Systems. I think Fairphone supports 2 OSes officially, Shiftphone has a whole custom ROM list of ~10.
https://www.shift.eco/en/shiftphone-8/
Ten? So like Android and Linux flavors? I'm not sure I even know of ten: e/OS, Calyx, Lineage, Ubuntu Touch, eh is there like Mobian or something still alive... how do they get to ten?? Do they also all fully work? Camera and calling (and not only on 2G) for example?
I'd be interested in the list, the website you've linked is super sparse (the full menu is like shop, some feel-good pages about device deposit and impact, blog, and contact us - no knowledge base, documentation, or somewhere where you'd expect to find OS info or even downloads)
their marketing is really low-key and they must improve it because they have enticing products. OS offers page: https://www.shift.eco/shiftos/
2 replies →
Anyone have any updates on why this device can’t support or get behind Graphene OS? A repairable and secure phone is my desired option for a phone that’s truely mine and I’m sure this is true for many others also.
From my understanding it’s not there as the Graphene team says that fairphone haven’t taken security hardware seriously and there’s key hardware security features missing that means they are not even interested to look at supporting the device.
Keen for latest updates on this, happy to be corrected.
Someone from GrapheneOS was very active in this thread: [0], here is a response the GrapheneOS person links to themselves: [1]
[0] https://news.ycombinator.com/item?id=49355122
[flagged]
While yes I am on GrapheneOS' side on these issues, I'm surprised nobody clones the GrapheneOS repo and simply disables the minimal handful of features which block it from working on devices. Maybe calling the clone CarbonOS? If MTE is required to boot GrapheneOS and Fairphones don't have MTE, then Fairphone clones GrapheneOS and disables MTE for its images. Graphene has so many features beyond just hardware security that other Androids lack, that it would be worthwhile to do this and it would still be higher security than the others (even if it's below GrapheneOS' own full security). Sensor & network permissions, storage & contact scopes, autoreboot, scrambled pin, radio auto-off, MAC address randomization, and more, I'm sure don't require MTE or Titan etc. Just follow GrapheneOS as upstream, making sure that the minimal set of changes needed to get it working on other/older devices transfers with the new updates.
7 replies →
MTE is not the only blocker here. Pixel 7 series do not have it and are currently supported by GrapheneOS. There are other concerns regarding things like a proper secure element implementation and timely firmware/binary blob updates.
4 replies →
That's highly inaccurate information. MTE is included on a large number of smartphones beyond Pixels. It's heavily integrated into iOS on the iPhone 17 as their Memory Integration Enforcement feature. MTE enables massive security improvements against exploits and Pixels have had it since the Pixel 8 in October 2023.
Traditional desktop computers have atrocious privacy and security throughout hardware, firmware and software. That isn't a relevant comparison for GrapheneOS. Recent Mac hardware does support MTE and so will non-Mac devices using Snapdragon chips. Qualcomm has added MTE support for their latest flagship mobile SoC platform and will bring it elsewhere. MediaTek and Exynos have also added MTE support.
MTE does not have the substantial performance or battery life impact you're portraying it as having. It's also far more useful than you're portraying it as being. Apple would not have extensively integrated MTE if they had to give up significant performance or battery life. iPhones have a lot of focus on security but aren't willing to make significant sacrifices in those areas for it, at least for the default settings. Their Memory Integrity Enforcement entirely based on MTE is always enabled in the kernel and the large portion of userspace where they deployed it. It's not only used for Lockdown Mode.
I've always been a bit curious about Fairphone, but as I only get phones that cost less than $200 (and use them until they physically break), I'll probably never get one.
Still only on my second smartphone, so I'm not worried about producing more e-waste.
[flagged]
Isn't the Pinephone getting super old now? And it was already very slow when it was released...
1 reply →
Never heard of that before. A quick search doesn't reveal sufficient documentation to form an opinion. Do you have better resources?
Can't find it for sale in the online shops I usually use (Germany), either.
3 replies →
Are ya'll really repairing your phones? I replace mine when it can't run Google Maps smoothly anymore.
After 4-5 years, on every phone I've ever had, user interactions begin to lag noticeably. Apps launch much more slowly. Intense graphical apps like maps become frustrating to use. At some point I can't take it anymore and replace the phone, long before its physical parts or battery have worn out.
I've bought new a Google Pixel 7a two years ago, paid for it 400 euros. After 1 year I've dropped it, landed on a corner, screen completely broken, replacement costed screen costed me nearly 120 euros (and was not an original screen, otherwise I would have spent more). Just costs much money because of the fucking fingerprint reader under the screen that why couldn't put it in the back of the phone as they did for many years. Broken it again, fuck it I will not repair it again, with the cost of the repair I may as well buy a new phone.
Then I've decided that is worth either spending money on phones whose replacement parts doesn't cost half of the phone itself, or just buying the cheapest Xiaomi or similar chineese brand phone and when it breaks buy a new one or repair it (funny enough cheap phones are more repairable than expensive ones, so I usually repair them).
Look at the cost of a FP screen replacement, 100 €/chf for the FP4. Mine is going black randomly until I reboot the FP4 one to five times.
I've replaced batteries on Pixel 3 XL and Pixel 6 Pro, both having run GrapheneOS. I use OSMAnd~ with no network permission (except during maps/POI updates). OSMAnd~ shows me where ALPRs are, so I can plan my routes around Flock. :^)
My family's Pixels have all lasted physically long enough for Google to stop supporting them. My wife was annoyed when I told her she needed a new one because from her perspective there was nothing wrong with her existing one ( lack of security updates is not on her radar.)
Genuinely, how do you make your phone so slow? I've been using my s10 for 7 years, and besides the minor crack in the corner of the screen from being dropped, and constantly juggling storage because I hoard media, it works as well as it did when it was new.
I'm typing this from a Galaxy S10 I got in 2020, with Lineage 22 (Android 15) running on it.
For sure it isn't the snappiest, but my only real performance issue is loading gifs on Signal, which takes several seconds for some reason.
Just tried maps now, actually still fairly fine for me.
No VoLTE on any Samsung phone running non-stock OS is a dealbreaker.
Sent from my Galaxy S10 running LOS
I am not sure what you are doing to your phone for it to act like that
I had the same experience. Repeatedly. IMO it's the software, not the hardware. The issues always start/get worse with a big update to Android or the main Google apps.
3 replies →
I have a Fairphone 5, chose that mainly because of repairability. :)
The Fairphone 6+ looks really interesting but I'm not seeing it having the ability to wirelessly charge. I exclusively charge my Pixel 10 XL Pro (25w+) phone on a wireless charger now in the car and at my house and really like it, I don't want to go back to plugging in a USBC cable anymore unless it's an emergency. Am I missing something? Does it support Qi 2?
Was really happy with my FP3 until it died: "sudden death". No power, nothing. According to their own forum, it's a very common problem after a while. Of course there is no warranty and replacing the mainboard is not possible...
> Of course there is no warranty
You always have the right to a minimum 2-year guarantee from the moment you received the goods. However, national rules in your country may give you extra protection.[1]
[1] https://europa.eu/youreurope/citizens/consumers/shopping/gua...
Would be neat if Fairphone would build a real compact smartphone, something with 4" or 5" screen. Current device is too large for human pockets and all those protruding camera bumps and buttons are really uncomfortable.
Ethical phone maybe only hardware wise, software wise with Google it is far from ethical
Why are the comments below flagged/dead?
[flagged]
[flagged]
[flagged]
Fairphone issue an annual director's report, has financial audits and list the titles of each director. You can easily find the name of and information about the CEO. They have an Impressum section on their site along with many other legal documents.
This is more than can be said about other projects in this space
I would love a Fairphone, but no headphone jack is a nonstarter for me. Still blows me away that a company saying they are focused on longevity would get rid of a universal audio interface that we've had for decades. In the article they claim it's to fit other features in, but frankly that's not a believable claim. Other manufacturers manage to get a headphone jack in just fine, without any noticeable downside.
The headphone jack is inside USB-C connector. You can use USB-C-to-3.5mm passive (!) cable to connect your 3.5mm headphones, or you can buy 3.5mm headphones with USB-C audio connection.
There's no additional DAC involved, the analog audio is already on a USB-C pins.
I can't find anything about that in the article or the Fairphone 6 manual. Do you have a source for this?
My main problem with USB-C headphones on my Android phone is how unreliable they are. But if the USB-C port can just pass through an analog audio connection, that should work much better, I expect.
Edit: This feature is apparently deprecated (removed?) in newer versions of the USB spec! https://en.wikipedia.org/wiki/USB-C#Analog_Audio_Adapter_Acc...
How do you charge your phone while listening to music?
8 replies →
I absolutely concour about the need of a headphone jack - I do not buy anything without it. So,
> to fit other features in
what exactly, one would ask. If there are tradeoffs, if would be nice if the customers can decide what to have, in a modular product.
At this point headphones with an usb-c connection have become nearly as common as 3.5mm trs ones. Additionally you can permamently hook a small usb-c dac with 3.5mm trs output to the headphones of your choice.
Only issue is some very cheap ones are actually bluetooth headphones in disguise where the usb-c connection only exist to power the bt recepter inside the headphone. I find this completely stupid.
1 reply →
> If there are tradeoffs, if would be nice if the customers can decide what to have, in a modular product.
A "modular product" has tradeoffs in and of itself (such as size, price, water resistance, …), which presumably would not fly for a majority of customers.
1 reply →
Given how severely that hard requirement restricts your available options, I'd suggest adapting to the USB-C audio world. No, it's not as nice as a headphone jack. But it is a relatively small con to just stick an adapter onto the ends of your 3.5mm devices and replace it a few times a year when it breaks. And yes, you can get a "charge and listen at the same time" adapter.
Serial is a universal data interface that we've had for decades. Don't need RS232 on my phone though.
Boy it would be nice however.
On that note, I remember reading how some phones were able to use the headphone jack as a serial debug port, which is pretty neat.
https://wiki.postmarketos.org/wiki/Serial_debugging/Cable_sc...
1 reply →
[flagged]
Linux is a kernel. Embedded, server and mobile Linux distributions without glibc, gcc, GNU coreutils, systemd, D-Bus, Wayland, Pipewire, etc. are Linux too. Linux is not a specific desktop software stack that's largely used on FreeBSD and elsewhere too. Android Open Source Project and GrapheneOS are Linux distributions.
[flagged]
[flagged]
[flagged]
It’s both superior engineering-wise and morally. The moral framing is probably more popular with folks that don’t care about engineering superiority, too.
Surely it's morally superior to limit resource use by using things for longer and repairing them when broken. I often use a weak Kantian Imperative that I couch as "if everyone did what you do would it be good, sustainable?" as a _guide_ to moral choice, it's a starting point really, but from that I think moral superiority of more repairable goods follows.
[flagged]
[flagged]
There’s a get-out clause in the law that allows your battery not to be required to be user replaceable if it can last 1,000 cycles while remaining at 80+%. Apple’s phones certainly meet that these days, and I imagine Samsung’s will as well (though I’m not sure if silicon carbide changes that at all).
> There’s a get-out clause in the law
As all too common
GDPR: "legimate interest"
EU261: "exceptional circumstances", no deadlines for paying compensation etc
yes yes, "no law is perfect" etc..nobody could foresee anything...downvote away
4 replies →
The new $650 Fairphone Gen 6+ is designed both for longevity and easy repairability.
I applaud the concept but to see how well this actually holds up in the real world, let's check the Fairphone web site.
Where are the parts to repair any version prior to Gen 6? I don't see them listed anywhere.
So it would appear that "longevity" is actually pretty limited.
Fairphone 4 (2021) parts: https://www.fairphone.com/shop/category/spare-parts-4?catego...
Fairphone 5 (2023) parts: https://www.fairphone.com/shop/category/spare-parts-4?catego...
Parts for the Fairphone 2 (2015) and Fairphone 3 (2019) aren't available anymore, but I suppose that's not all that surprising after 11 respective 7 years.
Afair, they started running out of some Fairphone 3 spare parts around 2024 and kept the ones they still had for warranty repairs. Source: I own one (and switched to the Fairphone 6 early this year).
Afair, they started running out of some Fairphone 3 spare parts around 2024
So "longevity" is actually about 5 years. Or less if you live in the USA.
https://us.fairphone.com/repairs
4 replies →
This is a good point. Ifixit has guides for all the phones, but it reports that none of the replacement parts are actually sold in the United States.
https://www.ifixit.com/Device/Fairphone
Reminds me of the cold steel throwing axe that I bought that specifically has replaceable handles in case you break one. No one actually sells the handles though!
I bought a fair phone 2 when I lived in Germany in 2016. Got a software update when I moved back to Australia. Bricked it. The kernel debug interface has no standard header, and required a fine pitch soldering iron header. I rented a German post box to send it to, as you need a European address for support. I tried to send it twice, and it was refused by German customs. I gave up and now I just buy cheap second hand Motorolas and unlock the bootloader, put lineageos on them. I think giving new life to discarded devices is more ethical anyway.
Didn't they launch only their first device (considering this is the sixth generation) in the USA a few months ago? Hopefully the replacement parts are yet to come. I'm not sure why it's so difficult, perhaps it's that they're stretched too thin and barely managed to get the base device to market there at all
I bought one a few years ago. Good device, too big for my hands (back then, there were still smaller options so I bought one of those smaller ones in second-hand). Not having spare parts available would make me hesitate since that's like 50% of the point (fair sourcing being the other half), but besides that it's a (big) phone like any other
It's in shop --> "all parts" (under the "spare parts" header)
Here are the ones for the fairphone 4: https://www.fairphone.com/shop/category/spare-parts-4?catego...
I however couldn't find the ones for the fairphone 3. The fairphone 4 is from 2021, which is not that old.
So "longevity" is actually about 5 years. Or less if you live in the USA.
3 replies →
A simple Google search showed they are right here: https://www.fairphone.com/spare-parts
When I had a Fairphone 4, regulars on the community forum repeatedly reminded everyone that repairability was not a primary goal of Fairphone, ethical consumerism was, and any longevity and repairability was secondary or coincidental.
Yes, that goes against most of Fairphone's own advertising, but it was consistent with my experience of the phone and discussions on the forum: security updates frequently so far out of date that some software could not be run, flimsy components inconsistent with advertising (yes, the battery was nominally swappable, but the snaps on the back would break easily, and support would claim that it was not intended to be removed regularly), parts that were frequently out of stock, and of course, whole new phone designs every generation rather than Framework-like component upgrades.
It seems like they may have improved since then, but those problems, along with the atrocious security (FP4 used AOSP's public test signing keys, with publicly-available private keys, for its firmware) and sketchiness around specs, standards and openness (especially for the camera), generally turned me off the company.