I’ve been conducting internal experiments under the <a title="188CM" href=" removed link " target="_blank" rel="noopener">188CM lab environment to evaluate Web MIDI timing across a range of Android devices. The goal is to understand how multi-channel MIDI events behave on mid-range phones with USB-MIDI connections under real-world conditions.

This setup is strictly experimental — not a public release. It focuses on measuring event latency, jitter, and buffer performance during extended sessions.

Test Setup

• Android Versions: 7.0 → 14

• Devices: 3–8 GB RAM, typical mid-range models

• MIDI Interface: USB OTG

• Browser: Chrome (stable)

• Load Scenarios: idle vs moderate background processes

Testing Methodology

• External metronome at 120 BPM as timing reference

• Capture timestamps via JavaScript callbacks

• Record 500–1000 event cycles per test

• Analyze median latency and variance

Observations

Baseline / Idle

• Average latency: 9–13 ms

• Jitter range: ±3–5 ms

• UI performance stable at 60 FPS

Under Background Load

• Latency spikes: 17–22 ms on Android 7–9

• Minor jitter during USB reauthorization

• Drift visible after idle periods over 15–20 minutes

Android 11+ Improvements

• Event buffer consistency significantly better

• Fewer spikes and lower overall drift

Additional Insights

• Older Android kernels seem sensitive to USB polling intervals

• Chrome stable handles event queues more predictably than some Chromium forks

• Resetting USB authorization occasionally improves long-session stability

Open Questions / Discussion Points

• Any experience profiling Web MIDI timing on Android 7 or 8 with high-resolution instruments?

• Recommended buffering strategies to keep drift below 10 ms for long sessions?

• Known OTG limitations for mid-range devices under sustained MIDI playback?

• Best practices for maintaining stable Web MIDI sessions over 30–60 minutes on mobile?

• Benchmark comparisons from real-world 188CM setups outside controlled lab conditions?

Would love to hear insights or shared experiences from developers working with Web MIDI on Android — especially if you’ve tested long-duration sessions using 188CM environments.