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.
Related
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.
Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S
just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5
+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.
me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does
+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.
Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!
Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse
DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it
Hello to all of you,
I am new the forum and I got my Omnia 7 just about 2 weeks ago. I really like it because of the excellent screen and build quality.
I also like the smooth and sleek feeling of Windows Phone 7.
However, I had regular issues during calls.
During about a third of my calls (including incoming and outgoing calls), I was not able to hear anything at some point during the conversation. The person called or the person who called me could also not hear me anymore.
The phone seems to work (no freeze) and the signal was ok. Turning the speaker on did not help.
Moreover, when I stopped calling and called back everything was fine and working again.
Sometimes it happened already when I picked up a call, sometimes after just a few words and sometimes in the middle of a longer conversation.
It seems to be random but regular, since about one out of three of my calls was interrupted.
It is really annoying and the phone is therefore going back.
However, I really liked the Omnia 7 and I would get another one, if the unit I got was just faulty.
So I would like to ask other Omnia 7 users if you have experienced a similar behavior of your Omnias during calls? Was my unit faulty or is it a general issue?
I would appreciate your feedback.
Thank you in advance.
Does really no one want to comment about how his Omnia 7 handles calls?
I would really appreciate your feedback, even simply stating your Omnia 7 works fine without any mic ans speaker issue.
I thus just added a poll to the thread, so that it becomes even easier to give some feedback.
Thanks in advance for your input.
Same with me on my Omnia 7 - A1 Telekom Austria
Spoke to Samsung but they were not able to help me out but sending me a contact info to a service partner (Extreme Communication in Vienna, btw)
Service Partner told me that there are issues with the Omnia 7 (amplitude control) and I should send my device to them...
As were are having the same troubles on approx 20 devices (95% of handed out devices) I have to check if repairing is an option (warranty from our provider)
will post later, if I have my device back...
No problems here, I've had an Omnia7 16GB since early February. It was unbranded about a week after I received it. No one I've heard of has had such issues but one who complains of "modem-like" sounds for him and the other part prior to missing a call. He also reported this happening every third time or so...
leoms17 said:
... but one who complains of "modem-like" sounds for him and the other part prior to missing a call. He also reported this happening every third time or so...
Click to expand...
Click to collapse
count me in...
having modem-sounds (or robot sounds) as well
and it's not only me - my co-workers have the same issues
but there are more issues:
it's annoying that my Omnia 7 (8gb version) is hardly able to receive calls at the first time (approx 75% of the incoming calls) - if I call back, most of the time it seems to be ok
these problems do not only affect my device, but about 95% of Omnia 7 we handed out to our co-workers
I had the chance to test a HTC 7 Trophy - none of the errors I have on my Omnia happened on the Trophy!
I have the same issue, using T-mobile in the netherlands, I just always assumed it was them.
I've noticed this only happens on 3G and 3G+ networks, if i turn off data and use the normal G network, I don't get call problems, which why I assumed it was t-mobile.
I'm having the same issue on most of my calls. In the beginning I thought it was a network issue. Haven't been able to figure out how to fix it so far. Will call Samsung support.
Has anyone here updated their ROM to the latest XENJK from samfirmwares.com? I had issues with the mic going silent during calls til I upgraded to that
Sent from my OMNIA7 using Board Express
simon marktl said:
count me in...
having modem-sounds (or robot sounds) as well
and it's not only me - my co-workers have the same issues
but there are more issues:
it's annoying that my Omnia 7 (8gb version) is hardly able to receive calls at the first time (approx 75% of the incoming calls) - if I call back, most of the time it seems to be ok
these problems do not only affect my device, but about 95% of Omnia 7 we handed out to our co-workers
I had the chance to test a HTC 7 Trophy - none of the errors I have on my Omnia happened on the Trophy!
Click to expand...
Click to collapse
Please post on your service results! Are you using 3G and 3G+?
Blade0rz said:
Has anyone here updated their ROM to the latest XENJK from samfirmwares.com? I had issues with the mic going silent during calls til I upgraded to that
Sent from my OMNIA7 using Board Express
Click to expand...
Click to collapse
I also have the latest from samfirmware.com. Maybe that does it? Someone?
Thanks for your comments so far...
At least I am not alone with this issue...
I am now really wondering if this could be a software/ROM/firmware issue given Blade0rz comment...
How can I check the firmware/ROM on the Omnia 7?...my Omnia 7 is unbranded from Germany and the "About" section in the settings of my Omnia 7 does not give any info on a build or version number...does anyone know?
@simon marktl:thanks for your feedback...actually 19 faulty units out of 20 sounds quite bad...I would be pleased if you could let us know if the service point could resolve the issue and especially how they did it once you get your device back...
@eqzgkxokwa: I would be pleased if you could let us know about the solution proposed by the Samsung support...thanks (by the way eqzgkxokwa, that´s a tricky nickname )
@ Phyx and leoms17: I actually use the 2G network 99.9% of the time...but as explained I have the issue regularly....so it is not limited to 3G or 3G+...but if 3G off helps for you it just makes the issue even more curious...I do not think it is due to the network, rather something is going on with the phone...
in diagnostic screen hit *#1234# you'll get all your info. Firmware ending in JK1 is the latest.
Thanks leoms17...I may sound stupid but how do I actually get in the "diagnostic screen"?...I did not find it in the menu, so I assume there is some trick...actually I do not want to brick the phone or do something wrong...
Is there no possibility to get a simple info about the firmware without using a crazy code?
also have this issue, assumed it was a poor signal or something like the death grip. Does not seem to make a difference whether im being called or place the call myself.
I got it several times, suddenly it just goes silent. Holding the phone away from the ear so the diplsay turns on seems to make it work again but not for very long.
I had the original T-mobile Germany branded firmware I8700DTMJJ6, updated to JK1 yesterday, but did not test if its fixed now.
One final idea would be to play around with the volume settings in diag mode, increasing volume for incoming calls or something.
Btw, did anyone notice that there is absolutely no background noise during a call, even if the person is in a noisy environment?
leoms17 said:
Please post on your service results! Are you using 3G and 3G+?
Click to expand...
Click to collapse
Yes, I'm on 3G and 3G+
Turning off 3G seems to help a little bit - at least I'm not running into troubles as often as having 3G enabled...
malin_77 said:
@simon marktl:thanks for your feedback...actually 19 faulty units out of 20 sounds quite bad...I would be pleased if you could let us know if the service point could resolve the issue and especially how they did it once you get your device back...
Click to expand...
Click to collapse
good morning
as soon as I have a feedback from my provider if the repairing is covered by our warranty contract, I'm going to send in a few more phones to the service point...
of course I will post the results here, but could take a while...
til later
simon
I've had this issue with my Omnia 7 (T-Mobile US) as well. There were a couple instances where I answered a call and was not able to hear the person on the other end.
malin_77 said:
Thanks leoms17...I may sound stupid but how do I actually get in the "diagnostic screen"?...I did not find it in the menu, so I assume there is some trick...actually I do not want to brick the phone or do something wrong...
Is there no possibility to get a simple info about the firmware without using a crazy code?
Click to expand...
Click to collapse
just dial ##634#
wait about 2 seconds, than you are in the diag menu
after dialing ##634# you'll find diagnosis on your phone for future use
leoms17 said:
I also have the latest from samfirmware.com. Maybe that does it? Someone?
Click to expand...
Click to collapse
I had this issues with the original firmware from my provider (I8700XXJJ3)
and I still have them with
Phone I8700XXJK1
PDA I8700XXJK1
CSC I8700XENJK1
Software on Phone itself is 7.0.7008.0, no NoDo available yet
Maybe the new firmware I8700XXKA1 (January) helps out - but I wasn't able to download it anywhere
Same issues here
I have issues with both modem/robot-calls but lately it's gone from 1/3 of the calls beeing robot to 3/4 of the calls loosing all sound after 20-60 seconds. Robotic cals are not as common. For me I have problem only when I receive calls and never when I make the call.
I have had my Omnia in for service a month ago but the short message from them was that they found no problems. They upgraded the firmware to the latest version but I still have issues as stated above.
My radio hardware version is
0.0.0.2
I have seen posts where radio hardware is much higher. Can the problem be related to old radio hardware?
I am hoping nodo and new firmware from Samsung will fix this but so far I havn't got it.
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'll try to make this quick. When making phone calls with my Nexus 4, I'm experiencing two issues.
1) I sound choppy to the other person. For example, I'll be talking and I'll be going in and out. I've tested this with different callers and it's true for all of them. They all say I sound choppy.
or
2) Sometimes, neither of us will hear each other for a few seconds before sound returns. Like, I'll say something, and the other person will sound quiet, and I'll go "hello?" and they'll say "I said, oh okay." As if it didn't get the immediate response. The same thing happens vice versa, where I'll respond and they'll ask if I said anything cause they didn't get it.
Issue 2 happens a lot less. It's issue 1 that is driving me nuts.
Is anyone else experiencing this?
I'm on Tmobile and I've switched SIM cards twice, tested the network with my family's phone that are part of the same plan (perfect call quality, so I don't believe it's Tmobile), and I've had Google replace my phone. The RMA still has the same problem, so I'm reaching out to the forum to see if anyone else is experiencing this too, and more importantly, has a solution or at least know what's the culprit.
This only started happening with the Nexus 4. When I had my Galaxy Nexus on the same line and network, calls were fine.
I called Google a second time, and they could immediately hear what I was talking about. The choppiness was really bad, they said, and they insisted that it's hardware related (though I'm not convinced. Could I have gotten two defective Nexus 4's in a row? Possible, I suppose). They convinced me to give it one more go, and so I'm waiting for another RMA to arrive.
Any thoughts, help? I haven't been able to find much on the web about it.
Thanks.
If you got 2 defective Nexus 4s in a row it's either you are really unlucky or it's a signal related issue, like your signal could be weak causing choppiness, or maybe a problem with your carrier? I guess. You should probably try a 3rd time before looking for your carrier and asking them about the signal. Try moving your SIM card to another phone to see if it's the problem with the carrier. If it's ok on another phone, get it replaced a 3rd time I guess.
Good luck
I have a OnePlus 6T with Oxygen OS 9.0.11, no root.
The phone worked perfectly until yesterday, when I was having a call and suddenly I began hearing a very unpleasant noise coming from the top speaker. Even after the call ended, I could still hear it and even at this time I do it too. It is not by any means loud, I can only hear it when my ear is really close to the speaker, typically when I would place my phone on my ear to take a call. The problem is that it is always there in the background. I must also mention that the phone didn't suffer any physical damage.
The sound itself is not a continuous beep. It interrupts at some times and it sounds like radio interferences or static, but of high pitch. Coil whine is similar to this noise too.
Now, I have tried rebooting the phone and turning wi-fi and mobile data on and off. As soon as the phone powers off, the noise disappears. But immediately after I start it, the sound begins as well, so I thought it may be a hardware issue. But then I played with the camera. When inside the camera app, if I switch to the front camera and place my ear next to the speaker: magic! The noise seems to disappear. If I exit the camera app, however, it returns.
I've already spoken with those at OP support, and after recommending a factory reset they suggested I should send it for inspection. The problem is that I need the device and can't have it away from me for a week.
What do you think? Have you ever heard of issues like this one? Should I downgrade the software to an earlier version?
I have the same problem , and a lot of users of 6t have this problem, i decided not to send it to service center and I stopped paying attention to it
lwajer said:
I have the same problem , and a lot of users of 6t have this problem, i decided not to send it to service center and I stopped paying attention to it
Click to expand...
Click to collapse
How long have you been noticing it for? Did you also encounter it on earlier versions of the OS?
I don't have any issues with the earpiece. You might try to reboot your phone into the stock recovery and clean the system catch that might help!
Caltinpla said:
I don't have any issues with the earpiece. You might try to reboot your phone into the stock recovery and clean the system catch that might help!
Click to expand...
Click to collapse
Tried that already... no effect . Now I've just factory reset the phone and the buzz is still there. Nothing seems to work, I guess I'll just have to get used to it.
unowen1 said:
How long have you been noticing it for? Did you also encounter it on earlier versions of the OS?
Click to expand...
Click to collapse
Since i bought the phone. I wrote about it with support of oneplus and even with the bug department but nothing in the system did not find, I was instructed to send a phone to the service but not somehow very irritating because you can not hear it when you do not have a phone very close to your ear.
unowen1 said:
Tried that already... no effect . Now I've just factory reset the phone and the buzz is still there. Nothing seems to work, I guess I'll just have to get used to it.
Click to expand...
Click to collapse
It appears you have a hardware related defect phone so upgrade or downgrade your OS won't help!
Had a similar issue with a Samsung phone once. Hardware fault; warranty service was the only solution.
Caltinpla said:
It appears you have a hardware related defect phone so upgrade or downgrade your OS won't help!
Click to expand...
Click to collapse
Yes, that's what I'm thinking too... Though, I don't get why it started doing it so randomly. I've used the phone just fine for one and a half months and it worked perfectly. Now, after no damage whatsoever, this noise appears... strange.
Is the problem solved? I've the same issue with my OnePlus 5T.
OP5T_25 said:
Is the problem solved? I've the same issue with my OnePlus 5T.
Click to expand...
Click to collapse
No, the problem is still there. However, I can still only hear it when the camera is not active. While in the camera app the noise disappears.