Ok, I've read of 1-2 other people who've had this same issue. Tried contacting them with no results.
Issue: When on a BT call in my car, the person on the other line hears themselves speaking...i.e. echo. If I mute the microphone on my phone, it goes away...but obviously they can't hear me.
ROMs tried: Calk's v1.4 and AOKP Milestone 5. Flashed both twice; tried method of going to ODIN and loading stock EL29, rooting, adding CWM, then going to CM7.2 as well as the stock to EL26 and then flashing. Cleared data/cache/delvik cache multiple times.
Went back to EL29 stock and works great.
Any ideas of what I could do to fix? Really liked AOKP.
chadillac3 said:
Ok, I've read of 1-2 other people who've had this same issue. Tried contacting them with no results.
Issue: When on a BT call in my car, the person on the other line hears themselves speaking...i.e. echo. If I mute the microphone on my phone, it goes away...but obviously they can't hear me.
ROMs tried: Calk's v1.4 and AOKP Milestone 5. Flashed both twice; tried method of going to ODIN and loading stock EL29, rooting, adding CWM, then going to CM7.2 as well as the stock to EL26 and then flashing. Cleared data/cache/delvik cache multiple times.
Went back to EL29 stock and works great.
Any ideas of what I could do to fix? Really liked AOKP.
Click to expand...
Click to collapse
My girlfriend complained about the same issue with my phone, and my "fix" was to lower the BT volume on the device, and max out the volume in the car, and she said the echo was gone.
If I did that I'd go deaf with the hang up beep in my car.
Glad to hear it's a little more widespread than I thought. Hopefully this gets fixed with newer releases of ICS.
Ok, going to ask what's most likely a stupid conceptual question:
For both my Calk's ICS 1.4 and the AOKP Milestone 5 installs I followed qbking's video's to the letter.
Now, to the best of my understanding, this ROMs come packed with a kernel such as FD26. However, you can load different kernel's such as the new FE07 which could very well affect my BT and potentially fix it (or not...)
So, to flash a new kernel, I'd have to use ODIN to install the EL26+CWM to get back to a GB recovery. From there I flash the new kernel, then reflash the ICS ROM.
Here's what I don't get...if the ROM comes packed with say the FD26 kernel, won't that overwrite the FE07 (or whatever) kernel I just flashed? What am I missing here?
Thanks!!! Really trying to see if my BT issue is something I can fix. Want AOKP back again, bad!!
chadillac3 said:
If I did that I'd go deaf with the hang up beep in my car.
Glad to hear it's a little more widespread than I thought. Hopefully this gets fixed with newer releases of ICS.
Click to expand...
Click to collapse
Lol...it won't be so loud, at least, not for me it isn't.
I'm an over the road truck driver and the only time I experience this is if I, or the person I'm talking to is in a really poor service area, i.e. South Carolina anywhere on I-95. Other than that I never have echo, & I'm on the phone for hours & hundreds of miles at a time spanning multiple states.
So it's not a ROM problem, kernel or modem related maybe, but I'm usually running the latest modem & kernel & have been on Team Nocturnal's ICS Blend "The Goodness" since about version 1.5, we're on version 8.0 right now. That would lead me to believe it's also not kernel or modem related
Fwiw, I use a Blue Parrot BT250-XT+, or Planatronics BB903, or a Blue Parrot VXi2 Expressway.
Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 Pro
So you're not using a vehicle's BT system but rather an earpiece?
The earpiece would not be an issue as the issue is the microphone on the phone is still on. So, over a car's stereo system it's plenty loud enough to feed into the phone. In a BT earpiece there wouldn't be enough volume to cause a problem.
I have not noticed this with any ics leak and my car built in bluetooth. My only complaint about bluetooth is that the volume is too low when streaming audio.
I know of three people from my searching who did...one person said they went to the latest version of CM9 and that fixed it...going to try this weekend.
chadillac3 said:
So you're not using a vehicle's BT system but rather an earpiece?
The earpiece would not be an issue as the issue is the microphone on the phone is still on. So, over a car's stereo system it's plenty loud enough to feed into the phone. In a BT earpiece there wouldn't be enough volume to cause a problem.
Click to expand...
Click to collapse
I was using a vehicle one, that I installed myself.
http://www.crutchfield.com/p_113BT300/Kenwood-KCA-BT300.html paired with http://www.crutchfield.com/p_113DDX512/Kenwood-DDX512.html?search=ddx512&tp=20217
I reduced the echo by lowering the BT volume during the call on the handset, and raising the volume on the car receiver.
I know, I know the thread title is BT echo with ICS ROMs...I am not running ICS, but for what it's worth, same issue here often, though NOT every call... I am running completely stock (still GB 2.3.6). Phone BT is paired with Motorola T215 that's clipped to the visor in my truck. ...and for me also, turning down the volume down a notch or two helps...In my case, I was actually thinking it is a feedback issue, where the other person hears their voice picked back up through the mic...that's why turning down the mic helps (or why they don't hear it when the mic is on mute)...
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
chadillac3 said:
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
Click to expand...
Click to collapse
Really? That's weird. In my car, adjusting the handset volume affects the system volume coming out of the speakers.
chadillac3 said:
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
Click to expand...
Click to collapse
When I press the volume on the BT module, the phone will display "Bluetooth In-Call Volume" and adjust accordingly. Conversely, the phone will display the same when pressing the volume on the phone during a call. It could be relative to your BT module - if I understand correctly the BT module needs the Audio/Video Remote Control Profile (AVRCP) - as what allows for volume control via BT (as well as the play,pause,etc. on music over BT). Does your device support it?
I also found that if I slightly lower the visor, the sound doesn't "bounce" off the roof of the truck and helps not create echo as often, so I can turn the BT module volume up higher, if need be.
Just an FYI - when I used to plug a line from the headphone out from my HTC Hero to the truck stereo aux in , I would use the truck's speakers and the phone's mic...but there would definitely be echo issues if I cranked up the volume on the stereo...which of course let me to believe the similar issue occurs with my BT device and the phone itself because the mic is close to the speakers on the BT device.
Yep, module is AVRCP 1.3 compatible...which is part of the reason I like AOKP. Bitpool on the BT is set much higher than stock, and the metadata is transferred correctly. Everything is wonderful except for the damn echo.
What's weird is stock works totally fine; AOKP M5 had the echo, and Calk's 1.4 had an echo and static per my parents on their ground line and their ET4Gs. Wife's iPhone didn't seem to have the issue, so I wonder if it had processing built in to cut out the echo.
Going to try the latest versions of the ROMs to see if it magically fixes it.
Related
I've used many ROMs (Viper, Bonsai, Nebula, currently ACS Syndicate) and I've had this problem on all of them. I've even ODIN'd back to stock before and it still didn't fix my problem.
After disconnecting my Epic from my Jawbone Icon headset, the sound often gets stuck inside the earpiece. Music, movies, games, ringtones will all play from the earpiece instead of the speaker behind the phone.
Is there some software fix to correct this? Can any of the devs point me in the right direction as to how I might troubleshoot this (maybe at the kernel level)?
Thanks in advance!
This doesn't really go in Development, and I suspect it will be moved soon.
I can tell you, though, that I've experienced similar problems, intermittantly, and here's what I've observed.
If I'm listening to music through bluetooth, before I disconnect, I'll stop the music. Then I'll turn the bluetooth device off. Then I'll turn bluetooth off on the phone. If I do it in that order, I don't seem to get the bug.
If you do still get the bug, rebooting fixes it.
Hope that helps!
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
daddymikey1975 said:
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
Click to expand...
Click to collapse
This stuff has been going on since DK28 and before. I believe Rodderick was looking into fixing it from the kernel side, but I'm not sure how much progress has been made. I know it's not as bad as it was on DK28, but still very annoying. It used to happen to me all the time (audio going through earpiece instead of speaker after disconnecting Bluetooth) when I would turn my car off and it would disconnect the Bluetooth to my car stereo. Now that I have the Samsung Car Dock, I just connect Bluetooth for phone only, and use the audio out on the Car Dock for Navigation and Media.
Moved to Q&A.
i am having a simular issue but mine is that when i connect to bluetooth headset i have to have media playing before i get a call or i will not hear the other person in the call.
it seems to me that ANY bluetooth headset with A2DP is doing this and i have tried 3 diffrent headsets. Jabra Stone, Jawbone Icon, and the Blueant T1.
all 3 of these headsets do this. does anyone have any solution yet?
Even if there isn't a fix, I wish there was an app to reset the sound settings post facto. Anyone know of one?
I just want to add my name to the list of those who are affected by this. Glad it's not just me, though. Hopefully it can be debugged easily.
For the record, a Quickboot Hot Reboot (reboot of Android only, not phone) does NOT solve the issue. Only a full reboot works for me. Seems like it may not be a software issue but something hardware-related.
Sent from my SPH-D700 using Tapatalk
Just want to add this happened to me the first time just now. I'm on rooted EC05. I was scared for a bit that the speaker had blown. Then when I discovered it all coming from the earpiece, I remembered this thread. A reboot did make it go away.
I wonder if it has any relation to the issue I see once in a while since the upgrade where my BT devices need re-pairing and ask for a passcode, when they really shouldn't.
I Also Have This Issue
I have had this exact issue since DI18.
After I hang up a Bluetooth call, I have popping sounds coming out of the earpiece. Turning off Bluetooth doesn't fix it. Turning Bluetooth back on after turning off doesn't fix it. In addition, after this happens, all devices sounds (phone ranging, notifications) all come through the earpiece and *not* the main speaker.
I've had all of the stock ROMs up until EC05 loaded on this Epic and have had the same issue throughout. I am now running midNIGHT ROM, which has cured most problems I’ve had with my device, except this issue.
I was just poking around trying to find some sort of tool or the name of the service(s) that I need to restart to fix this issue.
Same issue for me. Quite annoying as I listen to audible over bluetooth quite a bit, and then pretty much know I have to reboot when I turn bluetooth off.
SRF users have reported Bluetooth issues being cleared vs. stock builds. I can't say exactly why, but it does seem to work.
What are SRF users?
Nope...
Syndicate Rom Frozen...
Well, I'm on SRF 1.1.1 and I've got the same incredebly annoying audio issue.
Please, someone, come up with a fix!
i believe there is a bug in either the GNex's bluetooth hardware or Android ICS.
i have an A2DP adapter in my car to play music from my phone on my car stereo. my car also comes with the ability to connect to a phone for the purpose of taking and making calls thru its stereo and mics (using bluetooth HFP). when both are enabled simultaneously, i am able to listen to my music fine. if i get or make a call, the phone pauses the music, as you would expect, and goes into the call (although when i receive calls there seems to be a delay before the GNex switches over), but in the call the audio is garbled/robotic/scrambled...whatever you want to call it. this is the case both for what i hear and for what the person at the other end hears.
i wanted to start this thread to get more info about this problem from others that have experienced it, and maybe see if we can come up with a workaround.
there is an AC thread about this here:
http://androidforums.com/samsung-galaxy-nexus/524885-galaxy-nexus-bluetooth-bug.html
and i put in a bug at google here:
http://code.google.com/p/android/issues/detail?id=29564
any more info is appreciated!
According to other posts in the forums, the AOKP ROM does not have these issues.
I really did not want to root this device. I know, that's just not cool. But everything else was just working.
My Sensation did not have these problems, but alas I dropped it and it died and I was still on contract. The Nexus was more cost effective than bending over for the off-contract price from TMO.
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
I would be kind of surprised if it didn't exist in AOKP, because the problem definitely exists in CyanogenMod 9 (and AOKP is essentially a kang of that). In fact, I uninstalled CM9 and reverted to stock expressedly because I initially thought that this bug was a CM9 issue and it was annoying enough that I figured I'd revert to stock until CM9 reaches stable, only to discover that the problem is in the official Google builds as well.
ianken said:
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
Click to expand...
Click to collapse
Please let us know how it goes! I've been using Bugless Beast, but would switch to AOKP if it fixes this bug.
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
ianken said:
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
Click to expand...
Click to collapse
audio.conf does not seem to exists in 4.2.2. Has anyone found audio.conf in 4.2.2?
Hi everyone,
The bluetooth on my GSIII has been a complete failure. You can follow the saga here (http://www.benzworld.org/forums/w245-b-class/1662643-2009-w245-samsung-galaxy-s-iii.html), but basically it connects to my car and has no sound with the stock ROM and refuses to connect to the car at all with the AOKP JB build. It suggests an android problem, so I'm wondering if the bluetooth stack can be reloaded to reflashed with something different. If anyone has any ideas, I'm all ears. Thank you!
I have a problem with one of my Bluetooth devices dropping and reconnecting. Not sure why is just one. It works fine on an iPhone. I'm guessing your GS3 isn't the international version?
Sent from my SGH-I747M using xda premium
Nope not international, SGH-I747M from Bell.
I'm trying this. Will report back.
evilmonkey1987 said:
I'm trying this. Will report back.
Click to expand...
Click to collapse
Sweet! please let us know!
I'm having a different issue. it connects and stays connected, plays music but it doesn't list the song/artist info on my eclipse screen but the SG2 will..
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
evilmonkey1987 said:
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
Click to expand...
Click to collapse
Try CM9. Bluetooth works much better with it. CM10 should have it fixed as well in a day or two.
Here's a 'six months later' update. My phone went through various android updates and I'm now on Android 4.1.1 (up from 4.0.4). The problem was still not solved, but instead of no audio, I now have one way audio, where people hear me but I don't hear them through bluetooth. I have also gone through a number of custom ROMs and kernels for my phone (including CM9/10 and AOKP) and nothing helped with the issue.
A couple of days ago, my girlfriend's HTC One X (finally!) got its Android update, also from 4.0.4 to 4.1.1. Her phone now works like a charm with the in-car bluetooth.
The solution I ended up with was a car cradle and a couple of NFC tags to control my phone in the car. My NFC tag that's stuck to my car cradle turns off WiFi, starts car mode, starts a car home app and turns my volume to max. All I have to do after that is connect the 3.5mm audio cable and I use my phone in place of the car's infotainment system. That way the phone integrates into the car as well and the only thing I lose are the steering wheel controls (they still work for volume).
My less technologically inclined girlfriend now has everything work auto-magicallly with bluetooth. So I guess all's well that ends well, but to anyone considering a US-spec Galaxy S III, watch out: the bluetooth issue is still not fixed. If bluetooth is critical, consider the HTC One X (but be warned: it has awful battery life!)
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
colbynmeghan said:
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
luncht1me said:
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
Click to expand...
Click to collapse
What's wrong with stock? I have no major issues with streaming BT from my phone to my Mazda 3 head unit, or to my Sony MW600 earphones. Even track titles work (the only thing that doesn't work is time display). In my experience, Bluetooth works best on the stock ROM.
Stock Rogers ROM (DLK4 - JB 4.1.1), rooted
KT747 (1/9/2013) kernel
CWM Recovery 6.0.2.3
PlayerPro Music Player
On my old Xperia X10, I had CM7 and had no end of issues with BT:
- Sometimes it would connect and there would be no sound
- Sometimes it wouldn't connect at all
- Sometimes it would cut out after switching songs
- It would stutter a lot whenever Wi-Fi was enabled (but I think that was a problem with the Xperia).
When I tried CM10.0 on my S3 I had similar connection issues, just not as bad. Also, the volume gain over BT was much lower, so I had to turn the car speakers way up. Stock 4.1.1 doesn't have any of these problems. The only problem I had was the audio switching over to speaker after turning off the car, but I fixed it.
Also, BT is apparently broken in 4.2.1 in general, not just CM10.1. Google confirmed a BT patch that works on the Nexus 7, due for release with 4.2.2: http://www.expertreviews.co.uk/smar...confirms-android-4-2-bluetooth-streaming-flaw
TIP: Don't forget to turn up the volume on your phone. I don't know how many times I accidentally turned down the volume and thought that it wasn't working. Now I have Tasker do it for me whenever I connect. :good:
4.1.2 has Bluetooth working use it everyday. (Stock and ROM.) Can't tell u which combo I use at a time. I flash a different ROM everyday. As 4.2.1bluetooth is broken expect for task's AOKP. He has it workingish.
Now as connecting to a car. Depends on what it connects as. And I've learned going to and from ROMs when u connect a source hit the volume up 9/10 times it works
Sent from my SGH-I747 using Tapatalk 2
Having an issue with no sound emitting from any audio output on the phone, but sound will play through Bluetooth-connected device. No sound from front speaker (phone calls, dial pad), no sound from rear speaker (notifications, ringer, alarm, media) and no sound from wired earpiece/headphones. Seems like it's stuck in Bluetooth/headset mode, but turning off Bluetooth doesn't restore sound. Problem is intermittent, haven't determined pattern to the behavior.
Phone was rooted long ago but kept stock ROM. Flashed Paranoid Android 3.99 RC2 about a month ago, and problem seems to have started shortly thereafter, but not sure if related. Haven't tried to reflash.
Any suggestions? Tried searches, but didn't locate this specific issue.
SGH-T999 (US/T-Mobile Galaxy S3)
Is it a T999 or a T959? And flash back to stock.using Odin. If it still is a problem it's likely hardware related.
Sent from my SGH-T999 using Tapatalk
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
yardsale said:
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
Click to expand...
Click to collapse
Did some more investigating last weekend before flashing ROM (never did the reflash).....seems that often, not always, if I turn off the car ('13 VW) while still connected to phone Bluetooth, the phone's sound quits working (all sound). Rebooting phone and turning off Bluetooth does not restore sound. The only solution I've found is to reconnect to car's Bluetooth, then turn Bluetooth off before shutting down car, and that only works about half the time, but sound is instantly restored. My estimation is that this wouldn't be hardware related, is that a fair assumption?
I also have a Tasker profile set up on phone to disable PIN lock when phone is connected to Bluetooth device (enables Sena Bluetooth headset used with motorcycle helmet to function properly), could that be causing the problem? Anyone else experience this issue?
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.
I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.
Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
@yardsale
I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.
Hi everyone, hope someone can point me in the right direction. Flashed OmniROM on an HTC desire (bravo) and it's working great. Only problem is when making a call, no sound comes out of the earpiece. If I put it on speaker phone it's fine, and apparently when it's not on speakerphone the mic works fine, people can hear me on the other end, but I can't hear a thing. Suspect the radio is the problem here so need advice on which radio to use (especially for internet use too) and how to install it. I have Ext4 bootloader installed too. This is my interim phone after my Samsung Galaxy S2 died completely (will not power up since it died during normal operation), which looks like it would need a JTAG burn to fix, right after I successfully replace the USB board. Anyway, any help appreciated. Thank you.
Can it not be that the earpiece is simply broken?
Does it work for instance over Wi-Fi calling e.g.Skype? Can you get any sound to come out of it?
Was it working before you flashed the ROM? If you backup and flash different ROM or better yet back to stock, does it work?
Just want to do logic tests before concluding it's a radio issue, which I'm not sure it is.
So confirm above before playing about with radios as they carry a but more risk. To flash radios, you need to be S-OFF, and use fastboot commands. Check the md5 sum of the radio.img before flashing because a bad radio flash= proper brick.
There is no recommended radio, though latest one should generally be better. Depends on individual signal quality so different people get different results
Good point. Got around to thinking the same myself. Found a replacement speaker on ebay (local seller) which I ordered (it's cheap). Meanwhile searching the market for a speaker tester.
Desire adr6300 running cooldroid
old thread, but I have a similar but slightly different issue and it doesn't appear to be the radio
Cant hear anyone on call, they can hear me
Works on earphone - can hear caller no probs, they can hear me ok
If i switch to speakerphone during the seemingly silent call, as soon as some noise (voice or otherwise) is picked up from other end, then the speakers start screeching - quickly getting to max volume. Goes silent again if speakerphone option switched off.
Hadn't flashed anything when it started to my knowledge, but had been installing various things. Nothing significant to my recall.
Tried re flashing cooldroid after clearing caches - same
tried installing mildwild - same
reflashed radio (it is the latest and been on ages) - same
Cleared everything except sd data but including ext partition and reflashed coildroid - same.
Oh - audio tracks play fine :/
Help.
Slight update on this.
After trying different roms and reflashing the later radio:
Flashed an older radio on it that i had on it before - same.
Radio_32.56.00.32U_5.17.05.23
Radio_32.56.00.32U_5.17.05.08
Seems like mic (others hear me) ok when used normal, but I cant hear them
but some sort of feedback squeal when i put it on speaker voice does come through quietly along with the screeching (no its not the missus), the screeching only starts as soon as some noise is picked up through sending phone
When earphones connected (hence mic and speaker on phone disconnected) - all fine.
So possibly some sort of short in the ear speaker unless someone who knows the hardware better than me can suggest something else
(Do these have noise cancelling mic which is disabled when earphones are connected? - must look that up when I have some time again)
Update
it does seem to be simply a failed ear speaker
Update
Got around to replacing the ear speaker (less than £2 delivered from ebay)
SORTED
dead easy job - 10 minutes to replace and all ok now.
No sound through ear speaker now sorted
This is for ear phone - but shows how easy it is
Speaker is just under the top board - no cable just prongs and stickied in place.
http://morganbye.net/blog/2012/08/htc-desire-headphone-jack-fix/