I don't think I need to say much about why normal users should not buy it: old hardware, bad camera, ridiculous pricing
Running outdated hw is especially damning. I doubt any OEM will continue to update the OS after the components are no longer supported
Conversation
For enthusiasts, it is literally an existing phone slapped on an XDA logo and LineageOS.
If it wants to legally ship with GMS, it still needs to pass CTS, and you still cannot root without breaking SafetyNet.
Might as well just buy any popular phone and flash any custom ROM.
2
1
104
For developers, this is no different than any other smartphone, maybe even worse than Pixels.
If this phone is for developers, I'd expect almost everything, including the bootloader, to be open source so people can *really* mess around with it.
Look at PinePhone, not this one.
3
2
145
So yeah, unless you are a diehard XDA fanboy which drolls over the XDA logo when you look at the back of the phone, I cannot see any reason why anyone should buy one.
Let me know your thoughts though, I'd love to know the reasons why you would disagree 😉
7
2
149
Replying to
You're forgetting privacy enthusiasts who do not want to mess with their device and want to have a google free phone with a keyboard out of the box.
9
This Tweet was deleted by the Tweet author. Learn more
Both Copperhead and Graphene have very limited hardware support, plus a number of organisational limitations. I've been using e.foundation ROMs for over a year and like it quite a lot.
3
2
/e/ is trash. It's just LineageOS with MicroG slapped on top (which is not google-free at all) and it ships with some 20 prebuilt apps. /e/ is far from a fully open source and Google-free OS, it just doesn't make sense using it. Just use LineageOS with MicroG if you like that.
2
twitter.com/DanielMicay/st
microG is an alternate implementation of Google services, not a replacement or alternative to them.
I wanted to post this as a response to the post from , but they blocked me after I dismissed the nasty personal attacks they sent me via DM.
Quote Tweet
Replying to @DanielMicay @Stamina_Affrim and 4 others
Also, worth noting that despite a lot of apparent confusion about it, microG is primarily an implementation of Google services. Aside from the supplementary network location options, it's an alternative implementation of a small subset of the client-side APIs for Google services.
1
twitter.com/DanielMicay/st
Their participation here is based on their personal grudge due to the poor reception to their long, unconstructive posts in the GrapheneOS Matrix channel over a year ago. It was essentially concern trolling promoting /e/ which is a much different project.
Quote Tweet
Replying to @topjohnwu @kravietz_ and @konrad_it
I reached out to @kravietz_ to figure this out. They have an intense personal grudge against GrapheneOS. A bit over a year ago as someone not active in the community, they posted long rants in our Matrix channel with poorly informed, unconstructive criticism and promotion of /e/.
1
I interpreted their posts as being from someone with a poor understanding of GrapheneOS. They were (and are) misinterpreting the purpose, goals and what it provides. They're certainly acting in bad faith now and that reinforces my original impression of their concern trolling.
And to be clear, GrapheneOS has no beef with /e/. It's not their fault that someone came to our channel to concern troll and present unconstructive advice / criticism. Our goals, approach and focuses are much different. We aren't a business and we don't see them as competitors.