Skip to main content
Answered

Move 2: Missing AAC Codecs after January 2025 Firmware upgrade?

  • January 29, 2025
  • 7 replies
  • 216 views

Kanjandre
Forum|alt.badge.img

I just upgraded my Move 2 and I only got SBC codecs left. What went wrong?

Best answer by Kanjandre

I updated that software and now all is fine: AAC is back as viable option!

Thanks for bearing with me in this :)

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.

7 replies

Corry P
Forum|alt.badge.img+19
  • Sonos Staff
  • January 30, 2025

Hi ​@Kanjandre 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with the AAC codec not being offered for use with your Bluetooth connection to your Move 2 (note that Move 2 does not support AptX).

How are you determining this please? Can you provide a screenshot? Thanks.

I don’t have a Move 2 to test with, but I just connected to my Arc Ultra and am offered both SBC and AAC - it should be the same with the Move 2.

Can you please try rebooting the device hosting the Bluetooth connection, and the Move 2 speaker? Thanks.

Sonos Move and Move 2

  • Take your Move product off of the charging base.
  • Hold the Power button for at least 5 seconds, or until the status light turns off.
  • Wait 10 seconds.
  • Press the Power button or place your Move product back onto its charging base.
  • Wait for the white light to stop flashing

I hope this helps.


Kanjandre
Forum|alt.badge.img
  • Author
  • Contributor II
  • January 30, 2025

Thanks for the welcoming greetings!
I used to be able to choose between SBC and AAC…

Here my screenshot: 

 


Corry P
Forum|alt.badge.img+19
  • Sonos Staff
  • January 30, 2025

Hi ​@Kanjandre 

Thanks for the screenshot!

Are you using Windows 10 or Windows 11? According to https://www.bluetoothgoodies.com/a2dp/, Windows 11 already supports both SBC and AAC, and Move 2 does not support AptX, so if you are on Windows 11, I don’t think there is any advantage to using alternate Bluetooth drivers - do you still have this issue if not using the Alternative A2DP Driver? I can only assume we do not support it. Having said that, I don’t know how to ask Windows which codec is in use, though I did find this Reddit post: https://www.reddit.com/r/windows/comments/13ihgic/how_can_i_see_which_bluetooth_codec_is_used_on/?rdt=44962 which takes us back to https://www.bluetoothgoodies.com/tweaker/ and a different tool from that same company. 

Can you please test from a device other than your Windows machine? If you have Android, you can enable Developer options which opens an extra settings menu which will contain a Bluetooth Codec selection screen (better to search than to scroll - it takes a while). iOS seems to be fairly similar, from what I can gather. You can search for how to enable Developer options for your device, but please know that you do so at your own risk - though I did so on my Samsung phone without issue. The same goes for using third-party software.

I heard back from a colleague - we are not aware of any changes made to Move 2’s supported codecs.

I hope this helps.


Kanjandre
Forum|alt.badge.img
  • Author
  • Contributor II
  • January 30, 2025

I´m on Win11.

Actually, that´s the same company that made the app I´m using: “If you are interested in SBC CODEC optimization, you may also want to check Alternative A2DP Driver.
 

And it used to work: I could select AAC over SBC… just until few days ago!


On my phone it looks differently, working as per usual:

on Android

 


Corry P
Forum|alt.badge.img+19
  • Sonos Staff
  • January 30, 2025

Hi ​@Kanjandre 

Thanks for trying another device - as that offers AAC and SBC as it is supposed to, I can only presume that the issue is with the non-standard driver you are using on your Windows machine. As a result, I can only recommend that you remove it.

I hope this helps.


Kanjandre
Forum|alt.badge.img
  • Author
  • Contributor II
  • Answer
  • February 9, 2025

I updated that software and now all is fine: AAC is back as viable option!

Thanks for bearing with me in this :)


Corry P
Forum|alt.badge.img+19
  • Sonos Staff
  • February 10, 2025

Hi ​@Kanjandre 

Thanks great to hear! Thanks for updating the thread!