Imagine an Android device (possibly any device from any manufacturer) that is connected via bluetooth to a speaker (or any bluetooth audio device)... and there has been a "significant" amount of time where no audio has been played from the device.
At the moment audio resumes playing from this device, there is more often than not a "speaker is slowly waking up" phase where no audio is heard and the audio is late to become audible.
This is less obvious when the audio is being "kept alive" with constant audio, or only taking short breaks of silence, but what if you have an application that makes very short and intermittent sounds at unpredictable times... like an alarm that measures environmental conditions with a sensor?
I'm not sure if:
A) This behavior is some kind of power-saving feature of the output device and we would have no control over it other than to play some kind of fake audio/silence prior to our desired sound... or have a low-volume sound/white noise on a constant loop... in order to pre-empt/prevent the "warm up."
B) It's part of the bluetooth protocol/standard/definition
C) It's controllable in software with something like (on Android):
bluetooth.setMode(BluetoothMode.NO_NAPPING_ALLOWED);
I'm hoping the case is (C), and if so, then what is the proper code for this?
I'm sure there is a similar question out there that is asked in a different way, but I can't find it, and I have searched through the documentation for AudioManager and although bluetooth is mentioned in many places, I can't find this functionality.