Audio management in Android Enterprise

Rakib
Level 2.0: Eclair

From the feature list in Android Enterprise from https://developers.google.com/android/work/requirements#4.25.-system-audio-management_1,

 

I want to discuss the feature 4.25.2. IT admins can prevent users from modifying device volume settings (go to adjustVolumeDisabled). This also mutes the devices.

In theory a very good feature, in certain areas when you want to block users from either changing the volume to silent or the other way. Our goal was to use with Samsung Service Plugin where you can set the default volume, but since blocking the volume buttons on the phone, you are also stuck with a mute device. So my feature request would be to have the feature without muting the device.

3 REPLIES 3

Moombas
Level 4.0: Ice Cream Sandwich

(Regarding API, not Knox:)

I fully agree to this request as those are different things to be set:

- Volume set to a certain level

...and...

- do not allow the user to change it

So, if we want a muted device we would set the default volume to 0 and block the buttons, otherwise using a different default volume. So, i would have stumbled on this to be honest myself as this would have been unexpected behavior from my personal understanding of just blocking the adjustment of the volume.

Michel
Level 2.2: Froyo

I also agree with this request and have raised a feature request at Samsung for this but it hasn't been implemented yet (not even on the roadmap). 

 

@Rakib ,  Setting the default volume with KSP does not prevent a user to change it. As you are aware so it seems. But in KSP, there is also this feature I noticed recently. I haven't been able to test it yet but it might be worth a shot. 

 

1) Set default volume levels with KSP 

2) block media buttons in deep settings:

Michel_0-1731569346689.png

 

https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/configure-advanc...

 

 

Rakib
Level 2.0: Eclair

I have also talked with samsung, but I think this something that should be solved by Google, they are so close already and this should be vendor agnostic.

It would be nice if someone from Google also could comment here. 

 

@Lizzie