I’m just an ordinary human that loves learning, solving puzzles, and eating food!
For obvious reasons, we prefer linking updates and posts from our Mastodon instance rather than to the Twitter version of the same content.
End users who prefer RSS can add either:
https://grapheneos.social/@GrapheneOS.rss
or
https://grapheneos.social/@GrapheneOS/with_replies.rss
deleted by creator
The official statement from Google can be found here: https://support.google.com/pixelphone/thread/241474288
As for the bug eport itself, that is available on their issue tracker here:
https://issuetracker.google.com/issues/305766503
https://issuetracker.google.com/issues/307592536
The repos issue tracker is slightly more up to date.
There are some banking apps and apps in general that may be problematic. For such cases, here are the possible work around solutions.
You’re quite welcome.
No issues with running the RSA Authenticator (SecurID) app on both the Pixel 6 and 8 on the latest Android 14 build of GrapheneOS.
See previous reply for details as to why it wasn’t working for non-GrapheneOS users as well - over a year ago is when it started being problematic.
It works as far as I can tell. However, it wasn’t always the case.
My company also mentioned that GrapheneOS isn’t supported by them.
Version 4.3.12 is - I just installed it on both the Pixel 6 and the new Pixel 8, both running the latest GrapheneOS builds with Android 14.
they don’t support grapheneos though, specifically said the app won’t work on it
In the summer of 2022, numerous issues arose for non-GrapheneOS users as well, as reflected in the reviews. This was because the SecurID update began utilizing the Play Integrity API to detect non-certified OS/devices. The Play Integrity API has since replaced the now-obsolete SafetyNet attestation API.
Here’s a crowd-sourced list of international banking apps that are compatible with GrapheneOS:
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
The issue tracker has slightly more current banking app reports:
https://github.com/PrivSec-dev/banking-apps-compat-report
Some banking apps may be problematic and here are some possible workaround solutions:
https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos
Hi, I haven’t heard anything specific regarding AOSP’s gallery app that we bundled with GrapheneOS.
We aren’t here anymore, this is not where to get support for our project.
Please check use our official channels for support.
Issue tracker: github.com/GrapheneOS/os-issue-tracker
Live Chat support [matrix] : grapheneos.org/contact#community
Hi, @beknofaknu
Thank you for this post and the insightful information.
Firstly, I’d like to apologize for us being a way the last bit from this community on Lemmy.
I’ll be catching up on some posts soon.
Secondary. Would be able to please share the permalink to the peertube video mentioned in your post.
Thanks again!
Thank you for posting this @Lunacy@lemmy.ml
Thanks for adding this announcement @Lunacy@lemmy.ml
Thanks for adding this post @Lunacy@lemmy.ml
Hey that’s pretty cool! I’ll give your app a try this evening when I’m off work. Thanks
Lol, we always get one down vote every time. Think we all know who is doing that and constantly attacking us with harassments in their posts on other communities here. What a sad life they must live, full of anger and hate.
It certainly is. Super excited about it.
Thank you for your feedback.
Suggesting we use personal accounts for discussions like this overlooks the accountability we have to provide accurate and transparent feedback on issues directly impacting our infrastructure. Constructively critiquing software that affects the performance of hosting critical organizational chat rooms is not entitlement—it’s responsibility. These concerns are real and measurable, with tangible effects on user experience and scalability.
This is based on firsthand experience hosting our own Matrix homeserver instance for our community space chat rooms using their software, not on tautological reasoning.