Using ESP32 & Android to Create Rich IoT Experiences
summary
A working prototype smart ashtray demonstrates Android handling UI and configuration while an ESP32 runs the device logic and wireless stack; code uses ESP-IDF and the ESP32 hosts a small REST HTTP server for simplicity. Wi‑Fi runs in client or AP mode, Android Q requires a network specifier and extra permissions, and practical power budgeting assumes roughly 250mA for the ESP32. Alternatives covered: QR-code pairing, audio FFT with the Lyra T and esp-dsp.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:12MAN SPONSOR
- 0:52What's upcoming
- 5:15Throwback time
- 6:47Wireless MCU
- 9:27But: beware the differences
- 11:13Benefits and weaknesses
- 12:34Infrastructure mode
- 16:28Multiple permissions (WiFi-GPS)
- 19:40Step 1: scan for devices
- 20:04Broadcast Receiver
- 20:50Register it
- 21:05connect • Android Q requires user consent
- 21:44Android Q: two ways
- 22:31Old connection process
- 26:41Why go insane?
- 28:15QR codes - 11
- 31:33Audio "sideband" signaling - IV
related talks
22mAndroid Built for Radio over IP
19mAndroid all the things!
21mAndroid Things: The IoT Platform for Everyone
29mBuilding Industrial-Grade RFID Systems with Android and Ko…
34mAndroid All the Things!
39mUse-cases on integrating POS Hardware on Android and Linux
39mAndroid Things: High Level Introduction
22mHow My Android App Learned to Talk to Plants