I’m just an ordinary human that loves learning, solving puzzles, and eating food!
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
Requesting is not begging, hence the purpose of c/community_requests
You seem like an angry person replying out of hate. I’m sorry for whatever it is that happened to you to be this way. It doesn’t give you a right to attack, harass and bully people.
The only FUD around here is you @[email protected]
St Kitts & Nevis perhaps?
From Libera.chat’s guide:
Creating Channels.
Choosing the correct namespace.
Before creating a new channel on Libera.Chat, please take a moment to read up on our namespaces policy and ensure that your channel is named appropriately from the beginning. This will avoid disruptions in the future.
How to create a new channel.
Be identified.
You must be registered and logged in to services to make channels. You can log in by doing/msg NickServ IDENTIFY YourNickname YourPassword
Joining the channel.
The next step of creating a channel is to/join
it.
Pick a channel name without spaces and add the appropriate number of #’s to the beginning, according to our namespaces policy. Eg,
/join #awesomeprojectname
if it is for an official project channel or a community channel about a project, or/join ##yournickname-chats
for an informal channel.
Check that it is available.
You can check that a channel is registered or not with/msg ChanServ info #wanted-channel-name
If it is not registered ChanServ will tell you, otherwise it will show you the public information for the existing channel.
The first person to join an unregistered channel is granted temporary operator status. If the channel is empty and unregistered, you should have operator status now. If not, you will need to talk to the people already in the channel, or if there is nobody there with Libera.Chat staff either in
#libera
or on/stats p
.
If the channel is already registered and you are unable to claim it, you will need to choose a different channel name.
Registering the new channel.
Once you’re sure you can register the channel, you need to/msg ChanServ register #wanted-channel-name
If anyone is interested in power management and detailed explanation, check out https://gist.githubusercontent.com/Peter-Easton/4982f66e93387e02dd2c1d677d71f4f2/raw/4edf9a41ca3a4d053c8ad7bf365f97c923f01c61/battery-management.txt
deleted by creator