GrapheneOS

GrapheneOS , 7 days ago

@autistic_enby @alice

That recent apps text selection likely isn't available via Pixel Launcher as a 3rd party launcher, but whole system OCR is possible with an accessibility service.

A lot of those features are available on GrapheneOS and simply require using Google apps like Pixel Camera, Google Photos, Pixel Launcher, Google Messages, etc. if people want to have them. A lot of these apps are Pixel specific or have Pixel specific functionality and those things do mostly work on GrapheneOS.

GrapheneOS , 7 days ago

@autistic_enby @alice

GrapheneOS does support all of the same local AI/ML hardware acceleration features. The extended APIs that are specific to Google apps on the stock Pixel OS are still specific to Google apps on GrapheneOS but with a toggle available for them. They don't provide additional data access so it's enabled by default. We haven't bothered making it available to other apps as an opt-in feature since in practice nothing else uses it since they can't do that on the stock OS.

GrapheneOS , 7 days ago

@autistic_enby @alice For the most part, yes, but Google features which need to be built into the OS for privileged access aren't available unless we added toggles for granting a minimized form of that access. For example, we have toggles for granting a much more minimal form of the access needed by Android Auto. For wired Android Auto, it only needs to grant more direct USB access than a sandboxed app can usually get. For wireless Android Auto, it has to grant a lot of Wi-Fi/Bluetooth access.

GrapheneOS , 7 days ago

@autistic_enby @alice Most of the features people care about are available since they don't need any privileged access, such as all the fancy Pixel Camera and Google Photos features specific to Pixels since the hardware acceleration is available.

The always listening song detection feature isn't available since it requires privileged OS integration, although we could likely make our own implementing reusing their model but that kind of niche thing isn't in the scope of the project right now.

GrapheneOS OP , 14 days ago

Cellebrite's list of capabilities provided to customers in April 2024 shows they can successfully exploit every non-GrapheneOS Android device brand both BFU and AFU, but not GrapheneOS if patch level is past late 2022. It shows only Pixels stop brute force via the secure element.

Capability table described by the tweet. We can't properly format the tabular data as alt text but we can share it elsewhere.

GrapheneOS OP , 25 days ago

@h3artbl33d Yes, it will have the same SoC as the Pixel 8 and Pixel 8 Pro, although they do likely bin them based on efficiency with the Pixel 8 Pro getting the best ones followed by the Pixel 8.

GrapheneOS OP , 25 days ago

@h3artbl33d @chat The stock OS only supports it via toggling on support for it via a developer option and then enabling it by setting system properties in ADB shell. They don't provide a per-app toggle so you have no option beyond disabling it again to work around incompatible apps. They don't run it in the security-focused asymmetric mode so it can be bypassed. They use it in a much more limited way within each process. They have no way to fully opt in for base OS processes, which we always do.