I came Across a problem the last few week that the control on the headset doesn't work, some times they do work for a minute or two and than stop again.
Did anyone else encountered this problem?
Did someone managed to fix it?
I removed the buttons and it all seems fine, clean it a bit with high pressured air, but nothing.
I've had similar probs with Bluetooth buttons (including the car dock). I thought it may be related to CM6, since my probs started about the same time...
What ROM are you running?
Sent from my Nexus One using XDA App
Yes. Same problem dude......(cm6 stable)
Sent from my Nexus One using XDA App
Related
My phone has been doing this for 2 or 3 days now. When I accept an incoming call, the phone automatically enters speakerphone mode.
When a BT headset is connected, it is fine.
Anyone got a clue why it is doing this? I havenet installed any apps which should have this effect.
RTR
Been looking into this all night, with no luck. Has anyone seen this before?
Not had any calls come in on mine yet so can't comment on whether I am affected. I would have thought it would be well known about though if it was widespread.
Are you using stock rom? Tried re-flashing the RUU?
Had this to you need to make someone call you and keep trying with the button to switch between speaker or ear and eventually i got it right! Hold it against your ear then remove it and try button again thats how i did it!
Sent from my Desire HD using XDA App
Same here with that issue ever since those new updates started
Sent from my PC36100 using Tapatalk
Mine too but it hardly ever does it now. A sensor tries to detect how your phone is positioned and switches to speaker. It seems to go away on the stock rom, so persevere on the stock rom. It all worked out for me eventually. Word of advice though, DISABLE SENSE until it's ready. It makes your contact icons in messages disappear. Htc always releases questionable software which should be described as beta. If you use bluetooth for music, stick with stock for now. Yadda yadda. All in all, the dhd. Rules. Oh ya, anyone know how the htc hd2 rund witb android 2.2. I saw lots of great deals on ebay to buy a broken one and fix tbe software to run android. I just want a new toy really.
Sent from my Desire HD using XDA App
I had this for a while - turned out to be an iffy setting in my profile manager/switcher (phoneweaver). Are you using anything like that?
FIXED: Oh my word, how simple was this...
Should have said, I'm on stock everything as I have a poor track record with having to send stuff back to manufacturers to be fixed.
After spending all night looking for a solution, and trying a couple of things found on other forums (install phonespeaker app and turn it off in that - doesn't work BTW), I decided this morning to remove the possibility that the phone had simply got its panties in a bunch, switched it off properly and removed the battery. 10 minutes of being denied a power source has cured it. Most bizarre.
Thanks for the suggestions guys.
RTR
Sent from my Desire HD using XDA App
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.
Well this is an interesting issue that crept up on me a few days ago. If I go to switch on my Bluetooth, the switch will move to on position but the Bluetooth will remain off. Reboot does nothing.
So after poking around here and there I noticed in tibackup that Bluetooth share 4.2.2 is uninstalled. As soon as I restore it, Bluetooth works again. However somehow it keeps uninstalling itself and I need to repeat the process again before it lets me switch on Bluetooth. I can't figure out the cause of this problem and how it's u installing on its own. Any help and guidance would be appreciated! Thanks
Well I've found that the Bluetooth share uninstalls after a reboot. What is causing this? Permissions issue? Anyone?
Sent from my Galaxy Nexus using Tapatalk 2
Not sure what's causing your issue. More info would help. Such as what ROM you are using if any etc
Sent from my Nexus 10 using XDA Premium HD app
I'm stock and rooted with an extended power menu mod.
I might have found to problem, still testing. There was an update to that Bluetooth app that I uninstalled and it seems to be working now.
If I don't encounter the problem for a few more days I'll call it solved Lol.
Sent from my Galaxy Nexus using Tapatalk 2
I have a Nexus 4 that is about 2 weeks old. I love the phone, all except for the Bluetooth behavior. I couple my bluetooth heart rate monitor to the N4, and in order to do this in the morning, I have to restart the phone almost 100% of the time. I can't even turn the BT on with the slide switch, as soon as I push it to on, it goes right back to the off position. As soon as I restart the phone, all is well. Now I have read numerous complaints on other forums and on the Google help page with similar Bluetooth connection problems. Google recommended in several places that a total reset of the phone would fix these problems, which I thought was ridiculous, since my phone did this from day one. Anyway, some people have reset their phone as many as 3 times, and the problem is still there, so obviously, that was not a fix. Other Nexus 4 users have apparently got an RMA, a new phone, and have the same issue.
So it sounds like this is a software issue, and hopefully the new version of Jellybean will fix this problem, but somehow, I think that this issue is not being addressed, Any thoughts on this? h t t p ://productforums.google.com/forum/#!topic/mobile/nVjWKiUvvPs
This is a known bug, there's is no fix as of right now. I've had this issue on all 3 of my Nexus 4's.
It is software, remember 4.2 brought a new Bluetooth stack. I would assume that there are more than a few bugs left to work out.
Sent from my Nexus 4 using Tapatalk 4 Beta
Hopefully the next update will remedy this. They are recertifying the Bluetooth right?
Sent from my Nexus 4 using Tapatalk 4 Beta
Hi everyone
Recently I've been having problems with the USB connection.
I was on the stock rooted ROM, and I plugged in the phone and it came up with a message USB device not recognised because it malfunctioned. Tried different ports, cables and different computers, same thing.
Then I changed this morning to the Nexus 5 experience ROM. It worked initially. Now the problem has come back. However occasionally it does work and the windows explorer window pops up, but then after a second or two it goes away and the error message reappears.
What could be causing this?
It was fine a while ago.
Also, when it doesnt work, the battery settings thinks its charging on AC and not USB.
Sounds like it's a hardware issue
Sent from my Nexus 5 using XDA Free mobile app
Hmm, its likely but could a hardware issue suddenly present itself with no apparent cause?
raze599 said:
Hmm, its likely but could a hardware issue suddenly present itself with no apparent cause?
Click to expand...
Click to collapse
Absolutely, it worked for a little while and then didn't. Try flashing the factory image and see if it's still there. I don't think it's a software issue
Sent from my Nexus 5 using XDA Free mobile app
OK I will try that.
The only new thing I've been using with it is a new car charger. It works perfectly fine, but if it was giving slightly too much or too little voltage could it have caused this?
raze599 said:
OK I will try that.
The only new thing I've been using with it is a new car charger. It works perfectly fine, but if it was giving slightly too much or too little voltage could it have caused this?
Click to expand...
Click to collapse
I doubt it. There's built in circuitry that would take care of voltage or current fluctuations
Sent from my Nexus 5 using XDA Free mobile app
Just a quick update. I smashed the screen a few weeks ago so I had to replace it. When I finished replacing the screen this also started working lol dunno what happened there.