RoMee
1000+ Head-Fier
- Joined
- Jun 30, 2012
- Posts
- 1,174
- Likes
- 123
It's been more than a month and my CFW2 is still awaiting shipment.... V-Moda is going downhill. They don't respond to email either.
It's been more than a month and my CFW2 is still awaiting shipment.... V-Moda is going downhill. They don't respond to email either.
It's been more than a month and my CFW2 is still awaiting shipment.... V-Moda is going downhill. They don't respond to email either.
Should had went with the beats studio 3 instead... Oh well, too late now.
That is a totally normal and expected behavior of Bluetooth headphones.I have a question to those who own the crossfade 2. My own set hisses when a sound is played and stops about 1 sec after sound i stoped, there is also delays in the sound when tapping in apps and such. Searched the thread but couldnt find much.
That is a totally normal and expected behavior of Bluetooth headphones.
My set had a loud hissing too, and I disagree that this is expected: save for the ATH-DSR7BT, none of the other BT headphones I've listened to have had a hiss that was remotely as loud as the Crossfade's. Some people here and on Amazon have mentioned that their units had no hiss at all, or that they exchanged their noisy units for new ones that were quiet, so I've sent mine in for an exchange as well. Will report back once I get the new one in. If it's also noisy, oh well: you can't hear it over anything except very clean piano music. Still annoying, though.That is a totally normal and expected behavior of Bluetooth headphones.
Maybe my ears aren't as sensitive as others, but i've never noticed any hissing in my CFW2.I have a question to those who own the crossfade 2. My own set hisses when a sound is played and stops about 1 sec after sound i stoped, there is also delays in the sound when tapping in apps and such. Searched the thread but couldnt find much.
So this pertains to the gen 1 CrossFades, has anyone had the entire ear cup pop of the hinges? Mine did yesterday and am curious if this will turn into a constant issue now that it happened once