goodbye shizuku i guess, and maybe termux
Android may soon restrict on-device ADB
211–220 of 535 posts
Re: Android may soon restrict on-device ADB
#212Re: Android may soon restrict on-device ADB
#213Earlier quoted context omitted.
It can and will most probably turn to indefinite time depending on the answer to the question "will we have a viable alternative to jump ship before that happens ?". We don't need anything to completely capture the market, it has to be just enough to make Google hesitate or make it hard for Google to do it for legal reasons. Like how Firefox is ideally supposed to be for Chrome.
Many alternative AOSP-based systems work fine today and do not have the new Android Developer Verifier (wow, already rolled out to 500M+ devices [1], though still dormant). To be honest, it is quite scary that Google is able to remotely roll out an app like that to all GMS Android phones. Of course, we all knew that, but it highlights again that Google can remotely take away functionality that you had before, brick y…
Apple can do the same for iPhones. In terms of dark shit they can do there's no difference anymore.
Re: Android may soon restrict on-device ADB
#214There's only one reason for anyone, or for me, at least, to choose Android, and it's the only reason I've consistently chosen Android from the very first Google Developer Phone: It's more open. So, they don't want me to even have that one reason to keep choosing Android, I guess.
Re: Android may soon restrict on-device ADB
#215Thank you for telling me about Shizuku! Android world is so vast and full of resources
and google is doing all they can to try shut it down, because they saw how profitable a walled garden like iOS really is.
Re: Android may soon restrict on-device ADB
#216Earlier quoted context omitted.
They dont care about security; only about control. There are hundreds of millions of outdated Android devices that all Google attestation systems consider secure even though they all running Linux kernel that was never ever updated and can be rooted by anything. Now try to install your own firmware on them without said outdated kernel... How dare you.
Technically the security works, just for their threat model. An exploit would need root and root means you likely cannot pass attestation AFAIK. The fact that this same exploiter can download all your contacts photos and texts is immaterial to, say, Disney, who want attestation only to prevent ripping of their content.
Re: Android may soon restrict on-device ADB
#217Earlier quoted context omitted.
Toxic max security. Not everyone has the same threat model as you, $BIGTECHCORP.
It's not even "max security". We are talking about those big tech corps which are infamous for sharing all of your private information with the government, and analyzing it so as to manipulate you in to buying things, and possibly for other obscure commercial purpuses.
Re: Android may soon restrict on-device ADB
#218Android had a tradeoff - less vertical integration and more annoyances, a bit worse software quality, for a more open, customisable and utility-like experience. I loved that. Now, the tradeoff is - less vertical integration, double the integration layer trash (Google & OEM) and a much more locked down experience. But the quality of it hasn't improved, it just got worse. Doesn't make sense anymore. They can now do 99%…
and conveniently, google now has access to your photo, the meta data, and potentially able to scan it for advertising purposes.
Re: Android may soon restrict on-device ADB
#219Android is turning into the iOS/OSX/Win11 model. It’s not your device, you’re just renting it.
You need permission to install applications, or do anything else outside of consuming subscription services.
Where are the Linux phones ?
Re: Android may soon restrict on-device ADB
#220Earlier quoted context omitted.
> As if you didn't need any more proof you don't own "your" devices. Can you install your own OS? If yes, you own it. And Google consistently lets you do that. It other OEMs don't then direct your outrage at them.
>Can you install your own OS? If yes, you own it. Not before connecting it to the internet, even Pixels will go through hundreds of megabytes of data before allowing you to unlock them (see 0). Also, will Google let me browse the web with "my own OS" without their proprietary services installed on it? (see 1) And without developers pouring tens of thousands of work hours into making projects such as GrapheneOS viable…
What's the problem here? Are you roaming all the time and that imposes a unreasonable cost on you? You want to stay totally off the grid and using VPN/tor isn't enough?
>Also, will Google let me browse the web with "my own OS" without their proprietary services installed on it? (see 1)
Having control of something isn't the same as third party services granting you access. Many online games only supports windows with secureboot and TPM enabled, but that would be a silly excuse to say that you don't really "own" your PC.