BootManager Donate v3.7.1
Requirements: 4.0.3+ | Xposed
Overview: With this app modul you could prevent selected apps of running on system startup. Only apps with the permission BOOT_COMPLETED are shown in the list. System apps are marked with an exclamation mark.


IMPORTANT
Your device has to be rooted to install the required X-posed framework
Description for non-developers:
Each app with permission "android.permission.RECEIVE_BOOT_COMPLETED" is placed in a (Windows slang) "startup folder". For my 200 installed apps that are about 33%. On system boot every of these apps gets started. Possible options:
- app shows a notification
- app starts a (hidden) service in background
- app exits again (eg user has set an option)
If you disable an app in the BootManager it does not get that event and is not started at *next system boot*.
ReceiverStop
An app still starts at system boot? Android has many other events which could start an app!
Example: Skype has the permission "android.permission.MOUNT_UNMOUNT_FILESYSTEMS". This means, (again Windows slang) if you insert a DVD into you drive, "autorun" is executed and starts Skype.f000h
Note: As your sd-card is mostly always inserted, this could be used to start apps at system boot....
Other triggers are: A BlueTooth device (dis-)connect, connection type changes (2g/3g/wlan) or power adapter is (un-)plugged.
All these could be restriced with my other app "ReceiverStop". Be carefull and do not disable the wrong.
What's New
Bugfix: Android 4
Donate feature unlocked
This app has no advertisements
More Info:
Download Instructions:
patched: no key needed
https://userscloud.com/7x8zmn0vydbd
Mirror:
(Closed Filehost) http://tusfiles.com/lxs24a9xg9bp
original + donate key
https://userscloud.com/ou7dpg5p8bie
mirror:
(Closed Filehost) http://tusfiles.com/az79a7mmydi4
Requirements: 4.0.3+ | Xposed
Overview: With this app modul you could prevent selected apps of running on system startup. Only apps with the permission BOOT_COMPLETED are shown in the list. System apps are marked with an exclamation mark.
IMPORTANT
Your device has to be rooted to install the required X-posed framework
Description for non-developers:
Each app with permission "android.permission.RECEIVE_BOOT_COMPLETED" is placed in a (Windows slang) "startup folder". For my 200 installed apps that are about 33%. On system boot every of these apps gets started. Possible options:
- app shows a notification
- app starts a (hidden) service in background
- app exits again (eg user has set an option)
If you disable an app in the BootManager it does not get that event and is not started at *next system boot*.
ReceiverStop
An app still starts at system boot? Android has many other events which could start an app!
Example: Skype has the permission "android.permission.MOUNT_UNMOUNT_FILESYSTEMS". This means, (again Windows slang) if you insert a DVD into you drive, "autorun" is executed and starts Skype.f000h
Note: As your sd-card is mostly always inserted, this could be used to start apps at system boot....
Other triggers are: A BlueTooth device (dis-)connect, connection type changes (2g/3g/wlan) or power adapter is (un-)plugged.
All these could be restriced with my other app "ReceiverStop". Be carefull and do not disable the wrong.
What's New
Bugfix: Android 4
Donate feature unlocked
This app has no advertisements
More Info:
Code: Select all
https://play.google.com/store/apps/details?id=de.defim.apk.bootmanagerDownload Instructions:
patched: no key needed
https://userscloud.com/7x8zmn0vydbd
Mirror:
(Closed Filehost) http://tusfiles.com/lxs24a9xg9bp
original + donate key
https://userscloud.com/ou7dpg5p8bie
mirror:
(Closed Filehost) http://tusfiles.com/az79a7mmydi4
MSG ME FOR ANY PROBLEM U FACE ON MY APPS

MSG ME FOR ANY UPDATE OR REQUEST

MSG ME FOR ANY UPDATE OR REQUEST