I think the problem comes from old device then, cause i got skipped frame, rate alert, and sometimes the music is cutted, or just don't launch when it goes to next track (on android)

Hi Robin, thanks for the reply.

The issue appears specifically on older Android devices (e.g., Android 8.1 / API 27) and ROMs with aggressive battery management (like Xiaomi MIUI).

The exact scenario:

The app plays a track using AudioPlayer. A Foreground Service is running to keep the app alive.

When the track finishes (screen locked), the native player stops and releases the audio wakelock.

The Gap: At this precise moment—before the JS stop event listener can trigger and call play() for the next track—the OS suspends the WebView/JS thread because it detects silence + locked screen.

As a result, the next track never starts (or starts only when I wake up the screen).

Even with a Foreground Service, the round-trip to the JS thread (Native Stop -> JS Event -> JS Logic -> Native Play) is too slow or blocked by the OS on these devices.

I believe the only robust solution for these devices would be a way to handle the queue natively, to avoid depending on the JS thread for the transition.