Related
Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).
Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.
What carrier are you on?
this happens to me too.its so annoying. im on att
Can't find the thread but it was pretty long.
nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.
This sounds like an att problem not a nrsux one problem
I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.
I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One
Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.
I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.
Sounds more like a network issue than a hardware issue, IMO
This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.
Hi all.
Im having a bit of a problem with my HD2. Whenever im in a call if i adjust the volume the earpiece goes dead, starts making a quiet buzzing noise and cuts the other person off. If you want to call the person back the phone wont let you back into the phone menu, and starts to act all strange and slow and you have to pull the battery off. I have been searching the forums for a solution but i havent found one yet. I have even flashed 3 different Roms to see if that fixes the problems but no.
Please HELP!!!
Adam.
i had exactly same problem, so tried another rom. and everything ok. but i did do a task 29 first.....try doing that then re-flashing your rom.
Don't forget to change radio to a compatible one with the rom.
Cheers you guys. At least im not the only one who has had this problem Phew. I will try what you both have said and see if it solves the problems! Thanks again.
YAY Fixed. Cheers you guys for all your help!!
Adam
adamlayzell69 said:
YAY Fixed. Cheers you guys for all your help!!
Adam
Click to expand...
Click to collapse
please specify what solved the problem for you so that other people going through the forum and its threads can get some idea and so that this thread gets meaningful "closure".
lets try to avoid using the forum as personal tech support, and instead add information where necessary so that it can truly be the knowledge base it aims to be.
Don't get any info
Fido. I don't get any info from this thread. This user has opened up a thread and after some time he is saying that Ok my problem solved. What this thread can give others in terms of knowledge and info - Nothing but time waste.
Guys please help me, i have the latest rom cm9 gingerbread made by Epsilon, and i have a great problem (i had this problem on all custom roms, miui, cm7 etc.) after a call, if the other person that i was engaed in a conversation does not hang up, i canno't get the screen back ON. the only workaround is to remove the battery and boot up again. any ideeas? it might have someting to do about the proximity sensor... i think.
Sorry if this problem was discussed on another topic, i could not find any relevant answer. thnx in advance.
Do you have a screen protector?
Edit: But why on dev section?
nope, don't use one.
didn't pay attention
I think the Epsylon's CM7 builds have an option to force the screen on after a call. This should do the trick.
Thnx very much. Haven't thought about that till now. I'll come back with a result. Hope it works.
@robertocav
Got it fixed yet ?
Since a couple of weeks i have the same problem and its pretty annoying.
I'm running CM7.1.0 jordan
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.
I don't have enough posts to post in the thread... but I wanted to say its awesome, but the back light setting for the capacitive buttons is not working. Also camera still crashes if you refocus too quickly. Reboot is required to get it back.
truckfreak69 said:
I don't have enough posts to post in the thread... but I wanted to say its awesome, but the back light setting for the capacitive buttons is not working. Also camera still crashes if you refocus too quickly. Reboot is required to get it back.
Click to expand...
Click to collapse
And that's why you're not allowed to post yet. Both are known, it's being worked on (the camera is a CM9 issue, but Task may fix it first, and if you don't touch to focus while it's focusing, it won't freeze). The backlight problem has been reported so many times it's not funny, so before you get 10 posts I STRONGLY recommend you spend some time reading the forums, and learning how to search effectively (hint: use google search and use XDA as one of the search terms).
Then your first experience won't be the flame-tastic one it would be otherwise.
I'm in kinda the same boat as you although I've done quite a bit of snooping on the forums and in the thread and have not found any answers to my issues. Just to get the formalities out of the way, yes I did a full wipe, and I've wiped each time I've flashed an update to the ROM. These issues have been present on each iteration of the ROM thus far, and was not present on stock.
Issue #1 - Notification LED stops working correctly if device is sleeping, the color works fine and will blink on the correct times to start but after a few blinks it either will go solid or stop blinking period.
Issue #2 - While listening to Google Music or local music with the screen off notifications cause the volume of the music to drop but then not return to the level it was at previous to the notification until you hit the volume rocker.
I don't have time to read through the entire 150 pages of threads. I was aware that it had been a problem, but the latest build was just released right before I posted that. I did not see anyone discuss them since the new post. But thank you.
truckfreak69 said:
I don't have time to read through the entire 150 pages of threads. I was aware that it had been a problem, but the latest build was just released right before I posted that. I did not see anyone discuss them since the new post. But thank you.
Click to expand...
Click to collapse
Search Thread > Reading 150 pages of posts. It is a forum tool for a reason