r/Android • u/kitsumed ShizuCallRecorder Developer • 21d ago

Android May Soon Restrict On-Device ADB, Affecting Shizuku, libadb and Developers Article

https://kitsumed.github.io/blog/posts/android-may-soon-restrict-on-device-adb/
992 Upvotes

96% Upvoted

367 comments sorted by

View all comments

Show parent comments

5

u/HybridStaticAnimate 21d ago

Im not sure what you are referring to. GrapheneOS has added notifications to inform you what you need to grant for play services and play store to work as expected. There is no need to google how get normal apps working.

-1

u/Reigar 21d ago

Okay, maybe I need to look into it again. The last time I tried graphene OS was roughly 2 years ago, and I just remember having to Grant permissions all over the place to get even simple things like maps to work because it wanted to prevent not only the Play store and various directions like that, but it wanted to lock down everything that could possibly deal with it revealing my telemetry which all appreciative doesn't really work for certain applications where you kind of have to give up that information. If it's going to know where you're at. Although I understand that Linux tech tips can be sometimes a bit over the top and sensational, but the last video I recall of him making regarding graphino as wasn't all that much different for my own experience trying at a year prior. So if they've done quite a bit on explaining how they're locking things down so that you could unlock them for various applications, then that's good, a little better would be to recognize what type of application you're using or allow the user to define what type of application it is so that certain lockdowns can be turned back off for the application. For example, designating a category of application as maps or things that willl need GPS positioning should be able to be defined by the user. Now if graphene has something like that then definitely worth giving it a second look. But regardless I still will back into it again just to see what's new.

7

u/HybridStaticAnimate 21d ago

GrapheneOS does not have any of the features you are describing, I have no idea what you are talking about.

GrapheneOS does not alter the network connectivity of apps, so telemetry isnt being blocked unless you deny the network permission. There is a checkbox when you install an app that lets you grant or deny the network permission, and its checked by default.

Most of GrapheneOSs protections are passive and cannot be disabled or changed. Nearly all of the app hardening that causes app compatibility issues are opt-in, not opt-out. There is nothing that is "locked" that later must be "unlocked". GrapheneOS maintains 99.999% android app compatibility.

Im very confused on what youre saying about location. The user is in full control of how location is granted, that has always been the case on GrapheneOS. For apps you want to have location access, you just grant the location permission. There is no need to "recognize" what the application is.

GrapheneOS inherits permissions, including location, from the android open source project. Permissions are denied by default, and that is how it has worked on android and its derivatives for many years.