I mostly use apps installed from F-Droid, so I’m not sure how I’ll use the phone, except that it’s sometimes required as a contact method.
GrapheneOS
Giving more money to Google after they fucked u in the arse. Brain dead move
- In what way?
- What do you suggest, live brain dude?
Linux or bust. We need to humble these companies at any costs. Open software open hardware
Okay, I’ll just install debian on my phone then, thanks for the advice.
Jesus!
Which phone do you suggest then? Like I ALSO have a Librem 5, it’s just a lot of quirk. Its also not an answer to someone with an Android phone already unless they just have extra money for it. Hopefully we see better Android emulation on Librem type phones though and that gap closes.
This is a good idea, except that it requires money. I already have an old Pixel right here that I can put Graphene on.
I guess my point is, it’s not necessary to harass people about their choice of phone OS before you know their situation. 🤷
I’m not very good with technology, so I don’t understand most of what you’re saying. Could you explain it simply, as if I were five years old, how we protect the FOSS community and stop Google to pressuring us.
Leaving android
For what in partricular?
A pine phone which is otw now
Solid option
It’s a bit dated but it has an open bootloader which is what I mainly want.
Yeah, not the most impressive hardware, but it is what we have
A slow Linux phone is still better than a pedospyphone.
Made me wonder if they introduced CSAM detection to fill their collection…
I feel embarassed to say this as someone who is fairly techy, but I’m a little confused by the whole brouhaha.
Is Google making changes to Android, or to AOSP?
If Google is making changes to the Android fork they put on their own phones, then fuck 'em. Use Graphene. Use e/OS/, use Lineage…use something that forks their own branch of AOSP and Google can pound sand because those forks are in no way obligated to make the same changes as Google. AOSP is open source for that very reason.
If Google is making those changes to AOSP itself, which means that anyone who uses AOSP as a base have those changes by default, then isn’t Google obligated to keep those changes as Open Source, in which case anyone else who uses AOSP can just remove them from their own fork?
Someone explain like I’m a particularly dim five-year-old, please.
I’ve also been confused about this, but this is my take on it.
You’re correct that they are making these changes to Android and not AOSP. This means that an OS like Graphene or e/OS/ will still be able to use sideloaded apps and other appstores like F-Droid.
I think the reason everyone is freaking out about this, is that it hurts appstores like F-Droid. It has a chilling effect on apps that are released to alternative app stores and may cause those stores to fail over time, thus killing FOSS apps at the point of distribution.
That said, this is also over my head technically, so I would love if someone more knowledgable could weigh in.
install them with adb. its a crucial feature for developers, so they won’t easily get rid of it.
How do you get updates when installing via adb?
Install them via adb, probably
