How to get started
/e/ is currently available for more than :
We’re constantly adding new models to our list of supported devices.
You can find the list of supported smartphones here.
Ready to install /e/? Then follow the steps below and you’ll soon be on your way
Onze community Forum is de beste plaats om meer te weten te komen over het project en nieuwe functies, of om hulp te vragen / je oordeel te geven.
Voorkeur om te chatten? Developers en expert gebruikers zijn ook beschikbaar om technische ondersteuning te bieden via chat met Telegram.
Ben je een developer die graag directe toegang wilt tot onze middelen, of een probleem wilt melden?
Join one of the /e/ projects looking for contributors.
Help solving issues listed here.
Start building /e/ for a new device and become a maintainer.
Maybe you have other suggestions, feel free to contact us! Send an email to email@example.com, with a clear subject line (like : ROM Developer Mediatek).
/e/ is forked from LineageOS. We’ve modified several parts of the system (and we’re just beginning): installation procedure, settings organization, default settings. We’ve disabled and/or removed any software or services that were sending personal data to Google (for instance, the default search engine is no longer Google). We’ve integrated microG by default, have replaced some of the default applications, and modified others. We have added a synchronization background software service that syncs multimedia contents (pictures, videos, audio, files…) and settings to a cloud drive, when activated.
Also, we’ve replaced the LineageOS launcher with our own new launcher, written from scratch, that has a totally different look and feel from default LineageOS.
We’ve implemented several /e/ online services, with a single /e/ user identity (firstname.lastname@example.org). This infrastructure will be offered as docker image for self hosting: drive, email, calendar… to those who prefer self-hosting.
We have added an account manager within the system with support for the single identity. It allows users to log only once, with a simple “email@example.com” identity, for getting access to /e/’s various online services (drive, email, calendar, notes tasks).
Absolutely! /e/ was not made for geeks or power users, it’s designed to offer a credible and attractive alternative to the average user, with more freedom and a better respect of user’s data privacy compared to mobile operating systems offered by the worldwide duopoly in place.
We really appreciate your involvement though. Your beta-testing and valuable feedback will help to make this alternative available to many more people who can’t do this sort of thing for themselves.
In that case, you probably won’t be very happy with /e/, don’t use it!
No – we’re using the rules of open-source software. Just like AOSP-Android is forking the Linux kernel work, just like LineageOS is forking AOSP work, /e/ is forking LineageOS work. /e/’s focus is on the final end-user experience, and less on the hardware. We encourage core developers to contribute upstream to LineageOS. When thinking about LineageOS vs /e/, think about Debian vs Ubuntu.
Yes – a simple 1-click (well, that may be 2 or 3!) “over the air” update feature is available in settings.
Depending on the smartphone model, /e/ is forked from Android 7, Android 8 or Android 9. The /e/ experience is consistent across the various versions of Android.
No – we’re in beta stage at the moment. The system is pretty usable though, but use it at your own risk!
Yes! we are almost ready to launch the first premium grade refurbished smartphones with /e/! Discover them here.
No – please report bugs and send suggestions using our GitLab platform as explained here. Please avoid using email or IM for reporting issues, as it’s not an efficient process.
You can use our community forum to report suggestions. If you have suggestions related to improving privacy, you can also send an email to firstname.lastname@example.org.
We had to change our name for legal reasons as explained here.
/e/ is a textual representation of our “e” symbol which means “my data is MY data”.
It’s the current project codename, we will probably introduce a new and more convenient name for our mobile ROM in few months.
A known issue is affecting a small portion of users.
This problem leads to over-consumption of mobile data, and we are still working on fixing it.
Possible workarounds until we push a fix using over the air system update:
1- delete manually .thumbdata-something files at: https://ecloud.global/apps/files/?dir=/Photos/.thumbnails
2- change perms of /sdcard/DCIM/.thumbnails/ in read only (should only slow down a bit gallery app): chmod 0400 /sdcard/DCIM/.thumbnails/.thumbdata* ( Needs ADB connection)
Until we find a solution that will be available using our over the air system update, you can also try to do the following:
disable mobile data in Settings
or disable image/video synchronization in:
Settings-> Accounts-> */e/* ->username->Pictures and Videos
A know issue is affecting some Galaxy S7 smartphones with /e/OS.
This problem prevents bluetooth to work correctly.
A fix is now available as an over the air system update.
Some weird behaviour or even crash can happen using the default Camera application in /e/OS on Galaxy S9/S9+
If that happens you can try this:
- open the default Camera application (OpenCamera)
- go to settings
- enable “Use Camera2 API”
In some cases (/e/OS, probably Nougat version only) it’s not possible to send MMS using Free operator in France.
The reason is that the APN configuration is not correct.
Until this is fixed through an over the air system update, the easiest way to fix it is as follows:
1- Reset APN configuration:
In Settings > More > Cellular networks > Acces Point Names
Press on the 3 dots button at top right, and then Reset to default
2- Configure Free Mobile APN
Still in Settings > More > Cellular networks > Acces Point Names
Press Free Mobile
Press on MMSC and enter http://mms.free.fr
Press APN type and enter default,supl,mms
Press on the 3 dots button at top right, and then Save
More details and an alternative fix is available online at: https://gitlab.e.foundation/e/os/android_vendor_cm/issues/2#workaround
Some useful information is available on this page: https://e.foundation/email-configuration/
Try to connect to https://ecloud.global with the following credentials:
full login: email@example.com
:warning: use only lowercases! (MyName@e.email is incorrect, use: firstname.lastname@example.org)
your previously defined password
If you do not succeed to authenticate, try to change your password by clicking “Forgot my password” at https://ecloud.global/login