trueplay for Android?

I had read the thread - my reply still stands.

Try understanding the words then, your reply is nonsense. The reason they haven't done android yet is clearly explained. If anything the figures you quote reinforces the reason why android is so difficult.

reading comprehension issues

market share because of so many manufacturer devices instead of just one.

no trueplay because of so many manufacturer devices instead of just one.

They go hand in hand.

Yes LHC , I understand the issue of the varying devices. Somewhere there is a solution. But my decision would have been to get people working on the largest market share first by concentrating on just those Android devices that met their requirements for commonality.

Total world Iphones: 151 million units - Total world Samsung Android phones : 300 million units,- Other Android manufacturers: 460 million units. I understand where you are coming from.

This is just MHO

Sonos even said they tried to support at least a single manufacturer like Samsung ... but even then even on the same model phone they found variances in the microphone.

It seems the only solution non-ios is going to require a microphone (a plug in one or using built in one like in the new Play:5).

Why do I think if bestday were an iDevice owner, his "decision" would be to get the easiest implementation out to the public first, and work on the hard one later? Just a hunch.

I think that there would be significant market push back if there was a cost associated with an Android solution. Market research would be required to sort this out. When the CR200 was on the market there were numerous outraged voices shouting all sorts of nasty comments about being forced to purchase a high priced controller when their iDevice was already sitting in their pocket. In this context the controller is "free". I doubt if SONOS could have charged a small fee for their controller App without incurring market push back.

I know many customers would gladly accept a cost for a microphone accessory, but I don't know the fractions.

There are a couple options to explore:

First, it may be possible to use an existing PLAY:x to calibrate the Android microphone. However, one would need to exercise great care when positioning the Android microphone relative to the PLAY:x. This may turn out to be too "complicated" for the average user. In addition to researching the technical details, one would need some market research about the "complicated" part.

Second, the new PLAY:5 includes two microphones. This opens the possibility of using a PLAY:5 to calibrate an Android microphone or using a PLAY:5 to calibrate other PLAY:x units. Again, there are some "complicated" aspects with this approach.

Third (bonus option), dealers could provide a calibrating service for Android devices. The dealer would strap the Android device into a jig and develop a custom calibration curve for the specific customer owned device. I don't know if dealers would welcome this opportunity or grumble about the extra work -- and someone must foot the cost of the jig. I'm not sure how a Best Buy, TARGET, or web store could fit into this scheme. Actually, a very inexpensive jig (possibly 3D printed -- at home) and a new PLAY:5 could be strapped together to build a calibration facility.

Yes, as I've pointed out several times, ELAC has done it by first having the user calibrate the phone's mic by placing it in the near field while test tones are played. Simple enough for a sub, but might be a more complex process for full range speakers, requiring the customer to move the phone nearer to the mids, then the tweeters, etc.

Just have a Sonos "Trueplay" tuning party. Don't bring a bottle - bring an IOS device. Get all your Plays tuned AND have a party

I can accept the reasoning that there are too many Android devices to make the True Play run the way they want. Makes sense.

However, what doesn't make sense is that there is "no" Android devices supported. No one is expecting Sonos to come out with a new feature and support a wild amount of devices.

It would make far more sense, if they released True Play for the select top tier Android phones on the market (which probably number around the same, as all of the iDevices currently supported). This is the same as the PC market, where you need a certain level of hardware to run certain programs. Some is supported, some is not.

I can accept the reasoning that there are too many Android devices to make the True Play run the way they want. Makes sense.

However, what doesn't make sense is that there is "no" Android devices supported. No one is expecting Sonos to come out with a new feature and support a wild amount of devices.

It would make far more sense, if they released True Play for the select top tier Android phones on the market (which probably number around the same, as all of the iDevices currently supported). This is the same as the PC market, where you need a certain level of hardware to run certain programs. Some is supported, some is not.

If you actually read the responses you'd know that even on a single model of android phone there can be any number of different microphones used, the android manufacturers don't standardize on type, they just use whatever they can get their hands on.