- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
While they were happy with what the fairphone 4 brought to the table, they seem to like what was changed for the fairphone 5.
What are you guys’ opinions on this? A welcome change? would you get one if your phone died within the next year?
The Fairphone 4 supports /e/.
It seems graphene is limiting itself to Pixel devices. The developer is also mostly a one man show, so I don’t think he has the capacity to support many devices. He’s probably just busy keeping up with Pixel devices as-is.
What I would like to know is, how do /e/ and GrapheneOS compare.
Can’t really find info on that.
Calyx Os supports the FP4 and announced support for the FP5
That just to be said.
I have e os on FP4 and I would describe my experience as follows: Do you want to switch from IOS to Android without loosing the style of the launcher and gain some privacy? Go for it
If you want an Android that does a lot for you and give you tools like a vpn, a tracker blocker ect… Go for it
If you want to customize your experience (e.g. have an “normal” Android launcher, switch accent colors …) ? You get a very rocky experience to say the best.
And at least for the FP4, some stock apps like the Cam were just not working, but to be fair it seemed like that was a suppychain problem…
I consider changing to calyx Os, expecting to get a more customizable Android.
Is e os able to use all the camera lenses? That’s one problem I have with custom roms, they’re often unable to hook into the camera API in order to use anything other than the main back and front camera
Had to check real quick: Yes in the current Version of the stock cam it does recognise all cameras and even takes snappy pictures. That was the problem before but it seems to be patched.
Anyways due to this problem i switched to gcam
Such a shame that this kind of issue is a thing in the first place. I’d love to use a Fairphone and slap DivestOS on it, but potentially losing two lenses I paid for isn’t great at all
I think that should work, due to DivestOS being a fork of LinageOS just like eOS, and in fact the camera of eOS is just the cam of LinageOS (thats what i meant with supplychain problem). So i assume that DivestOS might just have the same camera app as eOS
But you could probably confirm that by looking into the repos
Now that you say it, I’ve never thought about the default cam, I’ve always been using OpenCamera
Yeaa but the open tool being sold for profit they are not my go to apps anymore…
But I still need to switch my calendar to the newly made fork
Do you mean simplemobiletools? OpenCamera is not part of that, I believe theirs is called Simple Camera
They limit themselves to Pixel devices because they have by far and away the best hardware security. Same reason for Calyx.
It’s mostly definitely not a one man operation and the guy you’re likely referring to has left the project.
Thanks, today I learned.
How do Calyx and Graphene compare?
I see Calyx does support Fairphone.
I would like that as well. In fact I’d like to switch to Calyx, but from eOS.
Check out iode.tech as well. Like /e/OS, also a lineage OS variant but with build in firewall which you can customize (or turn off). Fast security updates and great default informed FOSS apps (unlike /e/OS).