R

RemoverFan

Kerfluffle

Kerfluffle Does this sound like something the developers would have an interest in putting on the "To Do list"?

Maybe (I'm not one btw), though it also sounds somewhat low priority if it were to be added. I can imagine a few factors that would make this harder than it looks to implement at first glance, considering the standards this project keeps, such as how to handle connection failures, battery life, etc...

Personally, I think the possibility of having your location triangulated while moving defeats the purpose of not letting it be triangulated only when stationary. The amount of time spent at a place could still be known, for example, and I don't think it can be so precise to be able to present any meaningful risks to privacy when not moving.

flighty_sloth Stop turning e-waste material into actual e-waste... early...

@names_are_useless External, USB-based MicroSD readers don't need to have special security or privacy properties. They can't, it's the OS that has to have most of the protections that can apply to any USB device that plugs into the phone.

If cloud sans privacy concerns is an idea you're ok with and that's something you're into or a challenge you're up to, set up some self-hosted/managed cloud servers! If not, that's fine, but MicroSD isn't really useful if the phone doesn't have a reader built in. You could switch to a USB-C thumb drive, which would be more useful overall since some also offer USB-A in some creative ways, and are more compact and convenient than MicroSD to USB-C dongles + the almost obligatory USB-C to USB-A dongle.

The most that could happen for most people (and this is still pretty rare) is some USB device be a "rubber ducky", but that's pretty useless even on stock Android already, and has even less power on GrapheneOS with its security-minded USB handling.

It's the stock Google Pixel firmware, ripped straight from Google's system images for each phone. It gets updated as soon as possible with each GrapheneOS system update. Not sure about licensing, but this has been done for ages and Google couldn't complain. They are aware of this, and have been for long.

The firmware has to come from the device OEM since no community effort may possibly culminate in usable device firmware (there are no phones with open source, community-made firmware), and they are the only trustworthy source since they pretty much made it themselves and have their own security to take care of.