PHPeaceOfMind
Eternal Poster
Brevent.
In short, Prevent without Root. You can get it from here: You do not have permission to view the full content of this post. Log in or register now. or You do not have permission to view the full content of this post. Log in or register now., and source code: You do not have permission to view the full content of this post. Log in or register now.
There are several ways to prevent running for apps:
- Force-Stop, will set stopped state, no static broadcast, sinde Android 3.2, requires android.permission.FORCE_STOP_PACKAGES
-- can granted to privileged apps, /System/PrivApp
-- adb shell has it, Brevent can use
- App-Standby, since Android 6.0, requires android.permission.CHANGE_APP_IDLE_STATE
-- only granted to Framewok apps having the same singature with framework.apk
-- adb shell has it, Brevent can use
So as you can see, Brevent working on the adb shell, having the shell permission, and can do a lot of things.
Furthermore, Brevent use directy android hide methods, instead using dumpsys, am, cmd and so, more effective.
However, there is one restriction, as the permissions cannot be granted to apps, so Brevent requires you run the adb after every boot.
But, Brevent requires no-reboot to undate Brevent Server. And phone should be use, not for reboot.
In short, Prevent without Root. You can get it from here: You do not have permission to view the full content of this post. Log in or register now. or You do not have permission to view the full content of this post. Log in or register now., and source code: You do not have permission to view the full content of this post. Log in or register now.
There are several ways to prevent running for apps:
- Force-Stop, will set stopped state, no static broadcast, sinde Android 3.2, requires android.permission.FORCE_STOP_PACKAGES
-- can granted to privileged apps, /System/PrivApp
-- adb shell has it, Brevent can use
- App-Standby, since Android 6.0, requires android.permission.CHANGE_APP_IDLE_STATE
-- only granted to Framewok apps having the same singature with framework.apk
-- adb shell has it, Brevent can use
So as you can see, Brevent working on the adb shell, having the shell permission, and can do a lot of things.
Furthermore, Brevent use directy android hide methods, instead using dumpsys, am, cmd and so, more effective.
However, there is one restriction, as the permissions cannot be granted to apps, so Brevent requires you run the adb after every boot.
But, Brevent requires no-reboot to undate Brevent Server. And phone should be use, not for reboot.