Skip to main content
Avid Contributor II
Mar 31, 2022 9:19 PM UTC
Answered

lock screen volume android 12

I know this question has been asked before but there doesn't seem to be a fix and it's the one major issue that will make me return the Sonos Amp. 

I'm using Google pixel 3a with android 12 and can't get the volume controls to work when the screen is locked. Tried everything the articles suggested.

Not sure if it's an android issue or Sonos but Sonos should consider adding small remotes for volume and play/pause. Can be a wifi remote not IR necessary so no need for added complexities and components. This will reduce dependence on iOS and Android.

 

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Corry P
Corry PAnswer
Sonos Staff
Apr 5, 2022 8:47 AM UTC

Hi @Migo33 

Thanks for your post!

We are aware of this issue related to Android 12 - we expect that this issue should be fixed with the release of Android 12L (launch occurring around spring 2022).

I hope this helps.
 

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

12 replies

Contributor I
Jun 21, 2022 11:48 PM UTC

Hi @100RNR 

I believe the information I posted above came straight from Google, and as far as I know, there hasn’t been more since. Google may have delayed the fix, for whatever reason. For an updated timescale on a resolution, I can only refer you to Google.

I would recommend first disabling and enabling the lock-screen option in the Sonos app, and also uninstalling and reinstalling the Sonos app, however, as these steps could convince the app the option is available in Android again.

Control Sonos from the Android lock screen

If you continue to have issues, please get in touch with our technical support team so we can investigate. Thanks.

 

Yes, I still have the problem.  I got in touch with Sonos technical support and they pin the blame on Google.

Fix your mess.

Translate
Ken_Griffiths
Jun 22, 2022 12:11 AM UTC

Yes, I still have the problem.  I got in touch with Sonos technical support and they pin the blame on Google.

Fix your mess.

If Google didn’t include the fix in their 12L update for whatever reason. It’s not Sonos’ mess to fix by all accounts - you should perhaps be bothering Google to fix it.

Google did say they were going to include it in 12L, but clearly that was not the case. That subsequent delay is not any fault on Sonos’ part.

If customers ‘badger’ Google to fix it, aswell as Sonos making the request from their end, it might help persuade Google to get it done sooner, rather than them keep moving it further down their own list of development priorities.

Translate