-
@ 1GLENCo
2025-02-12 13:41:45
You're absolutely right about needing skills to verify it properly. It's very technical. I was a network engineer in my career job, so the extreme technicalities did not scare me away from trying it.
I tried it, not knowing if I would succeed. I did finally succeed in getting it all set up, but I feel that it took way too long, the process was very difficult, and there is a steep learning curve on figuring out how to use GrapheneOS once you've got it installed.
You could lean on someone technical to set it all up for you, but me knowing how difficult it was, I know you can't lean on me personally to do it for you. I say that because even if I set it up for you, I would not be able to handle responding to any technical questions that surely would arise afterwards, I'm already feeling overwhelmed with everything else in my life that I'm behind on. The entire OS has many quirks which require more research, more time, more fiddling with, in order to get it working properly.
It's certainly not for everyone.
Not doing it yourself requires that you trust someone else to do it for you, or to have a Help Desk that can open tickets, answer questions, troubleshoot problems for you as they happen. This is why mega corps like Apple are good for many people, but as long as Apple does not open-source their code, I know I will not use Apple since I'm 100% open-source only from now on.
My only advice would to challenge yourself by buying a Pixel phone (7a or better) and consider it to be your boredom-ending tool. You'll never be bored ever again as long as you own one. If/when you ever feel a tiny bit of boredom, use that time to learn the next thing about what your GrapheneOS phone can do, or read any open Issues you see on their various repositories on github (https://github.com/orgs/GrapheneOS/repositories?type=all) and think about ways to tackle those problems or even propose solutions to them.