I made your post a wiki and to keep it clean I closed it and moved @UPPERCASE comment back here
I can only speak for myself why I debloat my phone / pc / tv /anything with an OS, there are multiple factors:
- There are no custom roms available, the phone is bloated now
- It’s fun
- You get to know the inner workings of your device, what makes it tick
- Removing software that annoys me gives me a sense of true ownership over my device
- I get to purge all those trackers and privacy unfriendly stuff …
- … and replace them with shiny Open Source Software a beautiful community built for me
- Every failure teaches you how to fix stuff, empowering you to help others in the future
- Have I mentioned it’s fun
I am a former embedded system engineer. I tried to “degooglize” partially my Fairphone 4.
In my guide on Tutorial : Install MicroG on Fairphone OS you’ll find more details.
Points brought up when this question comes along include but are most probably not limited to:
microG being included in /e/OS in an unremovable way currently … there are users who don’t like having it if they don’t need it.
/e/OS of course needs microG to support the claim that you can still run most of your favourite Apps, which will be Google-dependent Apps in case of /e/OS’s main target group of users, and those Apps will need microG to have a chance to run on /e/OS.
Bliss Launcher, which is the /e/OS default launcher … being kind of an iOS lookalike and very short on customisation options for the sake of simplicity, which not every user likes.
Sure, you can install and use a different launcher of your choice, but users have to know that first (which is not a given), and users not liking Bliss see the resources poured into it as a waste and better put to use elsewhere in /e/OS.
/e/OS uses its own forks of popular Open Source Apps for crucial tasks like e.g. email and messaging, instead of using the original Apps … which gives control over the default Apps preinstalled with /e/OS to the /e/OS developers, which a project like that would want to have, but there are complaints about patches and new features from the original Apps not being added to the /e/OS forks in a timely manner.
Sure, you can uninstall preinstalled Apps in the default Android way and use Apps of your choice instead, but again users have to know that first, and it’s not an overly simple process, which is another regular complaint about /e/OS.
Lack of clarity in the communication about what /e/OS technically is and which limits it has as a consequence.
Which leaves a number of users surprised when they learn … No, /e/OS can not guarantee to run Google-dependent Apps reliably, it can only try its best, which might not be enough for this or that particular App. You can not degoogle and still have Google.
Making the Exposure Notifications part of microG an optional component to appease vocal Corona tracing critics … which led Corona tracing non-critics to abandon /e/OS because this detour took a lot of time to implement (in which many Corona tracing Apps were not usable with /e/OS) and still might cause problems after OS updates (with the component missing again when it was installed and active before).
/e/OS is kinda beta state as well.
They are not just launching a de-googled custom rom, which I would think is good. No, they try:
- build their own ecosystem → e.cloud
(don’t need it. don’t want it.)
- implement their own app store → cleanpk.org
(there is no info about where the apps come from. who is behind cleanapk, etc… Not trustworthy)
- they fork all possible standard apps
(which is not necessary and makes the whole thing worse)
- microG is always lagging behind
These are all points that put me off and keep me from looking at /e/ or trying it out.
There are alternatives:
- pure LOS
1+2 still takes some work to get the system google-free.
3 is a good approach. The only thing that can be criticized about iodè is that their iodè app is not open source. But I can live with that, because I know the sources.
Hello guys, first of all, thank you for your great commitment on this topic, it is really helpful in the waiting of LOS to be officially available!
I follow the simple uninstall process indicated in the current thread by @rar0 and everything runs smoothly so far, except I cannot sync my agenda through CalDav system. DavX⁵ is ok, but Etar won’t open, it closes immediately after opening. Did someone face the same issue by any chance?
Thank you again!
worked for me
I believe that’s used to let calendar applications talk to something like Davx⁵.
Edit: Too slow
Works well indeed! Thank you
Do I have the full 5-year-warranty on hardware if I was running some degoogled third-party OS (lineage, /e/ os, sailfish etc.), as long as I install Fairphone OS before sending it to Fairphone for repairs?
In the legal text Fairphone says:
[…] if you modify some Android partitions when you flash a Third Party Operating System, which makes it impossible to go back to the official Software version provided by Fairphone.
How should I read this? As long as it’s possible to install Fairphone OS and having that installed before sending it in, I have the warranty?
@ iodè: and how long will we have to wait for this OS?
I asked them in their community forum and they told me that they will get an FP4 in January and start the migration…
Why is there a /e/-OS phone, if I link to Iodé forum???
Because iodéOS forum has defined this picture as og:image…:
<meta property="og:image" content="https://community.iode.tech/uploads/default/original/1X/9d7bcd8ed3cdca25458be2744d5520231c780bfe.png" />
Possibly because they don’t have another picture (with iodé running on a FP4) yet? Still I’m not sure iodéOS has the right to use this picture…
Does anyone know if installing /e/ os raises problems to those partitions ? My plan was to buy a fairphone 4, install /e/ and test it, if I dont like it I would of course like to switch to regular fairphone OS again.
Official factory images are available now, so you can just flash the phone back to stock FPOS if you don’t like /e/.
Oh and welcome to the community
Just keep in mind that relocking the bootloader when reinstalling FPOS still comes with some risks (have a look at e.g. Trapped in fastboot mode with locked bootloader and corrupted /e/ OS).
Thx that some of the nightmares I want to avoid, should be included in the docs if not done yet
edit: doesnt seem like its safe to do that for now
Don’t know if it’s in the docs, but I’m sure FP is working on a fix so that likewise won’t happen in the future…