Thank you for replying.
Actually if you look at this article, 240 is pretty usual for an Android smartphone : https://medium.com/@juliozynger/your-app-and-low-latency-audio-output-d21d7b672305
Or if you look at Android developer website in the audio latency chapter :
" Typical buffer sizes include 96, 128, 160, 192, 240, 256, or 512 frames, but other values are possible."
I don’t think that putting my code here can be relevant as it seems to be a problem with JUCE Android code. Indeed I don’t have any problem with bluetooth on my desktop app (i have a stable 512 buffer size, bluetooth or not).
At each getNextAudioBlock call i increment a counter with my bufferToFill.numSamples in order to make a step sequencer like in this tutorial : https://youtu.be/M9NhoEs3Jzg
If this value doesn’t change my steps remain equal so everything works fine, but when connected to bluetooth this value goes crazy and my steps are not equals anymore.
Just wanted to know if someone experienced the same issue with Android. I will test on iOS today.