1. 02 Dec, 2010 2 commits
  2. 01 Dec, 2010 3 commits
    • Eric Laurent's avatar
      Fix issue 2641884: Bluetooth volume is dependent on in call volume. · 831ad524
      Eric Laurent authored
      The problem is that the code in AudioPolicyManagerBase::checkAndSetVolume() that forces
      voice volume to max when setting bluetooth SCO volume is not called if the bluetooth stream
      volume did not actually change. So even if we re apply volumes when switching to bluetooth
      device, the voice volume is not changed in audio HAL and remains what it was when routed to earpiece.
      What makes things worse on Passion is that stream volumes are limited when connected to bluetooth
      and their actual value does not change as soon as they exceed the limit threshold.
      
      Change-Id: Ieb72a71e06e9b3079cc8bc76c78ce83e060a2ea2
      831ad524
    • Eric Laurent's avatar
      am 3cb64cb8: am 2f2db765: Fix issue 3142808. · f9e18848
      Eric Laurent authored
      * commit '3cb64cb8':
        Fix issue 3142808.
      f9e18848
    • Eric Laurent's avatar
      am 2f2db765: Fix issue 3142808. · 3cb64cb8
      Eric Laurent authored
      * commit '2f2db765':
        Fix issue 3142808.
      3cb64cb8
  3. 16 Nov, 2010 1 commit
  4. 04 Nov, 2010 1 commit
  5. 03 Nov, 2010 1 commit
    • Eric Laurent's avatar
      Fix issue 3142808. · 2f2db765
      Eric Laurent authored
      There is a bug in the way audio policy manager handles A2DP interface suspend/restore
      when SCO is used. This bug is not new but has been triggered by a change in the timing
      of the events received by audio policy manager when a call is setup and torn down
      introduced by commit 164a8f86c7e48992691368c4895709c3bdb835a4.
      
      The fix consists in grouping the control of A2DP suspended state in a single function
      that is called systematically when conditions affecting this state are changed:
      - call state change
      - device connection/disconnection
      - change in forced usage.
      
      Change-Id: Ib76a999513b5afbfd59ba945f8650d2a48d6f480
      2f2db765
  6. 20 Oct, 2010 1 commit
  7. 14 Sep, 2010 1 commit
  8. 09 Sep, 2010 2 commits
  9. 03 Sep, 2010 1 commit
  10. 30 Aug, 2010 2 commits
  11. 28 Aug, 2010 1 commit
    • Eric Laurent's avatar
      Fix issue 2952766. · d6e68c3a
      Eric Laurent authored
      The fix for issue 2952766 showed some unused code in
      AudioPolicyManagerBase::checkOutputForStrategy(): since commit
      eb8f850d0b7e53956e917fd9645f808c1a09bc88: there is no need
      to update the hardware output device as it will be updated when the
      new tracks are created by audioflinger.
      
      Change-Id: I2f46fab58a5db3b4cd03fdaeebd7d6603c8dbbdd
      d6e68c3a
  12. 18 Aug, 2010 2 commits
  13. 09 Aug, 2010 1 commit
  14. 27 Jul, 2010 1 commit
  15. 20 Jul, 2010 3 commits
  16. 01 Jul, 2010 3 commits
  17. 21 Jun, 2010 3 commits
  18. 15 Jun, 2010 1 commit
  19. 09 Jun, 2010 1 commit
  20. 25 May, 2010 1 commit
    • Eric Laurent's avatar
      Fix issue 2641884: Bluetooth volume is dependent on in call volume. · 564c3032
      Eric Laurent authored
      The problem is that the code in AudioPolicyManagerBase::checkAndSetVolume() that forces
      voice volume to max when setting bluetooth SCO volume is not called if the bluetooth stream
      volume did not actually change. So even if we re apply volumes when switching to bluetooth
      device, the voice volume is not changed in audio HAL and remains what it was when routed to earpiece.
      What makes things worse on Passion is that stream volumes are limited when connected to bluetooth
      and their actual value does not change as soon as they exceed the limit threshold.
      
      Change-Id: Ic6c54b4a7fd54983f445de9a9b5cd2ea0025155c
      564c3032
  21. 14 May, 2010 2 commits
  22. 08 Apr, 2010 3 commits
  23. 06 Apr, 2010 1 commit
  24. 05 Apr, 2010 2 commits