Unfortunately, PayPal permanently locked our GrapheneOS Foundation account today. No reason has been provided for the account being locked. All we've done is accept donations. We added our bank account information yesterday in order to begin withdrawing money and it was locked.
GrapheneOS Foundation is a non-profit organization incorporated federally in Canada. PayPal required us to provide both proof of identity and address for each director along with other documents, etc. to have our account approved. We received CA$3,950.75 of donations through it.
Our GrapheneOS Foundation non-profit finally has official bank accounts and can directly accept Interac e-Transfers in Canada:
We'll be adding more donation options (Lightning inclusive) in the near future and also a simpler way to donate via credit card without an account.
GitHub Sponsors still charges 0% fees for credit card donations from individuals so we want to keep it as an option. We'll look into setting up an account for the GrapheneOS Foundation. We plan to add Stripe as another option for people who don't want to make a GitHub account.
We are also looking into Wise as a SEPA option for EU donations.
GrapheneOS version 2023072600 released:
https://grapheneos.org/releases#2023072600
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/6534-grapheneos-version-2023072600-released
For reference, the app uses this class: https://developer.android.com/reference/android/location/Geocoder
Can confirm no Geocoder implementation currently exists.
It would require us adding it to the GMSCompat layer that we provide for sandboxing Play Services.
Please add an issue to: https://github.com/GrapheneOS/os-issue-tracker/issues
If this is something you'd like to see provided.
Hey nostr:npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c would you know anything about this?
Investigating...
Vanadium version 115.0.5790.138.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/115.0.5790.138.0
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/6509-vanadium-version-115057901380-released
70.7 still had issues with Back functionality too, not tried 70.8?
GrapheneOS version 2023072400 released:
https://grapheneos.org/releases#2023072400
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/6496-grapheneos-version-2023072400-released
This release is now in the Alpha channel. It needs much more testing than usual, focusing on carrier support, both for existing setups and after resetting network settings and/or adding a new SIM.
GrapheneOS version 2023072400 released:
https://grapheneos.org/releases#2023072400
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/6496-grapheneos-version-2023072400-released
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z started to have weird back button/gesture behaviour over the last couple of releases.
When searching and tapping on a result, where once going back took me to the results again. Now it returns me to the home screen.
This was on 70.7, noticed 70.8 is out will test again.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z started to have weird back button/gesture behaviour over the last couple of releases.
When searching and tapping on a result, where once going back took me to the results again. Now it returns me to the home screen.
Auditor app version 74 released:
https://github.com/GrapheneOS/Auditor/releases/tag/74
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/6368-auditor-app-version-74-released
See https://attestation.app/about and https://attestation.app/tutorial for info about the app and optional monitoring service.
That is my experience however there are other apps out there with it and there are plenty of discussions related to it on the Google Issue tracker. Alas the fixes appear to have been focused on GBoard over the baseline AOSP keyboard.
It's not the GrapheneOS keyboard it is simply the default AOSP keyboard that was forked to create GBoard at which point Google stopped updating it properly.
Any AOSP based OS which includes this has the issue as it is a conflict between it and Jetpack Compose used to provide the text input field.
Many GrapheneOS users use Florisboard or GBoard with network permission revoked or you can use any other FOSS keyboard to replace the stock one.
However if you use a password not a pin for device access make sure it works BFU (Before First Unlock) otherwise you'll cripple access if it doesn't and it is made default.
Ever wanted to know what it feels like when you flash GrapheneOS?
Here is a hint...
GmsCompatConfig (sandboxed Google Play compatibility layer configuration) version 64 released:
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-64
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/6336-gmscompatconfig-version-64-released
How it feels flashing #GrapheneOS then booting it for the first time...
No the 3a cannot be used via officially supported install methods.
You would be required to build it yourself, look for the last release tag where pixel 3a was supported and continue on from there.
The 3a is also not a very good device to even get a taste of the OS as the 3rd Gen Pixels eMMC memory is terrible and a handicap for doing so.
Minimum supported device advisable is a Pixel 5.
However a 6a or 7a would probably be the most cost effective and provide a better resale option if not happy for whatevwr reason.
Vanadium version 115.0.5790.136.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/115.0.5790.136.0
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/6308-vanadium-version-115057901360-released
What sort of moderation tools do Communities come with?
What client is best use to administrate/moderate from?
Very much appreciate you taking it in the vein in which it was intended.
As many people do not always click through ensuring the information is propagated for brevities sake is a beneficial approach.
Thankyou
We drop devices that are no longer supported by OEMs for the provision of firmware/driver security updates. Especially after we exhaust our ability to provide harm reduction between their support ceasing and the next major OS update through our Extended Support Releases (only available to allow people to upgrade their devices).
We do this as we believe in genuine security and privacy provision and not using the terms as a marketing gimmick.
3rd Gen Pixels are end-of-life and are highly insecure. They do not have the most important security patches regardless of OS choice. LineageOS, CalyxOS, etc. really don't properly communicate the severely of how insecure these devices are to users.
It's not simply about having better security features on the newer devices. End-of-life (EOL) devices lack half of the privacy/security patches. They're vulnerable to known remote code execution flaws and other issues. You can't really have privacy and security on such a device.
There is a community collated resource here for Banking Apps, check the Issue Tracker for any not on the main page.
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
However most banking apps will work fine so long as sandboxed Play Services are present.
The paradigm isn't that we only support Pixel phones.
The paradigm is that only Pixel phones support our needs.
Only Samsung offer comparitive hardware to meet our requirements however they are hostile to alternate OSes as when unlocking the bootloader (required to flash one) they use Knox/efuses to break that hardware indefinitely even when returning to the stock OS.
Every other OEM cuts corners in this regard to cut down costs and increase profit margin. Many don't even properly support the hardware they ship with prompt security/driver/firmware updates.
Can you tell me what the issue was with the app? Were you trying to grant an accessibility service to an app? If so and if you haven't resolved it I can help.
Login at badges.page and you can accept badges. If you then use a client that supports showing them like #Amethyst or #Onyx they'll display automagically.
Appreciated guys, got it all figured out now. Early start lead to brain fart.
Man after my own heart...
This had all sorts on it back in the day. My G1 and HTC Desire stayed stock. The Desire HD became my playground.
It isn't. π Be a pleasure to help you if you needed/wanted.
Even though you've an axe to grind, the issues lie with AOSP Keyboard running on any AOSP based OS having a problem with the current versions of Jetpack Compose (used for text input). This is due to AOSP keyboard not being actively developed as the team was branched off to use it as a base to create GBoard which recieves priority.
This can be used safely with all network permissions revoked on MicayOS π or GrapheneOS.
Thanks Ryan appreciate your constructive helpful reply.
We'd always be happy to have you, I, here, and the community at large will be warm and welcoming if you need us.
[Matrix] GrapheneOS Community Space (Primary Support) https://matrix.to/#/#community:grapheneos.org
Forum:
discuss.grapheneos.org