Inconsistent audio received from developer audiobytes webhook

[AnkushMalaker]

Describe the bug

When using the OMI app’s "audio bytes webhook" with the OMI DevKit 2 device, the audio data received by the server is garbled and has significant timing issues. Despite setting the webhook interval (e.g., 5 seconds), the received audio can be much longer (e.g., 17 seconds) and plays back at inconsistent speeds—alternating between very fast and very slow segments.

To Reproduce

Steps to reproduce the behavior:

1. Connect the OMI DevKit 2 to an Android device.
2. Run a backend server such as https://github.com/mdmohsin7/omi-audio-streaming
3. Open the OMI app and configure the audio bytes webhook with a 5-second interval.
4. Begin speaking normally and monitor the server endpoint receiving webhook data.
5. Observe the audio payloads received—note the duration and playback irregularities.

Current behavior

The server receives audio that significantly exceeds the configured interval and plays back at fluctuating speeds. For example, instead of 5 seconds of clean audio, a 17-second clip may be received with distorted pacing and garbled speech.

Expected behavior

Webhook audio should match the configured interval duration (e.g., 5 seconds) and have consistent playback speed without distortion or timing slippage.

Screenshots

N/A

user ID (can we access the user info to validate the bug?):

NA

Smartphone + device (please complete the following information):

• Device: OnePlus Nord CE 2 Lite
• OS: Android 14
• Browser: N/A
• App Version: NA
• Device version: 2.0.9

Additional context

This issue typically follows a period of inconsistent webhook responses, possibly due to network latency or dropped requests. The app appears to mishandle this slippage, leading to invalid timing or buffering logic on the audio stream. This results in corrupted webhook audio unsuitable for downstream processing.

[AnkushMalaker]

#2165 is related but not exactly. "Time slippage" was mentioned and linked in that conversation.