Android browser automation

Android browser automation means programmatically controlling a real Android browser — not a desktop browser emulating mobile.

Damru is the first open-source framework built specifically for this. It boots a genuine Android 14 environment with Redroid in Docker, then drives Chrome through the Chrome DevTools Protocol with a Playwright-style Python API. Because the browser is really running on Android, the device, GPU, and network fingerprints are authentic — and Damru spoofs them at the OS level rather than injecting JavaScript.

Android web automation vs Android browser automation

"Android web automation" and "Android browser automation" are the same discipline — programmatically driving web pages in a real Android browser — and Damru does exactly that.

Whether you call it Android web automation, Android browser automation, or mobile browser automation, the goal is identical: run genuine web sessions on a real Android device under code control. Damru handles it end to end with Redroid + Playwright + CDP, so every session carries an authentic Android fingerprint.

Why automate a real Android browser?

How Damru does it

Android 14 runs inside a Redroid Docker container. Native hooks (LD_PRELOAD, resetprop, iptables) rewrite device identity, system properties, and network at the OS level; the GPU and hardware fingerprints are patched to stay internally consistent; and Chrome is driven over CDP via ADB. There is nothing injected into the page for a detector to read.

Quickstart

pip install damru
python -m damru install-image

from damru import AsyncDamru
async with AsyncDamru(device="random") as browser:
    page = await browser.new_page()
    await page.goto("https://example.com")

Android browser automation vs desktop tools

Desktop stealth tools — undetected-chromedriver, playwright-stealth, SeleniumBase — patch a desktop browser with JavaScript. Damru is the only open-source option that automates a genuinely Android browser. See the full comparison or the undetected-chromedriver alternative guide.

FAQ

What is Android browser automation?

It means programmatically controlling a real Android browser — Chrome running on an actual Android OS — rather than a desktop browser configured to look mobile.

Can I automate Android Chrome without a physical phone?

Yes. Damru runs Android 14 inside a Docker container (Redroid), so no physical device or emulator GUI is needed — just a Linux host or WSL2.

Why use Android instead of desktop headless?

Mobile-rendered sites behave differently, and real mobile traffic is the hardest for anti-bot systems to flag. Damru gives you a genuine Android fingerprint, not a spoofed desktop one.

Is Android web automation the same as Android browser automation?

Yes — "Android web automation" and "Android browser automation" describe the same thing: driving web pages in a real Android browser from code. Damru does exactly that with Redroid + Playwright + CDP.

Related: antidetect browser for Android · stealth browser automation · Android web scraping.

Get started →