diff options
| author | Eric Laurent <elaurent@google.com> | 2009-09-15 07:10:12 -0700 |
|---|---|---|
| committer | Eric Laurent <elaurent@google.com> | 2009-09-15 07:10:12 -0700 |
| commit | 296a0ec7e149b6b373b9271683eca286b1c376ed (patch) | |
| tree | 29d0e221e2719cc7fe816b5f45eb752607ff28ef /sax/java/android | |
| parent | 54c06152e0d9c666aec61ae5d9686d7d3327ea34 (diff) | |
| download | frameworks_base-296a0ec7e149b6b373b9271683eca286b1c376ed.zip frameworks_base-296a0ec7e149b6b373b9271683eca286b1c376ed.tar.gz frameworks_base-296a0ec7e149b6b373b9271683eca286b1c376ed.tar.bz2 | |
Fix issue 2118464: cannot play ring tones and notifications after disconnecting BT headset while in call.
The problem comes from the fact that when the duplicated output is closed after BT headset disconnection, the OUTPUT_CLOSED notification is not sent to AudioSystem. Then the mapping between notification stream and duplicated output cached in AudioSystem is not cleared and next time a notification is played, the duplicated output is selected and the createTrack() request is refused by AudioFlinger as the selected output doesn't exist.
The notification is ignored by AudioFlinger because when it is sent by the terminating playback thread, the thread has already been removed from the playback thread list.
The fix consists in sending the notification in closeOutput() and not when exiting the playback thread.
The same fix is applied to record threads.
Diffstat (limited to 'sax/java/android')
0 files changed, 0 insertions, 0 deletions