[Android Apps and Games] Dark3n:
SD Maid recognizes some of those tools, but only uses it to work better. E.g. LuckyPatcher creates weird files that don't fit in, but if deleted, would break apps, SD Maid understands that and works around it.

Generally, SD Maid's protection mechanisms are very light now adays (keep honest users honest). They have been much more complex around end of v2, early v3. The thing though is that it is a cat and mouse game just wasting time. I can spend hours making it more difficult, but it will be warezd anyways at somepoint I'm just delaying it. Downside of a popular app... Once the mechanism is "breached" my work on it was in vein. Legit users don't benefit from devs spending time on this. So I stopped spending time on such mechanisms and also removed some (made the code cleaner). This coincidentally halved the amount of "pro version doesn't work" mails I got around that time :rolleyes:.

If people like an app they should buy/donate/subscribe/whatever or else not be surpised why they are left with ****ty ad-ridden software that seems untrustworthy.

The issue the post you are referring to was describing is purely with the super-user management app. It's common among all super-user apps and is some sort of race-condition. I think it causes a bad entry in the superuser apps database.

SD Maid does nothing more than trying to open a root shell, but then nothing happens, e.g. neither DENIED nor GRANTED.

See: https://github.com/d4rken/sdmaid-public/wiki/Frequently-Asked-Questions#hanging

SystemCleaner and AppCleaner have advertising/bugreporting related filters but no app can combat this technique. It's not based on files on the device.

There is no corpse left behind. The app no longer responding (due to being uninstalled) is what they track. The only solution I see is to change the Google advertising ID after reach unintalled app that does something like this. They would still know you uninstalled the app, but wouldn't match you again because your advertising ID changed. Some apps (and ****ty SDKs) place extra identifiers via files on public storage, which is something SD Maids CorpseFinder can help with, just gotta make sure SD Maids explorer shows the files as recognized (little app icons).

Those are BroadcastReceivers. Permissions can't just be disabled with out a shim like AppOps or exposed as apps don't expect not to be given certain permission.

There are 3 basic components for Android apps: Activities, Services, and Receiver. Receivers (`BroadcastReceiver`) receive things, they react to events, e.g. BOOT_COMPLETED, or `INCOMING_CALL` or `HEADPHONE_PLUGIN`. These 3 archtypes can be disable per app individually. The idea is that apps can disable components if they are not needed. With root we can also do that. This can break apps and apps can turn their own components own again. In many cases disabling receivers don't break an app completely, so if you don't want an app to react to certain events that the system may send out, you can try to disable the receiver for it.

But be careful: https://github.com/d4rken/sdmaid-public/wiki/AppControl#receiver-manager-autostart

No worries, just distracted with other stuff and SD Maid is running fairly stable :cool:. Happy to see discussions going without me!