Audio Latency fix on Android

So Ashley I know you've been saying that Google should fix Android to have lower latency. It seems they have

android-developers.googleblog.com/2021/03/an-update-on-androids-audio-latency.html

And it's evident in apps like Real Guitar on Android, where sounds play immediately after a touch event. On the same mid range phone, a simple construct 3 test apk produces 0.3 to 0.4 seconds of latency between touch and sound played. That's such a long delay, you can definitely hear and feel it.

However, even google seem to be recommending an open source library called oboe.

developer.android.com/games/sdk/oboe/update-build-settings

Is there a way to use this in c3?

Since my device and Android can perform with next to 0 audio latency (see Real Guitar), doesn't that mean that Construct 3 is lagging behind the times? We can't blame it on Android or the devices any more.

Thank for reading

It's the Chromium browser engine that needs to be updated, not just Android. The work appears to be tracked in this issue which mentions moving Chromium to Oboe.

Ah! You're the best 😍 as ever. Thanks

I'm sure we already configure everything on the JavaScript side to be as low latency as possible without risking glitching audio. There must be something in the Chromium engine that's not using the lowest possible latency, but that's up to Google, and why that issue was filed.

I know you do on your end, it's easy to see since sounds trigger *immediately* in Firefox Android.

It boggles the mind that the chromium team think this has been solved. I get being super busy or audio not being a priority, but solved implies it's been tested and works.

It doesn't work.

The linked issue remains open, which implies Google know there is still work to be done on it.

Thank you Ashley