Connect:AMP keeps cutting out...all components hardwired

Curious that this failing flash memory issue is not surfacing in Connect Amps running in S1? Or is it just going unreported?

I read that Staff post differently here and that @Corry P was just referring to this users specific Connect Amp, rather than every device out there. Stating that any forthcoming fix might not resolve their own reported issue, as it appears the device has memory locations that are perhaps ‘already’ marked internally as being unusable. This can apply to S1 or S2 updates, was my thinking - In fact I wonder if the S1/S2 downgrade process might in fact make things even worse with such devices, as I guess that can ‘perhaps’ put additional demand on a devices memory🤔? 

Hi, I appreciate you being up front about this.  But specific hardware failures aside (and this would not be the case for everyone), I don’t see how anything other than restoring the level of  reliability present before your software update would be acceptable here.  If Sonos pushed this update, you are responsible.  I have 3 Connect:Amps that you rendered unreliable.  
Rather than clarify your answer has increased doubts that a viable fix is forthcoming.  Sorry, this not good enough. 
 

andrew 

All muddy water to us on the outside. And while a serious issue for individual users, I would think that the total number of affected Connect Amps - the ones that could and were taken to S2 - is small compared to say play 1 units. I remember reading somewhere that play 3 and play 1 units are also in line to suffer the same issue with S2, and if so it will be a much bigger problem given the numbers of those units out there as compared to Connect Amps. Makes me glad that I stuck to S1 with units whose hardware was meant for S1; and nothing really changes now in S1 for months on end and when it does, it is probably minor tweaks. Reading all these has made me decide to not apply even S1 updates to my 12 Sonos units going forward; I don’t think that the risk of being exposed to new security issues is large enough to risk breaking the units by the next S1 upgrade. Let sleeping dogs lie!

Hi @Kumar 

You seem to be confusing two completely separate issues with each other.

The failed flash memory issue predominantly affects older components that are S1-only devices.

Hi @Andrew-s 

You also seem to confusing the two issues that have the same symptoms, rather like @Kumar. I gather your 3 Connect:Amps have been affected more recently? In that case - though I cannot verify without diagnostics - it seems likely to me that, in your case, a fix will be coming soon. The same cannot be said as confidently for @Gerald Harmon, however (whose diagnostics I have seen) as he is affected by a completely different issue. Technically, this makes you off-topic for this thread, but understandably so.

I hope this helps.

Corry,  you seem not to have understood Kumar’s point.

His suggesting that it is somewhat suspicious that Connect:Amp users running S2 are likely being pointed to failing memory as the cause of their issues, as opposed to the update you pushed last year, thus conveniently removing yourselves from any blame.  The number of users with this issue *could* point to many many Connect:Amps suffering memory failure around the same time, but this is unlikely.  It is more likely to be due to your firmware update.  

I would have thought his point was obvious. 
Andrew 
 

I must have erred in thinking that the Gerald issues were in an S2 environment. But your last sentence quoted makes it doubly clear to me that I should shut down all future S1 updates for my system. I don’t want to expose my two Connect Amps that work perfectly, to any S1 update change driven exposure in future. Or any of my other ten units including play 1 units and early years Sub, to such.

Hi @Kumar 

S2 is in use. I did emphasise “predominantly” for a reason.

Hi @Gerald Harmon 

Apologies - there was in fact a Service Pack release for S2 last week (on the 24th), but a typo led me to believe otherwise. I can’t find any information on what it addressed, but as a Service Pack, it would not have been a great deal.