Callers hearing their echo in redmi note 7 pro - Xiaomi Redmi Note 7 Pro Questions & Answers

I bought redmi note 7 pro on the very first sale from Flipkart on 13 march 2019
But unfortunately i had a problem in the handset..
The caller was hearing his own echo..on the receiver side during normal calls and..even on whatsapp or facebook messenger calls
I got the handset replaced ..
But unfortunately i am having the same problem even now..
I chatted with your customer support and even called them atleast 4 times..and everytime they told me to wait for an update..but i had received that update..(miui 10.2.7.0) but still the problem is not getting resolved..they told me to factory reset the device..but it was of no use..they told me to swap the sim cards .but no use..
And i think i am the only one facing this issue
What should i do ?

Same problem
I am facing the same issue on Redmi note 7 pro. I also went for a replacement but the replaced product also has the same issue. I don't know what to do?? ?

Aurek said:
I am facing the same issue on Redmi note 7 pro. I also went for a replacement but the replaced product also has the same issue. I don't know what to do??
Click to expand...
Click to collapse
when did u buy?

Aurek said:
I am facing the same issue on Redmi note 7 pro. I also went for a replacement but the replaced product also has the same issue. I don't know what to do??
Click to expand...
Click to collapse
update your device its fixed

I am on 10.2.8 and problem still persist

Replacement handset has same problem
Replaced handset, did factory reset, updated MMuI 10.2.10.0. Still problem persists.
Absolute peice of rubbish junk.
Is there a way I could ask for refund.
Learnt my lesson hardway.. Never trust Chinese crap... At least not the latest release to market.
Regards
Kk

I am having Redmi Note 7, I am having the same issue. After replacement of Device, the problem is still the same.
Done factory reset
Tried multiple Sim card
If I use the headphone issue get resolved but without headphone, you will get the echo.
Anyone here who got this issue resolved.

Maxpayne_12 said:
I bought redmi note 7 pro on the very first sale from Flipkart on 13 march 2019
But unfortunately i had a problem in the handset..
The caller was hearing his own echo..on the receiver side during normal calls and..even on whatsapp or facebook messenger calls
I got the handset replaced ..
But unfortunately i am having the same problem even now..
I chatted with your customer support and even called them atleast 4 times..and everytime they told me to wait for an update..but i had received that update..(miui 10.2.7.0) but still the problem is not getting resolved..they told me to factory reset the device..but it was of no use..they told me to swap the sim cards .but no use..
And i think i am the only one facing this issue
What should i do ?
Click to expand...
Click to collapse
My device got replaced 2 times (Note 7) but still, the issue is same. Could you please share me your job sheet number. As service center team saying that issue is reported only from me . I will also share jobsheet ID for your referance.
Hello All please share your jobsheet id to get this issue resolved.

Could you please your jobsheet details ? Which will help all

Remove silicone cover from the device. Hope issue will never persist.

All of you fellas have a backcover installed.Remove the back cover and check

This is killing me man. I really need my back cover.

Even I am facing the echo issue. Also sometimes screen became inactive during call and i am not able to see or do anything on screen.
Is there any solutions available. Please suggest.

vlouis said:
It's just a theory, but... the phone have two microphone, the second, in top it's for noise cancelling. These two microphones if not syncornized well, the echo appear. If without cover the sound it's clear, no echo, check if the silicone case have hole where the second mic.
Click to expand...
Click to collapse
I saw posts about the second noise canceling mic. Anyways, I thought it had to be the design of the case that had to carry sound from the earpiece to mic or mic to 2nd mic or whatever.
Note the original openings on the side of the case.
Therefore I carved out section in the case where you find the main microphone. (used a red hot nail to do that)
Echo is now gone.

Solved it Myself
If your phone is rooted download Build.prop editor (By J Rummy apps). Navigate to System>Build.prop through the app.
Check for the following codes in the file
#Audio
ro.qc.sdk.audio.ssr=false
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
If the aforesaid lines are not there in that file, simply paste them there and your echo problem will be resolved.

Related

[Q] nexus 5 jack problem

I bought a nexus 5 like 10 days ago. It was working perfectly fine but recently my earphone jack started giving problem. Whichever earphones i use (and I've tried like 5 different ones) but the right earpiece gives a very faded sound where as left works fine. The phone has not been damaged at all. Can it be a software issue or is it faulty hardware? What should i do?
rohan.10594 said:
I bought a nexus 5 like 10 days ago. It was working perfectly fine but recently my earphone jack started giving problem. Whichever earphones i use (and I've tried like 5 different ones) but the right earpiece gives a very faded sound where as left works fine. The phone has not been damaged at all. Can it be a software issue or is it faulty hardware? What should i do?
Click to expand...
Click to collapse
Faulty hardware. If you bought it new or used from eBay or something, you should be able to return it. If there's no warranty available for it, you can repair it yoursefl. LGs are very modular, and you can pick up the headphone jack module for $7 on eBay. Go to ifixit.com for a teardown tutorial.
rohan.10594 said:
I bought a nexus 5 like 10 days ago. It was working perfectly fine but recently my earphone jack started giving problem. Whichever earphones i use (and I've tried like 5 different ones) but the right earpiece gives a very faded sound where as left works fine. The phone has not been damaged at all. Can it be a software issue or is it faulty hardware? What should i do?
Click to expand...
Click to collapse
It's probably a hardware issue. You might have dropped the phone somewhere or the phone might got damaged while in your pocket by getting in contact with something else which caused pressure on it and the right(clip, in the jack) got damaged. You can go and show it to someone who repair phones and he might help you out with a cheap method(except of doing it yourselve which might creat another problem, but you can always find tutorials and try to do it yourselve which I prefer no to do in this case). Good luck!
If any further help needed or have some other question just go on this thread http://forum.xda-developers.com/showthread.php?t=2911338
Please press the thanks button if you think I helped

Google Pixel Mic and Speakers not working

Hi, the speakers and microphone on my Google pixel do not work and I also noticed that video recording and the Google Assistant would refuse to work as well. My pixel also fails to recognise that a headphone has been connected to the the headphone jack. I got this phone second hand from someone but they told me they had factory reset the phone but the speakers and microphone would still not work so I think it is a hardware issue.
Help would be greatly appreciated thank you ?
jameskim153 said:
Hi, the speakers and microphone on my Google pixel do not work and I also noticed that video recording and the Google Assistant would refuse to work as well. My pixel also fails to recognise that a headphone has been connected to the the headphone jack. I got this phone second hand from someone but they told me they had factory reset the phone but the speakers and microphone would still not work so I think it is a hardware issue.
Help would be greatly appreciated thank you ?
Click to expand...
Click to collapse
It's a hardware defect affecting pixel devices produced before January 2017. It would eventually happen to the phones produced in 2016 and there's no way to tell when it would happen. Only fix is to change the motherboard. If you're able to return the phone then do it.
Arju said:
It's a hardware defect affecting pixel devices produced before January 2017. It would eventually happen to the phones produced in 2016 and there's no way to tell when it would happen. Only fix is to change the motherboard. If you're able to return the phone then do it.
Click to expand...
Click to collapse
Unfortunatly I bought a second hand pixel and did not know this issue until I tried to use audio. I'm trying to repair it myself and I read in another forum that replacing the headphone jack or the mic/speakers would solve the problem. Do I need to buy another mother board and replace it with the current one I have right now?
jameskim153 said:
Unfortunatly I bought a second hand pixel and did not know this issue until I tried to use audio. I'm trying to repair it myself and I read in another forum that replacing the headphone jack or the mic/speakers would solve the problem. Do I need to buy another mother board and replace it with the current one I have right now?
Click to expand...
Click to collapse
I personally have not done any such procedure so would let someone else answer. What I could do is to identify when your phone was produced to narrow down if that could be the issue. If that's the same then the motherboard needs changing and you might just find a beaten up working pixel for cheap and try swapping the parts unless you find the motherboard for cheap though. Could go to settings>system>about phone>status>serial number. Give is the 5 first characters. Mine is FA77M. I could read from this that it's produced in taiwan on the 21st-07-2017.
Arju said:
I personally have not done any such procedure so would let someone else answer. What I could do is to identify when your phone was produced to narrow down if that could be the issue. If that's the same then the motherboard needs changing and you might just find a beaten up working pixel for cheap and try swapping the parts unless you find the motherboard for cheap though. Could go to settings>system>about phone>status>serial number. Give is the 5 first characters. Mine is FA77M. I could read from this that it's produced in taiwan on the 21st-07-2017.
Click to expand...
Click to collapse
It says that my serial number is FA69H
jameskim153 said:
It says that my serial number is FA69H
Click to expand...
Click to collapse
FA – Taiwan Taoyuan B factory
69H - 2016-September-17th.
Your device is probably suffering from motherboard issues unfortunately.
Arju said:
FA – Taiwan Taoyuan B factory
69H - 2016-September-17th.
Your device is probably suffering from motherboard issues unfortunately.
Click to expand...
Click to collapse
I saw some units @ the shop as I'm looking to buy one. Are any of these safe from mic problem? Some of it is still nougat. Thank you!
FA6A6
FA69H
FA69G
Hiyaslalabs said:
I saw some units @ the shop as I'm looking to buy one. Are any of these safe from mic problem? Some of it is still nougat. Thank you!
FA6A6
FA69H
FA69G
Click to expand...
Click to collapse
FA6A6 - Produced in Taiwan Taoyuan B factory - 2016-October-6th
FA69H - Produced in Taiwan Taoyuan B factory - 2016-September-17th
FA69G - Produced in Taiwan Taoyuan B factory - 2016-September-16th
From what I understand, all devices produced in January 2017 and after should have this issue fixed. Pixels made in 2016 is pretty much a ticking "bomb"... someday the issue will occur. I personally would stay away from the devices you mentioned. If you find a device with the third character being 7 then you should be safe. My device is FA77M which reads - Produced in Taiwan Taoyuan B factory - 2017-July-21st, which should be safe.
Arju said:
FA6A6 - Produced in Taiwan Taoyuan B factory - 2016-October-6th
FA69H - Produced in Taiwan Taoyuan B factory - 2016-September-17th
FA69G - Produced in Taiwan Taoyuan B factory - 2016-September-16th
From what I understand, all devices produced in January 2017 and after should have this issue fixed. Pixels made in 2016 is pretty much a ticking "bomb"... someday the issue will occur. I personally would stay away from the devices you mentioned. If you find a device with the third character being 7 then you should be safe. My device is FA77M which reads - Produced in Taiwan Taoyuan B factory - 2017-July-21st, which should be safe.
Click to expand...
Click to collapse
Thanks for that information mate. It's hard to find that version of yours though.
I have a november 2016 pixel and uBreakiFix (canada & US, but I did it through Canada) replaced the motherboard free of charge even 8 months outside of my warranty period.
I'd consider going to them.
Unfortunately I bought it second hand and I don't have the receipt ( I live in Sydney btw), so even if I did go to my local ubreakifix I don't know if they'll fix it for me.
Audio and microphone stopped working about 1 month ago.
It stopped working on Phone (the local Google app), WhatsApp, Skype & HangOuts.
I could still hear podcasts and music and YouTube. Though I did notice that bluetooth and wired headphones with microphones didn't appear to work.
I tried Safe Mode.
The issue still occurred.
I did a complete Factory reset of the phone.
The issue still occurred.
I have only installed the apps that I use constantly, which includes WhatsApp and Hangouts.
The issue still occurs with bluetooth and wired headphones.
---------- Post added at 02:04 AM ---------- Previous post was at 01:58 AM ----------
Hiyaslalabs said:
Thanks for that information mate. It's hard to find that version of yours though.
Click to expand...
Click to collapse
FA69D0301461
What about this? I have same issues help me
Similar Issue, but I suspect MindTheGapps or Lineage Update
My sons Pixel has similar issues. It started around August.
During Calls he could listen but the mic did not work. Then in Whatsapp and Youtube app videos would not play, while the same videos from youtube played fine in the Browser app.
Usually after restart it works until Spotify crashes the phone, or at least Spotify was active while the phone crashed. Why comes MindTheGapps with pre-installed Spotify anyway? After install from Playstore there are two versions on the phone.
Sometimes after a hard phone crash, mic and speaker work for a while, also a short time after factory reset (until Spotify, Youtube and Whatsapp are reconfigured), then mic and speaker stop to work again. Sometimes the Speaker works for a longer period but the mic does not.
Sometimes there is a message that the system process has stopped responding and if I want to stop it or wait. After the next phone crash this message disappears.
Its hard to believe that this is a hardware issue, while the phone falls into the manufacturing dates of the reported motherboard issues.
Next thing I am going to try is to use OpenGapps and if that does not help, revert to Stock ROM. Maybe this resolves the issue.
Thanks.

Earpeice, Microphone, and Headphone Jack not working, even after reboot and updating

I've been having problems with my pixel. After about 20 mins after rebooting the phone the mic, Earpeice, and Headphone Jack don't work. It just happened out of the blue one morning and it's stopped working since. I've already completely wiped the phone with twrp and flashed Android P, nothing is working. Any ideas?
It's a hardware issue with the audio codec inside the motherboard. If you got warranty still you can replace it from Google.
Alaadragonfire said:
It's a hardware issue with the audio codec inside the motherboard. If you got warranty still you can replace it from Google.
Click to expand...
Click to collapse
Is this confirmed? My Nexus 6P recently died, so I picked up a Pixel secondhand to replace it. It worked fine until I updated it to 8.1 and then all these issues started, which made me think it was software related. I've read a ton of threads all over the internet on this, and I see people replacing the mic/charger port, the headphone jack, and the daughter board and still having the same issues.
I saw somewhere (can't remember where now) that someone finally had this problem fixed by installing the Android P preview. Has anyone else had any success with that? Since I got this secondhand, I can't just get a warranty repair/replacement. I can send it back, but then I'd have to pay almost twice as much to get a Pixel 2, so I'd prefer to get this working if possible.
Thanks
velvet_man said:
Is this confirmed? My Nexus 6P recently died, so I picked up a Pixel secondhand to replace it. It worked fine until I updated it to 8.1 and then all these issues started, which made me think it was software related. I've read a ton of threads all over the internet on this, and I see people replacing the mic/charger port, the headphone jack, and the daughter board and still having the same issues.
I saw somewhere (can't remember where now) that someone finally had this problem fixed by installing the Android P preview. Has anyone else had any success with that? Since I got this secondhand, I can't just get a warranty repair/replacement. I can send it back, but then I'd have to pay almost twice as much to get a Pixel 2, so I'd prefer to get this working if possible.
Thanks
Click to expand...
Click to collapse
It is confirmed unfortunately. Many people had this problem with their devices that are manufactured in 2016 and before January 2017. If you are able to send it back I suggest you do.
I have a november 2016 pixel and uBreakiFix (canada & US, but I did it through Canada) replaced the motherboard free of charge even 8 months outside of my warranty period.
I'd consider going to them.
Thanks guys. I sent the phone back. It was a certified refurb through Amazon, so I should get a full refund once they get the phone back in the mail. I want to order another one, but how do I verify that it was made after Jan 2017?
Thanks!
truvatech said:
I have a november 2016 pixel and uBreakiFix (canada & US, but I did it through Canada) replaced the motherboard free of charge even 8 months outside of my warranty period.
I'd consider going to them.
Click to expand...
Click to collapse
I want to second this experience for anybody that finds this thread. My wife's phone was purchased Dec 2016 and lost microphone/speaker last week. Used the help feature to chat with google, they sent us for repair and uBreakiFix replaced the motherboard at Google's expense 8 months out of warranty. I'm very happy to see Google standing behind their device.
OK, so here's my 2pence worth... I have a Pixel manufactured in 2016 and it has been faultless for 10 months. I have been very craeful with it. I applied the 5 July 2018 Security Update and my microphone stopped working. I tried all the usuals to fix it but nothing. As a last resort I enrolled in the Android P beta program and installed it. My microphone started working again with Android 9. However, with the latest update build PPP5.180610.010 the microphone is buggy again... so I think it's a software driver issue. Anyone else want to confirm this?
plittlefield said:
OK, so here's my 2pence worth... I have a Pixel manufactured in 2016 and it has been faultless for 10 months. I have been very craeful with it. I applied the 5 July 2018 Security Update and my microphone stopped working. I tried all the usuals to fix it but nothing. As a last resort I enrolled in the Android P beta program and installed it. My microphone started working again with Android 9. However, with the latest update build PPP5.180610.010 the microphone is buggy again... so I think it's a software driver issue. Anyone else want to confirm this?
Click to expand...
Click to collapse
I don't think so. Flakey hardware - not a complete failure, but bad enough connection that it isn't reliable. Had you done a complete factory reset, I bet it would have worked for a bit. Then, when the signal is bad for long enough the system can't deal with it and the behavior re-surfaces. You could design resilient software to account for the slow failure. At least that is my guess, based on the experience I had (swapping SIMS would fix the phone for a while, sometimes microphone would go out first, sometimes wireless data).
Note10.1Dude said:
I don't think so. Flakey hardware - not a complete failure, but bad enough connection that it isn't reliable. Had you done a complete factory reset, I bet it would have worked for a bit. Then, when the signal is bad for long enough the system can't deal with it and the behavior re-surfaces. You could design resilient software to account for the slow failure. At least that is my guess, based on the experience I had (swapping SIMS would fix the phone for a while, sometimes microphone would go out first, sometimes wireless data).
Click to expand...
Click to collapse
Damn, hope not
OK, so what serial number do I need to check for on eBay, so that I get a 2017 manufactured Pixel?
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
udahy.manna said:
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
Click to expand...
Click to collapse
Yes, 3 weeks is exactly the same time as when I updated to the 5 July 2018 security update, and then my microphone started going funny. Please try going to SAFE MODE and then clear the CACHE from the Phone app.
Press and hold the power button to bring up the power options. Press and HOLD on the Restart icon. Choose SAFE MODE.
Once in SAFE MODE, press and hold the PHONE app icon, and choose the 'i' for information. Choose Storage, then press the CLEAR CACHE button.
Reboot the phone again in SAFE MODE, and try calling your OWN mobile number then leave a message.
Tell me if your microphone is working again.
plittlefield said:
Yes, 3 weeks is exactly the same time as when I updated to the 5 July 2018 security update, and then my microphone started going funny. Please try going to SAFE MODE and then clear the CACHE from the Phone app.
Press and hold the power button to bring up the power options. Press and HOLD on the Restart icon. Choose SAFE MODE.
Once in SAFE MODE, press and hold the PHONE app icon, and choose the 'i' for information. Choose Storage, then press the CLEAR CACHE button.
Reboot the phone again in SAFE MODE, and try calling your OWN mobile number then leave a message.
Tell me if your microphone is working again.
Click to expand...
Click to collapse
No bro.. I tried like you said..but not working..
udahy.manna said:
No bro.. I tried like you said..but not working..
Click to expand...
Click to collapse
That's a shame.
I can absolutely confirm THAT MY PROBLEM IS A SOFTWARE ISSUE... I have just installed an update to the PHONE app from Google on Android 9 and made 3 telephone calls this morning with NO PROBLEMS at all.
Here's the summary again for those that it might help.
1. Pixel on 8.1.0
2. Update to 5 July 2018 Security Patch
3. Microphone not working
4. Enroll in Android 9 P beta
5. Install Android 9 beta
6. Microphone now working
7. Sometimes microphone fails
8. Reboot in SAFE mode and clear Phone app CACHE
9. Reboot in SAFE mode and make a few calls with microphone working
10. Update to latest Phone app version 22.0.204206752 (31 July 2018)
11. Phone and Microphone working perfectly
That's all I can say really.
Paul
OK, so it's been another trouble free day with the phone, making calls and using Google Assistant with my WORKING MICROPHONE fixed by software... and not a soldering iron
I made and received a dozen calls and asked Google for help with all sorts.
So, things can be fixed without sending it away.
My serial number begins FA69M which means...
FA = Where it's been built
6 = Year of production (2016)
9 = Month of production (September)
M = Day of production (21)
...so it's a pre 2017 Pixel Sailfish which had the problem and now it doesn't thanks to Android 9 beta.
Paul
udahy.manna said:
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
Click to expand...
Click to collapse
Did you fix?
Damn, I've been thinking to buy it, the 128GB model, since I'm not kinda guy who changes cellphone like cloths, just updating for another 2 year or more. I'll be updating the device to Android Pie for the app support. Please advice me if I should buy it or not. I'm fully convinced to buy Google Pixel 128GB model since it is compact has a great camera and it provides a real smooth experience with stock android. only thing holding me back is that MicroPhone Issue that people are complaining about. Please help me make the decision.
Sam33t said:
Damn, I've been thinking to buy it, the 128GB model, since I'm not kinda guy who changes cellphone like cloths, just updating for another 2 year or more. I'll be updating the device to Android Pie for the app support. Please advice me if I should buy it or not. I'm fully convinced to buy Google Pixel 128GB model since it is compact has a great camera and it provides a real smooth experience with stock android. only thing holding me back is that MicroPhone Issue that people are complaining about. Please help me make the decision.
Click to expand...
Click to collapse
i had this issue a while back but since ive updated to the december update i havent had any mic, speaker issues at all. its the best phone to me ive had...and ive had alot. i say get it..im gonna get the pixel 2 xl and the pixel 3 as well..

I think this call quality issue is actually a SIM issue

Hi there,
I'm one of the many that's been hit by the call quality issues of the Pixel 3. I use a Pixel 3 white with Tele2 in the Netherlands and I cannot make or receive calls when the problem hits. I also have the problem where I'll cut out every 20 seconds or so any people will tell me they can't hear me.
Restarting it fixes it temporarily and then it just goes on again. It's ridiculous. I'm on my second phone already.
I've found that when this happens, when I go to settings in the Phone app, go to calls and then call forwarding or additional settings, nothing loads. It may even say SIM read error. When I restart the phone, and I can make phone calls properly again, these settings load again. Seeing as these settings are loaded from my SIM settings, I have a feeling something with the phone reading the SIM isn't quite right.
Got T-Mobile NL and especially at home, most times, people can't hear me properly.
call quality
I'm on verizon, and when I call into work conferences from home, I get complaints that I sound like I'm underwater. I've tried disabling advanced calling and that doesn't change anything (was a recommendation in a Google forum). I haven't experienced dropped calls yet, but I don't make a ton of phone calls, so that doesn't mean much.
There are tons of threads like this talking about sound issues when calling. For me the only problem I have is when someone calls me they cant hear me on speaker phone until I turn that off and talk on the regular mic. I dont know why Google hasnt addressed it yet? Leads me to believe that it may not be a software issue that it is more like a hardware problem so they will just keep swapping them out until you are good or they are done swapping and your screwed.
Super-Veloce said:
Got T-Mobile NL and especially at home, most times, people can't hear me properly.
Click to expand...
Click to collapse
Same here, if a call goes through. Usually it won't even connect
Archangel said:
There are tons of threads like this talking about sound issues when calling. For me the only problem I have is when someone calls me they cant hear me on speaker phone until I turn that off and talk on the regular mic. I dont know why Google hasnt addressed it yet? Leads me to believe that it may not be a software issue that it is more like a hardware problem so they will just keep swapping them out until you are good or they are done swapping and your screwed.
Click to expand...
Click to collapse
It's so strange, it seems like a software issue. I got one replacement and it does it as well. But a restart fixes it and doing some of the cache clearing fixed it for me for 3 days. Now it's back again.
It would be nice if it were a software issue but it doesnt even seem to be on Googles radar to fix? If they just swap out enough phones for the next few months until the next phone is announced by Google, everyone will want the Pixel 4 and forget about these issues.
Legendhidde said:
It's so strange, it seems like a software issue. I got one replacement and it does it as well. But a restart fixes it and doing some of the cache clearing fixed it for me for 3 days. Now it's back again.
Click to expand...
Click to collapse
P3 white / SIM O2 Germany. I have No problems.
The SIM card is not the problem. When I had my Pixel 3XL and my wife had a Pixel 3, we replaced both our SIM cards. This failed to resolve the issue with both phones. Go read the official product forums. Too many people have ruled that out.
After 3 months without the ability to make phone calls, the only troubleshooting step that worked was to returned the phones and get another model (Oneplus 6t). Calls have been crystal clear using the same SIM cards in all the same environments.
This is either a software issue, or a component issue. I suspect its a component issue. I would put money that there is a bad transmitter or chip-set in the phone. As someone who works with electronics on a daily basis, the intermittent nature of the problem follows the type of symptoms I see when a circuit is slowly building stray capacitance and has no way to bleed out extra potential. Similar to static electricity. This would explain why it goes away for most people for a brief period when they power cycle their phone. It would also explain why not everyone experiences it.
Google may be able to band-aid the hardware defect with software by actually cutting out HD quality on calls and fudging it, and most people won't be able to tell the difference. They might have the ability to power cycle and fulling resent a single component after each phone call. They did the same type of thing when the bottom speaker on the 3XL was buzzing at certain frequencies. They simply programmed the software to prevent the bottom speaker from playing sounds from within those frequencies. Most people aren't going to notice that one of the two speakers is slightly muted.
The only way to remedy this is to have 4g enabled at all times. Calls should then be using volte or HD voice and the issue goes away.
I anable 4g even when wifi is on and calls on both my Pixel 3 (Sold) and Mate 20 Pro are clear and rock stable if not a tiny bit tinny or raspy at the high end due to HD voice.
This is on EE Uk , but I would imagine is similar on cariers from other countries.
On a side note, with O2 I do not have this issue at all so maybe it's something to do with the frequencies or bands the mobile operator is using.
It is definitely not related to the SIM. I have replaced my regular SIM with eSIM on T-Mobile CZ and I still have this issue. I have even transferred my number from Vodafone CZ due to my contract expiring, and its still there.
Hoping after Android Q , this issue will shine [emoji848][emoji848][emoji848]
Sent from my Pixel 3 using Tapatalk
I have this issue too, updated to the Android Q beta in hopes this would stop it from happening - but it is still happening.
I can hear everyone perfectly well but they say I am breaking up or sometimes I hear terrible interference and the call is dropped. Tried all the troubleshooting steps.
One thing is I noticed if I am using hands free (car's bluetooth or the pixel headphones) the issue never occurs (so far). I am thinking the antenna might be interfered with while it's in my hand. Can everyone try using hands free solutions while not holding the phone and see if it persists?
Thanks
Factory reset and removal of certain third party apps seems to have fixed the problem for me
Div250 said:
Factory reset and removal of certain third party apps seems to have fixed the problem for me
Click to expand...
Click to collapse
and now we need to know which are those "some 3d party apps"
please, thank you
Remove recently downloaded apps one by one , restart phone normally, then make a call to see if removing that particular app solved the problem. If not, continue until you do find that app. In my case, I had my suspicions on the two that I removed and that was it.
check SIM for scratches
My SIM card is scratched. Could the phone be damaging the SIM upon insertion?
I saw on another forum that their call quality issues go away when they use the headphones that come with the phone. So that would not be consistent with a SIM issue... hmm.

Call on Speaker Problem

Hey guys i have bought one plus 7 pro few days back , i have been using the phone and frankly speaking i am in love with this phone . i have to say that this is the best phone i have ever used.
Recently i came with a problem that while i am on a call if i put the call on speaker, my voice not go the other side. The person on the other side cant hear me.
So i tried to do it with two phones side by side thinking that it might be some network issue or something might be wrong in other user phone, but still it was like that while on speaker the person on other side cant hear me.
If anyone can help me out of this it would be appreciable.
Thanks
Yes ! Had the exact same issue with my one plus 7 pro. Would also get weird sounding feedback when on calls. No solution to the problem. Ended up turning it in under warranty and got a new phone sent to store, picked it up on Friday and haven't had any issues with new phone. Can't replicate issue with new phone either

Categories

Resources