<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Report events about volume change" href="https://bugs.freedesktop.org/show_bug.cgi?id=42445#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Report events about volume change" href="https://bugs.freedesktop.org/show_bug.cgi?id=42445">bug 42445</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>There are two separate problems for the two bluetooth profiles. The original report seemed to be about problem 1, but I think you're talking about the second problem in <a href="show_bug.cgi?id=42445#c2">comment 2</a>. 1) If the user changes the headset volume in the HSP mode, PulseAudio will send a notification about changed sink volume, but a client implementing an OSD doesn't know whether it should show a notification or not. This is solvable by sending more informative notifications. 2) If the user changes the headset volume in the A2DP mode, PulseAudio doesn't know that the headset volume changed. With A2DP there are two volume controls that affect the final volume: the volume that PulseAudio applies, and the volume that the headset applies. This is bad user experience, but at least in the past bluetooth simply didn't provide a way to sync the two volumes. I think newer bluetooth versions have added the necessary functionality, but it hasn't been implemented in PulseAudio.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>