60
How Android 16's new security mode will stop USB-based attacks
(www.androidauthority.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Apr 2025
60 points (100.0% liked)
Android
18914 readers
214 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.
🔗Universal Link: !android@lemdro.id
💡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: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰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 !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
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
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 2 years ago
MODERATORS
After using Graphene for a year it would be unthinkable to go back. Wild how good a product can be when it is designed with the interests of the user in mind, rather than viewing them as a resource to be harvested.
Can you get Google pay to work in it?
Mobile payment is the only major problem I've encountered. Fortunately, for me it's just a nice-to-have, not a must-have.
I've heard that some banks have that feature within their own app, but I've never actually seen that. If anyone knows of specific banks that support that, please share! I suspect there's no such thing in my country but who knows?
No, also some banking apps won't work. Those are easy enough circumvented by just making the bank browser page an icon. They require some strict certification that is basically exclusive to being android even though Graphene is designed to be more secure.
Google pay apparently just requires too much access, so including it would undermine the entire purpose.
I am a massive fan, and the drawbacks are few but very real if you value the things it cannot do. Definitely worth looking into its deficiencies before switching of course.
Its not cos google pay needs to much access its cos google pay needs a special certificate to sign the operating system. The Google android devs love GrapheneOS as they push lots of security patches and bug fixes so they tried to get GrapheneOS signed. Google then ignored GrapheneOS and their own android devs and refuses to sign GrapheneOS. Its purely because google are assholes who don't want it to work on GrapheneOS.
I'm 100% on linux and FOSS at my home - except for my phone unfortunately because of this reason. I've worked in FinTech, I understand why theoretically they won't want to, but I was hoping some work around had been done. Unfortunately I depend on google pay, so it will have to wait for me.
If you have a smartwatch, does it support contactless payment? I have a Fitbit that does, technically it implements Apple Pay even though Fitbit is owned by Google now. I was able to set it up just fine through the Fitbit app on GrapheneOS (though I don't think I've actually tested it yet).
My credit card works just fine 🤷
Credit cards are less secure then using tokenized payments
Not really a big deal. Card gets stolen, I report it, they refund the charges and send me a new card.
Takes me longer to unlock my phone than just pull a card out of my wallet
As of right now, afaik no, Google pay won't work with it