Impossible to say until we see it, but if they're willing to do this then why bother doing any of it? Scammers will easily walk the clueless through whatever steps Google sets up.
comments
We are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified.
Isn't this what we wanted?
Just disabled that through Canta with Shizuku rather than adb on a Samsung Note 20 and rebooted. Should be fine to disable.
Fucking infuriating.
Oh good, I was getting worried that Google products and services might become deshitified
Ffffffuuuuuuuuuuck…
So now everyone gets to know our search history...
Yeah no idea about the Pixel 6a or how difficult it is to swap batteries, but 400 cycles is at least a couple of years, right? If the swap isn't a big hassle, just do it again. Or for that matter if the old battery is still good after 400 cycles and the phone wants a replacement, just take the old one out and put it in again.
It doesn't look too bad:
https://www.ifixit.com/Guide/Google+Pixel+6a+Battery+Replacement/152516
The question is whether you'll see the dreaded message again after 400 cycles.
Yeah, who could have predicted it, right.
I don't have an answer for you, but I took mine to a repair shop for battery replacement and the wait time for a replacement battery is 4 to 6 weeks. I mean it's nice that people are replacing the batteries rather than just getting a new phone, but that must be a LOT of bum batteries to make them so scarce.
I've generally used eBay and done fine.
If they really cared they'd just have some big warning if the all is from an "unverified" developer. It's all about control.
Google gets no say outside their monopoly store. That's the whole goddamn point of "sideloading." It's people treating their pocket computer like they own it.
Fuck entirely off.
This will make it more difficult and dangerous to make and publish the apps needed by people who work against oppressive regimes and cynical businesses. Bad megacorp, Google
Blatant shill article
And people wonder why I want a Linux phone. They're slowly closing the door and it won't ever reopen.
What you describe are feature requests not issues.
The reason you don't find them is simple: many projects don't want q myriad of form based user requests. Depending on the specific project it's either vote based or non existent in my experience.
AOSP as specific example is mainly maintained by Google who are notorious for being very ... Wet in their own ways on how to do feature roadmaps.
I think you're naked by both your life and that of the projects you want to support tougher by thinking about these things as issues. Just a rule of thumb m: it's an issue if it's not working as documented or behaving in a way that can be described in terms of "right" and "wrong", not preference.
Otherwise it's a feature request.
Your points for example are all aimed at quite advanced users. I'm not an AOSP dev but just looking at the way they developed their menus over TR years I'd be surprised if they'd share your evaluation.
Just to herd a warning then from a Dev perspective: you want to remove them before interacting, not just opening.
I can send files without ever opening them and the sharing would keep the meta data if you'd not open the files manually with the cleanup tool.
Personally I've had a camera app a while back that I could configure which meta data it saved but I simply stopped sharing photos on social media and so this become s non issue for me :)
I can't say whether it can execute, but the metadata is a privacy concern if you are posting online. Depending on the camera taking the picture it can include the model of the phone, date, or even GPS information
I'm a longtime dev but never work with images. What's the disadvantage or danger (or whatever) of the metadata? Can metadata execute?
https://github.com/Tommy-Geenexus/exif-eraser
I use the above, it's reliable.
If you're feeling twitchy, another option is
https://gitlab.com/juanitobananas/scrambled-exif/tree/HEAD
Which replaces the exif and other metadata with garbage.
(sort of related?)
I use "exifcleaner" to clean metadata from media
https://github.com/szTheory/exifcleaner
Can't wait to see what security features this will come with by default.
honestly, how many people use large displays attached to a phone. I think I connected mine to a TV once to watch a movie with friends.
I'm not denying anything that you outlined and also share your concerns about Google exploiting the FOSS community.
GrapheneOS seems to be able to side-step Google's fuckery while also having an Android OS that keeps Android's most important functions usable.
I guess we'll see over time if the projects that don't have the funding that GOS has will be able to keep up with an increasingly hostile AOSP.