My Pixel 6 was confiscated by the German police after a political rally. I was recently able to pick it up again. From an inquiry with my lawyer, the following emerged: The authorities tried to read the device with both UFED4PC and Cellebrite Premium Touch. In addition, software from other forensic providers was used without success. The software did not succeed in breaking the system. The device was in BFU mode and had a 30-digit PIN. USB port was deactivated. As of March 2025, I can therefore say that it is not possible for Cellebrite to break a secured GrapheneOS.
PPanda-na
- a day ago
- Joined Apr 19, 2023
GrapheneOS version 2025032500 released:
https://grapheneos.org/releases#2025032500
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2025032100 released:
https://grapheneos.org/releases#2025032100
See the linked release notes for a summary of the improvements over the previous release.
The annual Proton Lifetime Charity Fundraiser from the Proton Foundation has concluded for 2024. We were one of 10 organizations selected for their fundraiser back in 2022 and received a donation amounting to $10,000!
Now they have sent us another $5000 as part of their commitment to support projects that were recipients in previous years. We want to thank the Proton community for all their generous donations making all of this possible and Proton Mail for matching their donations. Their financial contributions to other privacy and security software and organisations is commendable and we're happy to see their users are supportive as well.
Donations are what fund our work on upcoming features and improvements to GrapheneOS, maintaining our current ones, and the upkeep of our infrastructure.
It may be from Android 15 QPR2 rather than a Chromium issue. It hasn't been narrowed down if it's a Chromium or OS issue.
GrapheneOS version 2025031400 released:
https://grapheneos.org/releases#2025031400
See the linked release notes for a summary of the improvements over the previous release.
I had the same problem and due to the hint with graphics driver I enabled 'Skia Graphite' options via brave/chrome://flags for Brave+Vanadium and it seems to help until now.
GrapheneOS We've fixed this and will be starting the official builds for a new release soon.
GrapheneOS version 2025031300 released:
https://grapheneos.org/releases#2025031300
See the linked release notes for a summary of the improvements over the previous release.
It may be an OS GPU driver issue rather than a Chromium issue. Someone should test an older Brave release based on Chromium 133.
GrapheneOS version 2025030800 released:
https://grapheneos.org/releases#2025030800
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2025030700 released:
https://grapheneos.org/releases#2025030700
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2025030500 released:
https://grapheneos.org/releases#2025030500
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2025030300 released:
https://grapheneos.org/releases#2025030300
See the linked release notes for a summary of the improvements over the previous release.
Fartimoji Our network location feature provides an opt-in toggle for detecting location based on retrieving the location of nearby Wi-Fi networks from a service. Compared to satellite-based location (GNSS), this is much more power efficient, quicker to get an initial estimate and works where there isn't satellite reception. We provide a choice between Apple's services and a GrapheneOS service proxying to their service. We're building our own database of Wi-Fi networks and cell towers in order to provide our own service. Our service will also have offline support added to it similar to how you can download maps for Organic Maps to use offline. You'll be able to download a database of Wi-Fi networks and/or cell towers for an area from our service for offline usage.
Network location is a standard feature in iOS and Android with Google Mobile Services integration. People are used to having it enabled and expect location to work indoors, etc.
Most apps support network location via the fused location provider able to use both satellite-based and network-based location. However, apps choose the power mode they want and most use a low power mode where satellite-based location won't be used unless needed. This is why it can save a lot of power. Many apps are written to assume network-based location is available and don't want long enough for satellite-based location to get an estimate. This means having it improves app compatibility.
It was already possible to use Google Play's network location on GrapheneOS for apps which use the Google Play location service directly, but now there's going to be little reason to use that since people can simply use ours. Using the Google Play network location service required multiple steps: disabling the sandboxed Google Play location rerouting toggle to have apps using it directly send their requests to it instead of the OS, enabling background Location for Google Play services and enabling their network location service through their menu for it. Wi-Fi and Bluetooth scanning toggles are also relevant in the same way Wi-Fi scanning toggle is relevant to our service (just read the description, it just makes it so apps with Nearby Devices / Location can do scans when Wi-Fi / Bluetooth are otherwise off).
- Edited
GrapheneOS version 2025022700 released:
https://grapheneos.org/releases#2025022700
See the linked release notes for a summary of the improvements over the previous release.
This release adds an opt-in GrapheneOS network location client providing location detection based on nearby Wi-Fi networks using a local trilateration algorithm run on the device. It fetches a list of nearby Wi-Fi networks from Apple's location service either directly or through a GrapheneOS proxy.
It currently only has a very basic approach to altitude estimation which we'll be properly integrating into the trilateration algorithm in the near future.
It currently only uses Wi-Fi networks but we'll be extending it with support for using cell towers as a fallback in the near future.
We're in the process of building our own network location database based on scraping all of the cell tower and Wi-Fi data from Apple's service. Scraping all the cell tower data is quick and will be easy to keep rapidly updated. A contributor scraped more than 2 billion Wi-FI APs over 3 months.
This data isn't copyrightable and Apple freely offers it without requiring authentication. It will be the initial basis for our database, but we'll add other sources including an option to send us data from GrapheneOS devices. We'll provide database downloads to support offline network location.
Secure PDF Viewer app version 26 released:
https://github.com/GrapheneOS/PdfViewer/releases/tag/26
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
GrapheneOS version 2025021100 released:
https://grapheneos.org/releases#2025021100
See the linked release notes for a summary of the improvements over the previous release.
fid02 Our recurring expenses are significantly more than the donations we regularly receive. We received several massive one-time donations including one from Jack Dorsey and several from Vitalik Buterin. We're holding onto the cryptocurrency as Ethereum and Bitcoin which has increased a lot in value, which is the main reason we have a lot of money saved up and we'll be able to fund the project for several years despite not receiving enough recurring donations to cover expenses. We're using minimal risk fixed income investments for the USD we have saved up provide some recurring income. We're in no rush to burn through all the money and end up unable to pay expenses. We don't know how long the large donations we received will last in practice since it largely depends on volatile cryptocurrency price fluctuations, but it should last a few years. We'll need to find sources of other large donations or manage to get far more people to make small recurring donations. The available money heavily limits how much we can expand but we definitely don't need to scale things down.
- Edited
It is not necessary for a Canadian not for profit to spend funds within any time limits.
It is however very useful to have recurring donations as they have the potential to provide some certainty of future income for the GrapheneOS Foundation.
Having said that the project has received a small number of large one-off donations which have been instrumental in enabling the project to fund a lot of development and other project expenses. One off donations are also gratefully received, especially if they are large!