Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I am trying to get my DI to run through my car stereo. Can anyone recomend a 3.5 jack to RCA that works well with the DI?
Using a random old cable from a set of computer speakers, I experienced this issue plugging into my wife's Civic aux jack.
Just playing with the cable in the jack a little made it go away. It only happens when it "detects" a microphone (I'm assuming because it turns on a bunch of voice command type stuff automatically). You can tell when it does this, because the icon in the notification bar will show a full headset.
I just wiggled the connector a little bit until I got just the regular headphones icon in the notification area and it worked fine after that. She uses it pretty regularly in her car now and hasn't had a problem.
Perhaps adding some kind of software toggle for mic on/off would be the simple solution here, so the user can just override it if it happens to erroneously detect a mic plugged in.
Thanks for all the feedback. I will try a different cable and see if it works.
Please let HTC and Verizon know. The concept that "a different cable" is the solution is asinine.
Please let HTC and Verizon know. The concept that "a different cable" is the solution is asinine.
The grounding/electrical issue doesnt sound like something that can be fixed by a software patch, seems more like a hardware issue, and if so, I doubt they would come out and replace hundreds of thousands of phones since it seems like it happens to everyones. Best that would come out of it is improving it on the next model or edition.
Then again I could be wrong and it could be a software issue. Hmmm..I wonder.
Not necessarily. The fact that different cables demonstrate different behavior shows there is a good amount of wiggle room in the spec. When a new variable is added to a situation and a problem arises, that doesn't always mean it's that new variable's problem. Often the new variable is just exposing an existing problem that wasn't previously detected. This happens constantly in the software world. It's less common in hardware, as specs are usually more rigid, but it's not at all rare.
I'm not saying that's the case here, I'm just saying it's certainly possible. The cables exhibiting this issue could indeed be out of spec, but they've just gotten away with it because no popular device has been as "picky" in the past.
I have 4 different sets of headphones. ALL of them experience this problem. They range from $10 cheapos, to Apple earbuds, to a $100 Shure set. It's not a problem with the cable and Verizon/HTC need to be made aware.
Are you sure you don't have something preventing the cable from being inserted all the way?