-
Hugo Lefeuvre authored
Busy tone is broken by design: since there is no way to play a tone for a given amount of time, callFailure() was calling stopTone() just after playATone(), meaning that the tone was only played for a few milliseconds. callBusy() was even more broken because it was calling checkAudio() just after playATone(), meaning that (1) the tone would only play for a few ms and (2) the tone would start again when the audio layer is restarted. Even worse, callBusy was not calling stopTone(), meaning that if an incoming call tone was being playing played then it would never be stopped. This feature might be reintroduced for accessibility purposes at some point in the future, along with a refactoring of the tone system in the daemon. Change-Id: I15957e050688bfe5f5ce84f971d5a14b875028b9 Reviewed-by: Sebastien Blin <sebastien.blin@savoirfairelinux.com>
da92d30b