I have the Fairphone 6 with /e/os (dumbest name and annoying to type IMHO) and though i love it, I don’t trust the business side of Murena. In one recent patch, they removed the seedvault backup app and replaced it with their own backup solution that depends on their own cloud service. Another point is that the support overall is chaotic between Fairphone (the hardware) and Murena. I literally was told to raise tickets to both companies when my WiFi stopped working properly because of the mentioned patch (still no fix - only a the compromises privacy).
I’ve been using /e/OS on a FP6 for a few months now and I’m very happy with it (edit: for context I’m in Europe). I had doubts about whether it could run certain apps like bank or government apps but they work just fine. Most of the default apps work well, but I did replace the launcher because the one that comes with /e/OS doesn’t have as many features as I would like.
Battery life is also better than previous phones I’ve used. I don’t know if that’s because of the hardware or because the OS is less resource hungry.
One thing to watch out for is it doesn’t have a headphone jack, though you can get a separate adapter that plugs into the charging port.
My expetiences differ.
The default launcher regularly breaks, so I need to clean the cache, or wait until it succeeds. So for what I can, I use droidify or obtainium. Some apps also dont work properly as they are reliant on google services. Netflix comes to mind first.
Bank works, but governmental app (ID & payment) dont work, so I am still rel on work phone for those. Check forums, theres a list for these crucial apps and their status.
Other than that it’s been mostly smooth experience.
For anyone interested, there’s also an official lineage image now.
ELI5: Why use /e/OS over Graphene? This isn’t a rhetorical rant; I’m genuinely curious.
Edit: See below. I misphrased this question.
Because the hardware isn’t from google.
I never used /e/ but I used iode (https://iode.tech/) and it worked really well. Main differences:
-
Graphene doesn’t support pattern unlock because they claim PIN is more secure. This is stupid because you can just as easily see what PIN someone typed as the pattern. Since PIN is less convenient most people will use finger print unlock which means you can be easily forced to unlock your phone against your will
-
iode has support for shortcuts when using 3 button navigation, Graphene doesn’t for some reason
-
iode has really nice tracker blocker which can run next to a VPN, Graphene doesn’t
-
Graphene let’s you install Google Services in a separate work profile and separate apps that have access to them from other apps. In iode you will have microG installed system wide
For me that were the biggest differences. When it comes to app support they worked pretty much the same. I’m on Graphene now and it would be too much work to change now but for my next phone I will most likely go with iode.
Couldn’t a guy with a gun force me to enter my pin?
Would police threaten to kill you if you don’t unlock your phone? Not likely. Would they just use your finger and say you agreed to unlock it? More likely.
In defense of Graphene for the first point:
Graphene has a pin scrambler, so the numbers are in a different position everytime you have to enter them.
It isn’t hard at all to get used to it, and it circumvents the pattern recognition bit.
Fingerprint unlock…that’s a different discussion especially with biometrics not being protected under the law, but for first unlock you always have to enter in a pin
Quickly looking at my phone, you can enter in a passphrase (though personally I think that’s too cumbersome). There’s also a swipe option, I THINK that might be pattern, but I’m not sure. I can’t test it, because it means deleting the already in place measures, and I don’t wnat to do that at the moment.
I don’t know enough about other points to comment on it.
Graphene has a pin scrambler, so the numbers are in a different position everytime you have to enter them.
It doesn’t matter. When I’m inserting my PIN on a bus or while standing or line with people behind me or something I know that anyone interested can clearly see my screen and learn my PIN, scrambler or not. Also, scrambler is not mandatory (I don’t have it enabled) so Graphene OS devs explanation that “we will not enable patter ulock because it’s not secure” while normal PIN can be enabled still doesn’t hold.
This is actually a broader problem with Graphene OS. The devs often fixate on some minor security issues that don’t impact 99% of their users at all and refuse to introduce features that they request. It’s exactly the same with supporting phones other than Pixel. 99% of users would be completely fine using Graphene on a different phone (CIA is not going to hack them) but the devs prefer to directly reject all those users.
It’s not as easy to see. If you miss the first two numbers then you can’t reasonably guess it. You can see the whole pattern even if you glanced for 0.3 seconds
Thank you, I was curious as well. Bit I did notice Graphine has pin scramble, so as annoying as it is sometime couldn’t use your finger pattern for your code. Assuming they didn’t see what numbers you were hitting and just your fingers.
-
You don’t own a pixel?
Sorry, I realize that question could be interpreted in two ways: I meant for Fairphone not to try to get Graphene working on their phone. I know Motorola is trying to do that right now, for example.
The team behind GrapheneOS want to to be really secure so they have specific requirements that the phones from Fairphone sadly doesn’t meet.
For a phone to meet all of these requirements AND still being everything that a Fairphone is would make the phone more expensive than the average consumer would be willing to pay. I know several enthusiasts (me included) that would pay for one, but there are simply just to few of us.
From what I’ve read elsewhere (seen some comments here, don’t remember the exact threads) the Graphene team has a specific hardware requirement that Fairphone doesn’t supply. Would be cool to see both projects working together though
GrapheneOS is also open source. Fairphone could realistically fork the project without meeting the requirements deemed necessary for the maintenance effort by upstream.
I don’t actually see why they aren’t actually developing this. A lot of the work is done.
Well in that case, it’s cool to see Fairphone using /e/OS!
That hardware requirement is something they could work on for upcoming phones.
That would be awesome if they do so. I like /e/OS for what it is and does, my FP4 works great after all. That said, having the option for Graphene OS I feel would do nothing but benefit all parties, so hopefully that can be addressed at some point.
Yes, but Fairphone is partnered with Murena (e/os), and there seems to be a beef between them and graphene, so I imagine its out of spite, too.
If Motorola does I’ll dump myPixel9 in a heartbeat… Google has too much of a hand in it…
I don’t believe Graphene supports Fairphone.
Fairphone can’t meet graphene security standards.
Graphene isn’t also that much better than the alternatives (when it comes to things other than security).
It’s mostly a thing of what’s available for your phone. For pixels 6 and newer (and I think some new motorolas as of recently) you can use graphene. If you are on fairphone or a bunch of other devices, you have support for e/OS. In general, graphene is a bit more secure than e/OS, so if you have the choice, it’s probably the way to go but if you don’t have a pixel and don’t want to buy one, e/OS is probably one of the better maintained degoogled android versions out there.
Here you can find a list with a feature comparison.no motorollas are supported yet by GrapheneOS. only new ones projected to come next year will be.
/e/OS is just a fork of LineageOS, with dubious software choices and practices. LOS is available for many more devices and is the cleaner almost-degoogled (like /e/ and other LOS forks) basic AOSP-like experience with lots of customization to use even in old devices that keep running modern android this way.
GOS is much more secure than LOS or any of its forks (including /e/), even more so when the latter is running in old devices that no longer have firmware updates. and it’s properly degoogled, with the option to use Google Services in the best way possible - without it having root access to your system and isolated from other apps, if you so wish
so, GrapheneOS is your best option. if you can’t or won’t, use LineageOS
Hello @[email protected] 👋
You will probably be my next smartphone
Hope you use T-Mobile because that’s the only carrier getting full support. AT&T has only native support, while its MVNOs are shown as “partial” (a.k.a. “pot luck” with regard to which capabilities are supported). Verizon is a total no-go.
I doubt he’s using T-Mobile in Australia. (take a look at his instance then realize lemmy is not just for Americans)
Fair enough - I’m aware it’s not. I was still thinking of the American release since this is the first one officially supported in the USA, and I had just read another article focused upon that a couple days ago - which probably primed me for staying in that mindset. Apologies for being tunnel-visioned. I’m just very frustrated since I’d like to get one, but can’t use it under these limitations.
No Verizon support makes it incompatible with my absolutely essential truly unlimited data via their Visible subsidiary. My job takes me away from home far too much to go without it.
I am interested. If anyone out there has one in the US, I would like to hear your opinons about it
I have the Fairphone 6 (not the plus) running /e/os. It’s pleasant enough that when I had to use a vanilla android tablet I was kind of like (is this how you people live?! 😄 this is awful!)
Could you please tell how long battery lasts? Friend of mine with FP5 and CalyxOS is not very impressed
About 1.5 days, 2 if I stretch it.
I dont have this newest gen6 plus, just the slightly less new gen6 with e/os, but I wouldn’t imagine the difference is huge. Has generally worked about as well as any regular android phone Ive had, with a few minor annoyances like the “paste” button for text often being invisible, such that I just have to press where it should be to make it work.
I want to love this but I can’t compromise my security for this device. If y’all ever add MTE and the other features required by Graphene I’ll be the first in line
Fair enough. But too many people think privacy and security are the same thing.
GrapheneOS is dedicated to both privacy and security, whereas e/os (while it does have some security improvements over stock android) is much more focused on the privacy side of things.
There is some overlap. Can’t have privacy problems if everything’s encrypted and they have no access to your data in the first place
You can still have privacy issues. For example, everything’s encrypted, but you’re the only one with the exact fingerprint so every adveriser and government agency knowns who you are
They only need to know who, where and when, they dont really care about what or why.
Yeah, same for me. I’m sure I’m on top of CIA’s list of “people to hack” so no security compromises for me.
I get the sense this is sarcastic lol. In my opinion though, privacy without security isn’t very useful. Yes I can avoid corporate or government spying when I’m in physical control of a device like this, but what if I get arrested on some false pretenses and they use cellebrite to gain access? Or the same at an airport when traveling? If you’re any form of political dissident, activist, or a member of a marginalized group, being targeted this way is a very real possibility. And as soon as that insecure but “private” device is out of your hands, all that data is free game for the govt.
This is why threat modeling is important.
but what if I get arrested on some false pretenses and they use cellebrite to gain access?
Chances are they can clone the eMMC and wait for a CVE. Or threaten or hold you until you cave. If a lawsuit is your only recourse, I would expect any constitutional barriers to be ignored in practice. Your best bet is to never end up being an explicit target, which may be more difficult for certain individuals.
My threat model considers dragnet surveillance as the primary threat, so I’d compromise on surviving dirty maid type attacks in favor of reducing the information my device gives out.
Obviously if your device is being actively exploited, you cannot be private. But your security requirements increase greatly if your data footprint indicates to them that you warrant targeted scrutiny.
100% agree with you, for who I am and what I do I know that I need a device that is as tamper resistant as possible with the smallest attack surface feasible. That goes for remote execution as much as the evil maid scenario. But this is entirely catered to my threat model and risk tolerance. And sure there is the possibility of the rubber hose cryptanalysis but that doesn’t mean we should give up on securing as much as possible on the device side. It’s the swiss cheese model and we’re plugging a hole at a time lol
I advocate for everybody to use as secure a device as practical, and for these mitigations to be the default, but I’m fundamentally speaking for myself in this thread with my stance on fairphone and /e/OS right now. I want to support repairability and ethical supply chains too without compromising on my more core tech needs
Or you have a funny picture of Vance on your phone and immigration doesn’t allow you in
political dissident, activist, or a member of a marginalized group
or a journalist or a politician. Vast majority of people aren’t any of those and don’t have to worry about cellebrite. Most people here that talk like Graphene OS is their only option really just need deGoogled device, not the most secure phone in the world.
