Longevity vs Obsolescence (software)

In my opinion the order is like this: software, batteries**(see Stefan below), the SoC.

It’s always software support … and even if there is software for long time … newer software often wants a stronger chipset and later (just think of VR headsets) a more powerful display/graphics cards.

It’s also easy to repair well designed non-modular phones, if you have the tools and spare parts. Modular design is good, but a bit overrated sometimes.

As far as I know, the FP project builds the batteries custom fit. At least it was like this for the FP1.

1 Like

Yes and no, software sometimes also gets more efficient. If you look at Android, Android 4.4 was more resource-efficient than 4.0-4.3 and thus some devices were able to run previous versions could easily make the jump to 4.4. Also, Windows 10 runs more or less acceptable on hardware with just 1GB of RAM - try this on Vista!


I am not a fairphone owner. One major reason for that is because if I’m going to pay >500€ for a phone, I need to be sure that I’ll still be able to use it in 5 years. I could buy a very basic phone for that, but the point is to have a smartphone that allows me to access all the latest apps and technologies. The modularity kind of solved the issue of breaking the phone. But what about the software?

Quite often, the reason why new phones are bought is because the latest apps can’t be installed (because of software or hardware compatiblity) or because it’s getting too slow. What’s Fairphone’s approach on this? Geeking around the different parts of the phone to be able to install the latest Pokemon Go ~like app at all time?

1 Like

Hi, I moved your post here to keep related posts all in one place. :slight_smile:

1 Like

Thanks @Stefan !

What I see here is not very reassuring though… ! If I understood correctly, it’s basically “let’s hope that we chose a popular processor that will get software support and hardware manufacturing for as long as possible, but even then the phone’s software and hardware won’t be compatible with the latest apps”.

You should also follow the discussion here:

Like @z3ntu says, an Android 7 build without Google Apps pre-installed will still be possible. It would be practically the same as it is now with FP1, which receives an official update almost 3 years after the first phones have been shipped (and that’s with a much less developer friendly chipset = Mediatek).

What are your exact concerns? Which technologies do you fear you’ll miss?

1 Like

That’s it. Android is not developed on a rolling release model; it is developed, instead, on a version release model, more prone to planned obsolescence.

This means that, at some point in the year, Google releases the source code for Android, which needs to be adapted to the chipset by the chipset manufacturer (often called OEM; Qualcomm, in this case), and then adjusted to other components by the end-product maker (Fairphone, in this case).

So, before Fairphone, Google and the chipset maker impose their will in form of requisites and hardware limits, e.g: if Google drops support for ARMv7 devices (as they did with ARMv6 ones), Fairphone is screwed up; but if the chipset maker doesn’t adapt the new Android version to (what they consider) old chipsets, Fairphone is screwed up in the same manner.

(There are further issues Fairphone should resolve, but I tried to keep the explanation as simple as possible. You have a more in-deep explanation at the thread @Stefan linked)

1 Like

This HTC infographic Fairphone also references to here gives great insights into update processes.

To be independent from all these factors Fairphone would practically have to develop their own chipset and their own operating system.


No. This is only true if FP would stick with the bin blobs. If Fairphone would instead use an open chipset there is a high chance that some people from the community might develop the necessary drivers.

1 Like

If Fairphone would instead use an open chipset there is a high chance that some people from the community might develop the necessary drivers.

Are there already open chipsets?


Interesting discussion. Reading a lot of comments on the forum makes me think that some people are looking for a fair and ecological phone, that would be one of the best on the market and would hypothetically last forever. I wish for such a phone, but since I have been following Fairphone for quite some time, have read articles, reviews, forums, etc., I knew before buying my FP2 that I might have some issues (furthermore I installed FP open OS which is known to have some issues one can often easily fix with some good will and some valuable help on the forum).
Fairphone is a great concept. Something needed to be done. Great work with the mining part (even if there is more work to do), great thinking with the modular conception (even if we might have issues with some parts, as explained here), great support with the FP open OS (even if there still are issues and if we would like to have updates as soon as the problems are known :wink: ). There sure are problems, but most of us knew it before buying the phone.
Before my FP, I owned an old Samsung SIII someone gave me. It was 4 years old, slow (and no 4g) and did freeze quite often at the end. If you are patient, don’t rely on your phone for work and use it for easy tasks (call, write messages, take pictures ans some Internet), no doubt you will be able to keep your Fairphone 2 up to 5 years. As for the greater public, I think that Fairphone will reach maturity soon, but it takes times, tests and a trial period to achieve a great phone.


I agree to @kuleszdl although I have no overview about chipsets that are both powerfull and free and open for writing drivers. I noticed in the regular wikipedia entry about FP2 that FP has been criticized in public for their decision about qualcomm. Also I never heard about software named replicant as a possible substitute for android. Also with lollipop I would expect for FP2 to have a platform for free community for real open source software like replicant for my FP2.

Why? The FP1 had Mediatek, not Qualcomm.

And well, Replicant is just a “de-blobbed” version of CyanogenMod that contains really no Blobs. It runs on some quite dated devices (the best is the Samsung Galaxy S3) but without the Blobs it has no Wifi, no Bluetooth, no GPS, laggy 2D graphics and no 3D graphics. The first two can be overcome by using an USB-OTG cable and a wifi stick, but I doubt that’s a practical solution for most people.


I am not sure why you ask me after I only repeated an excerpt from wikipedia. I guess enough people discussed there about every single phrase. Maybe you ask them or you ask me again but more precisely. After I could even agree again to the rest of your answer I am not sure to do so again. Maybe you ask me again why I agreed :wink:

Well, personally I think it’s not a good idea to repeat stuff from sources which are obviously wrong. But apart from that - Wikipedia refers to the Replicant blog which is indeed cited wrong. In the blog entry, FP’s choice for Mediatek is critized - at least the way it’s cited with the 2013 timestamp. There is also criticism about the choice for the vendor of FP2 but only in a small comment which is from 2016.

1 Like

Although the first cite (14) in wiki’s paragraph is not 100% correct the next phrase in the same paragraph ‘Critics’ is cited 100% correctly about FP2’ qualcomm and not FP1’s mediathek (cite 15) So I am rather sure that it was a good idea from me to repeat things that are obviously not wrong due to a true follow-up phrase about FP2 and not FP1.

Obviously you don’t agree with wikipedia critics about FP2 in itself.

I didn’t say that, I’m just not a fan of citing things wrong (indeed 14 is cited wrong while 15 seems cited right). And it’s hard to say if the critics are right - of course I would have welcome an open platform. But the question still remains if there are any blob-free LTE modems our there.

Maybe you oversaw Samsung’s free LTE modems at replicant.us after you wrote everything from replicant is for outdate devices. Yes, they are, but maybe also because FP denied to follow replicants advice.


Also NXP/Freescales Android processor i.MX6-8 (1,2 GHz) and TI’s OMAP, and even chinese cheap Allwinner’s processors especially for Lollipop-android they all had opensource drivers. After replicant’s developer explicetly contacted FP during FP1 times to have better replicant support for FP2 I cannot understand why you neglect FP’ s reaction to replicant.

Is it maybe because you criticised only one simple citing mistake at wikipedia about replicant’s mission ?

1 Like

In my opinion, Fairphone took into advice them, but chose Qualcomm because they actually need to sell a device with a good processor, and Qcom’s fame was and is a benefit for that. If Fairphone cannot sell a bunch of devices, they won’t be able to have the manpower to update the software of their two devices.

Let’s not forget that an utopic product without market share is useless; Fairphone needs to open that space first. They are working hard on that.

And no, there’s no perfect and top chipset (powerful, fully libre and highly demanded by consumers) yet. It is hard even on computers.


This logic about ‘sell & forget’ implies that FP in the most critical issue (processor) intentionally decided against longevity and in favour to obsolescence(!). Replicant’s main developer also gave a frustrated statement about this decision: Fairness at FP shouldnot be mistaken by fairness for users e.g. in the sense of transparency about the whole device.

I am not sure if it makes sense to offer a device with an outdated processor from 2014 starting in 2016 and trying to talk around by explaining that a “flagship” processor that was already outdated was needed to get a market share.

You cannot have both as you already made clear by that valuable web link that I rather appreciated