Vik

I appreciate the analogy

It’s a shame that consumer oriented TR ended with the 3000 series. Platform owners must have felt massively short changed by that (my friends and associates with 2 and 3000 series TRX rigs certainly did)

aye she’s a lil pumpkin

big paws are for big adventures! 😊

such a beautiful pup 🥰

well, at least they provided some rationale for switching browsers. still, it’s good thing we have bazzite.

For that cost I would have expected HBM but the package size would be ridiculous (and I’m not even sure I’d BW’s memory controller is designed with different memory technologies (besides G7) in mind)

I feel that, I just wanted to set your expectations. I prefer and will continue to use CalyxOS but I have no expectation that they will deliver the same level of protections/mitigations at the OS side as Graphene given their project scope is different.

CalyxOS aims for a private, yet simple (attainable) Android experience, and I align more closely with their ideology on having a FOSS replacement for Google Play Services in MicroG.

I suppose one thing you could levarage is work profiles on Calyx to “jail” apps you do not trust, though I’m not sure that meaningfully builds upon Android 15s own application sandboxing.

Perhaps as a long term goal you could look into making a custom fork of CalyxOS for your device and incorporating parts of Graphene’s hardening but this will be a lot of work.

As a calyxOS user, if your key concerns are security and device hardening, I’d recommend you just make a seedvault backup and switch to graphene.

The two projects have somewhat different scopes and I don’t think you’ll achieve the same degree of sw security on calyx.

I wish I had a ricky style shitmobile to park next to cybertrucks for comedic effect

such happy pups 🥺