I'm no where near qualified to place input on ROM development but I did have a random thought.
Is it possible that the Mic issue with most KitKat ROMs, could be caused/fixed/related with the headset jack?
I remember hearing somewhere that random occurrences of mics not working when a headset that wasn't made for your device was used and taken out, that it may cause the device to not recognize the removal and therefore not switch back to the mic.
Like I said, im sure it's not that simple, but hey, it's a shot in the dark.
Related
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 chaps,
Wierd issue. Headphones are not detected when plugged into my phone unless I do a reboot. Similarly, when I unplug the headphones they are not 'un-detected' until a reboot.
However, using an app called toggleheadset I can force audio through to my headphones. This is a bit of a pain because 1) I have to remember to do it and 2) I lose Beats functionality.
I have tried using different headphones but this has no effect.
Any ideas as to why the headphone state is only detected at boot?
I have tried different Kernel/ROM combinations but to no avail.
Any help would be greatly appreciated.
also, if anyone can provide me with some pictures of their headphone port so I can compare it to mine that would be great.
Hi,
I have the exact same issue with my HOX since yesterday.
At first I thought the ROM had something to do with the issue, but after flashing several other ROMs, it still wasn't solved. (I haven't flashed back to stock btw)
"toggleheadset" works ok, but I can't use the microphone that way; I can't use my headphones to make calls anymore.
Also when answering phonecalls, sometimes my headphones are still toggled on, so I can't hear the other end. And the worst thing is: when I try to toggle the headphones off during the call, my screen dimms and I struggle to activate the widget. THATS a pain in the ass.
Does anyone know if the issue is software/hardware related? And the best way to solve this?
I'm wondering if this issue affects bluetooth headsets. If it doesn't, I'll consider buying one.
Old thread, but me the same... But my HOX survived waterboarding... I felt into the wather while sailing. Changed battery and screen, but now I see i have one more problem to solve. If any one have solution - please write. But for now I'll try to fix by my own
Cleaning Hole
Try to clean the hole where the Headphones are put in...
If its clean, try to reinstall the rom.
This is a cross post from the thread I found on reddit, I take no credit for this find.
The problem for this person was "I purchased some Beyedynamic DT990 Pros (low impedance ersion; 32ohm) and there is some issue with the jack. It seems to trigger the button of me pressing the microphone button, with minimal movement. It either brings up voice command or just pauses the music, even if I just turn off the screen. If I try to increase the volume it also brings up the voice command sometimes.
Just moving the phone slowly causes the music to stop (if it doesnt already when turning the screen off.
Anyone have any solutions to this? These are good headphones, they work with my pc perfectly. I will test with my ipod aswell.
I was thinking of getting a female to male jack just to see if a different connector works. But these are audiophile headphones so the quality isn't really questionable."
and the solution was
"Download the app SoundAbout. It lets you force your phone to detect the headphones correctly. My G3 was doing the exact same thing and ever since I downloaded SoundAbout around a week or so ago everything has been working fine." "What I do is put the headphones into the jack, but not all the way until it clicks in. Just put it in enough to where the phone senses them. If the phone senses them as a headset, remove the headphones (not necessary to take them completely out, just off of the sensor inside the headphone jack) and try again. Once it detects them as regular headphones you can click them in like normal."
Sorry for the poor formatting, and unable to link the reddit thread because my account lacks posts but I found this extremely helpful and hope everyone with this issue does too.
Credit goes to tmfrosch9
Thread is LG G3 can't deal with proper headphones-
Another method from goldswimmerbj
"I have seen that many people are having issues with the phone picking up headphones as headsets and pausing music on it's own and also causing LG voice to pop up. This issue is caused by the phone picking up headphones incorrectly.
Put the headphones in slowly until you hear 2 faint beeps. Once you hear those just continue plugging in the headphones."
Hope this solves your problems with the LG G3,
My LG G3 has a different problem I guess
Thanks for the info OP.
Mine has headset issue, but only during phone calls.
When I play music, I have no problem at all, during the phone calls, this is where the issue comes. the sound is bad, just like the phone is in a really bad reception area, however, when I unplug the headset, use the phone itself, there is no problem at all, same for the speaker.
i tried with different headset, all same result. I tried the options in the thread above, same. also, my phone detect the headsets ok, once the headset is plugged, the phone has the headset icon appeared
my phone is LG G3, 32G, Canadian Bell version.
any help would be much appreciated
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/
I got my OP3 quite recently so I installed 3.2.7 almost as soon as I set it up so I have a couple of issues but I'm not sure if they were already there when I was on 3.2.6…
Firstly, there's a strange bug where sometimes the keyboard won't actually put onto the text field what you're typing but the keyboard app still acts like you're typing it in (suggestions change, you have to hold down the backspace button for longer to delete words that aren't actually on the screen), or the text will be inserted in the wrong place (as I was reminded while writing this!). A quick fix is to switch keyboard. I have Xposed installed, but not many modules that I didn't have installed on my previous Nexus 5 on stock Marshmallow that didn't have this issue.
Another issue is that the inline mic on my earphones doesn't work. Or perhaps the mic broke around the same time my Nexus 5 did, or it's a hardware problem with the phone? But the earphones and the playback buttons still work as well as they ever have, with the exception that the earphones buzz a bit when I'm charging (but the Nexus 5 had the earphone jack on top). This buzzing was actually a recording of me saying "Testing, testing, 123" etc with the inline mic right in front of my face.
These aren't *huge* issues for me but if anyone can help resolve them it would be great.
Xposed log and logcat here.