BootManager v3.8.4 [Donate]
Requirements: 2.3.3 and up | Xposed Framework
Overview:
With this application modul you could forestall chose applications of running on framework startup. Just applications with the authorization BOOT_COMPLETED are appeared in the rundown. Framework applications are set apart with a shout check.
Imperative
Your gadget must be attached to introduce the required X-postured structure: http://tinyurl.com/cd46qco
Depiction for non-designers:
Each application with authorization "android.permission.RECEIVE_BOOT_COMPLETED" is put in a (Windows slang) "startup envelope". For my 200 introduced applications that are around 33%. On framework boot everything about applications begins. Conceivable alternatives:
- application demonstrates a notice
- application begins a (shrouded) benefit in foundation
- application exits once more (eg client has set an alternative)
In the event that you handicap an application in the BootManager it doesn't get that occasion and is not begun at *next framework boot*.
ReceiverStop
An application still begins at framework boot? Android has numerous different occasions which could begin an application!
Illustration: Skype has the consent "android.permission.MOUNT_UNMOUNT_FILESYSTEMS" . This implies, (again Windows slang) in the event that you embed a DVD into you drive, "autorun" is executed and begins Skype.
Note: As your sd-card is generally dependably embedded, this could be utilized to begin applications at framework boot....
Different triggers are: A BlueTooth gadget (dis-)associate, association sort changes (2g/3g/wlan) or power connector is (un-)stopped.
All these could be restriced with my other application "ReceiverStop". Be carefull and don't handicap the off-base.
What's New
- Updated interpretations
https://userscloud.com/kv5pgsxp7u10
No comments:
Post a Comment