First, as nobody forces you to use graphene, they're not getting in the way of your ideals, I'm saying some of the FSF's ideals may compromise the security of their followers. When it comes to Google's blobs, It's not like they can release the source even if they wanted to, samsung wouldn't even let them cuz google leases their IP and trade secrets for the tensor chips. I don't like IP either, but I keep my feet on the ground, the blobs aren't there for firmware-level who-knows-what, due to the hardware and software model themselves, most of what they'd do would be super detectable. Go read the edit of my prior comment, educate yourself on embedded devices, the pixel hardware model and graphene's security model, then we might have a productive conversation and not uneducated conspiracy speculation.
alonely0
Graphene is against GNU ideals getting in the way of security, because as it turns out, they do. FSF's definition of "ok" and "not ok" firmware blobs is bogus anyway.
Edit: for all the people who don't get this: THE FSF IS FUCKING OKAY WITH PROPRIETARY FIRMWARE BLOBS, but only if they are in a separate (usually user-inaccessible) storage chip and if you don't update it; they only deem that morally ok, yet it'd be the same as loading the blobs from the disk (which makes devices MUCH SAFER to update, you don't risk a brick). They get in the way of security by abusing the trust y'all give them, cuz thank god nobody who does embedded dev takes their opinions seriously anyway. Also, you're not giving up "A bit of security", you're giving up fucking microcode updates, the ones that patch well-known vulnerabilities that allow webpages to gain root access. FFS.
They're an embedded device, plain and simple. Among other things, this means that there's not a layer that handes off the hardware in a ready state to the OS, and not even an ACPI to tell them what and where the hardware is, the OS needs to already know via a device tree.
That's the headset renegotiating the codec probably. Update the firmware in the app if you haven't, maybe it'll fix the issue.
Momentum 4 owner here too. ~~Can you provide the details of your distro?~~ You already have aptx/aptx-hd available, it's what you should use with them. Ima look into it when I get home.
Lmao it's not framework's fault if linux can't handle hidpi well. The display ain't broken, linux is. Btw I have a display of the same resolution on my laptop, and I have had zero issues on plasma at 125% scaling (most apps of my apps are wayland-native) and gnome works great after setting it to 125% via dconf too.
Nope, not that close to the edge, and especially not in this laptop cuz it must have them firing down. It's the hall effect sensor of the lid.
It is designed to be stable in spite of being regularly updated.
I use openSUSE. Zypper is a PITA compared to pacman.
Good luck bricking a Pixel while following Graphene's installer. If it protected the phone from me, someone who bricks basically everything they touch, it'll be fine for you.
Yeah it's because they ship the same OS image for everyone, be it US on a carrier plan or otherwise. Google services has complete control over your device (more than just locking it down), and that's what you should be upset about. For you that app is just harmless bloat, what's actually spooky is google play services as a system app. Do yourself a favor and install grapheneOS.
Oh, the FSF doesn't get in the way directly (they have neither the funding nor the personnel), they just misinform you to do so, so they're guilty in my book. Go read the edit in my prior comment.