GrapheneOS version 2022082300 released: https://grapheneos.org/releases#2022082300.
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2022082300 released: https://grapheneos.org/releases#2022082300.
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2022082100 released: https://grapheneos.org/releases#2022082100.
See the linked release notes for a summary of the improvements over the previous release.
Friedemann Regarding your second point, there has been a long time issue filed to create an extra factor when enabling fingerprint unlock. https://github.com/GrapheneOS/os-issue-tracker/issues/28
I also want to mention that a shorter password on a GrapheneOS device is more secure than on a traditional desktop/laptop device. That's because Pixels have a security chip which limits how many password attempts an attacker can attempt. (I'll leave the technical explanation for someone more qualified to explain) So while a second factor authentication would obviously increase security, unless your threat model includes a security chip exploit, it may be overkill.
pixelkitten unfortunately not, dual boot often requires either the bootloader to be unlocked or to be patched breaking the security model while actually being unaware of a fully working stable multi-boot option available on Android 12L. Last time I used such a solution was back in the Ice Cream Sandwich days though so you may have more up to date information and a link to a working project?
GrapheneOS starts from the ground up with locked bootloader and verified boot to start the chain of trust in the OS and as such wouldn't be a plausible candidate for a live boot situation either.
Hi everyone, I just learned about GrapheneOS and don't yet know much of anything about it or Android OSs in general yet, so if my question is ridiculous, please forgive me in advance as I don't know how it works..
I was just wondering if there is (or if it is feasible to create) some kind of portable bootable version of the GrapheneOS that could be plugged into the USB port of the phone, or create a sort of dual-boot setup like with what can be done on a PC.
If it can be done, I think it would be tremendously useful and provide a lot of flexibility.
It's probably not possible since I've never heard of any smartphone OS being able to do this, but I thought I'd ask just in case it can be done.
FU6QydnIELkx No edited appropriately sorry got ahead of myself. Your 4 will cover you nicely until the 7.
FU6QydnIELkx typically the next phone is released at the same time as the next Android release. So expect your 4 to be supported until the 7. However unlike the 6a which could have GOS ported within days if not 24 hours due to hardware being similar to the 6/6Pro, the 7 could be a week to several. If you want the 7 I'd wait for the 7. You 'may' end up on a Extended Support release but not for long.
While future device support is speculative by definition, in the past porting GrapheneOS to a new device took a couple of months at least. And since Pixel 7 is coming out around October, that means I would expect GrapheneOS to come to it around December. (Just an estimate, could be sooner or later)
Pixel 4 is expected to lose support around October. So that means there would be an overlap of a couple of months where you wouldn't have full security coverage.
GrapheneOS has been offering extended releases a year after the end of life support, but note that these do not cover all the security patches (notably the firmware).
So the decision is up to you. Are you okay using a device without full security for a few months? If so perhaps wait for the 7. If that is unacceptable then you should get the 6 or 6a.
I can appreciate where you're coming from and the energy you have for the project in proposing this.
Thing is there are already numerous donation channels. Some rough figures based on estimated user base were done too recently looking at the funding model. It was worked out that if every user donated between $1.50-$2.50 each then the project would be in rude enough health financially that most of the issue tracker would be covered that way. If that is already an issue then I see people less likely to contribute small amounts to singular issues.
Honestly I think the lack of a constant funding stream is the main issue and small regular amounts from numerous sources is better long term, than larger one off amounts or bounties. However I do see their merit, experiencing them working well for finding root methods over on places like XDA etc. I'm not a member of the dev team so like you just throwing my two penneth into the conversation.
GrapheneOS version 2022062200 released: https://grapheneos.org/releases#2022062200.
See the linked release notes for a summary of the improvements over the previous release.
FU6QydnIELkx In addition to what Wonderfall said, there is an open issue for denying Sensors by default for system apps which don't need it at https://github.com/GrapheneOS/os-issue-tracker/issues/597.
FU6QydnIELkx You actually can add Startpage as a search engine in Vanadium. Before you search (also make sure it's not in incognito mode) you have to go into the settings of Startpage & change the HTTP request method from "POST" to "GET." Then do a search on Startpage & you should see it show up in the list of search engines.
As a rule of thumb, do not touch permissions of system apps. You won't gain much by doing that, and you may end up breaking things.
Sandboxed Google Play compatibility layer: allow Vanadium to use GMS FIDO2 implementation
EDIT: oops, just realized inline pictures might be an issue. Sorry for that one.
[deleted] there is only one Thatcher™ and this one is boot verified™, OEM locked™, JIT-less™, attested™, trademarked™™, copyrighted©™ across all 16 user profiles™ and certified 100% safe by Norton 360™.