I know it almost certainly isnt, but please god let it be Fairphone.
Privacy
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
While they're at it, can they talk their oem into adding a headphone jack? Literally the main reason I don't already do Pixel + Graphene. (And yes I know one of the supported Pixel phones does have one, but it also happens to be the exact model that I have personally seen do the black screen of death, so no thanks).
my car set up that only gets used once or twice a month:
- phone to usb c charge + accessory dongle
- charge line from dongle to cig port charger dongle to usb c to double 3.5
- 3.5 speaker to cassette adapter
- 3.5 mic to microphone clipped to sun visor
- janky bluetooth button thing zip tied to the steering wheel and routed to cig port charger for answering calls and skipping tracks
Better and cooler than android auto
the audio quality is surprisingly excellent too. stock radios aren't bad, though the speakers have been hit and miss as I take all the junk to different cars. I think there are different types of cassette adapter too. My mom broke the one my parents had from before I existed by putting it in the wrong way and getting the cord stuck inside the slot and I replaced it, but the new one sounded way better in the same car.
Only took like twenty years
I thought Google's plans to kill AOSP effectively put a nail in Graphene's coffin?
Google has made it harder (it may kill AOSP in the long run but not yet) by delaying public release of source trees later than before. To counter that, they partnered with OEM, who in turn are partnered with Google, who are likely to get sources faster.
I still don't how they (and F-Droid) plan to bypass the whole de al with Google killing non-PlayStore aproved© apps, tho. GrapheneOS relies on that as well.
Graphene doesn't rely on any Google Services. They compile the OS themselves and don't include those services.
If you want it, you have to choose to install them.
You can install apps freely with ADB so it will work that way or simply by removing google services, from what i understood(but i may be wrong) it's done by using google services so you need to uninstall them
Can they please make it work for Samsungs? I made the mistake of getting an S23 and I didn't realize it was incompatible with all non-standard OSes.
Samsung phones blow e-fuses when you unlock their bootloaders, so there's no going back. I think this would prevent a proper GrapheneOS installation.
Perhaps Samsung could start shipping phones with GrapheneOS natively installed, but since the phone's owner would not have control of the OS, that would arguably not be GrapheneOS as we know it today. Or maybe Samsung could change their chain of trust implementation to be more like Google's, allowing the bootloader to be re-locked.
Wow. That is some grade A bullshit!
that reminds me, samsung has been advertising knox on their TVs now. samsung really likes permanently self damaging electronics
Samsung would never. Their customized OS is this nested egg of vendor lock-in, with your data at the center. They would rather harvest data from 99.5% of their customer base than see the 0.5% of us that actually like their equipment buy it and do anything other than sink into their ecosystem.
I got a z flip 4 the other week for 90 quid off ebay. Was in perfect condition, and it felt nice in the hand. Liked the big screen, all that stuff. They I started running into the Samsung customised OS. It took less than a day to piss me off so much I gave it away.
Samsung make really nice phones, but then ruin them with their custom OS and bloat.
I have a pixel 8. I've wanted to degoogle myself for years. How risky is Graphene to install? Do I need to root it? Can I brick it? Are there things it does that Google doesn't? Apps that don't work for it?
If you use the web installer provided on GrapheneOS website, you can't fuck it up. Just make sure you use a chromium browser when you do it, for some reason it crashes on Firefox (but it didn't brick my phone, so don't worry)
No root needed, just follow the instructions on the website (read before doing it). You probably could brick it like anything else, but I didn't and I barely knew what I was doing (and like I said, it crashed on me when trying it via FF).
Neat things they do that Google doesn't (afaik):
- Auto turning Wifi and Bluetooth off if it's not connected (security and saves battery)
- Being able to deny wifi permission to an app just through regular settings (Stock androids need root to do that). Like, I use Gboard, but it had no wifi, so it can't send telemetry to Google.
Notable things that don't work:
- Some banking apps, really depends on luck. My debit card bank doesn't work, but my credit card bank does. Check this list to see if your banking app is tested. The reason is out of GOS hands, Google changed from SafetyNet to Play API or smth. If you can, just do web banking.
- RCS is finicky enough on stock devices, but GOS ramps it up to a new level. There's workarounds, but don't be surprised if it breaks a few months later. Highly recommend getting your friends/family to communicate with you through a different E2EE app, like Signal, XMPP/Jabber, etc. or else you'll be stuck with insecure SMS
- Some people have Android Auto issues? Idk, I've never used it
Good on ya for sharing a helpful response
-
Follow the instructions as they're presented and you'll be fine
-
Installing it will make rooting easier, but afik root is not required (though you will be accessing the device at the recovery/bootloader level, something with far more control than root)
-
Yes, pay attention, follow the instructions and you'll be fine though
-
Respect your privacy, allow you to sandbox apps which want to spy
-
Everything should work because of the sandbox function, the same cannot be said for most other custom ROMs unless the Google apps have been installed.
If, God willing, it ever becomes available on a dual screen phone, I'll shit bricks.