Open gnuhead-chieb opened 3 years ago
This is what the FOSS app Autostarts does which I've revived few months ago. Android's package manager is, unfortunately, very unreliable and full of bugs. This will be implemented after implementing my own alternative package manager.
This is what the FOSS app Autostarts does which I've revived few months ago. Android's package manager is, unfortunately, very unreliable and full of bugs. This will be implemented after implementing my own alternative package manager.
Autostarts basically just disables broadcast receivers, right? With regard to that, I am sorely missing the listing of the intents a receiver listens to in App Manager. Autostarts does that, and e.g. MyAndroidTools looks like this:
whereas App Manager only shows this:
Any update? Why not combining AutoStart into AppMgr
Any update?
None. If there were any updates, you would find it in the labels section (at the right hand side or bottom).
Why not combining AutoStart into AppMgr
Because it's not possible to combine both as they are designed and implemented in a different way. As a result, AutoStarts also has additional issues with some APK files which cannot be solved without altering its implementation.
AM should be show and make toggllable app actions(written in app manifest with action tag). https://developer.android.com/reference/android/content/Intent
This feature already implemented in 3C App Manager.