Hitting Uninstall on a system app in PackageManger brings the user to an "Uninstall with ADB" page, and recommends the following command:
adb shell pm uninstall -k --user 0 com.android.adservices.api
Looks like there is a change in A17 that you can no longer disable root packages this way. The user is now met with:
Failure [only root can delete system app for a particular user]
Perhaps this page could be updated to use the disable-user command: adb shell pm disable-user <package> on A17+
adb shell pm disable-user com.android.adservices.api
Which outputs:
Package com.android.adservices.api new state: disabled-user
(Unfortunately google mandates that adservices should be a system level app and that you are not allowed to remove... 🤮)
This is a apparently a google change, not a Graphene change. Just linking the discussion for reference.
Hitting Uninstall on a system app in PackageManger brings the user to an "Uninstall with ADB" page, and recommends the following command:
adb shell pm uninstall -k --user 0 com.android.adservices.apiLooks like there is a change in A17 that you can no longer disable root packages this way. The user is now met with:
Failure [only root can delete system app for a particular user]Perhaps this page could be updated to use the disable-user command:
adb shell pm disable-user <package>on A17+adb shell pm disable-user com.android.adservices.apiWhich outputs:
Package com.android.adservices.api new state: disabled-user(Unfortunately google mandates that adservices should be a system level app and that you are not allowed to remove... 🤮)
This is a apparently a google change, not a Graphene change. Just linking the discussion for reference.