I'm fairly sure Android used to have an internet permission back in the early days. But then basically every single app requested it so the utility was diluted. Then they switched away from a static list of permissions and more to a ask for permission at the time of use model.
replyThe old permissions model was always a bit of an illusion of choice. The app presented a massive list of permissions and you could take it or leave it. But when every app asks for every permission you don't really get a choice and just had to accept it. The new model where you can install an app and then reject it's permissions is much better.
Almost a decade ago, I wrote and published a small companion app for a game and set a hard rule for myself that it didn't need the internet permission (and thus stuff like a privacy policy). It still managed to be useful despite that, which made me pretty proud at the time.
replyStock Android has always classified internet as a "normal" permission that can't be toggled by the user. I think it still might have to be requested by the app, and you could see it in the app details, but it has always been auto-granted with no way to turn off.
replyMy recollection is that I stopped seeing the “Internet” permission a couple of years before Android acquired the ability to toggle permissions, or do anything at all with them aside from displaying the list from the manifest during app installation.
replyAh, "The Network is the Computer" [1]
reply[1] https://en.wikipedia.org/wiki/The_Network_is_the_Computer
FWIW, GrapheneOS supports disabling internet access for apps.
replyIt's a rite of passage of every Android app to crash on the first launch because you forgot to declare the INTERNET permission in the manifest. It's been there since day one.
replyIt's auto approved and non declineable in the settings, but technically it's a permission you can revoke, just needs to be surfaced.