PSA: 16 July Firmware Blocks v16.1 App

@press250 
Confirmed. 😣

Thanks @rosswells127 for that. The two of us have been Great Explorers of Doom today, amirite? 

@press250 Unfortunately, “Yes”. 😓

Hey @rosswells127, this post may kinda-sorta help you out of the latest snafu …

Running hardware 80.1-55014 (updated this morning). Android app 80.04.05 (updated 1st July)

Can confirm that loading any content from library just shuts my app down immediately I play the loaded content, so that’s conclusive enough for me.

Noticed on 16.2 Windows controller that that the ability to update library has been greyed again (they did that with 16.1 a while back), and they want you to update the app (to 16.3 I’m concluding) had a quick look at Macbook and it’s the same story there. No chance I’ll update until the app behaves better.

Android app still has blank swimming lozenges after showing Recents/Favs for about 5 secs.

Using Hi-Fi cast from Phone for Library/Amazon app via Sonos for some playlists created there and Desktop for Sonos playlists if I am so inclined. What a Fred Karnos! 

Hi @B33Jay, if you’ve already succumbed to  the v16.3 (build 80.1-55014) firmware you might as well install the latest v16.3 Windows desktop app. That version re-enables Update Music Library Now. The only PITA element that I found was a tiny bit of nagging to perform a system update, but we’ve established you’ve already taken that plunge. YMMV, natch.

Yep me too.

I went to my cottage today, and those devices were on auto update.

I saw the 'update required' in 16.1, and figured it might be new device firmware.  So I fired up my old phone which has the new app. It (unsurprisingly) reported no system found.  Then I wiped the cache for the app and started it up again.  Join system etc... and when it finally worked It reported that devices were up to date.

But no dice with the 16.1 android app any more.

I used to be pretty unemotional about all this since I could fall back to the 16.1 app until the new app was fixed.  I already feel my aggravation rising.

Sadly I’ve run the update of the Desktop controller and can’t use the S2 app now. Wish I’d ignored the update option - it’s been fine before now.

Out of interest has anyone tried to roll this back and/or factory reset speakers to see if the older version works? I’ve spent too many hours on this now and have lost the will to do it again, I’m assuming also that tech support are useless too… 

This is beyond a joke now, wonder if there might be users who’re considering legal action against these shysters, they damn well deserve it!

About that. Would anyone know what the MuseTransportError$TimeOut errors are - are those because of the network or is it the Android/Sonos app somehow losing those UI entries?

I checked with (adb) logcat -b all >log.txt on a Samsung Android phone because after almost exactly after 10 seconds from the Sonos app UI finishing showing the home screen entries ok, the Recents/Sonos Favorites turn exactly like that.

I have 8 Sonos Favorites showing in the new app. Those are Sonos Radio stations. I used to also have 7 older TuneIn custom URL stations - the new app doesn’t show these. One of those stations is now also in Sonos Radio. I’m fairly sure these entries cause the Android app to lose the content after initially showing them. iPad app has no problems showing the 8 those so it’d be odd if these were network issues. iPad app also doesn’t show the 7 old ones but it doesn’t seem to mind them either. The 16.1 sonos app shows those older ones as well.

Since the iPad app can show content correctly this seems an error either the new Sonos app or something caused by Android.

I can see this in the log. I’ve cut the text here a bit:

Home screen shows Recents/Sonos Favorites ok after this entry:

07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: <-- 200 OK https://api.ws.sonos.com/content/api/v2/households/…./%2Fstations%2FSONOS_FAVORITES/browse?muse2=true&defaults=...ZX0 (4ms)
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: Content-Type: application/json
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: Content-Length: 9975
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: Cache-Control: max-age=300, must-revalidate
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: Vary: Authorization, Accept-Language
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: X-Response-Time: 1273ms
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: Date: Thu, 04 Jul 2024 19:38:11 GMT
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: Connection: keep-alive
07-04 22:38:11.501 26713 26844 I okhttp.OkHttpClient: <-- END HTTP

The certain home screen entries then change to those swimming lozenges after 10 seconds.

There are then four similar entries in the Android log - below is one example entry. It looks there are 6 sources - could these be the 6 TuneIn stations (one of the 7 now also being a Sonos Radio so maybe that’s why there is just 6 sources).

// Potential Home screen error where icons are greyed out, 10s timeout?
07-04 22:38:21.121 26713 26758 W System.err: com.sonos.sdk.musetransport.MuseTransportError$TimedOut
07-04 22:38:21.121 26713 26758 W System.err:     at com.sonos.sdk.musetransport.PersistentConnectionImpl$ResponseDispatcher$insertDemand$1$1.invokeSuspend(Unknown Source:60)
07-04 22:38:21.121 26713 26758 W System.err:     at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:8)
07-04 22:38:21.121 26713 26758 W System.err:     at kotlinx.coroutines.DispatchedTask.run(Unknown Source:115)
07-04 22:38:21.121 26713 26758 W System.err:     at com.google.android.gms.tasks.zzo.run(Unknown Source:28)
07-04 22:38:21.121 26713 26758 W System.err:     at kotlinx.coroutines.scheduling.TaskImpl.run(Unknown Source:2)
07-04 22:38:21.121 26713 26758 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(Unknown Source:98)

Then there are 4 cancellation entries for the above: 

07-04 22:38:21.130 26713 26775 W System.err: kotlinx.coroutines.JobCancellationException: Parent job is Cancelling; job=DeferredCoroutine{Cancelling}@c3ed996
 

@kpr Did you open a (free) account with TuneIn and have you deed this account as a music service to Sonos?

Many thanks, that was the reason! I’d read about that need to change to TuneIn (New) but my brain didn’t make the connection. I created the free account, added TuneIn (New) service and now the Recently Played and Sonos Favorites sections do not lose content.

In the Android log I no longer see errors and all are OK requests.

Interesting, not a 'technical' so don't know whether this is a clue - since update to 80.1-55014 two days ago I am seeing in Sonos Favorites some favourite radio stations from ages ago, I'd guess loaded back before S2 app and deleted long since and even before I even had android phone ( showing greyed out).

My wife and I received the same notification about updating in the app yesterday.  We had been holding off on doing so and sticking with 16.1 for as long as possible because of all of the complaints.  For what it’s worth, when we did the update we had zero issues.  No problems with finding speakers or zones in our system (we have over 20 Sonos products across 8 zones in the house), Trueplay, volume controls, speaker groupings or losing any of our pre existing favorites thankfully.   
 

Admittedly we never had a local library (everything was streaming only) and we’re iOS users rather than Android, so I’m sure that helped.  
 

My wife summarized it best:  “The old app was crappy and the new app seems kind of crappy too, so I don’t think I’ll notice either way.”

Me too. 

I managed to find and install a previous version of the desktop app, but sadly the speakers all have the new build on them. No idea how I can roll back the speaker version though 😡

I’ve installed the new app on an old android phone and it is truly shocking. And 1 thing I notice from all the ‘we are going to fix’ updates is there seems no mention of the widgets. For me, they were 1 of the better features… Very sad 😓 

I can confirm that the firmware update is blocking me from using the version 16.1 as well. 

Is anyone able to even open the “new” app anymore?  Two days ago I tried using it, and it would occasionally crash.  Yesterday, I found that I couldn’t even open it anymore… just gives me the “app not responding” and offers “info” or “close app” options.  That’s what prompted me to try the old version 16.1, but I guess due to firmware update, that is now blocked as well.  So, at this point, I have to go turn on my laptop and use the windows app to do anything with Sonos. 

Are there any decent alternate apps out there?  I don’t need anything that fancy… select speakers, add songs or a playlist from my own library, control volume, play/pause, etc.  I’m surprised a company as large as Sonos can’t seem do that effectively.  (I’m on Anroid - Google Pixel 6a.  See my original post for more details and my recent issue… which are now moot since I can’t even open the app.) 

Same problem. Identical Motorola G7s running Android 11. Frozen splash screen culminating with “App not responding”. I get cancel or wait options. Selecting the wait option will normally allow the app to open. It will find the system and my services but is compromised. Volume slider does not function correctly. Uninstalled and reverted to 16.1 from a mirror. It was an improvement in that it actually opened and found the system but an unimprovement in that everything on the content part of the app were greyed out lozenges with the omnipresent “Upgrade Required” message at the top. System is essentially bricked. Can’t run on desktop, Win 7 seems to have broke S2. Can’t run on iPad, my device is too old to support the minimum required iOs. Can’t run on Android. Game, Set, Match.

Back in the early days Sonos came with a dedicated controller, man that would be handy here.

Sooo...Start buying devices until I get some that will run this dog or wait for some period until they manage to produce a viable application?

I’m intrigued to know if Noson still works with the new firmware - but I’m not so curious that I’m going to let my system upgrade to find out!

But… if there are any other Linux users reading this thread (and have upgraded to latest firmware) then it would be interesting to hear from them...

Hi @Antifon, fwiw SonoPhone/Pad work with the v16.3 firmware. 

TBH, I’m surprised. Perhaps there is hope (for me) that I can cut my system free from Sonos and continue to run it on current firmware forever!

I think I could live with that, provided Sonos don’t decide to enforce firmware updates in some way...

Yeah, @Antifon, so far Sonos is only enforcing firmware updates on their own apps. Last week the v16.2 Windows desktop app insisted (most functions grayed out) on a system update to the v16.3 firmware … and said firmware killed the widely beloved v16.1 Android app.

The desktop apps and all third-party apps continue to use the old APIs to communicate with Sonos devices. When some future firmware drop removes the old APIs … ouch.

For me, a very convincing reason to never again allow my system to update itself.