Easy tips to make your FP2 fast and long-lived

Looking for the community support to make my FP2 (5 yr old next February) fast a lot more.
It ve some screen block with camera app, google browser crash and sometimes to open more apps togheter. It working, but very slowly.
Write under yours best tips, or your best practices, to have a easy manual for anyone will have need to. The common target is a life as long as possible for our phones.

I think the two best options are

  • to do a #dic:factorydatareset (click on this link to find more information) if this has not been done for long time. But sure, it will mean to install everything again from the scratch… or
  • clear some space on the internal SD card if that might happen to be very full (I assume for this no detailed manual is needed).

@Volker @my SD card is quite free. How do I transfer data from phone memory to SD quickly?


One possibility is to connect your phone via USB to a PC and move it there from internal to external phone storage.
Another possibility is to use a file manager app. Total commander is quite powerful (but imho sometimes a bit confusing).
I’d recommend to have e.g. mp3 files (or even movies) on the external SD card. Normally camera apps con also be configured to store photos and movies on external SD card. I also have some Osmand offline maps on the external SD.


Yo tengo instalado el sistema operativo /e/ os:

Estoy muy contento. El teléfono funciona rápido. Las fotografías son mejores que con el Fairphone Open.

There is no wo way to make an old phone much faster. While the hardware is unchanged, software has been evolving since you bought the device and will continue to do so, requiring ever more computing power. Using old software is not an option, because it will not be updated and therefore insecure. A less power hungry Custom ROM OS might remedy the issue, but not in the long term (and you will probably run into compatibility options).

And all of this is not going to change until our societies at large drop out of capitalism, which builds on the paradigm of endless growth.

Best wishes,

Well, yes – but in the mean time, it’s useful to have tips that may help extending the life of FP2s (or FP3s, for that matter), like Volker’s above.

My FP2 (stock OS) hasn’t gotten slower, at least not that I noticed, but then, I don’t use demanding apps I suppose, and not more than a couple of apps at a time.

I’ve disabled some Google/Android apps, including Chrome. As primary browser I use Lightning [EDIT outdated? Alas … ]

Occasionally, when an app crashes repeatedly, I clear the app’s cache – seems to help.


The sistem by the “easy install” support FP3 and not FP2.
Are you downloaded /e/OS by Gitlab?

If you want to give /e/OS a try, here’s the set of instructions for the FP2:

If you want, you can even backup your current Fairphone Open OS with TWRP (before “Installing /e/ from recovery”). That would allow you to go back easily if you do not like /e/OS.


@Volker Could you gently tell me like swape up multimedia files from internal storage to SD, via phone. (NO PC).
I need an APP or I can do it via “settings”?

Thx for your help.

Settings->storage->portable storage/[name of SD card]->hamburger menu->[select internal storage and move to directory or file you want to move and long press it]->three dots at top right->move to …->[select destination, if necessary by using hamburger menu again]->MOVE

Hamburger menu: Screenshot_20201221-114558_Dateien

Three dots at top right: Screenshot_20201221-114616_Dateien


Yes, FP2 is also supported. I downloaded it from the following link:

1 Like

Two weeks ago, I decided to switch my FP2 (with Fairphone Open OS) to the MicroG-enabled LineageOS operating system.

I had just tested e-Foundation’s /e/OS over the last 24 hours, but I was not satisfied:

  • The default applications prevented me from using all the apps I wanted, to sync with my self-hosted Nextcloud server.
  • The included MicroG did not seem to help much with the one app from Aurora (i.e. Play), that I hoped to be able to use.
  • I did not like the launcher.

All in all, I did not want to suffer the disable-and-replace dance I usually do on Closed Android.

By contrast, with LineageOS 17.1 built by the MicroG project (with the latest code from both projects), I now feel as if I had a brand new phone! I am so happy :slight_smile:

  • I couldn’t hope for a better launcher. It is customizable in grid size so that I can put what I want where I want without having too many screens. I feel like I have the FP1’s launcher, which I missed when I switched to the FP2.
  • The default applications are from a newer AOSP code-base, compared to FP2 official OS, and it shows. For example, the latest camera application is good enough that I did not feel the need to switch to OpenCamera (which is a bit overwhelming for the FP2…).
  • MicroG is up-to-date, and I was able to run the application I wanted to run, that “requires” Google services.
  • OSMAnd feels less sluggish than it did with the official (Open) OS.
  • It even seems like I gained a tiny bit extra battery life (time between charges)!

The only difficulty I had, is that the Google recovery wouldn’t let itself be overwritten with TWRP. I had install the TWRP app from the store, while in Open OS, and install the TWRP recovery from there! After that, it was just a matter of following instructions.

The only (minor) drawback I found is that LineageOS is not rooted, whereas Open OS was. But from what I’ve read, it’s easy enough to fix that using Magisk; I’ve had no need for root so far however (root is still available through adb, by the way).

Screenshot :slight_smile:


I think it’s because of Moore’s law, partially. Developers get access to better machines, then write SW requiring more resources, just because they can. The result is the Wirth’s law: https://en.wikipedia.org/wiki/Wirth’s_law

1 Like

Couldn’t agree more.
Developers should be obliged to use G-1 hardware (ie previous generation, not next gen!). And fed on bread and water.
By the way, I’m a developer, among other things.
Back in the day (1980s) we were writing software that did incredible things, with 32 kB (yes, kilo, not even mega) of RAM (another 32 were used by the OS and interpreter). Storage on 1.2MB floppies! Nowadays the simplest calculator on Windows requires more than 14MB of RAM. Talk about bloatware!

Seriously, of course the GUI is a major reason, and it’s made computers accessible to all sorts of people, and I’m not suggesting we return to single-line text editors :wink:
But still …


This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.