Building Pixel Control Center: High-Performance Android Mirroring on Desktop with Flutter & Scrcpy

If you have ever mirrored an Android handset to your PC or Linux workstation using scrcpy, you know it is the gold standard for low-latency screen casting and remote control.

Yet, running scrcpy on a modern flagship device like the Google Pixel 7 Pro (Tensor G2 SoC, Android 17) inside a real-world multi-network desktop setup quickly reveals four frustrating failure modes:

1. The "Black Screen with Working Controls" Bug: Invoking --turn-screen-off calls SurfaceControl.setDisplayPowerMode(POWER_MODE_OFF). On Google Tensor hardware, the video encoder buffer blanks out completely—your mouse clicks still work on the phone, but the desktop window renders pure pitch black.
2. The Ghost Virtual Display Bug: Previous sessions or headless services spawn lingering app_process instances (Display 73, Display 105). Without explicit display binding, scrcpy attaches to an invisible virtual display instead of your active phone screen.
3. The Dynamic IP / AP Hopping Nightmare: Moving between your home Wi-Fi, office router, or phone hotspot changes your handset's DHCP IP address. Static wireless ADB scripts fail every single time.
4. The Disappearing Soft Keyboard: Forwarding hardware keyboard inputs via --keyboard=uhid signals Android to hide the on-screen virtual IME, making it impossible to type emojis, passwords in secure fields, or use the dialer.

To solve all four issues with zero configuration, we built and open-sourced Pixel Control Center—migrating from an initial Python prototype to a high-performance Flutter Desktop (Windows & Linux) application.

Here is what we learned, the hardware workarounds that worked, and how we structured the architecture.

---

1. Taming the Hardware Quirks: Google Tensor & Android 17

Echoing insights from the community on managing ADB wrappers—such as Thoughts on Building a GUI Workflow Around scrcpy and Giving an AI Agent a Real Phone: What ADB Automation Actually Looks Like—handling ADB in production requires accounting for device-specific hardware behavior:

A. The OLED Dimming Workaround (Instead of POWER_MODE_OFF)

Rather than cutting display power via --turn-screen-off (which shuts down the hardware encoder pipeline on Tensor G2), our supervisor dynamically reduces backlight brightness to 0 via Android system settings before starting the stream:

// Dim display to 0 to preserve OLED longevity without breaking the encoder buffer:
await adbService.execute([
  ...deviceTargetFlags,
  'shell',
  'settings',
  'put',
  'system',
  'screen_brightness',
  '0',
]);

When the user closes scrcpy, the supervisor catches the process termination and automatically restores normal brightness (100).

B. Forcing Physical Display Binding & Purging Zombie Daemons

To prevent scrcpy from accidentally latching onto ghost virtual displays spawned by Android background processes, our configuration builder always enforces --display-id=0 and kills lingering app_process daemons:

await adbService.execute([...deviceTargetFlags, 'shell', 'pkill', '-9', '-f', 'app_process']);
args.add('--display-id=0');

C. Keeping the On-Screen Keyboard Active & Dismissing Keyguard

To ensure the touch keyboard stays visible even when physical keystrokes are forwarded via Linux UHID, while automatically waking up and unlocking the screen:

await adbService.execute([...deviceTargetFlags, 'shell', 'input', 'keyevent', '224']);
await adbService.execute([...deviceTargetFlags, 'shell', 'wm', 'dismiss-keyguard']);
await adbService.execute([
  ...deviceTargetFlags,
  'shell',
  'settings',
  'put',
  'secure',
  'show_ime_with_hard_keyboard',
  '1',
]);

---

2. Zero-Config Dynamic Wi-Fi Discovery (4 Tiers)

Instead of forcing users to check their Android settings or type IPs into a terminal, our NetworkDiscoveryService executes a multi-tiered heuristic search:

graph TD
    T1[Tier 1: Check Active Wireless ADB Connections] -->|Not Found| T2[Tier 2: Query USB Device IP via wlan0 / ip route]
    T2 -->|No USB Device| T3[Tier 3: Query ADB mDNS Services Daemon]
    T3 -->|mDNS Unreachable| T4[Tier 4: Multithreaded Subnet Socket Probe Port 5555]
    T4 --> Connected[Auto-Connect TCP/IP Session]

1. Tier 1 (Active ADB): Checks adb devices -l for existing wireless TCP endpoints, filtering out phantom emulators (like BlueStacks on 127.0.0.1:5555).
2. Tier 2 (USB Query): If connected by USB, queries ip addr show wlan0 directly.
3. Tier 3 (mDNS Discovery): Queries Android's native wireless debugging mDNS service (adb mdns services).
4. Tier 4 (Subnet Socket Probe): Inspects the host machine's local network interfaces (NetworkInterface.list), isolates the /24 subnet prefix (e.g. 192.168.100.x), and asynchronously probes port 5555 across candidate IPs in concurrent batches of 60 with a fast 200 ms socket timeout.

---

3. High-FPS Performance Optimization & Thermal Protection

On a high-DPI device (1440 × 3120 pixels on the Pixel 7 Pro), raw unconstrained mirroring over Wi-Fi generates massive encoder load, battery heat, and eventual thermal throttling.

By default, Pixel Control Center caps video resolution to 1080p / 1200 px (--max-size=1200) at 8 Mbps:

• Drops Tensor G2 video encoder strain by >60%.
• Slashes stream latency to sub-30ms.
• Prevents extreme thermal throttling on low battery levels.

---

4. Flutter Desktop Architecture & Atomic Commits

We ported the core logic into clean, layered Dart modules:

• AdbService: Process management, device listing parser, and hardware adjustments.
• ScrcpyService: Process supervision, stream piping to real-time log consoles, and lifecycle cleanup.
• NetworkDiscoveryService: Cross-platform network socket and interface probing.
• Material 3 Desktop UI: Responsive dark dashboard with live battery telemetry, quick actions, remote navigation controls, and terminal drawer.

Following atomic git commit discipline ("AND / ET" principle where every commit represents exactly one logical unit of work), the entire history was built across clean, bisectable Conventional Commits:

cb00a85 docs: add initial project readme and hardware notes
cc7620b chore(flutter): scaffold flutter desktop application
7490a10 feat(models): implement device and connection configuration models
d92f8b2 feat(services): implement adb interaction service with pixel quirks support
56f42e7 feat(services): implement scrcpy process supervisor
bb289cd feat(services): implement dynamic local network wifi discovery
dca7037 feat(ui): implement modern material 3 desktop dashboard
9d4ba53 test: add unit tests for adb parsing and device models
045105f fix(launcher): disambiguate adb targets and dismiss keyguard to prevent black screen
d97b61a fix(app): target device flags for adb shell and unlock keyguard
faf8282 fix(services): filter emulators and dismiss keyguard to prevent black screen
2c679e6 perf(app): optimize discovery timeout and target telemetry to prevent lag
b51c1cf perf(launcher): cap stream resolution to 1200 to prevent thermal throttling

---

5. Open-Source & What's Next

The complete code is open-source and available on GitHub:
👉 github.com/arispacco/pixel-control-center

We are preparing Pixel Control Center for MLH Global Hack Week: Builders Week (November 6–12, 2026), expanding support for automated MSIX packaging for the Windows Store and native Linux AppImage/Flatpak distribution.

If you have encountered black screen issues or thermal throttling on Tensor or Exynos devices when using scrcpy, try these workarounds—and let us know what you think in the comments below!