Android

18720 readers

68 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 2 years ago

MODERATORS

[email protected]

185

Researchers uncover Android zero-day exploits affecting billions of devices, used to unlock a protester's phone in Serbia (techcrunch.com)

submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]

27 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 56 points 3 weeks ago (20 children)

It should be noted that these were already being mitigated by GrapheneOS before this came out, mostly thanks to the hardware-level USB disable feature. https://grapheneos.social/@GrapheneOS/114081913638905015

[–] [email protected] 20 points 3 weeks ago* (last edited 3 weeks ago) (16 children)

I wouldn't use Graphene OS personally since they refuse to accept negative press or the fact there may be alternatives. It is all about Graphene OS and how Graphene OS is grand. Don't you dare criticize or use your device in a way they don't endorce. I'm not even sure they would be willing to admit if there was a serious flaw in Graphene OS.

With that being said, I think Linux and AOSP have made a lot of progress in the right direction. Just because I don't like the Graphene OS team doesn't mean that some of there techniques can't be applied outside of Graphene OS. Android and the Linux kernel have bith seen significant improvements in security.

Graphene OS will not work for everyone. It also only supports a handful devices even thought there are other devices that support bootloader relocking. Graphene has decided to instead frame everything that isn't a Pixel running Graphene as universally bad.

[–] [email protected] 25 points 3 weeks ago (1 children)

I agree, Graphene is not for everyone, and what you wrote is a perfectly fine opinion when it comes to privacy- and security-focused daily driver OS's for smartphones. If you're a protester or a journalist though, it's all or nothing. There are no alternatives, no compromises that can be made. If you use a smartphone you are at risk, even if it's a Pixel with GrapheneOS.

Graphene has decided to instead frame everything that isn't a Pixel running Graphene as universally bad.

They did say on several occasions that they would support other phones if they weren't locked down (Samsung) and commended the security of upcoming Mediatek and Qualcomm chips.

[–] [email protected] 1 points 3 weeks ago (1 children)

I'm not sure I would even recommend it for a journalist. There are better tools for desktop and having basic opsec will go way farther than any tool. It also doesn't support MicroG which is a deal breaker for me.

[–] [email protected] 9 points 3 weeks ago

the debate on microg v sandboxed GPS is not settled tho

for example with sandboxed GPS you have option to cut network connection to GPS both store and service and maintain functionality of most apps

while with microg you are still pinging google with the spoofed identity

furthermore, microg is generally used in deployments like lineageos which is inherently insecure while buying decently private because bootloader is not locked unless it is pixel and because it is running in debug mode.

I think calyx upgrades on this decently from OS perspective.

Nobody should be going to a protest with their MF bootloader unclocked, bottom line.

GrapheneOS also has several hardening upgrades deployed through out the OS that is lacking in stock android. This upgrades are critical if your concern are state actors who have access to the best and freshest zero days sometimes know as backdoors depending on who you talk to.

load more comments (14 replies)

load more comments (17 replies)