strcat

53 ms·

601.
by strcat 3y ago
> AOSP engineer here; I don't have a deep knowledge of the issue at hand as I don't work on the bluetooth part of the OS, but I did just want to call out that GrapheneOS (while a really cool project!) supports ~11 total device
602.
by strcat 3y ago
Pixels are currently the only devices meeting our security requirements. Other Android devices don't even come close. Hardware memory tagging support is one of many major security advantages of Pixels. Our official list of hardware req
603.
by strcat 3y ago
GrapheneOS and CalyxOS are very different. GrapheneOS is a hardened OS with substantial privacy/security improvements: https://grapheneos.org/features CalyxOS is not a hardened OS. It greatly reduces security vs. AOSP
604.
by strcat 3y ago
Enabling it via developer options is only the first step. You also need to enable it via setprop using ADB in the desired mode. The official documentation for using MTE on the stock Pixel OS is available at https://developer.andr
605.
by strcat 3y ago
That's not the same as what's being used on GrapheneOS. It also excludes a significant portion of Bluetooth. Enabling support for memory tagging in the stock Pixel OS via developer options only makes it available for usage but doe
606.
by strcat 4y ago
> You've threatened to unleash this upon people in the past [0], despite constantly claiming that you're the one being harassed and attacked. Dishonest claim. > You have failed to provide any evidence of anti-GrapheneOS sock
607.
by strcat 4y ago
> I provided a link to a GitHub issue that you opened. I don't think anything in my OP was objectively untrue. You made numerous baseless claims without evidence in your posts. > You can keep calling me a sockpuppet but that does
608.
by strcat 4y ago
GrapheneOS does not support SafetyNet or Play Integrity hardware attestation and there isn't a way to use them on GrapheneOS. The whole point of that article is encouraging developers to move away from those Google services to the stan
609.
by strcat 4y ago
The goals of the projects are not the same. CalyxOS is not a hardened OS and it doesn't aim to be a hardened OS. They don't work on the kinds of privacy and security features we do. For the most part, they work on much different t
610.
by strcat 4y ago
> IMO "reviewing a pull request" is a far cry from "working with". You really expected Bromite to immediately close the PR, even if it contained valuable contributions, just because GrapheneOS claims (without evidence
611.
by strcat 4y ago
Separately from this, it's a misconception that CalyxOS and GrapheneOS are similar projects or that they're working on similar things. They are not. GrapheneOS is a hardened OS with substantial privacy and security improvements:
612.
by strcat 4y ago
Using GPLv2-only licensing to prevent a GPLv3 project from taking our code while disallowing us from using their code (since we can't use GPLv3) is hardly anti-FOSS. GrapheneOS can't use GPLv3 for Vanadium because it's incomp
613.
by strcat 4y ago
We were unable to update the Pixel 6 devices to r38p1 due to more changes being required beyond the kernel driver update. The security patches were shipped regardless, and that also happened upstream for AOSP and the stock Pixel OS for the
614.
by strcat 4y ago
Please see our release notes: https://grapheneos.org/releases#2022121400 > kernel (Pixel 7, Pixel 7 Pro): update Mali GPU driver to r38p1 along with other changes included in the QPR2 Beta 1 including a bunch of security
615.
by strcat 4y ago
Android 13 QPR2 Beta 1 came out on December 12th. This included backports of the ARM Mali GPU driver security along with a separate update to r38p1. GrapheneOS shipped these for the kernel driver. We had already done earlier work on updatin
616.
by strcat 4y ago
> as far as I can tell GrapheneOS doesn't have the patch, yet. That's not correct. Android 13 QPR2 Beta 1 came out on December 12th. This included backports of the ARM Mali GPU driver security along with a separate update to r3
617.
by strcat 4y ago
It's the same over 3 year old thread from April 2019. GrapheneOS has gotten so much better since then that the comparison to iOS there is hardly relevant anymore. You can now use nearly every app from the Play Store on GrapheneOS due t
618.
by strcat 4y ago
This post was from over 3 years ago. GrapheneOS today has much broader app compatibility via sandboxed Google Play compatibility layer ( https://grapheneos.org/usage#sandboxed-google-play ) combined with the per-app exploit p
619.
by strcat 4y ago
This is about non-Google OEM OS signing keys. v1/v2/v3 APK signing has nothing to do with the Play Store requiring Play Signing for newly published apps. App bundles / split APKs also don't inherently have to be used the
620.
by strcat 4y ago
You can freely update from a v2 signature to a v3 signature. If the minimum SDK version is below when v2 was introduced, Android will include both a v1 and v2 signature by default. If the minimum SDK version is above when v2 was introduced
621.
by strcat 4y ago
> Only the SoC firmware signing key and firmware for other secondary components with the key burned into the hardware can't be rotated. Side note: those components do have fuses burned via updates that are used to implement downgrad
622.
by strcat 4y ago
The post title here should really be corrected. It's editorialized and is completely wrong. There is no 'Android platform signing key'. Android is not a single OS provided by Google. It's an OS family. Each OEM has their
623.
by strcat 4y ago
Note: GrapheneOS is simply an OS. It's currently available as an aftermarket OS but will be available on devices built to run GrapheneOS eventually. It's not a ROM and we don't use that incorrect terminology. It's needle
624.
by strcat 4y ago
See https://news.ycombinator.com/item?id=33567766 .
625.
by strcat 4y ago
GrapheneOS was started in 2014 and was previously known as CopperheadOS. I co-founded the Copperhead company in 2015 and I still own half of the shares today, which gives me 50% control over the company. GrapheneOS (formerly CopperheadOS) r
626.
by strcat 4y ago
Please read https://grapheneos.org/usage#exec-spawning . You can choose not to use this feature if you can't tolerate up to a 200ms delay for cold start app spawning. Application spawning on GrapheneOS is as fast as the
627.
by strcat 4y ago
Google Camera works perfectly on GrapheneOS, and unlike CalyxOS runs as a regular sandboxed app. It's as simple as following our instructions and installing GSF from our app repository followed by Google Camera: https://grap
628.
by strcat 4y ago
GrapheneOS uses our own camera app, not Open Camera. Our camera app supports HDR+ for images and HDRnet for videos on Pixels along with zoom-based multi-camera on devices with support for it in 3rd party apps including Pixels and current ge
629.
by strcat 4y ago
> - some crapplications do not want to run on custom rom If you need help getting apps working, please ask on https://discuss.grapheneos.org/ or #grapheneos:grapheneos.org on Matrix. We'll be happy to help you get t
630.
by strcat 4y ago
> I used it for a year and it was not very smooth GrapheneOS isn't any less 'smooth' than the stock OS. You should read https://grapheneos.org/usage#exec-spawning about the optional secure spawning feature

More ›