Related
Hey guys. I installed CM7 over the weekend and am sporadically getting issues when receiving calls. Occasionally I get what, more or less, sounds like an odd ring/alarm sound over my set ringtone. This issue isn't a big deal in and of itself, but when it happens, the ring/alarm sound continues on through the call and both the person who made the call and I can hear it. This results in me having to end the call and call them back. I never have this problem when making calls and it doesn't happen all the time when receiving. The way the lock screen stutters when it happens makes me think it has something to do with it but that's a wild guess.
Is anyone else running into this issue? It's happened twice since I installed CM7. Everything else seems to be working great btw, it's nice to have this rom out. Just thought I should make this post since I doubt I'm the only person with the issue.
Also -- I don't use any ringtone apps or sound software at all other than whats on the rom.
There's probably a hundred posts about this over in the fascinate forum for this rom. I have been running CM7 for a few days now and haven't had this happen. I don't get many calls tho. Check out the fascinate development thread for more info on this.
Sent from my SCH-I500 using XDA App
Ahh. I should have done some searching over there considering it's a port. My apologies - thanks for the heads up!
I'm running AOKP 35, and I'm being told by multiple people that when they talk to me, they hear an echo of themselves.
I've confirmed this with 3 people now, on cell and land lines, and cannot figure out what is going on.
Has anyone else experienced this? I'm not hearing an echo of myself, but rather, the other person hears themselves echo. I'm about to perform some tests:
1. Install stock ROM and retest
2. Test without the case installed on the phone
3. Turn the vol down on my ear-speaker
UPDATE: see my post below. I have now confirmed AOKP to be the issue. Frustrating, but hopefully ProTekk will be able to tackle this one.
I only seem to have that on bluetooth--there are some other threads on speaker issues also--
I just got off the phone with my brother (he called me). He has a One S also and is running AOKP.
I could hear myself echoing also. So yeah it looks like it might be an AOKP thing.
OK, I've done some testing, and I am 100% sure that AOKP is the culprit.
ProTekk: On a fresh installation of b35 and 4/22 gapps and NO OTHER INSTALLS (apps, etc), the echo occurs. Here's my findings:
1. If another T-Mo user calls me, their end only rings once, then goes silent. My end rings more than once, and I answer only to hear silence as well.
2. I can call other T-Mo users, and DO get through. However, they can hear an echo of themselves quite a bit.
3. In-call volume is quite low compared to stock ROMS, so there's a volume issue here as well.
I've talked on the phone w/b35 with several people today, and all of them noticed an echo. I also called myself from a landline and verified it. I then decided to wipe everything (/system too) and install the stock USA ROM. Upon installation, I retested with these people, and not a single person had an issue with echoing. I also noticed that the volume through the ear-speaker was significantly louder on stock ROMs.
With this in mind, I decided to make absolutely sure that AOKP was the problem, so I wiped everything again, and then installed AOKP b35 and 4/22 gapps. I made sure not to install any other apps or utilities. I immediately tested it in the same process, and everyone reported back that they were once again hearing the echo, and I was once again experiencing an issue where T-Mobile users cannot get their calls through to me. Land lines can call me just fine, interestingly.
ProTekk: I hope this information is helpful, as I've tried my best to eliminate any doubts in my testing.
I'd like to ask that each and every one of you that is running AOKP on a USA One S (please indicate which build/milestone of AOKP) to test what I have just laid out.
I'm 99% sure that everyone else will get the same results. I just need a few of you to confirm, then every last doubt will be removed.
UPDATE: OK, I've talked to some people in the CM9 IRC channel, and theyre experiencing similar issues (on US models, if it matters). This is obviously not JUST aokp, but rather a problem with source-based ROMs. I'm betting MIUI has the exact same problem as well.
Callers hear an echo on mine as well. Running build 35.
Sent from my HTC One S using xda premium
AOKP build 36 does not fix this either
---------- Post added at 09:41 PM ---------- Previous post was at 09:19 PM ----------
The echo is worse when on speaker phone.
In my tests, on speaker phone you can clearly hear just about everything you just said as an echo.
Without speaker phone, you'll faintly hear the last bit of whatever you say and maybe a little in between.
I would test it but AOKP just boots straight to recovery. Though I did get MIUI up and running (was loving it) I could receive calls from anyone, including T-Mo users, but couldn't make any outgoing calls.
The next release of AOKP will have this issue fixed.
ProTekk said:
The next release of AOKP will have this issue fixed.
Click to expand...
Click to collapse
Awesome. Thanks Jacob! Always appreciated! Can't wait to get back to my fav ROM.
Dear All.
My samsung galaxy s2 skyrocket had been working with ParanoidAndorid (v 2.55) for 2 months without problems, but since a week ago I couldn't place regular calls. I can dial the numbers and receive calls, but in neither case I can hear any sound. The rest of the functions work just fine (youtube, chrome, etc). After checking for sound configurations, such as noise reduction, the problem persisted. I have to say that the problem goes away after rebooting the system, but is happens again at random times. I've change to Cyanogenmod 10, but the situation holds.
I noted that two apps seems to be producing this problem: Viber and Line. Immediately after I receive a Viber/Line call the problem arises. This is strange as I've been using Viber from the beginning, but the problem has been happening only from last week.
I would appreciate any suggestions. Thanks in advance
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
hechoen said:
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
Click to expand...
Click to collapse
I'll try using the phone without Viber/Line for a couples of days just to be sure that is a app-driven problem. Given the popularity of these apps, I would be surprised if this is only happening to me.
Did the app update recently? I'd unistall it then clear caches and reboot. If the problem goes away it's the app.
Hi @MarceloR -
I am a rep. of Viber here on XDA.
Thanks for sharing the details of the problem.
First, please note that Viber does not officially support your device, s2 skyrocket (here is the full list of fully compatible devices: http://bit.ly/Hm5k9p). Furthermore, we (Viber) don't claim to fully support devices with Custom ROMs, since it is impossible for us to adapt our app with all of the Custom ROMs out there.
Both these issues may be the sorurce of the problem you're experiencing. Have you tested this issue on Stock ROM on your device? (though it's not fully supported).
Having said that, the problem still sounds odd - Viber should not affect your ability to use your phone for regular calls.
Same problem, different software
I'm having the same issue - no mic, no sound on phone calls. I do not have either of the above-mentioned apps installed. I'm running CM10.1, though (Rogers). Tried installing the CLI3 modem, and the stock Rogers modems to see if that might help.
I did notice that the ear speaker was getting quite hot when I tried to use the phone, and the phone app itself is performing tremendously slow.
If anyone has thoughts / suggestions about how to fix this, I'd really appreciate it.
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Update: pulled SIM card, battery. Reboot, shut down, insert SIM card. Everything works again. Using the same 3/3 nightly. No other changes.
lingowistico said:
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Click to expand...
Click to collapse
Common for whom I don't have these issues. I swear how do you guys have all of these crazy problems.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
http://forum.xda-developers.com/showthread.php?p=39678817
@lingowistico -
Thank you for sharing this valuable information, that will help us aide our users as well.
If you have any news in this matter, please do let us know
lingowistico said:
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
Click to expand...
Click to collapse
I circumvented this problem by installing an old version of viber (one from Dec 2012). I found the old version here: http://www.androiddrawer.com/
So far, no problems. Everything seems to be back to normal.
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Using my N5 in germany and it's the best phone I've ever held in my hands Running CM12 (based on Lollipop) for now. Have also been using stock Lollipop for a few months. Both run extremely stable. To be honest: I never heard about your issues. I'm not that big of a fanboy. Never owned a Nexus device before, but I guess I'll never move away from Nexus
Just my honest opinion about the device
By the way: I've got a moto 360, too. And the connection is great - up to 10 meters at least and no random disconnects
I have zero issues with mine, but I'm on stock 4.4.4 so that may have something to do with it. I'm not a fan of Lollipop at all. Too many bugs, and I don't like the look of it.
After one year with my Nexus 5, running stock no root, never a problem. I'm a former owner of HTC flagships phones, never a problem with them.
Sent from my Nexus 5 using Tapatalk
Using Stock 5.0.1 rooted and with ElementalX kernel is good for me and have been using that setup for over a month now. No issues like what you're describing at all. :S
No problems here like that. Bug report issue is normally a poorly fitting case
Hmm... So it seems that the only people that are having these bugs live in my area... Do you think its possible we all got a bad batch of n5s at the rogers store here?
Edit: everyone experiencing these issues has bought their phones from rogers stores here in my city.
OFWGKTADGAF said:
Hmm... So it seems that the only people that are having these bugs live in my area... Do you think its possible we all got a bad batch of n5s at the rogers store here?
Edit: everyone experiencing these issues has bought their phones from rogers stores here in my city.
Click to expand...
Click to collapse
Yeah the devices purchased at the play store seem to be fine now. At first, me personally, I had tons of bugs at release. But those issues have been fixed with updates. Mainly concerning the signal and camera speed.
Thread cleaned.
If you think a report is breaking the rules or shouldn't be there for any other reason please report it and move on, antagonizing them adds nothing to the forum but makes our job harder. Thanks, Tijmen.
No issues here besides the occasional Mobile Radio active wakelock, which I did also see occasionally on KK. I did have some memory leak issues on 5.0.0 but either 5.0.1 fixed it or me removing some 3rd party background services did.
OFWGKTADGAF said:
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Click to expand...
Click to collapse
A reboot a day keeps the android bugs away
kevtrysmoddin said:
A reboot a day keeps the android bugs away
Click to expand...
Click to collapse
Rebooting is normally my go-to solution for problems but it doesn't seem to help these bugs. I installed CM Security and it constantly warns me about my CPU usage/RAM and battery Temperature. The culprit almost always seems to be the Facebook app (sometimes using 250+ mb of RAM just for background services) Could this be a bug with the Facebook app making my phone perform poorly... Does anyone know of any solid alternatives to the official Facebook app?
OFWGKTADGAF said:
Rebooting is normally my go-to solution for problems but it doesn't seem to help these bugs. I installed CM Security and it constantly warns me about my CPU usage/RAM and battery Temperature. The culprit almost always seems to be the Facebook app (sometimes using 250+ mb of RAM just for background services) Could this be a bug with the Facebook app making my phone perform poorly... Does anyone know of any solid alternatives to the official Facebook app?
Click to expand...
Click to collapse
Fast for Facebook I'd a good alternative
I've been without issues since the factory images were first released, running CM12 CAF builds without issues (besides cm12 bugs)
So call me crazy but I deleted the Facebook and Messenger apps about 6 hours ago and have had 0 problems since... I'm using the official Facebook "Lite" apk I found online and while it is very ugly, things are running much smoother, just hoping that maybe this will solve the bugs I've been experiencing and I'll be able to help my friends get there phones back to a usable state.
OFWGKTADGAF said:
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Click to expand...
Click to collapse
I know it's really late in the game now, but have you tried starting in safe mode to see if you have the same issues? It could be an app causing all the grief.
Has anyone else experienced problems with call quality on their Pixel 3 or Pixel 3XL?
The issue I'm referring to is the one where you can hear the other party, but they cannot hear you.
I have a Pixel 3 (my wife) and 3XL (mine). Both my wife and I are told nearly every call we make that we are breaking up or sound like we are robots or underwater. I even RMAed the P3 and have the same problem.
Its a tricky problem to notice right away, because it depends on other people telling you that the call quality sucks. The quality is fine on the P3 side.
Google seems content to ignore the issue.
There are multiple threads on this over on the official Google product forums with hordes of people chiming in that they have the same issue, and nothing fixes it. I'm starting a thread here, because I've seen almost no mention of it on XDA.
Yeah, there are a few threads on XDA about this already. There is no real fix or solution, but my personal opinion is that it is caused by relatively weak signal strength, but not because of the carrier, but because something in the Pixel 3 does not grab onto cellular signals as well as it should. My wife and I have both suffered with this until T-Mobile gave us a cell spot to install in our house. Now, the issue is gone when calling from home but pops up again when we leave the house. And we are not in small town (Houston, TX). This issue didn't happen with either of our Pixel 2, iPhones, or Honor 8 Devices. RMA replacement didn't fix it either.
Me too. Call issues with Pixel 3XL on 4G/LTE. Telus, Canada.
Sent from my [device_name] using XDA-Developers Legacy app
Same here on T-Mobile US.
Sent from my Pixel 3 using Tapatalk
Just a thought. Couldn't we just start a petition on one of the free petition sites and point all forums and sites to that location to get Google to address the problem? Eg.
Google Pixel 3/3XL Calling Issues
Google has failed to even acknowledge many of the known 4G/LTE issues of the Pixel 3/3XL. Through this petition I hope to make visible how large this problem is and force Google into acknowledging and addressing these various issues.
Poor connection issues during 4G/LTE phone conversations including but not limited to:
a.) buzzing, static, interference
b.) dropped calls
c.) voice delays
d.) inaudible voice
A large amount of users have already tried resolving these problems through Google's customer support channels and RMA's processes to no avail.
Although various users have discovered temporary workarounds by disabling features and settings on their phones, nothing has totally rectified these aforementioned problems. Google's customers deserve to have their devices operate as advertised. By failing to acknowledge any problem exists with these phone's during regular 4G/LTE conversations Google has demonstrated bad faith. Furthermore they continue to sell the device knowing people will experience these issues. If you are experiencing any of the aforementioned problems please take the time to sign this petition.
Sent from my [device_name] using XDA-Developers Legacy app
Do it up and I'll sign it. Online petitions don't really have a great track record for being effective, but anything to raise awareness. Its not getting a lot of traction on this forum, but the activity on other sites and social media indicates that its affecting a very large number of people. After doing more research on this, I would go so far as to say it is the most important and widespread defect that exists in the Pixel 3 line at the moment, and Google is totally ignoring it.
It literally stops people from using their phone as a phone.
I suspect this issue might heat up in the near future. Lots of people will have received the P3 over Christmas, and will soon be discovering that no one can hear them when they talk. There is likely to be an influx of confused, disappointed, and frustrated people throughout January.
Google has been able to ignore it because of the lack of coverage. Anything to spread awareness is good. I would sign a petition. I will say that I'm hoping not to be a Pixel 3 owner in the near future. I'm fighting with Google to authorize a return for my 3XL and my wifes 3, but their support has been a nightmare to deal with. I may have to go through Mastercard for a charge-back. I know someone I work with who did that, and she claims that the person she dealt with at Mastercard was well aware of the issue and the Pixel 3 is a popular charge-back over the last month.
I plan on purchasing a Oneplus 6t for myself and my wife. I will do so out of pocket if I have to. Its not perfect, but Oneplus seems to be on point with acknowledging issues, and the model has a fairly solid track record so far.
A $1500 lesson learned not to buy hardware from Google again.
JohnnyRebel said:
Just a thought. Couldn't we just start a petition on one of the free petition sites and point all forums and sites to that location to get Google to address the problem? Eg.
Google Pixel 3/3XL Calling Issues
Google has failed to even acknowledge many of the known 4G/LTE issues of the Pixel 3/3XL. Through this petition I hope to make visible how large this problem is and force Google into acknowledging and addressing these various issues.
Poor connection issues during 4G/LTE phone conversations including but not limited to:
a.) buzzing, static, interference
b.) dropped calls
c.) voice delays
d.) inaudible voice
A large amount of users have already tried resolving these problems through Google's customer support channels and RMA's processes to no avail.
Although various users have discovered temporary workarounds by disabling features and settings on their phones, nothing has totally rectified these aforementioned problems. Google's customers deserve to have their devices operate as advertised. By failing to acknowledge any problem exists with these phone's during regular 4G/LTE conversations Google has demonstrated bad faith. Furthermore they continue to sell the device knowing people will experience these issues. If you are experiencing any of the aforementioned problems please take the time to sign this petition.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll sign it as well. Nice write-up
Sent from my Pixel 3 using Tapatalk
---------- Post added at 10:59 AM ---------- Previous post was at 10:55 AM ----------
When it's family or friends on the other line it's a nuisance, but when it's an important business call and you've been forwarded through several layers of customer service with no way to call back if it happens it really creates a headache.
Sent from my Pixel 3 using Tapatalk
Well one thing that has fixed mine was simple troubleshooting. These are the steps I've done.
1. Force Stop the Phone app
2. Clear both cache and Storage for Phone App
3. Uninstall and reinstall the updates for the Phone App
4. Reset WiFi, Mobile, & Bluetooth
5. Restarted the phone.
So far going 3 days without any issues with it. Still monitoring it but so far so good.:fingers-crossed:
rtlalipon said:
Well one thing that has fixed mine was simple troubleshooting. These are the steps I've done.
1. Force Stop the Phone app
2. Clear both cache and Storage for Phone App
3. Uninstall and reinstall the updates for the Phone App
4. Reset WiFi, Mobile, & Bluetooth
5. Restarted the phone.
So far going 3 days without any issues with it. Still monitoring it but so far so good.:fingers-crossed:
Click to expand...
Click to collapse
Why didn't I just think of "simple troubleshooting"? If that fixed your problem I'm happy to hear it. The closest I came to eliminating the problems was my 4th complete factory reset. Then instead of restoring settings, apps, etc. via the cable from my 2016 Pixel, I manually restored my contacts from my Gmail account online. I made sure to not install any additional apps for testing. Then I installed the latest updates/security patches. This did seem to eliminate some of my other minor issues but did not fix the calling issue. Disabling 4G did, but why should I have to use the 3G network on my brand new phone. I also tested various beta apps like phone (Google's dialer) to see if they might address the problem. I tried different dialers and also preformed various safe-mode tests. I tested my phone in multiple cities (London, Windsor, Sarnia, Goderich, Wasaga Beach). I'm pretty sure at this point software cannot fix it. Don't get me wrong, a patch might come along that can mask or hide the problem but I think the only true fix would be hardware replacement.
Sent from my [device_name] using XDA-Developers Legacy app
Well just saw there was a new carrier services update. Maybe a glimmer of hope.
Sent from my Pixel 3 using Tapatalk
Same problem, T-Mobile NL here.. sometimes I'm hard to hear..
Same issues here, Partner (Orange) IL.
Weird buzzing (really weak though) static background noise, sometimes people tell me that I'm cutting off (I hear them great on my end).
Luckily, I don't use the device so much for phone calls these days, but it's a damn shame.
Carrier Services?
perfoliate said:
Well just saw there was a new carrier services update. Maybe a glimmer of hope
Click to expand...
Click to collapse
This one? Carrier Services
I have an older version installed. The Google Play web site shows a newer version. They must be rolling it out in waves?
perfoliate said:
Well just saw there was a new carrier services update. Maybe a glimmer of hope.
Click to expand...
Click to collapse
Unfortunately, no.
Carrier Services doesn't effect call quality. It's an RCS client, which has to do with messaging.
Besides, people on the official product forum are saying the issue persists following the Jan 9 carrier services upgrade, the Jan security upgrade, and with the beta phone app.
Sadly, it looks like this is hardware.
Most people, including myself, notice that the problem goes away when you disable WiFi. I suspect there is a conflict between transmitters (eg. phone and wifi radios fighting over power, etc). It really should be a recall, but I bet Google will just band-aid it with a software patch that automatically disables then re-enables WiFi during phone calls. Most people won't notice their WiFi turning off during phone calls anyway.
Either way, QA on google hardware seems to be steadily declining since the Pixel 1. Looks like Google is realizing they can get away with it.
To those of you in this thread who are having problems, please check your signal strength and report your results to this thread:
https://forum.xda-developers.com/pixel-3/how-to/finally-solve-call-quality-issue-t3888549
I got an RMA device. Still have the issue with VoLTE enabled. I still get the screen flash with unlock, too. I will have to go back to plaguing their customer service for a refund. I'm not going through six phones. I just want my money back so I can get the hell away from this company.
I've used WiFi calling to help in house with weak coverage
It looks like this problem wont ever get any traction with Google even though there seems to be a lot of people having the same sound issues. Its sad though because this is such a great phone to have such a profound basic issue. I like to use my speakerphone when I receive calls and no one can hear me when they first call. I have to play with the speakerphone button switching it off and on for them to even hear me a little bit?? I guess millions have to have the same problem in order to get a fix. I see some people say to turn off advanced calling,,,well I shouldnt have to do that for one,,,and if I do my android wear watches wont work.
Wonder if anyone has tried a custom rom here and if the problem still exists?
It frustrates the living **** out of me, I am sorry - but reading about all the people here who has this TOTALLY unacceptable issue with their brand new Pixel 3 saddens me deeply! Google doesn't seem to really give a dang about it, as there are no official comments either confirming the issue or reporting on it as some work-in-progress.
Is it paranoid to think that this is a deep hardware issue that is "too expensive" for Google to acknowledge? Because, I mean, as a professional who relies on my phone in work, I have pissed off about 10-15 potential customers the last month, and my mom and dad, quite a lot as well. To the point where they get frustrated because of the choppy quality.
When it happens I tend to get a small x over my signal. As if signal is lost.
I am following all threads closely and will report back if Google support ever hits me back with that promised phone call...
Sending peace and love to my fellow brothers who has this frustrating issue! I feel you
pacificwing said:
Has anyone else experienced problems with call quality on their Pixel 3 or Pixel 3XL?
The issue I'm referring to is the one where you can hear the other party, but they cannot hear you.
I have a Pixel 3 (my wife) and 3XL (mine). Both my wife and I are told nearly every call we make that we are breaking up or sound like we are robots or underwater. I even RMAed the P3 and have the same problem.
Its a tricky problem to notice right away, because it depends on other people telling you that the call quality sucks. The quality is fine on the P3 side.
Google seems content to ignore the issue.
There are multiple threads on this over on the official Google product forums with hordes of people chiming in that they have the same issue, and nothing fixes it. I'm starting a thread here, because I've seen almost no mention of it on XDA.
Click to expand...
Click to collapse
I get this, it's reception issue. I fixed it by keeping data on so it uses VoLte 4G HD voice whatever it's called.
I have the issue with my Mate 20 Pro as well but the Mate doesn't have VoLte to fix it.