Aggressive Mode can be useful when an app expects certain system properties to exist and may behave differently when they are missing. However, creating these properties can also introduce another detection vector.

(Agressive Mode comes disabled by default btw)

Majority of apps usually rely on checking whether a property has the expected value, and once the value matches, they consider the check passed. Duck Detector goes a step further by verifying the same properties through multiple methods, making its detection more difficult to bypass by simply creating or modifying the expected properties.

To handle this, I've added two independent methods that successfully bypass Duck Detector even with Aggressive Mode enabled. I've also added every property checked by Duck Detector to the Duck Props section, so any mismatched properties can be fixed seperately.

I've also tested this on Android 12 and Android 14, where I couldn't reproduce the detection. So far, it appears to be specific to Android 16+