“As of late 2015 there are two versions of the QC 25. Is the only difference between the two versions, the cord? Can I buy a Samsung Cable for optimum compatibility with Samsung phones and I buy IOS Cable for optimum compatibility with Apple Phones.?”
Answer This Question
1-4 of 4 Answers
The product is the same it just depends on which type of devices you prefer to connect it to. Honestly you can use either or. It just wont let you change volumes via in-line remote but it will let you pause/resume your music via in-line remote. On the downside your mic might work or might not it all depends on how old your device is and which brand half the times
Sorry, there was a problem. Please try again later.That's my understanding, and what I'm planning to do. I have an iPhone issued to me by work, and my personal phone is a Samsung. I didn't realize until it was too late that there were two versions and I had gotten the iPhone version of the QC25. I looked into it and I can buy the Samsung compatible cord directly from Bose, so I'm going to be doing that. That way I'll have both cords. The iPhone cord works with my Samsung to hear, fine, but the button functions don't, except "pause".
Sorry, there was a problem. Please try again later.Your instincts are correct here. The only difference is the cord. You can certainly buy the Apple or Samsung version of the headphones and then purchase the other cable to have functionality for the buttons and microphone on both types of phone.
Sorry, there was a problem. Please try again later.I don't know about changing the cord. That's beyond me. However, the comfort and build of these headphones are a lot better than the qc15. As you can see from the pictures, these are different from the qc15 in that these don't have that joint holding them together which was a bit fragile looking. These are more comfortable, the ear cups seem better made and a little more snazzy with the color and L/R inside them. If it was just about operating the phone with the cord I'd have stayed away.
Sorry, there was a problem. Please try again later.