**Wanted to update this post with a website I found that has info about this topic for regular people, in case anybody finds this later. ** Privacy Focused OS For Everyone
It has info about the different os options as well as apps for phones using regular android.
Pretend I am five and please be nice.
Say I want to free my phone and tablet from samsung/google/skynet but I neeeeeed to be able to use my printer and external cd drives and their silly proprietary apps, as well as flash drives, cds, and normal apps without alternatives like bandcamp and libby and and all that. I also need to be able to use government websites and use my wifi and pay bills and just generally do everything that I do now on samsung's/motorola's software.
(Most of these things were issues for me when I tried to use linux years ago which is why I'm listing them. I do not possess the technical ability to solve these problems on my own when they come up. I also do not possess any other devices to use if my main ones can't do these things anymore.)
Is this realistic in 2024 for Graphene or any other free open source os? And if it is, how do I install it safely and properly?
Are there any known issues with it like slowness or not being able to use the camera, etc? Most of the places with information about this stuff are not written in a langauge I speak.
Edit: does anyone want to work on creating or collecting some simplified tutorials with me? I'm thinking of installing one of these on my phone and it it goes well I will probably write the details down. It might be good to have a place for other people who have done so, or want to, to do the same for their respective devices.
Honestly, I'm with you - I've had people here even get indignant about how "easy it is" to install and use. Yet I have never seen someone here share clear, simple instructions. The official install instructions have phrases like "high quality standards compliant USB-C cable" or "Get a carrier agnostic device" or "4th and 5th generation Pixels only show the first 32 bits of the hash so you can't use this approach."
How do I know if my USB-C cable is compliant? How do I make sure my device is carrier agnostic? Hash? I know for most people here, these are trivial questions, but they are opaquely technical for 99% of the people out there. That's fine, by the way - there is nothing wrong with a quality OS meeting the needs of a hobbyist community with the technical know-how to use it. Just don't pretend that it is not a niche OS or that it is simple and user-friendly. I say this without any criticism, just as a basic reality check.
PS, in case it was not obvious, please do not answer the example questions. I know that they have answers and that many people here have that knowledge at hand. They are examples of just a few issues that require a base technical knowledge that not everyone possesses.
My partner is trying to break into open source and I keep suggesting that she tries to focus on making and producing quality documentation for existing projects.
Documentation on most projects sucks donkey balls and if you aren't used to reading through 16 seemingly unrelated forum posts before you even start, you're gonna have a bad time.
Seems like a bad idea unless she’s very familiar with the projects she would help document. Documentation is notoriously not something that can be produced by a newcomer, because it requires experience that a newcomer doesn’t have.
I guess the best way for a newcomer to help would be to try to use the product and ask every little question they have to make sure they receive the correct answers and context and, at the end of the process, enough knowledge would be gained to contribute at least one piece of documentation. But the bulk of the knowledge would still come from people that already know the product, so in terms of efficiency it’s way worse than having the authors write it.
Of course, if the authors are unwilling or unable to write good (or any, even) documentation, having someone that has the will to gather the scattered information into a central place and work on it so it’s digestible and high quality is still unbelievably useful.
But yeah, my point being that documentation is far trickier than it seems as far as open source contributions go.
They say a carrier unlocked phone is recommended because carrier locked phones often disable the option to OEM unlock your phone in the Developer settings.
Well, you see, now we are having a conversation about the difference between "carrier unlocked" and "carrier agnostic," which only seems to prove my point.
I'm not a person who had previously done much messing around with their phone but I have installed Linux on several computers. I put graphene on my phone nearly a year ago and I recall the process being fairly straightforward. I think I just followed the instructions on their website.
Maybe it's not an "any idiot could do it" level of user friendliness but the examples you've listed as stumbling blocks aren't exactly brain-busters.
The graphene install docs is in your language and will walk you through the install process. Their support page points you to discord, telegram, matrix support channels as well.
As a general rule anyone that asks for a non-proprietary thing that will do everything their proprietary thing does without alternative solutions allowed is so far from the reality of non-proprietary software in a proprietary world that they can not be made happy so I'll leave the support of that to others.
There is a lot of mixed information out there about whether or not non-proprietary things have 'caught up' in usability for the average person. Thanks for the feedback.
Some things are less important than you might think. A slave doesn't worry about paying rent or buying new tools. So is slavery a useful convenient solution. The exploitation has a hook. Some people like living in the matrix.
Graphene has google play junk. I don't touch it, but it is there.
You'll still be able to use Google Play and the apps found there, if you want to. I'd heard of people having trouble with banking apps. I access my bank using their website, not an app.
Just understand going into this that the priority is privacy, not compatibility. Maybe keep your old phone around in case there's some must-have app that doesn't work but you need occasionally.
I don't have any complaints about the performance of graphene on my pixel 7a but I don't do much outside of texting and browsing webpages. I also get about 3 days of battery life out of a charge.
One thing to consider is Graphene and Calyx both say they are designed to work on Google Pixel phones. If you have a different kind of phone you should search on your phone model and see if anyone has installed those on it and how it went for them.
Other than that, they are basically just de-googled Android so I would expect the things you mentioned to work. You can get many apps from Fdroid or use the Aurora client to get them anonymously from the Google store, though I don't know for sure if that works in all circumstances. My brother uses Calyx and I know he has been able to install at least one proprietary app (for his car) and I think one from an insurance company or something like that.
edit: update, I just checked the CalyxOS site and it says they also support Motorola moto and the Fairphone.
Because GrapheneOS is only available for Pixels, and current ones at that. I'm still on a Pixel 4a, and GrapheneOS considers my phone end-of-life and support for it will eventually stop. So unless you just got a brand new Pixel... kind of a waste.
Secondly, since you're less tech savvy, you'll probably want to use the official installation via WebUSB but as a point of warning, Firefox purposefully chooses not to use WebUSB or WebSerial because of security risks.
Google built WebUSB and WebSerial because Chromebooks are a useless fucking joke of a computer without them, since it doesn't have a real OS, and just a glorified web browser. This is fuckstupid, pathetic, and absolutely a security risk.
That being said, the WebUSB install is definitely going to be the "easier" path for you, but you'll be forced to use Chrome to do it.
Are there any known issues with it like slowness or not being able to use the camera, etc?
No idea, I always went LineageOS because it supports more devices, has better support for Google services, and isn't quite as obsessive about privacy. Unlike GrapheneOS, updates for devices will come as long as maintainers are able to make new versions of Android run on older hardware. With LineageOS, I'm looking at likely years of security updates for my Pixel 4a.
Alas, it looks like none of the devices I own right now are actually compatible with Calyx, graphene or lineage right now. :( I own less popular models of devices, but I erroneously thought any android device would be interchangeable here when I first made this post.
For LineageOS at the very least, you might be able to find an unofficial ROM for your device over at XDA developers forums. There are often ones built for less popular phones, but they don't have as much frontline support as the supported devices listed on the LineageOS site.
...but it's exactly as I said earlier. There are technical walls to scale, including whether or not you even have access to the right hardware to start the process to begin with. It sounds like you learned a bunch today, which is good, and hopefully you can either find an unofficial ROM that works for you, or you can eventually invest in a phone that fits one of the ecosystems that you would like to pursue.
I have an unlocked galaxy s21 ultra and was considering giving it new life with a new OS but the amount of "don't brick your Samsung" and "galaxy phones aren't compatible with custom roms" put me off. Not sure what to do either
I have a moto g 5g 2023 which is apparently different than the moto 5g, and an A9+ tablet. I found a thread talking about the difference and some regional reasons why my phone and others like it don't always have support. It looks like versions of these OSes often just don't exist for a lot of devices, because fewer people use them. The lineage website did have a lot of samsung devices listed though and might have yours, so there definitely are some options. But it's not every phone, which sucks, but i think the warnings about bricking are real and not just discouragement.
Honestly opening up software on consumer devices should be the law and mayyybe one day it will be in the us (eu allowed some semblance of alternative app stores recently and that's something? ) but I think those of us with the less common and budget mobile devices might just have to wait for now. Or continue living inside the matrix, as someone else here said.