Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Choose LineageOS if you want a relatively direct custom-ROM foundation and are comfortable deciding which apps and services to add. Choose /e/OS if you want a more curated, privacy-oriented setup with an alternative launcher and default apps, microG integrated by default, built-in privacy controls and optional account and cloud services.
Neither choice can be made safely from the phone brand alone. Check the exact model and regional variant, current official or community-build status, bootloader rules, Android base, and compatibility of every app you cannot live without. Banking, payments, digital-rights-managed media and push-dependent apps are the most common reasons a technically successful installation still fails as a daily-driver migration.
As an Amazon Associate I earn from qualifying purchases.
The short answer: compare the phone first, then the operating system
LineageOS and /e/OS are related but serve different priorities. LineageOS is the more direct custom-Android route: you install a supported build and decide how much of the Google ecosystem, alternative services and third-party software to use. /e/OS is based on the LineageOS/AOSP family but changes more of the out-of-box experience. The /e/OS project describes its system as including a different launcher, modified or replaced default applications, integrated microG, alternative service defaults, privacy controls and optional online services.
Recommended Free Tools
That makes /e/OS feel more like a prepared product, while LineageOS gives you a comparatively open starting point. “De-Googled” does not mean that every application, network request or user configuration is incapable of contacting Google. It means the operating system is designed to avoid depending on Google’s proprietary service stack by default. Your installed applications and choices still determine what leaves the phone.
#1 Best Overall
- Include 3 PCS Screen Protector For Fairphone 5, Tailored-fit to your device's screen, Maximum Strength.
- Made of Japan Hardnest Glass, High Scratch Resistance, Smooth and high touch responsive with Superb Oleophobic Coating.
- HIGH GRADE COMPONENTS: Mr.Shield Ballistic Glass screen protectors use the Silicone adhesives for viewing clarity and easy installation and removal.
- 99.99% HD clarity and touch accuracy.
- From scratches to high impact drops, you are protected with Mr.Shield HD Clear Glass.
There is no universal winner. A supported device with working essential apps is a better choice than a theoretically preferable ROM that cannot be installed or cannot run your work and payment tools.
LineageOS and /e/OS at a glance
| Decision point | LineageOS | /e/OS | What it means for you |
|---|---|---|---|
| Project model | Custom Android ROM project with device-specific official builds | LineageOS/AOSP-based fork with additional system, application and service changes | /e/OS adds more decisions and defaults on your behalf; LineageOS leaves more assembly to you. |
| Device support | Official devices must meet LineageOS support requirements; the live device list is decisive | Separate support decisions, with official and community builds shown in its device selector | Compare the exact model and variant, not a brand-level assumption. |
| Google-service approach | Depends on the LineageOS installation and any optional packages you add | microG is integrated by default, with alternative defaults and services | Both require app-by-app checking; /e/OS provides more compatibility plumbing initially. |
| Privacy controls | Vary with device, build and what you install | Documents tracker management, location faking, IP faking through Tor redirection and alternative defaults | /e/OS exposes more controls in the standard experience, but controls are not a guarantee of private behavior by every app. |
| Default experience | Closer to a configurable custom-ROM baseline | Own launcher, default applications, settings changes and optional account integration | Pick LineageOS for a hands-on setup; investigate /e/OS for a packaged one. |
| App compatibility | Verify the exact setup and any Google components you choose | microG can supply some Google-service interfaces, but applications requiring the complete Google code base may fail | Test banking, payment, DRM and push-dependent apps before changing phones. |
| Installation | Follow the device-specific official procedure | Supported models may use a Chrome-based WebUSB installer or command-line tools | “Supported by /e/OS” does not necessarily mean “supported by the easy installer.” |
| Bootloader locking | Device-guide dependent | Only some device/build combinations document support for relocking | Never relock a bootloader until the exact guide says that build supports it. |
What “de-Googled” means in practice
It describes defaults, not an absolute network guarantee
Android applications can bundle their own libraries, call web services directly or require a particular push, location or payment API. Removing a preinstalled service package therefore cannot make every application independent of Google. A privacy-focused ROM can reduce the operating system’s default reliance on Google while leaving you responsible for the software you install.
LineageOS is a foundation you configure
A LineageOS installation gives you a custom Android base. You then choose an app source, browser, mail client, maps, synchronization tools and, if needed, a compatible service package. That flexibility is useful when you already know which open-source or self-hosted tools you want. It also means the final privacy and compatibility profile is partly your own project rather than a single preset.
/e/OS packages a set of alternatives
The /e/OS technical FAQ explains the project’s approach in its own words: “We’ve integrated microG by default, have replaced some of the default applications, and modified others.” It also says the project changed the installation procedure, settings organization and defaults. The result is not simply a renamed LineageOS build; it is a fork with an opinionated user experience and optional online services.
Device support is the first compatibility test
Check the complete model identifier
Two phones sold under one commercial name can have different chipsets, modems, storage layouts or regional firmware. Before downloading anything, record the exact model identifier from Android’s About phone screen, the original box or the manufacturer’s support page. Check carrier variants and regional editions separately.
Rank #2
- 対応機種 for Fairphone 5
- 【TPU+PU】しなやかで丈夫な素材を使用し、携帯電話を傷から守ることができます。
- 【キックスタンド機能】フリップスタンド機能付きの携帯電話ケースは、読書や映画鑑賞を容易にし、日常生活に必要な両手を自由にします。
- 【精密なカット】すべてのポート、ボタン、センサー、カメラにアクセスしやすいように精密なカットが施されたスマホ用レザーケースです。
- 【財布カバー】カードや小銭を収納できるカードホルダー内蔵。
Understand official versus community builds
/e/OS’s device selector distinguishes official and community builds and presents device-specific information such as the Android base and bootloader details. Its support decisions are independent of LineageOS’s; a model can be supported by one project and absent from the other. Treat a community build as a different maintenance and documentation proposition from an official build.
LineageOS requirements are not a maintenance promise
LineageOS’s Device Support Requirements document says, “All devices MUST support software encryption.” The requirements also address retaining stock capabilities such as cellular calling, Wi-Fi, GPS, camera and NFC when those functions are present and within the charter’s conditions. Meeting a charter requirement does not prove that every device build receives identical attention or that a particular model is currently maintained. Confirm the live device page and the latest build notes.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Buying a phone with /e/OS can simplify the starting point
The /e/OS device selector lists the Fairphone 5 as an official-build device, and the project says some phones are sold with /e/OS preinstalled. Availability, inventory, geography and pricing change, so treat a preinstalled handset as a purchase option only after checking the current model and support entry. A phone that ships with /e/OS is not automatically supported by LineageOS, and the reverse is also true.
Privacy and service differences
/e/OS’s documented controls
/e/OS describes an Advanced Privacy feature set that includes tracker management, location faking and IP faking. According to the project documentation, IP faking redirects traffic through Tor. These are controls you can configure; they are not an independent audit or a promise that every application respects the same privacy choices.
Location faking can confuse applications that need a genuine position, such as navigation, delivery or emergency tools. Tor redirection can add latency, trigger fraud checks or be blocked by a service. Tracker controls can also break an application whose analytics or advertising component is improperly coupled to core functionality. Use the controls deliberately and keep a troubleshooting path for apps that stop working.
Rank #3
- ❣[COMPATIBILITY]: Specially designed for for Fairphone 5 (6.46 inch), case with screen protector, every button and cutout fit perfectly with your smartphone, easy to operate, support wireless charging.
- ❣[Premium Material]: The case is made of eco-friendly, non-toxic flexible TPU, which is very durable and won't deform or fade. With a hydrophobic and oleophobic layer, it is dustproof, waterproof, and anti-fingerprint, and is very easy to clean.
- ❣[360°Protection]: The package contains a screen protector (tempered glass), the case has enough raised edges to protect the rear camera and front screen from scratches and cracks, the inside of the case is a soft ultra-fine fiber material, Protects the back of your phone from scratches and provides 360-degree full body protection.
- ❣[Screen Protector]: High-quality tempered glass screen protector, suitable for for Fairphone 5, easy and fast installation, ultra-thin thickness of only 0.25mm, high definition, sensitive, no bubbles. 9H hardness, enough to resist scratches.
- ❣[Light and Portable]: The non-slip material provides a comfortable grip, and it is not easy to slip off when operated with one hand. The ultra-thin and smooth design fits tightly to the phone body, providing good protection without adding any weight, and the slim volume can be easily put into a pocket for easy portability.
Optional accounts and cloud services
/e/OS presents a mobile operating system plus optional account-linked services for mail, contacts, calendar, notes, tasks and file synchronization. The documentation describes Murena Workspace and self-hosting as storage options. These services can replace several separate accounts, but they also create a new account and synchronization dependency. Decide whether you want a hosted service, self-hosted storage or local-only data before enabling sync.
LineageOS’s privacy profile is assembled
LineageOS does not give every installation one identical service configuration. The device build, optional packages, app source, permissions and network tools you select determine the result. This can produce a lean setup, but it demands more research and ongoing maintenance from you.
Do not turn architecture into a security ranking
The available project descriptions establish how each system is assembled and which controls it offers. They do not establish that one project is categorically more secure or private through an independent comparative audit. Security still depends on current patches, bootloader state, application provenance, permissions, account recovery and your ability to update the device.
App compatibility: the tests that matter before installation
Why microG helps but cannot promise success
/e/OS integrates microG to provide compatibility interfaces used by some applications. That can allow a wider range of software to install and operate without the complete proprietary Google code base. The /e/OS support FAQ nevertheless warns that applications requiring the complete Google code base may not work.
High-risk app categories
- Banking and finance: device-integrity checks, proprietary push services, root detection and certification checks can block sign-in or transactions.
- Contactless payment: payment tokenization and hardware-attestation requirements can fail even when the app installs.
- Streaming and DRM: protected video may require certification or a DRM level your chosen build does not provide.
- Push-dependent communication: delayed or missing notifications can occur when an app assumes Google’s push infrastructure.
- Enterprise tools: work profiles, device-management policies and certificate checks may reject an unlocked or modified system.
- Location-sensitive services: spoofing controls, missing proprietary APIs or altered network routing can affect results.
Build an app inventory before wiping anything
- List every application you use for money, work, identity, transport, authentication, media and messaging.
- Mark which ones are essential daily, which have a web fallback and which can be replaced.
- Check the current /e/OS compatibility information, including its banking-app list where relevant, for your exact device and build.
- Search the application developer’s support page for requirements involving Google services, device certification, NFC, DRM or push.
- Plan a reversible trial: keep your original phone usable until sign-in, notifications, payments and account recovery have all been tested.
Compatibility lists change. A result recorded for one Android base or device variant should not be generalized to every /e/OS or LineageOS installation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- [Compatible with]: Fairphone 5,NOT for other devices.
- [RFID Blocking Card Holder]:This Fairphone5 case which made with RFID Blocking Materials holds 3 cards and some cash securely against unauthorized scans and theft.
- [Flip Case With Wrist Strap]:Guards your Fair phone 5 against drops, dirt, scrapes and fumbles and raised edge offers added camera and screen defense.Flip case does as kickstand for hands-free viewing.
- [Unique Texture]:Each case has own texture to offer a unique look and its soft finish provide great grip.
- [Wireless charging compatible]:Charge on without losing the protection and is easy to remove and install.
Installation: what the process actually involves
Common preparation for either ROM
- Confirm support: use the project’s current device page for the exact model, variant, Android base and build status.
- Read the complete device guide: note required stock firmware, firmware versions, recovery steps, partitions and rollback instructions.
- Back up off the phone: copy photos, authenticator recovery codes, messages, contacts, documents and application-specific exports. Unlocking normally erases user data.
- Plan account recovery: verify passwords, two-factor recovery methods and offline backup codes before disconnecting the old system.
- Charge and stabilize: use a reliable cable, a charged battery and a computer with the required drivers or platform tools.
- Accept the bootloader trade-off: an unlocked bootloader can affect warranty terms, security posture, certified payments and resale value depending on the manufacturer and region.
/e/OS browser installer
The /e/OS installer documentation says the browser route works only with a Chrome-based browser that supports WebUSB; Chrome is the stated example. The installer is available only for selected devices. A model appearing in the /e/OS support selector does not automatically qualify for this easier route.
- Open the current /e/OS installation page for your exact model and confirm that the browser installer is listed.
- Use a supported Chrome-based browser with WebUSB enabled and connect the phone as the guide specifies.
- Unlock the bootloader only at the point instructed by the device procedure, understanding that the operation can erase the phone.
- Follow the installer’s prompts for recovery, system images and reboot stages; do not disconnect during a write or verification step.
- Complete the first boot, apply offered updates and test your app inventory before restoring every backup.
/e/OS command-line installation
/e/OS also documents command-line installation for more than 200 devices. That figure describes the documented command-line route, not the total number of supported phones or the number supported by the browser installer. The exact commands, firmware and partition sequence vary by model, so use the device page rather than copying a procedure from another phone.
LineageOS installation
LineageOS installation is likewise device-specific. The official guide determines the required bootloader-unlock method, recovery image, firmware, package sequence and first-boot procedure. Do not substitute an image built for a similar-looking model, and do not assume that an optional Google package is required or compatible without checking the guide for that release.
Bootloader relocking
Some /e/OS device/build combinations document support for locking the bootloader again. That status is not universal. Relocking the wrong build can prevent the phone from booting and may require a complete recovery. Follow only an explicit instruction for your exact model and build; never infer relock support from another phone in the same family.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteUpdates, support and day-to-day maintenance
Patch timing is device and source dependent
/e/OS says it may apply security patches when patches are available from the source. That wording matters: availability and timing depend on upstream patches, the device maintainer and the project’s release process. LineageOS’s charter defines entry requirements, but a charter is not a guarantee of identical update speed across all models.
Best Value
- Compatible with Fairphone 6 5G
- 【TPU+PU】Made of (PU Leather+TPU Soft Shell) durable material, can protect your cell phone from damage.
- 【Wallet Magnetic Closure】The cell phone case with flip stand function makes it easy to read and watch movies, free your hands for daily needs.
- 【Wallet Cover】Built-in card holder for your cards and change, equivalent to your small wallet, space-saving.
- 【Precision cut】This is a leather case for your phone with precision cut holes for easy access to all ports, buttons, sensors and cameras.
Official and community maintenance have different signals
Use the build status, recent release date, changelog and known-issues section for your exact device. Official status generally provides a clearer project-supported path; a community build may still be useful, but you should identify its maintainer, update cadence, recovery method and rollback instructions before depending on it.
Keep a recovery plan
- Retain the manufacturer’s stock firmware and the device-specific restoration instructions.
- Save copies of your recovery and boot images only when the project guide permits it.
- Record the working build number and modem or firmware version before experimenting.
- Install major updates when you have time to test essential apps, not immediately before travel or a critical payment.
- Keep recovery codes and an alternate communication method outside the phone.
Which ROM fits which kind of user?
Investigate LineageOS first when…
- You want a straightforward custom-ROM baseline rather than an integrated service bundle.
- You are comfortable choosing an app source, browser, synchronization method and optional service components.
- You value control over the final software stack and are willing to troubleshoot individual app requirements.
- Your exact phone has a current official LineageOS build and your essential apps work with the setup you intend to install.
Investigate /e/OS first when…
- You want a prepared launcher and set of default applications instead of assembling every replacement yourself.
- You want microG integrated by default and prefer the project’s alternative service defaults.
- You value built-in tracker, location and IP controls and understand their effects on compatibility and performance.
- You want optional account-linked mail, contacts, calendar, notes, tasks and file synchronization, whether through hosted or self-hosted storage.
- Your exact phone has a current official /e/OS build and your essential apps pass compatibility checks.
Choose neither yet when…
- Your phone is absent from the current official support information.
- You cannot unlock the bootloader without an unacceptable data, warranty or carrier risk.
- A required banking, payment, work-management or authentication app has not been tested.
- You need guaranteed certified payments, proprietary push behavior or DRM playback for work or travel.
- You do not have a verified backup and a way to restore the stock system.
A practical decision procedure
- Write down the exact device identifier. Include carrier and region, not just the retail name.
- Check both live support pages. Record whether each build is official or community, the Android base, recent update information and bootloader notes.
- Choose your operating model. Decide whether you want to assemble services yourself or start with /e/OS’s integrated defaults.
- Audit essential apps. Test banking, payments, work, authentication, messaging, navigation and media requirements against the intended build.
- Choose the installation route. For /e/OS, distinguish the Chrome/WebUSB installer from the command-line path; for LineageOS, follow the exact device guide.
- Back up and rehearse recovery. Confirm that you can restore contacts, photos, messages, accounts and two-factor access without the original installation.
- Install and test in stages. Verify calls, Wi-Fi, mobile data, GPS, camera, NFC, Bluetooth, notifications and battery behavior before importing your entire app library.
- Make the final call after a trial. Keep the old setup available until your daily workflows survive several days of normal use.
Common failure modes and fixes
The phone is not detected by the installer
Confirm that your model qualifies for the browser installer, use a Chrome-based WebUSB-capable browser, try another data cable or USB port and follow the guide’s driver instructions. If the model is supported only through command-line installation, use that documented route instead of repeatedly retrying the browser tool.
An app installs but will not sign in
Check whether it requires the complete Google code base, device certification, a particular push service or hardware attestation. Look for a web interface or supported alternative, and test the current build’s compatibility information. Do not assume that reinstalling the same application will fix a service-level requirement.
Notifications arrive late or not at all
Review the application’s background, battery and notification permissions, then identify whether it depends on proprietary push infrastructure. A privacy control, network filter or Tor routing can also alter delivery. Test with the control disabled only long enough to isolate the cause, and decide whether the resulting trade-off is acceptable.
GPS, payments or media playback fails
Check whether location faking, missing proprietary APIs, certification or DRM requirements are involved. Restore the relevant setting, consult the exact device/build notes and verify the app’s requirements before changing the entire operating system again.
The phone will not boot after an update or relock
Stop experimenting with additional images. Use the project’s device-specific recovery procedure or restore the manufacturer’s stock firmware. A relock operation is especially sensitive to build signing and must never be improvised from instructions for another model.
Bottom line
LineageOS is the better starting point for a reader who wants a configurable custom-ROM foundation and accepts responsibility for selecting services and solving app compatibility. /e/OS is the better starting point for a reader who wants a more integrated alternative experience, with microG, changed defaults, privacy controls and optional cloud services already organized.
The decisive question is not which name sounds more private. It is whether the exact phone has a current, maintainable build and whether the exact applications you rely on work under that build. Verify those two facts, back up before unlocking, and treat any privacy control or compatibility claim as a setting to test rather than a guarantee.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
