My Samsung T989, which was running Cyanogen 10.1.3, recently starting having the problem where I wasn't getting any sound from the earpiece during calls.
Speaker phone works, headphones work and the person on the other end can hear me (so microphone works). But nothing from the earpiece.
I've tried every setting but nothing. I've also tried Cyanogen 11 just to see if perhaps it was a bug that has been fixed, but still no sound, so I assume that this is a hardware problem.
Is there any way of diagnosing this better as either hardware or software? Any known fixes?
WTF is the deal with AOKP 10.1 MR2 and Sound
bosth said:
My Samsung T989, which was running Cyanogen 10.1.3, recently starting having the problem where I wasn't getting any sound from the earpiece during calls.
Speaker phone works, headphones work and the person on the other end can hear me (so microphone works). But nothing from the earpiece.
I've tried every setting but nothing. I've also tried Cyanogen 11 just to see if perhaps it was a bug that has been fixed, but still no sound, so I assume that this is a hardware problem.
Is there any way of diagnosing this better as either hardware or software? Any known fixes?
Click to expand...
Click to collapse
You are not the only one. Mine the sound other than calls is GONE! I am trying to figure this out. Tried to Flash the ROM from a clean flash with reset to factory and the works and went directly to AOKP ROM Directly with the latest Gapps. No dice. The phone ear piece works but speaker phone and any thing else via the speaker does not work any longer. I am dead in the water here and need a fully functional phone.
This is not my first rodeo. I have flashed many Andriod devices, Cliq+, Nexus S, Nook Color, Acer 500 etc... and the Galaxy S II.
Heck I am also now having issues with the CWM Recovery as well. I can not flash it current. The CWM ROM Manager says flashing and never completes. It has Root privileges. Really has me beside myself at the moment and it is my primary driver so it is interfering with WORK now and really has been ANGRY!
Maybe try out different radios or make sure you using the required version of TWRP?
I'm using UVMC6
Related
Hi guys,
Because of this problem I get almost sorry that I had taken a Galaxy Nexus.
I can pair Nexus with my carkit (parrot) and I can play audio through the speakers.
My problem is: When I call or receive a call I can hear almost nothing. Sound is so low that I can not even notice that the sound from the speakers or coming from the phone. I am using Volume+ too but nothing helps!!
It's look like that Nexus somehow even loses the connection, without any reason.
It's a rooted Nexus and running on AOKP.
Is there a better ROM for my bluetooth issue or do you guys have any suggestions?
Thanks in advance..
No one??
Has nobody has an idea or experince with this??
The market description for Volume+ says:
A Cyanogen Mod 7 or MIUI ROM is HIGHLY recommended. Running this app on a Stock ROM/Kernel may result in it not working, being far too quiet, or getting even quieter. PLEASE don't comment or rate badly if you are on a Stock ROM as this is most likely the problem.
Click to expand...
Click to collapse
The feature list for AOKP says it uses the "Unsecure boot.img (stock AOSP kernel)."
You might want to try uninstalling the application to see if that fixes your sound issues over bluetooth.
I am using a stock (unrooted) GSM Galaxy Nexus. It pairs just fine with my Jawbone Era bluetooth headset and do not have an issue when making/receiving calls with volume. Where I notice the volume is quite low is the voice dialer prompt only (the actually call is fine). Apart from that, no issues.
miui..
Hi guys,
Thanks for your replies.
I flashed the rom of miui and it's seems to work till now. So this rom dealing better with bluetooth.
Hi everyone, I'm hoping someone has a suggestion for me wrt to audio problems with my wife's Sprint Galaxy S3.
On a fully stock up to date S3, about 3 days ago all sound stopped working, this includes alarms, answer calls, key press sounds, playing music. However after a reboot, it would start working again for 6 hours or so, and then quit again. I assumed this was a software issue of some sort. I have an older rooted phone which I love and have had for years, I suggested that we finally root her S3, so she could get all those benefits plus fix whatever little software problem this was.
The rooting process when fine, and the phone now has CWM and CM 10.1.2 (Android 4.2.2). However the audio issue is still there and in fact a reboot no longer fixes the issue.
I have tried pluggin in the ear buds w/ built in mic, and those too fail to work. I also have paired various bluetooh devices like mini boom boxes etc.. they all pair fine however there is no audio output from them. No audio in the dial pad when hitting the numbers. When trying to play music the DSP Manager will crash, and then the music app crashes (tried Apollo and Google music). If I go to the sound recorder and hit record, it pops up with "Internal application error.".
So it seems all audio (speaker, mic, bluetooth, and headset) is broken which again makes me think software, but even after rooting and installing a new rom like Cyanogenmod the issue is here.
Any thoughts on what else I can try? Any firmware updates that I could apply specific to audio issues like this, or perhaps it is some sort of hardware issue that is preventing the software drivers from behaving properly?
thanks,
fishtek
I would Odin back to complete stock and see if the issue still arises. If it does then it could be hardware related.
Same problem
metalfan78 said:
I would Odin back to complete stock and see if the issue still arises. If it does then it could be hardware related.
Click to expand...
Click to collapse
I have that sane issue and nothing I do seems to work.
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/
Hey everyone. My note 2 gas given me many troubles, first the chip EMMC failed. I created a thread explaining the situation. Bootloop, recovery failed, etc. So I bought a phone that had a broken screen. I replaced the motherboard and everything was going fine but cellular signal was failing, I gave it back to the owner. (I also created a thread about it).
Now, I bought another phone with the broken screen. So I replaced the motherboard one more time. Everything works ok, cellular signal, wifi, camera (both front and back camera), wifi, speakers, etc. But I have a trouble with the microphone. When I'm on a phone call I can hear people but people can't hear me, unless I use the speaker then they can hear me. I suppose that the mic from the top of the phone is the one that is working when the speaker is turned on.
I've done some reading, and there are many solutions, cleaning the mic, factory reset, installing other ROM,etc. The mic isn't the problem. I tried the mic of my note 2 and the other mic too. The problem is present with both mics. (Both phones are the same variant by the way, GT N7100 international version).
The phone is on 4.1.2 Jellybean, I'm thinking on update to 4.3 first via Odin, if problem is still not solve then upgrade to 4.4 kit Kat via Odin as well. If problem persist, then flash a recovery via Odin and then install a custom ROM 5.1.1 and if the mic problem still not solved then flash a 6.0.1 custom ROM.
I don't know what else I should do concerning this issue. Any advices? Or solutions? Has anyone had this very same issue?
The mic doesn't work at all, I tried video recording and the only mic that works is the top one, not the bottom one. Voice recording doesn't work as well. Headphones does work. If I unplugged the headphones while having a phonecall the bottom mic still isn't working.
Hope you could give any advice or solutions! Thanks in advance.
Sorry for my English skills.
Did you try moving the swapping out the USB fix cable between both phones?
I doubt that it's a software problem because I have not come across a situation where a mic does not work on a particular stock rom.
audit13 said:
Did you try moving the swapping out the USB fix cable between both phones?
I doubt that it's a software problem because I have not come across a situation where a mic does not work on a particular stock rom.
Click to expand...
Click to collapse
Yes I did. Problem still there. I also did a factory reset. I'm thinking that at least one of those mics are working OK. I mean, it would be really really bad luck having the 2 microphone malfunctioning. My microphone was working fine before the EMMC chip crashed. After I replaced with other motherboard with no cellular signal it was working fine as well. This motherboard tho everything is working fine but both microphones.
Yes, that is weird. Maybe you need a new mic? That might be the cheapest solution.