summaryrefslogtreecommitdiffstats
path: root/docs/html/resources/tutorials
diff options
context:
space:
mode:
authorEric Laurent <elaurent@google.com>2009-12-14 03:45:41 -0800
committerEric Laurent <elaurent@google.com>2009-12-14 03:45:41 -0800
commitda4cc34308d65730c404b669926a92e37b378555 (patch)
treef6b554ebc694a89a7cc4bdce29ec1ba639e96074 /docs/html/resources/tutorials
parent54bb575e85d1e40efbfbb868f37553cdd8ed318f (diff)
downloadframeworks_base-da4cc34308d65730c404b669926a92e37b378555.zip
frameworks_base-da4cc34308d65730c404b669926a92e37b378555.tar.gz
frameworks_base-da4cc34308d65730c404b669926a92e37b378555.tar.bz2
Fix issue 2324029: In-call (and other) audio screwed up after using Pandora (ERD72).
The problem is due to spurious headset connection indications received from event observer when a 3.5mm headset w/o mic is connected. In this particular case, The HeadsetObserver first received a valid indication of headset with mic connection, followed by a headset with mic disconnection and finally a headset w/o mic connection. The HeadsetObserver delays the headset disconnection intent to leave time to music app to pause music before the output path is switched. As the last headset w/o mic connection indication is received from the event observer before the intent corresponding to the spurious headset with mic disconnection is broadcast, the later is discarded. Results a state where the headset with mic is always considered as connected. The fix consists in not canceling pending intents when a new headset state is received and carrying the HeadsetObserver state with the delayed message triggering the broacast of the disconnection intent.
Diffstat (limited to 'docs/html/resources/tutorials')
0 files changed, 0 insertions, 0 deletions