BootManager

Run only the apps you want at system start.

Installation: Install this module, enable it in Xposed Installer, reboot device.
Usage: Open this app and select the apps that should not start at system boot. Done.

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. To restrict system apps you have to donate.

Donation:

• No self-promotion in the app.
• System apps could also be selected
• You support this app and further development!

This app does not connect itself to any websites or hosts!

Website: http://apk.defim.de

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.
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.