Skip to main content
Hi, I never had any issue with true play before, but yesterday I purchased a second play5 gen2 in order to create a surround with my first play5 gen2 and combined with a playbase. After maybe 10 trials I have still the same issue with trueplay. It’s coming up with the following message: cover more of your room, you’re not walking around enough, please walk all around your room, both close to your speaker and further away. Unfortunately I tried walking everywhere, and I tried with both speakers horizontal and vertical. Restarting my iPhone. Can anyone help me please?
Hey there, Francois B. Trueplay is mainly focused on your iOS device and the internal microphone, not the Sonos speakers themselves. The error you describe seems like it's getting a lot of the same readings and is unable to determine any changes while you walk around the room. Be sure to remove any cases on the iOS device and ensure you are holding the iOS device properly.



Alternatively, is it possible to try another iOS device to Trueplay?
Hi Keith, thanks for your answer, no case was used on my phone and I was holding the phone correctly. After posting the previous message I decided to retune the play 1 in my kitchen which was already tuned using trueplay before. Surprisingly I had the exact same message, so now, like you,I think that issue is coming from the iOS device I’m using. It has the very last update, so I will wait for my wife to come back from work to try with her iPhone.
Finally worked with my wife’s iPhone 🙂
There was someone who posted about 6 months ago who finally determined that it was the microphone on the iOS device that was being used that was blocked. As I recall, it used a separate microphone than the one you would normally use for voice. They were able to take it to the local Apple store where they discovered the mic hole being blocked.



Just looked at my iPhone, it's different than that original device from 6 months ago, but it's something to be considered, at the very least. Which is probably why Keith suggested the potential issue with a case, which might possibly block/obscure correct access to the mic in use.