I just checked Lineage OS and it looks like Google Play Services doesn't let you disable sensors permission. Can you do it on Graphene OS?
Yep, there's a toggle to disable by default globally. I also individually checked Google Play Services, Google Play Store and Google Services Framework, and all three can be denied the Sensors permission.
This is due to Sandboxed Google Play: "GrapheneOS has a compatibility layer providing the option to install and use the official releases of Google Play in the standard app sandbox. Google Play receives absolutely no special access or privileges on GrapheneOS as opposed to bypassing the app sandbox and receiving a massive amount of highly privileged access. Instead, the compatibility layer teaches it how to work within the full app sandbox."
Sensors permission toggle: disallow access to all other sensors not covered by existing Android permissions (Camera, Microphone, Body Sensors, Activity Recognition) including an accelerometer, gyroscope, compass, barometer, thermometer and any other sensors present on a given device.
the ground should absolutely be on the bottom because gravity.
Not necessarily. You typically want the ground longer so it's the first in and last out. Type G has the ground on top. I vaguely remember hearing that's because if it comes slightly out and something sharp or metal falls on the plug, you want it to hit the ground and not the live part...but I don't know how reliable that story is.
OP was gifted a phone for Christmas, and your solution is...
Except I wasn't replying to OP. I was replying to someone who said (and I quoted them) they only use older phones due to proven flashing support, so I was saying they don't have to for the Pixel reason. I wasn't suggesting OP do this if they don't want.
...suggest dropping $700 on a new phone so they can immediately void its warranty.
Where does it say that unlocking the bootloader and flashing an alternate OS voids the warranty? I've done it with every Nexus/Pixel I've had, and have traded them all in for credit...and even sent two in for warranty repair which Google honored.
A quick search (link below) said it doesn't necessarily void the warranty...unless what you did breaks the device and they deem it your fault. And with how good rhe flashing process is on Pixels, I feel you'd have to try and actively break it. Please don't spread unverified rumors (unless you have an official source, which I'd like) and potentially scare people away needlessly.
Pixel 8 Pro. Google's current flagship device, arguably the most secure device on the market, and is first to include Memory Tagging Extension (MTE). As such, it is supported by GrapheneOS, which I highly recommend due to the increased security and control over your own phone (starting with sandboxing the Play Store if you use it, and not giving Google full system privileges like stock/OEM OS does).
When fully integrated into the compiler and each heap allocator, MTE enforces a form of memory safety. It detects memory corruption as it happens. 4 bit tags limit it to probabilistic detection for the general case, but deterministic guarantees are possible via reserving tags.
In hardened_malloc, we deterministically prevent sequential overflows by excluding adjacent tags. We exclude a tag reserved for free tag and the previous tag used for the previous allocation in the slot to help with use-after-free detection alongside FIFO and random quarantines.
They answered the "who is the huge privacy concern" with the link. I literally just said that.
so I don't know how you could possibly know who they were speaking of.
I read the link that was the replied to you, and applied context. It's not hard to understand what a person means when they literally write it down. It's one method of communication. Or do you constantly read articles, and never know what the authors meant unless you can quiz them directly?
Plugging your phone in doesn't suddenly make your car more or less private so I don't understand the relevance.
They weren't necessarily talking about making the car more or less private via plugging in the phone. The original comment in this thread was wishing GrapheneOS was on cars, and then "modern cars are bad for privacy" link. They were talking about the existing poor state of privacy on modern cars and wishing it was fixed via wishing GrapheneOS could be flashed to the car. There was nothing in this thread about plugging your phone into the car making it more or less private. Again...context.
It's these issues that keep me on devices that are a little older, ones with well-documented root/flashing processes.
Just grab a Pixel, even the newest one. Those have the best documented alternate OS support, bonus points if you use GrapheneOS. Granted, rooting is frowned upon there as they're more about security.
Which question? The one you asked who was the huge privacy concern? If so...did you read the article they linked you? Because the answer is there, and I'm not going to read it for you.
Yeah, I'm not saying it's hard, just illogical. To me, it came across similar as: "I'm moving to this other distro because they have Firefox." Your current distro also has Firefox, so why are you moving again?
Flatpak is the primary way that apps can be installed on Fedora Silverblue (for more information, see flatpak.org). Flatpak works out of the box in Fedora Silverblue...
Just seems very odd to distrohop for one main reason (flatpak in this scenario), without even checking if that reason is available in your current distro....which it is, out of the box.
It's the whole "if you're not paying for the product, you are the product." But I guess the downvoters are perfectly fine with having their data harvested for "free."
"There are no seeding rules...if you fall below a 0.5 ratio, your downloads will be disabled."
That there sounds like a seeding rule.