Also, here is the original article, from It's FOSS News /e/ OS is a hard-to-search-for (please change the name ... again ...), Google-free version of Android, a well-supported LineageOS fork with...
/e/ OS is a hard-to-search-for (please change the name ... again ...), Google-free version of Android, a well-supported LineageOS fork with microG plugged in and assorted consumer-friendly extras.
This has been my main phone for almost two years now (specifically, an S7 Edge, bought refurbished from the /e/ Foundation, running the same preloaded /e/OS), and the result of a crowdfunded project I supported almost four years ago. They have been selling these refurbished preloaded phones here in the EU for almost two years (PS: they've got /e/Fairphones now, too).
It's a good phone, good OS. No contract (duh), no Google, 1-year warranty, at least 3 years of free software support/updates. It was a bit buggy when I first got it, but I haven't noticed a single problem that I would blame the OS for, in well over a year now, and they keep pushing upgrades every couple of months, and it just keeps getting better.
Not OP but I would expect calling and texting to be comparable to the stock OS. It's still Android under the hood and unlike something like Replicant, /e/ probably doesn't mind using some...
Not OP but I would expect calling and texting to be comparable to the stock OS. It's still Android under the hood and unlike something like Replicant, /e/ probably doesn't mind using some proprietary "blobs" to keep stuff like that working.
The only thing I would be worried about is the newfangled RCS thing, as the last time I checked it didnt work on basically anything other than Google's own "Messages" application. Though I heard this is being worked on and might even work nowadays.
Calling is fine. I rarely text using regular SMS/MMS, and when I do, I am using alternative F-Droid app; it is possible I have never used whatever stock texting app came with it. But, FWIW, I've...
Calling is fine. I rarely text using regular SMS/MMS, and when I do, I am using alternative F-Droid app; it is possible I have never used whatever stock texting app came with it. But, FWIW, I've never had any trouble with my SMS/MMS when I've had to use it (primarily receiving 2FA codes).
Regarding @admicos comment, IDK about RCS specifically for the same reason (I used Wire until recently, switched over to Matrix) ... but broadly speaking, the /e/ project is very motivated to rip out and replace any "blob" functionality that has been documented to phone home to Google or other Corporate Overlords ... and ultimately, to replace all closed-source everything. I haven't followed the project's progress over the past year or more; it is possible they have already completed this work.
I really, really hope this phone and others like PinePhone, etc. continue to be available, and become a valid option for more people as their daily driver. Also, yeah that name...hmmm....it looks...
I really, really hope this phone and others like PinePhone, etc. continue to be available, and become a valid option for more people as their daily driver. Also, yeah that name...hmmm....it looks cool on paper but not easy to search for or pronounce, etc. It pains me to state this but maybe they need a marketing or PR sort of person. Nevertheless, I'm rooting for them to succeed!
Worst thing is, it's already their 2nd try at a name. The project/OS was originally called Eelo (Gael apparently thought the French word for "eel" would make a great name for a phone OS...),...
Worst thing is, it's already their 2nd try at a name. The project/OS was originally called Eelo (Gael apparently thought the French word for "eel" would make a great name for a phone OS...), except that name or something really close was already taken and they got sued into changing it.
So they've stuck with /e/ for 3+ years now, always insisting that they are waiting until they come up with the perfect 3rd try.
ETA: Funny ... 3 years after the name change, I still get better search results for /e/OS when I search for "eelo".
Very cool. I recently replaced my old phone with a Pixel 4a in order to run GrapheneOS, but had I known about this earlier I would have strongly considered buying a Fairphone from them. Also great...
Very cool. I recently replaced my old phone with a Pixel 4a in order to run GrapheneOS, but had I known about this earlier I would have strongly considered buying a Fairphone from them. Also great to see them transitively supporting the open-source projects they build off of by marketing for K-9 Mail.
Between /e/, LineageOS, GrapheneOS, and now CalyxOS, it seems like the Android ecosystem is in quite a healthy state (at least for the limited number of supported phones).
I've been a fan/follower/supporter of the Calyx Institute for a decade or more, but this is the first I've heard of CalyxOS ... sounds very similar to /e/ ... only supports a limited number of...
I've been a fan/follower/supporter of the Calyx Institute for a decade or more, but this is the first I've heard of CalyxOS ... sounds very similar to /e/ ... only supports a limited number of devices so far ... I've got an old OnePlus One sitting around waiting for a new ROM ... as soon as I see that get added to their 'supported devices' list, I'll take it for a spin.
Also, here is the original article, from It's FOSS News
/e/ OS is a hard-to-search-for (please change the name ... again ...), Google-free version of Android, a well-supported LineageOS fork with microG plugged in and assorted consumer-friendly extras.
This has been my main phone for almost two years now (specifically, an S7 Edge, bought refurbished from the /e/ Foundation, running the same preloaded /e/OS), and the result of a crowdfunded project I supported almost four years ago. They have been selling these refurbished preloaded phones here in the EU for almost two years (PS: they've got /e/Fairphones now, too).
It's a good phone, good OS. No contract (duh), no Google, 1-year warranty, at least 3 years of free software support/updates. It was a bit buggy when I first got it, but I haven't noticed a single problem that I would blame the OS for, in well over a year now, and they keep pushing upgrades every couple of months, and it just keeps getting better.
How is calling and texting?
Not OP but I would expect calling and texting to be comparable to the stock OS. It's still Android under the hood and unlike something like Replicant, /e/ probably doesn't mind using some proprietary "blobs" to keep stuff like that working.
The only thing I would be worried about is the newfangled RCS thing, as the last time I checked it didnt work on basically anything other than Google's own "Messages" application. Though I heard this is being worked on and might even work nowadays.
Calling is fine. I rarely text using regular SMS/MMS, and when I do, I am using alternative F-Droid app; it is possible I have never used whatever stock texting app came with it. But, FWIW, I've never had any trouble with my SMS/MMS when I've had to use it (primarily receiving 2FA codes).
Regarding @admicos comment, IDK about RCS specifically for the same reason (I used Wire until recently, switched over to Matrix) ... but broadly speaking, the /e/ project is very motivated to rip out and replace any "blob" functionality that has been documented to phone home to Google or other Corporate Overlords ... and ultimately, to replace all closed-source everything. I haven't followed the project's progress over the past year or more; it is possible they have already completed this work.
I really, really hope this phone and others like PinePhone, etc. continue to be available, and become a valid option for more people as their daily driver. Also, yeah that name...hmmm....it looks cool on paper but not easy to search for or pronounce, etc. It pains me to state this but maybe they need a marketing or PR sort of person. Nevertheless, I'm rooting for them to succeed!
Worst thing is, it's already their 2nd try at a name. The project/OS was originally called Eelo (Gael apparently thought the French word for "eel" would make a great name for a phone OS...), except that name or something really close was already taken and they got sued into changing it.
So they've stuck with /e/ for 3+ years now, always insisting that they are waiting until they come up with the perfect 3rd try.
ETA: Funny ... 3 years after the name change, I still get better search results for /e/OS when I search for "eelo".
Very cool. I recently replaced my old phone with a Pixel 4a in order to run GrapheneOS, but had I known about this earlier I would have strongly considered buying a Fairphone from them. Also great to see them transitively supporting the open-source projects they build off of by marketing for K-9 Mail.
Between /e/, LineageOS, GrapheneOS, and now CalyxOS, it seems like the Android ecosystem is in quite a healthy state (at least for the limited number of supported phones).
I've been a fan/follower/supporter of the Calyx Institute for a decade or more, but this is the first I've heard of CalyxOS ... sounds very similar to /e/ ... only supports a limited number of devices so far ... I've got an old OnePlus One sitting around waiting for a new ROM ... as soon as I see that get added to their 'supported devices' list, I'll take it for a spin.
Thanks for the tip.