Volume buttons keep controling Bluesound volume

Answered

Marthijn Ketelaar

• July 02, 2020 15:41
• Edited

I have a samsung  phone with android 10. The problem is that when I have openend the BluOs app the volume buttons from my phone keeps controlling the volume of the BluOs. When I close the BluOs app then there is a BluOs widget which I can not close, only when the music is paused then I can close the Widget. I don't want to pause because when I am listening to music  and want to do something else in the mean time with my phone then I have to pause the Music (BluOs) first to be able to control the volume of another app.

I know that I can force to close the widget in settings of my phone, but that can not be the standard.

 

Having more people in our house with the same problem (all android phones). Am I watching youtube on my phone and want to put the youtube volume up then BluOs volume goes up..

Please help.

 

 

2

• 

  Julie Berrow

  • April 19, 2024 11:16

  We have just bought a BlueNode and having exactly the problem outlined above, that the app stays on in the background and takes precedence over any other volume controls. I've just tried restricting the battery (see Onno above, 9 months ago), but it really would help if Bluos could solve this for Android. Just annoying!

  0
• 

  Sam R.

  • December 16, 2020 22:23

  Hello all, 

   

  In speaking with one of our Android developers, they have mentioned that this is how a the media widget work on Android -- similar to what other media apps do when media is actively playing outside the current context. When the volume controls are pressed that media widget takes precedence over other volume controls. The same occurs with examples such as Spotify playing via Spotify Connect on a Bluetooth device.

   

  That being said we have forwarded this to our QA Team for future review. 

   

  Regards,
  Sam R.

  -1
• 

  Tony W.

  Product Support Manager

  • July 04, 2023 12:31

  Hi Apoorvgoyal

  This cannot be resolved by BluOS Development as it appears to be an exception error in Android v12. In our Quality Assurance research, it is only affecting devices running Android 12. It does not happen in 13 on and in versions 11 and older.

  -3

Please sign in to leave a comment.