Lamda Tutorial: Connect, Automate, and Intercept Android Devices
A step-by-step tutorial on using Lamda: connect devices, drive the WebRTC remote desktop, automate with OCR and image matching, and intercept traffic with one-click MITM.
Getting a fleet of Android devices under control usually means juggling scrcpy, adb scripts, proxy tools, and Frida commands in separate terminals. With Lamda, all of it lives in one place. Here's a practical walkthrough of what a typical session looks like.
🚀 Want to deploy Lamda yourself?
Docker configs, system requirements, and installation guides — all on one page.
View Lamda Tool Page →Step 1: Connect devices
Plug in or provision your Android devices and let Lamda auto-discover them over adb. Each device appears in the dashboard with live status — battery, network, and screen state — so you can spot problems before they affect your tests.
Step 2: Drive the remote desktop
Click any device to open the WebRTC/H.264 remote desktop. The stream is low-latency enough for real interaction: tap, swipe, type, and drag just like a local screen. This is your everyday control surface for manual checks and ad-hoc fixes.
Step 3: Automate with UI, OCR, and images
Lamda's automation engine lets you define triggers three ways:
| Trigger | Best for |
|---|---|
| UI hierarchy | Stable, native apps with predictable layouts |
| OCR | Reading text, captchas, and dynamic labels |
| Image matching | Visual elements that lack text or stable IDs |
Chain actions — wait, tap, assert, screenshot — into repeatable flows that run unattended across every device in a group.
Step 4: Intercept traffic with one click
Instead of configuring a proxy and trusting a CA on each device, Lamda's one-click MITM handles interception per device. Open the traffic view to inspect requests and responses in real time — invaluable for API debugging and security review.
Step 5: Instrument with Frida
For deeper work, Lamda ships with Frida built in. Attach to a process, run hooks, and read memory without standing up a separate Frida server. Combine that with MITM output for a complete picture of what an app does under the hood.
Step 6: Automate at scale with the API
Every action you can do in the UI is available through the 160+ REST APIs, and MCP/agent support means an LLM agent can operate the fleet programmatically. A single script can spin up a group, run a flow, and collect screenshots across hundreds of devices — then hand the results back to your CI pipeline.
🚀 Ready to try Lamda?
System requirements, Docker configs, and install steps are waiting.
View Lamda Tool Page →Lamda turns Android fleet management from a patchwork of scripts into a single coherent workflow — connect, automate, intercept, instrument, and scale, all from one open-source platform.