So, this is my millionth time with this issue. basically the problem seems to be that my headphone jack thinks that my headphones are still plugged in. this leads to- no audio during calls without my headphones, no music without my headphones. ive had this problem with my last epic. i got sprint to replace that one because of the issue. now that ts back again on my new epic im concerned its no longer hardware failure and something wrong that im doing. possible problems could be- the headphones i use(they went through the wash once) ,mis-matching baseband/modem/kernel/rom... or perhaps too much wiping and flashing.
I am rooted with cwm3.1.0.1 and i recently applied the eh17.zip update but im still on ec05 baseband. ive been constantly switching roms between stockeh17, redbeast(ec05?) urban vendetta and regen and some starsky rom on eh17, desperately looking for one that actually works.
any advice or insight would be excellent. thanks guys.
Maybe your headphones are messing with your device. So try a different pair
Sent from my HD7 using XDA Windows Phone 7 App
Related
Has anyone found that their headphone adapter has stopped working for some reason?
Was working fine, and now seems that the phone no longer recognizes the adapter. Power passes through just fine - however, can't get audio out.
Please let me know if you have any suggestions? I don't have a spare adapter to test.
Thanks,
Chip
I'm afraid that is the test. Either use your headset on a different phone, or a different headset on your phone.
You should be able to test a headset at your local phone retailler (just tell them you want to check it works before you buy it)
I'm having the same problem, just not at your stage yet.
I have audio but it's obvious there are some connections that aren't quite lining up since I get mono out of both speakers now instead of stereo and moving the connector at all gives me the typical "short out" garble you hear when you've disrupted a short in an audio cable.
The only time anything is plugged into my phone is when it's laying flat on a desk (I even make sure the wire comes out straight with NO pressure on it at all). I've never forced the cable, had it in my pocket where it could have put pressure on the connection, or anything else that might have caused the problem...
I think it's just wear. I can still charge the phone just fine, it's just audio that is screwed up now. I'm just waiting for the day when I don't hear anything...
...and I'll probably never buy HTC again... since this happened with my Star Trek too.
Beeble said:
I'm afraid that is the test. Either use your headset on a different phone, or a different headset on your phone.
You should be able to test a headset at your local phone retailler (just tell them you want to check it works before you buy it)
Click to expand...
Click to collapse
So I went to the AT&T store - a headset worked fine.
I went out and bought a new headphone adapter - same thing, doesn't get recognized by the Phone, so still SOL.
Question - any idea of this could be software related? I had installed skype (uninstalled to see if this was the cause) and wondering if that did something to the headset settings.
Any value in reimaging with a new ROM to see if this fixes it before calling AT&T warranty?
Thanks,
chip
igolfchip said:
So I went to the AT&T store - a headset worked fine.
I went out and bought a new headphone adapter - same thing, doesn't get recognized by the Phone, so still SOL.
Question - any idea of this could be software related? I had installed skype (uninstalled to see if this was the cause) and wondering if that did something to the headset settings.
Any value in reimaging with a new ROM to see if this fixes it before calling AT&T warranty?
Thanks,
chip
Click to expand...
Click to collapse
If you have flashed cooked ROMs then you will have to flash back to stock for warranty reutrn anyway, so this could likely be your issue.
If you're on the stock ROM, then I would suspect hardware.
Bruce Inman said:
If you have flashed cooked ROMs then you will have to flash back to stock for warranty reutrn anyway, so this could likely be your issue.
If you're on the stock ROM, then I would suspect hardware.
Click to expand...
Click to collapse
Thanks Bruce - about to call AT&T warranty to get relief (within 1 year).
anyone out there can fix the issue when headset is plugged into 3.5 jack and a call comes in and you can just take the call instead of unplugging the headset?
Thanks,
I guess nobody is bothered by this.... strange
hackercity said:
anyone out there can fix the issue when headset is plugged into 3.5 jack and a call comes in and you can just take the call instead of unplugging the headset?
Thanks,
Click to expand...
Click to collapse
Every phone I've had since the iPhone has done this.
craighwk said:
Every phone I've had since the iPhone has done this.
Click to expand...
Click to collapse
my og droid and droid 2 and incredible did not do this. I was able to take the call with an aux cable plugged in. The mic would work and I was able to use my phone over my car speakers. The thunderbolt disables the mic if the aux cable is not 4 pole, as in has a mic. The only solution I have found is to buy http://cgi.ebay.com/ws/eBayISAPI.dl...49206&ssPageName=STRK:MEWNX:IT#ht_2617wt_1141
I used this in both my cars with the thunderbolt and it works perfectly.
Is this something that can be fixed by the ROM/Kernel developers?
Here's a fix!
Okay guys so here's a work around that I've been using for a while and I don't really remember where I saw it so I'm sorry for not giving proper credit. So you go to Home>Settings>Call>TTY mode> and pick "TTY VCO". The only negative thing is that you're gonna have a few extra icons up there in the notification bar but you get used to them right away.
Does that disable the ability to change in-call volume?
No issue here on Das Bamf Remix 1.7
I've been running Das Bamf Remix and since a few versions ago (1.6 I believe) I have not noticed this issue -- calls work fine with headphones.
I'm pretty damn sure this was fixed, or supposed to be fixed with MR1. Ever since I upgraded to an MR1 based ROM, the issue went away for me. It also fixed video chat. The issue is related to something software based with having 2 noise cancelling mics. Basically, they were cancelling each other out.
Can anyone PM me on how to get needed software to root plz? If asked a few with no responses. Tried one click option but cannot get galaxysense Rom because link 404's
Sent from my ADR6400L using XDA App
ZuneNinja! said:
I'm pretty damn sure this was fixed, or supposed to be fixed with MR1. Ever since I upgraded to an MR1 based ROM, the issue went away for me. It also fixed video chat. The issue is related to something software based with having 2 noise cancelling mics. Basically, they were cancelling each other out.
Click to expand...
Click to collapse
I just tried this on bamf 2.0-5 and I still have the problem. The mic turns off when headphones are plugged in.
This has been addressed, but not thoroughly. It works sometimes, but not all the time and its very irritating when it doesn't work. Maybe when the June 30th update comes in. That's wishful thinking though. My dinc, iphone, droid, all the way back to my touch pro had this functionality.
This has been strange for me to and I posted about it in the bamf kernel thread. Some headphone mics work and some don't. The same mic that doesn't work on my phone works on other non htc phones.
Sent from my Xoom using XDA Premium App
I've run stock, rooted, Das BAMF 1.4 - 2.0.5, and preview4. Every single one cuts off the mic if I have headphones in. Very frustrating. I took to buying headsets with built-in mic. Unfortunately, they all seem to last about 3-4 weeks before going bad and randomly hitting play/next/back on my audio book app. I've gone back to standard headphones and would LOVE to be able to leave them in and use the built-in mic.
I've been having bluetooth problems with this phone since day 1 & I'm wondering if it's just my phone or if anyone else is having the same experience. No matter what rom or headset I use, I get a craptastic connection. I don't have any problems pairing devices, but I can't get 10 feet away from the phone without it disconnecting and I can't even turn my head without the audio cutting out. It also randomly disconnects for no reason & sometimes won't reconnect until I reboot. This has happened with every rom I've tried & every headset too. I've bought & returned multiple headsets thinking it was just my Blueant, but it happens with every one.
Could I have a faulty unit or does the bluetooth on this phone really suck this bad? I listen to podcasts & music all day long at work so I need to have a decent connection. Opinions needed please.
I think it may be a bad phone.
I have and used the following bluetooth devices:
Plantronics 590A
Jawbone Icon and Era
BlueAnt S4 which I use in the car. And auto connects before I sit down to drive when I have it on.
Sony Ericsson MW600
And Jabra Pro 9470 (office phone setup that connects to my phone via bt)
All connects without a problem. Have you done a titanium backup and perform a factory reset? And after the reset use titanium backup to restore app and data only and leave the system settings alone. You can restore the wifi stuff if you like. From there that's like a fresh install. Hope that works for you.
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
kabuk1 said:
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
Click to expand...
Click to collapse
Well before leaving the store...if you are going to a brick and mortar to do the exchange, bring the bt headset with you and try it out there and try to replicate the problem with a new phone.
I do not have range problems but I don't usually have my phone more than 5 ft way from me when talking on it via bt.
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Macklessdaddy said:
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Click to expand...
Click to collapse
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
rosedog said:
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
Click to expand...
Click to collapse
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
kabuk1 said:
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
Click to expand...
Click to collapse
No you will have to call T-Mobile and do a warranty exchange. I have no problems with BT on my phone at all.
http://androidforums.com/htc-sensation-4g/375199-white-noise-bluetooth-htc-sensation-4g.html
http://community.htc.com/na/htc-forums/android/f/133/p/12494/52795.aspx
http://forum.xda-developers.com/showthread.php?t=1184936
a few threads about bluetooth problems
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
rosedog said:
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
Click to expand...
Click to collapse
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
kpjimmy said:
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
Click to expand...
Click to collapse
You've been running what and what?
MIUI / Sense-o-maniac 3.5?
I'm running the latest ARHD w/sense 3.5
horrid bluetooth sound quality
it seems a lot of people have been having issues with the bluetooth sound quality. i have mine paired with a motorola HF850 car kit, which has bluetooth v1.1, or something like that. i wonder if the problem is with backward compatibility, as people seem not to have as many issues with newer devices. would flashing a different radio potentiall help this problem? is it possible to downgrade the bluetooth version with a custom ROM? any other thoughts on ways to address this issue?
Hi all,
I have successfully rooted and flashed Paranoid Android 2.54 onto my ATT HOX and it is a wonderful ROM for sure. I love the options that it provides and the silky smooth, almost stock interface. The only real issue that I have come across is when I try to use a headset for calls. I am defining a headset as a 3.5mm plug in set of earbuds with mic (Klipsch S4i to be exact). When I listen to music, be it on Pandora, Google Music or Apollo all is well. As soon as I try to use the phone, no sound comes through the earbuds and the mic does not function. In fact you can see a noticable slow down in the dialer app when the headset it even plugged in. If I make a call, then plug in the headset, everything goes silent and the other side can't hear me until I unplug the headset from the phone.
Here is the real kicker though! I have my car stereo modded with an aux 3.5mm plug for listening to music and if I plug the phone into that it works just fine in phone mode! Now, I do realize that the Klipsch is setup as a TRRS and the car aux is just TRS (so when using the car stereo I am effectively bypassing the mic portion of the 3.5mm plug and using the phone's mic), but I cannot for the life of me understand why the headset will not work.
I am hoping that someone can enlighten me or least tell me that they to are experiencing this same issue. I will gladly provide any more info that someone might need to help diagnose the issue, and thanks in advance!
Update so far...
So, up to this point here is what I've found. If I plug in a normal set of earphone (read buds only no mic inline) then I will get sound through them no matter what I am doing (youtube, music or phone). Also, in this configuration anyone I am talking to on the phone can hear me just fine as I am using the phone's mic. However, when I plug in an earbud/mic combo the phone will not function. I get silence and the other side cannot hear me speaking either. It's as if the software has somehow told the headphone jack to act differently than it used to with earbud/mic combos. I am stumped as to why the OS would not allow this type of use when it is so standard. Anyone have any thoughts?
I actually have the same headset and I started having problems with it on the stock rom before I even rooted and flashed a custom one. I honestly just thought it was because they're really made for apple phones. Sometimes I'll just unlplug and plug them back in for them to register. Other than that I haven't seen a fix for them.
P.S. Klipsch control from the play store seemed to make things worse for me
sourshin said:
I actually have the same headset and I started having problems with it on the stock rom before I even rooted and flashed a custom one. I honestly just thought it was because they're really made for apple phones. Sometimes I'll just unlplug and plug them back in for them to register. Other than that I haven't seen a fix for them.
P.S. Klipsch control from the play store seemed to make things worse for me
Click to expand...
Click to collapse
Thanks for the response! Yeah, I think I am going to try another ROM just to see if it will help, but I have the distinct feeling it might be a hardware issue. I just can't understand why this would all the sudden malfunction right after rooting for me. Maybe just a coincidence. I will definitely respond here though if flashing to a new ROM helps...
guitarman710 said:
Thanks for the response! Yeah, I think I am going to try another ROM just to see if it will help, but I have the distinct feeling it might be a hardware issue. I just can't understand why this would all the sudden malfunction right after rooting for me. Maybe just a coincidence. I will definitely respond here though if flashing to a new ROM helps...
Click to expand...
Click to collapse
I've never tried paranoid but King kang(which has paranoid elements) works fine for the most part. nocturnal'd dirty rom, miui, and cm10 have all worked for me tho. I'm currently on the unofficial cm10.1 4.2 and that's working for me as well, except when I have the headset plugged in while booting.
Final Update....And SUCCESS
So, it appears that it was some sort of ROM specific issue. I flashed CleanROM 5.1 to my phone and "wah-lah"! The headset works perfectly in all modes. I am not sure what it was about Paranoid Android 2.54 that would not allow the headset/mic combo to work with the phone, but I am free of it now I guess. I will miss the interface of PA, but boy does CleanROM run FAST!!! I am in awe of the speed and responsivness. I hope the battery life holds up like PA did for me and I also think that the quick settings on CleanROM basically RULE.
I've had my Skyrocket (I727-R) for little over a year now. Bought it used. For the first seven or so months everything seemed to work fine. I had no issues and was flashing ROMs fine. Around November last year, I attempted listening to music only to realize that I couldn't hear anything from my earbuds. At first I thought it may have been my crappy old earbuds so I tried playing music without the earbuds and making a call. The other side could hear me but I could not hear anything. Since then, I've taken it back to the place I bought it from and they have been co-operative. Usually they charge for diagnostics and such but since I was a recurring customer they did it for free. Anyways, at first, it seemed like they had fixed it by replacing the speaker. They also wiped my SD, flashed the phone back to GB and told me not to root or update the software. I didn't see why it would be an issue however so I used Odin to update to stock JB and root, flashed some ROMs, etc. The audio worked for a day and stopped again while listening to music the next day. I took it back to them and they said it was a motherboard defect and would cost as much as a new phone to replace the motherboard.
I am currently running Dirty Unicorns 4.4.2, 20140331-0105, radio is T989UVMC6 (I'm on Mobilicity's network)
My question is, is there anyway I can be 100% sure it is a motherboard issue? And if it isn't, how can i fix the audio? If it is in fact the motherboard, what is the recommended course of action?
Thanks.