«Programmatic taps same pixel 0 ms» - forum proven detection। Android API hypothesis, Meta confirm नहीं।
«WA analyzes touch area» infrastructure = overpay या wrong solution। Confirmed risk ≠ forum hypothesis।
GBWhatsApp, Plus banned - signature hash mismatch, not behavior। Only solid point - vs gray automation observation reconstruction।
Before: WA scans Accessibility + package list।
After: community assumes antifraud weighs automation; Meta publishes nothing - assumption।
Before: 0 ms taps vs 50–150 ms finger।
After: MotionEvent coords/area - WA use = hypothesis। Web parallel: isTrusted।
| Exists | WA ban use | |
|---|---|---|
| AccessibilityManager | Yes | Unconfirmed |
| NotificationListener | Yes | Unconfirmed |
| MotionEvent | Yes | Unconfirmed |
| PackageManager | Yes, 11+ limited | Unconfirmed |
| APK signature | Yes | Yes mod clients |
Screen read, button press - documented। Common in farms। isEnabled() ≠ WA sees which app bans।
Android 11+ QUERY_ALL_PACKAGES limited। Full list spam name ban - contradicts modern model generally।
APK clicker, 5s interval - ban msg 24; fixed X/Y, zero pressure। MotionEvent real; ban cause - reports, speed - unproven।
Root input tap vs Play Integrity - observations only; neither auto-ban nor guaranteed bypass confirmed।
50–150 ms tap; 50–100 msg/day Accessibility - behavioral antispam style orientation।
Confirmed: mod clients; server signature check।
Hypothesis: app list scan, pressure/coords, pause randomization, non-Play APK alone।
Replace GBWhatsApp/Plus first - only official confirmed risk।
Infrastructure में mod client? पहले replace।
Practical rule:
Android क्या pass कर सकता ≠ WA provably क्या use करता।
