Android phone UA reports a screen larger than any real Android phone
br.android_phone_screen_oversized · convicts
What it catches
DEVICE<->screen coherence on the ANDROID manifold — the Android sibling of br.ios_screen_oversized and the FIRST device-coherence check on Android (the detector had none). Scoped to the UA 'Mobile' token, which Android Chrome OMITS on tablets and Android TV / Auto (those UAs carry 'Android' WITHOUT 'Mobile') — so this keys on PHONES + foldables only, whose logical screen is bounded: the largest current Android phone/foldable tops out near ~1100 CSS px in either dimension (unfolded foldables ~884 wide). An Android+Mobile UA reporting max(screen.width, screen.height) > 1400 is therefore a DESKTOP faking an Android phone — a Mobile UA over a 1920x1080 (or similar) desktop screen, the direct Android analog of the desktop-faking-iOS ios_screen_oversized catches. FP-SAFE by the hardware bound (no Android phone CSS screen approaches 1400; tablets/TV are out of scope by the Mobile-token gate). Complements br.mobile_no_touch (which catches the SAME desktop-faking-mobile only when it also forgets touch); this fires on the screen regardless of the touch spoof. GROUNDED LIVE: a Chromium given a Pixel-phone Android+Mobile UA + KS_SCREEN=1920x1080 fires android_phone_screen_oversized; the same UA + a real Android phone screen (412x915) is SILENT, as is a coherent KS_DEVICE Android phone.
Signals it reads
browser.android_phone_screen_oversized
How it fires
present
Bypassed by 10
Frontier evaders that reach the detector uncaught (scored only suspicious, defeating every convicting tell) — this check is not one that stops them. The red-team frontier this detection still has to convict.