Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Isn't it actually a privacy nightmare?
https://cybernews.com/security/google-pixel-9-phone-beams-data-and-awaits-commands/
But security ≠ privacy. So if you want to give all your data away, just not directly but through google, it's perfect.
Or you could use graphene.
will using a custom ROM not break the security of the device as designed by Google? or will relocking the bootloader be enough?
Graphene is custom developed specifically for the security hardware features of pixel phones
As designed by Google? Yes. Does it break security in general? No. I am not deep into Android security, but AFAIK the main issue with custom ROMs is the open bootloader, which Graphene does not have.
All of the security features mentioned in the article even started from work done by GrapheneOS - they're simply upstreamed now
I haven't seen any security problems unique to custom ROMs, especially if you relock the bootloader. The biggest issue is that you can lose device integrity or safetynet checks, which means you may not be able to use some apps, like banking.