I’ve already seen it try to disable sideloaded apps. Was yet one more motivator to go to a de-googled device (specifically DivestOS). I can’t do Graphene with my current device, but my next phone will be a Pixel 5.
They could, but I think that would be too obvious. Why such system they could flag it at OS level with a big, scary warning and claim it was for security sake.
I bet a cookie that this will be used to kill apps like NewPipe and Revanced.
Yep.
I’ve already seen it try to disable sideloaded apps. Was yet one more motivator to go to a de-googled device (specifically DivestOS). I can’t do Graphene with my current device, but my next phone will be a Pixel 5.
Just curious, why a 5?
Yeah. Pixel 8 just launched. If you want a cheaper phone go for the 7s
Google offered $150 for my nearly new 7, I’m sure there will be quite a few on the used market.
Probably because of ROM support
That and the form factor, feature set, weight, brightness l, fingerprint sensor, weight, materials.
I’d prefer a 4 since it’s plastic, but the 5 is almost exactly same size and weight.
Why a Pixel 5? It’s end of life already.
Or more an excuse to monitor and read app data
Or things like AdGuard.
I have sideloaded apps where the malicious code has been removed (e.g. a Spotify client without ads). I bet this is an attempt to block them.
But… they could’ve already done that with current tools? Not like these change the package ID often.
They could, but I think that would be too obvious. Why such system they could flag it at OS level with a big, scary warning and claim it was for security sake.