fix audio port ID generation for new AudioTrack and AudioRecord
commit 0f4b3c54 introduced a problem in audio port ID generation by audio policy manager when a new playback or record track is created: audio flinger was passing a random port ID to getOutputForAttr and getInputforAttr. This caused audio policy to confuse several record tracks and fail to process capture stop properly. Bug: 72628781 Test: manual camcorder tests Change-Id: I55e18e2e6ccb9f69c36372d9bf9becf85e7c2614
Loading
Please register or sign in to comment