Sonos S2 App Update Issues : This May or May Not Help

FWIW @Draddy, I’ve poked and prodded the new architecture at the app level (performance profiling) and the network level (tracing, down to packet capture) so my comments in the posts above and elsewhere on these forums are not idle opinion. Bringing it back to the thesis of this thread—which started out constructively enough!—people can feel confident that:

• If their mobile/tablet meets the OS requirements to install the new Sonos app, it is perfectly capable of running the new app.
• If their Wi-Fi network is solid enough to reach all their Sonos gear, it is perfectly capable of running their Sonos system. Streaming even the high-res FLAC tunes needs less than 1mbps of bandwidth, a fraction of what basic video streaming pulls down.

Man I was burned by the s1 to s2 transition, and wanted to know what was coming for this update 

appreciate the work digging in!  That’s what’s so infuriating about the boot licking OP is doing.  It is unbelievable how powerful an old iPhone 10, or utility provide router, or basic high speed internet is.  
 

Even with GB+ internet, I’m rarely using more than 100mbps at a time.  

if a speaker company can’t produce software that modern hardware can run (could we agree that anything after an iPhone 8 is modern?)….they’ve got a problem.   Something is wrong with their architecture.  
 

and you’ve proved it according to what you’ve said.  It’s not device or network side that is the problem,    It’s the call outs to random APIs that is resulting in a s*** user experience.  

Moderator Note: Modified in accordance with the Community Code of Conduct.

What do you think about the change from SSDP to mDNS for device discovery? 
 

@Draddy

Here’s my video of volume control with new app. Even with the old app the volume slider was not “buttery smooth” as each speaker will have a slight delay/advance versus another. Some of the delay/advance difference is due to my finger as I didn’t want top move the slider too fast. However, you can see that the volume levels are within “one click” of each other for the most part.

Would love to hear press250s perspective.  I know that I had a terrible time with Sonos and igmp snooping/stun rules.  Maybe mDNS solves some of that? 

Appreciate the visual.  Yours is about as bad as mine.  So it’s potentially not hardware related since you have newer hardware than I do. I honestly feel like you should be annoyed as well based on that video. 
 

do you remember the s1 days? It was so smooth then.  I could actually fade down audio with the slider. Even looking at yours, you probably can’t fade down audio that smoothly either since it’s jumping 5-10 digits at a time for the fireplace which I’m assuming is an ARC. (And I mean like 50 to 15 in 3-5 seconds, not over 10+ seconds.)   

I will say that s2 pre facelift did operate more smoothly than you’re showing for me.   My master volume slider felt like it was connected to the speakers fairly directly.

let’s say you’re watching tv and you haven’t opened the app in ~30 minutes.  Do you also find that it opens as if it hasn’t been opened at all recently and takes 5-15 seconds to load your speakers and figure out which speakers are playing what before you can make an adjustment?

@Draddy

Nope. App loads as normal which is instantly if left running in the background. If the app is stopped and re-started it takes 2-3 seconds to load. I don’t see that as excessive…maybe you do 🤔. I really don’t have anything else to add to this thread.

As far as my video is concerned…Nope…I don’t feel annoyed and for you to suggest that I should is not your place. Furthermore, just because I have a positive experience by my way of thinking is not “boot licking”.  In any event why anything I say or write should “infuriate” you (or anyone who disagrees) is beyond me and childish on yours and their part.

I’m not willing to join your choir of dissatisfaction. If I have an issue I’ll handle it without your suggestions in my own manner.

Here’s an idea….start your own thread describing your issue, run a diagnostic within 10 minutes of the next occurrence, post the reference ID and later call Sonos Tech support to discuss the results.

Good luck to get your Sonos working as you like 👍 

Hard to say, @Draddy. FWIW, mDNS and igmp are both non-routable protocols that can be finicky. mDNS is better supported nowadays, so adopting it makes sense, I suppose.

let’s say you’re watching tv and you haven’t opened the app in ~30 minutes.  Do you also find that it opens as if it hasn’t been opened at all recently and takes 5-15 seconds to load your speakers and figure out which speakers are playing what before you can make an adjustment?

This feels like an “out and back over the internet” issue, as opposed to an “inside the app” issue. (I recognize that sentence isn’t helpful in your case.) Here’s an experiment for you, if you’re game: try using the Windows/Mac desktop client in parallel with the iOS client, performing the exact same things in both, and see how the behaviors compare. Hardly apples-to-apples, tho’ it could be insightful.

Been trying to figure out why I can't see my devices. Apparently setting any DNS to a manual number will make your Sonos not show up on airplay. Thanks for this fix. Now I get error code 1,000 & 1,105

I KNEW IT.  IT WAS SO OBVIOUS SONOS REDIRECTED ALL MY USAGE TO THEIR SERVERS FIRST.  THE APP IS UNUSABLE BECASUE OF THIS.  THERE IS NO REASON SONOS NEEDS TO SEND MY VOLUME AND DEVICE INFO BACK TO THERE SERVERS FIRST.  ITS ALSO OBVIOUSLY WHY IT WAS COMPLETELY UNUSABLE FOR THE $TH OF JULY SINCE EVERYONE IN THE US WAS PROBABLY USING IT AND THE SERVERS GOT OVERWHELMED.  WHAT MORON THOUGHT THAT WAS A GOOD IDEA?????  FIRE YOUR CPO - MAXIME NEEDS TO GO.