Android app constantly freezes / crashes with update 9.0.1 update.

Anyhow, the amount of complaints would have been overwhelming if lots of customers were affected by a constantly freezing/crashing Controller app.

Anyhow, the amount of complaints would have been overwhelming if lots of customers were affected by a constantly freezing/crashing Controller app.

Again that is a wrong and dangerous assumption to make. When dealing with very complex systems such as this, there are so many different permutations of hardware and software options (not to mention network options) that you can’t just say that it would affect lots of customers. Anyone who’s ever worked in proper development or support should know that :)

Please note that I’m not saying categorically that there is a bug freezing the app, I’m just pointing out that there could be and people just blindly trying to deny that Sonos ever has problems can do more damage than good. People may rip their networks apart thinking the problem is with their hardware when in fact it isn’t.

Please note that I’m not saying categorically that there is a bug freezing the app, I’m just pointing out that there could be and people just blindly trying to deny that Sonos ever has problems can do more damage than good. People may rip their networks apart thinking the problem is with their hardware when in fact it isn’t.
I don't deny anything – I'm not with Sonos, I'm just a customer like you are. But I have been an active member for two long years now, mainly on the German board though, and I'm a keen observer.

I came across a system where a wired computer's Internet connection was running about half of the expected speed. There were no reliability issues, but it was perplexing. Eventually, I discovered that a construction project had damaged a network wire to a switch. Since there was a SONOS unit also attached to that switch, the SONOS unit was sharing its SonosNet connectivity with the switch. SonosNet is not as fast as a wired connection.

In my own network I like to say that I don't have any issues, but there was a case a couple years ago that blindsided me. It seemed like an ancient NAS drive was finally showing EOL (End of Life) symptoms, but they were not the symptoms that I expected and they were intermittent. This couldn't be a network issue because I'm too smart for that, right? Finally, I swallowed my pride and checked the network in detail --- !! --- duplicate IP address. A couple weeks prior I had reconfigured the DHCP range slightly. Unfortunately, I forgot about a little palm sized gadget hidden away and rarely used. It was also the only device on my network that had a fixed IP address. As is the custom with Murphy's law, this device was now inside the DHCP range, using the IP address assigned to the NAS. Easy fix, injured pride.

I mention this only to point out that when in diagnostic mode, after one assumes the problem must be [...] or cannot be [...], one is likely to be blindsided. However, one should play the percentages. It's pointless to concentrate on the 0.001% probability first.

JohnG666, are you familiar with the [player-IP-address]:1400/support/review data? Pick through this, especially the Network Matrix at the bottom. Colored squares indicate SonosNet links. Make sure that everything is connected as you expect. BTW, this is a static display, refresh the page if you are attempting to follow a dynamic situation.

Your symptoms are consistent with communication problems.There is very little "chatter" between the controllers and the players. Controllers are on a notification list. If a controller misses a notice, for whatever reason, it will be out of sync with the system status.

Note that there is a rare SONOS player failure mode where the internal connection between the network switch and the main board fails. The switch works as far as the network is concerned, but the player is not wired. If this connection is intermittent, the player will tend to flap between wired and SonosNet or offline. (or, depending on your setup, WiFi might be thrown into the mix) This sort of failure can disturb the network.

By the way, are your Androids using WiFi or SonosNet?

It appears there is a software bug which is responsible for the problems I'm experiencing with the app opening up in the wrong zone.

It appears there is a software bug which is responsible for the problems I'm experiencing with the app opening up in the wrong zone.
Do you have a source for this?

It appears there is a software bug which is responsible for the problems I'm experiencing with the app opening up in the wrong zone.
Do you have a source for this?

An email from support about my ongoing issues.

I had a working android app then Sonos did some updates and so did android now it just freezes if it opens at all. I've reinstalled the app several times with no change. Sonos works fine from Windows laptop. Its the phone app/Sonos update combination that seems to be the problem so has anyone actually found a solution. Please don't tell me to change anything other than the app or Sonos as nothing else has been changed or stopped working so it is only these things that are the problem and I suspect it is the app since the android update.

Basically, that means you don't have a clue what Sonos is, muss less how it works.

In my case, downgrading to the 8.6 APK on my phone solved my issue.

If you're having trouble with the current release of the Android software, go to https://www.apkmirror.com/apk/sonos-inc/ and download one of the previous packages. I installed 8.6 which fixed my "network" problem (or lack thereof). I'm sorely tempted to go a few point releases earlier to when the first little bugs appeared.

Moderator note: Sonos does not endorse or encourage the use of the versions listed in link. Proceed at your own discretion. User assumes all risk of downloads from a third party. Also note that we will not support outdated versions of the Sonos application.