Bluetooth volume not changing

[mase76]

Hi!
The (bluetooth) media volume does not change. I have set up to change the media volume to full when connecting to my car stereo. However the profile is loaded. All permissions are set. My system is Omnirom 8.1.0.

[renyuneyun]

Thanks for reporting.
I'll fix this soon.

(Note to myself)
STREAM_BLUETOOTH is not documented, but Android is using 6 for it (see https://stackoverflow.com/questions/4472613/android-bluetooth-earpiece-volume ).

[renyuneyun]

This should have been solved in v0.5.7 (which should appear anytime on f-droid).

Feel free to reopen this issue if it's still there.

[mase76]

No, bt volume does not change here with 0.5.7.
Maybe a look into the app would help:
https://github.com/jroal/a2dpvolume
BT volume changing works there.

[renyuneyun]

Just to confirm: are you using (in the new version) the "bluetooth" volume meter?
It's a separate meter, added in v0.5.7

[mase76]

Yes, I noticed and use the bt volume meter.

[renyuneyun]

My fault...
I forgot to put the line which changes bluetooth volume...

I have fixed in the code, and the fix will appear in next release (v0.5.7.1 I think).

Anyway, thanks for reporting!

[mase76]

I installed 0.5.7.1. The bt volume does not change.

[renyuneyun]

They seem to be using the same one (and there is nothing to do with the new "bluetooth volume" I added in v0.5.7.1)...
Just to confirm: have you tried to treat "music volume" as bluetooth volume (when connected to bluetooth)?

[mase76]

Yes, I used bt volume, not music volume.

[renyuneyun]

Errrr, I mean that music stream is seen as Bluetooth volume (by Android) when Bluetooth device is connected. mase76 <notifications@github.com> 于 2018年5月5日周六 01:06写道：

…

Yes, I used bt volume, not music volume. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#83 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADJCG6odu2T9X-lQ9Sh-r74yTnezl6oYks5tvOzpgaJpZM4TQdpJ> .

[mase76]

I tried both. After connecting I see a volume dialog coming from Android, which sets the bt volume to half. I found no way to disable this. A2DPVolume also had problems in the past. But in this app you can add a delay until adjustment. After setting it to 6 seconds, it worked.

[renyuneyun]

Hmm, thanks for the info!

So the solution is simple adding a delay. That's why I don't see that since in my test I use "charge" as the trigger and bluetooth headset is always connected.

There are two solutions, but I'm not sure which one you (and/or other people) would prefer:

1. Keep only the "music" field, and tell the user they'll need to add a delay (which is possible in Easer, through chained events) if want to set bluetooth volume, and let them do that manually. This gives user more control, and is visible in the future (when a graph is used to show the relationship of those triggers).
2. Add a "bluetooth music" field, and silently wait for a few seconds (maybe configurable) to adjust the volume, and user is responsible to choose the correct one ("bluetooth music" or "music" [or both, but doesn't make sense]).

By the way, let me check: is "music" the only volume setting which will vary/change between bluetooth and non-bluetooth?

[mase76]

I would prefer the second. A delay of 6 seconds is the default in A2DPVol and works fine. When I connect a bt headset, Android or my ROM (Omnirom) sets bt volume to half. I don't know how to disable this. But Easer could override this by setting the volume 6 seconds later. Or you could make the delay configurable, maybe for all volume adjustments, because I don't know the behaviour when connecting wired headsets. Doing this with an event chain wouldn't look very nice.

[mase76]

With the delay option it works fine now.

[renyuneyun]

That's great.
Maybe this issue can be closed?

[mase76]

Yes, I think, it can be closed.
But I would suggest to add the delay option generally to the volume change, independent
from bluetooth. When the delay is not needed, it can be set to 0.

[renyuneyun]

Not sure if I understand you correctly: do you suggest to "move" the delay to the whole "volume" setting (in one Profile)?

[mase76]

Yes, so the delay can be set when needed, independent from the volume channel.

[renyuneyun]

Then I think it's better to chain a "delay"/"timer" event and set the volume there.

The reason why I prefer this way is because I'm planning to add a "visual graph" for the scripts (yes, the previously UI element called "event" is renamed to "script"), and the delay can be easily seen there.

[mase76]

But therefor the order of the elements in the chain must be changable.

[mase76]

I don't know what happened. Since a few days, the bt volume changes not to the prefered value. When I configure full volume, I get only about 60%. When I set half, I get only about 30%. The action itself works, including the delay.

[renyuneyun]

The order of elements are changeable, at least from what I understand. Maybe you are experiencing some problem related to the old unclear semantics (of Event/Scenario), but this should be solved when all suitable Events have been transferred to Conditions (,which is not yet happened, but is happening).

For the volume, I think this may be a result of using different metrics, and BT has a different "highest" value than non-BT volume. I think the only solution is to use percentage...

[mase76]

I did a fresh install of my rom. Now volume change works again as it should. For now...

[renyuneyun]

I'm closing this as the issue seems to be fixed.

Feel free to reopen it :)