During a voice call on cellular or wifi calling doesn't matter which I am on I hear this odd noise that can overpower the conversation at times. Best way to explain it that it sounds like an electrical current in the background and it comes and goes. I have asked several of my friends/colleagues to see if they hear it and so far no one else does. I do have really good hearing so perhaps it's only me and the phone is fine and I just have to deal with it? Perhaps I'm hearing a certain frequency that others cannot hear? Anyways, if anyone has a similar experience please let me know. If it is a hardware defect I'll submit contact Google and get a RMA. If it's my own personal defect I'll just have to deal with it :silly:. Thanks for your responses in advanced!
zetsumeikuro said:
During a voice call on cellular or wifi calling doesn't matter which I am on I hear this odd noise that can overpower the conversation at times. Best way to explain it that it sounds like an electrical current in the background and it comes and goes. I have asked several of my friends/colleagues to see if they hear it and so far no one else does. I do have really good hearing so perhaps it's only me and the phone is fine and I just have to deal with it? Perhaps I'm hearing a certain frequency that others cannot hear? Anyways, if anyone has a similar experience please let me know. If it is a hardware defect I'll submit contact Google and get a RMA. If it's my own personal defect I'll just have to deal with it :silly:. Thanks for your responses in advanced!
Click to expand...
Click to collapse
Google phones usually have this issue... If this is the only problem do not change it, as whatever they are going to send it's going to have the same issue... Google phones have it since Nexus one
NICEGYPT said:
Google phones usually have this issue... If this is the only problem do not change it, as whatever they are going to send it's going to have the same issue... Google phones have it since Nexus one
Click to expand...
Click to collapse
Hmm I see thanks for the info. On my 2 XL there was the distortion/rattle at higher volumes for certain frequencies but was mostly fixed by repositioning the speakers grill but that's a different issue. I don't remember experiencing this on my 6 or 6p and OG Pixel .
I have this issue as well. I didn't have this issue when I used my Pixel 2 XL. I DID RMA mine. I also have a display distortion as well from the notch up.
Is this in general use, or is this while charging?
wtharp2 said:
Is this in general use, or is this while charging?
Click to expand...
Click to collapse
General usage regardless if it's on or off the charger. Nothing downloading in the background etc.
MLIGN said:
I have this issue as well. I didn't have this issue when I used my Pixel 2 XL. I DID RMA mine. I also have a display distortion as well from the notch up.
Click to expand...
Click to collapse
Hopefully it's just a few devices that have this problem. Please update when you get your RMA and let me know if the issues persists. Thanks!
I am getting the same thing. Its like a high frequency ticking - phone earpiece only. Bluetooth is clear and the Pixel buds are clear. I call it objectionable. Coming from OG Pixel XL with no sounds like this.
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
bobbyricha said:
I am getting the same thing. Its like a high frequency ticking - phone earpiece only. Bluetooth is clear and the Pixel buds are clear. I call it objectionable. Coming from OG Pixel XL with no sounds like this.
Click to expand...
Click to collapse
I just noticed - by accident.
I placed another call to test, forgot bluetooth still connected. Put the phone to my ear to check. The ticking sound was at the earpiece on the phone and the audio was at the bluetooth earpiece on the desk. They were separate.
The call was clear on the bluetooth earpiece, but the sound on the phone earpiece was there, alone. It sounds like data noise on the phone earpiece during the call.
---------- Post added at 01:14 AM ---------- Previous post was at 12:33 AM ----------
MLIGN said:
I have this issue as well. I didn't have this issue when I used my Pixel 2 XL. I DID RMA mine. I also have a display distortion as well from the notch up.
Click to expand...
Click to collapse
What is a good path for RMA?
bobbyricha said:
I am getting the same thing. Its like a high frequency ticking - phone earpiece only. Bluetooth is clear and the Pixel buds are clear. I call it objectionable. Coming from OG Pixel XL with no sounds like this.
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
I just noticed - by accident.
I placed another call to test, forgot bluetooth still connected. Put the phone to my ear to check. The ticking sound was at the earpiece on the phone and the audio was at the bluetooth earpiece on the desk. They were separate.
The call was clear on the bluetooth earpiece, but the sound on the phone earpiece was there, alone. It sounds like data noise on the phone earpiece during the call.
---------- Post added at 01:14 AM ---------- Previous post was at 12:33 AM ----------
What is a good path for RMA?
Click to expand...
Click to collapse
If it is indeed data noise then it could be a shielding issue and I'm not sure if that could be fixed with a software update. Did you buy your device from Google? If so I'm positive they will RMA for this issue.
zetsumeikuro said:
If it is indeed data noise then it could be a shielding issue and I'm not sure if that could be fixed with a software update. Did you buy your device from Google? If so I'm positive they will RMA for this issue.
Click to expand...
Click to collapse
It was from Google.
bobbyricha said:
It was from Google.
Click to expand...
Click to collapse
They will definitely RMA for the issue. Give them a call and report the issue.
Just wanted to chime in that I had the same issue on my brand new pixel 3. I would recommend that if this bothers you, you not RMA the phone but rather return it for a refund. I do not believe this is a defect isolated to a select few units but rather an electromagnetic interference issue inherent in the design. I had the same issue on my Nexus 4 and it was never fixed. My pixel one does not do this, so I will be keeping it until at least the next model refresh. Still, who knows; please post if an RMA fixes the problem. Also, many people may never notice it. But at this price point, I'm not going to deal with waiting it out. I'm too busy to be a beta tester for a multi-billion-dollar company.
I've only had three calls so far, but I have not had any issues. All three were clear, and there was no background noise at all. I was only using the mobile network, so I don't know if Wi-Fi calling has anything to do with it, but I noticed in settings right after setting the phone up Wi-Fi calling was enabled by default. I turned it off. Maybe check that setting, and change it to see if it makes any difference?
bobbyphoenix said:
I've only had three calls so far, but I have not had any issues. All three were clear, and there was no background noise at all. I was only using the mobile network, so I don't know if Wi-Fi calling has anything to do with it, but I noticed in settings right after setting the phone up Wi-Fi calling was enabled by default. I turned it off. Maybe check that setting, and change it to see if it makes any difference?
Click to expand...
Click to collapse
The issue we are describing happens via WiFi and mobile. It may be related to certain cellular bands or the wifi radio causing interference (I had a Nexus S that exhibited a similar issue on GSM 1900, but not AWS HSPA). I personally tested 2.4 and 5 GHz wifi calling, an AT&T sim, and a T-Mobile SIM using band 4 volte calling and band 2 hspa. All exhibited the noise. More likely, you simply are not noticing the noise, but it is present. If it doesn't bother you, or you can't notice it, enjoy the phone!
Again, if it does bother you, it is unlikely to ever be fixed. Return the phone for a refund while you can.
In preparation for contacting Google for RMA I reset the phone. I did not restore from backup. It was much better, if not gone. I reset again, this time restoring from the earlier Pixel 3 XL backup. Made 2 calls. Its like 10% of what it was last night.
So for me it is varying. Before the resets, the clicking was there and hard to miss. My wife answered my phone and mentioned it, and she doesn't notice those things. Now, with a reset and restored phone, it doesn't seem to be an issue. Makes no sense to me but I'll take it. I love the phone otherwise.
Time to get back on the search for any screen protector that does not suck!
Add me to the list. Getting faint electrical static noises once a call connects. Over cell modem and with wifi calling apps like Signal.
theslug said:
The issue we are describing happens via WiFi and mobile. It may be related to certain cellular bands or the wifi radio causing interference (I had a Nexus S that exhibited a similar issue on GSM 1900, but not AWS HSPA). I personally tested 2.4 and 5 GHz wifi calling, an AT&T sim, and a T-Mobile SIM using band 4 volte calling and band 2 hspa. All exhibited the noise. More likely, you simply are not noticing the noise, but it is present. If it doesn't bother you, or you can't notice it, enjoy the phone!
Again, if it does bother you, it is unlikely to ever be fixed. Return the phone for a refund while you can.
Click to expand...
Click to collapse
Yeah, sadly I don't think it will be fixed or addressed even on this premium flagship. Since with the XL 2 they never did anything to alleviate the speaker buzzing/rattling. The only fix for that was to preposition the grills yourself to reduce it. They granted a RMA for the problem so if the next unit has it and the screen etc is fine I guess it will just be a have to live with it deal.
Another one for the list. I am having the same issue. Mine is a Pixel 3 XL from Google. I think I may RMA it because it definitely is apparent and bothers me. I'm not a hardware engineer but why is this a continuing issue for these devices?
zetsumeikuro said:
During a voice call on cellular or wifi calling doesn't matter which I am on I hear this odd noise that can overpower the conversation at times. Best way to explain it that it sounds like an electrical current in the background and it comes and goes. I have asked several of my friends/colleagues to see if they hear it and so far no one else does. I do have really good hearing so perhaps it's only me and the phone is fine and I just have to deal with it? Perhaps I'm hearing a certain frequency that others cannot hear? Anyways, if anyone has a similar experience please let me know. If it is a hardware defect I'll submit contact Google and get a RMA. If it's my own personal defect I'll just have to deal with it :silly:. Thanks for your responses in advanced!
Click to expand...
Click to collapse
On Pixel 3 here, and it's the same behavior. It's hard to believe Google is having this problem 2 years in a row. Last year they were able to mitigate it somewhat with a patch... I doubt RMA will do anything because all seem to be the same.
For those who RMA'd let us know if the replacement is any better.
Related
Well, as you can see from the video below, the guy set the highest volume, then place the smartphone near the Galaxy Nexus and the Galaxy Nexus respond to it. This is CLEARLY hardware issues. This could be the real reason Verzion still haven't release the Galaxy Nexus yet.
www.youtube.com/watch?v=BIFRYY25fDo
Thanks dnlsmy.
www.youtube.com/watch?v=y_mO_K7OYR0
Update 1
Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk
Update 2: Lee Johnston explain of "volumegate" issue
Let's talk about the Google Nexus "volumegate" issue.
Today Google said that they have fixed the problem in software, and that a fix is coming.
I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.
I'm a Systems Engineer and also a Developer. I deal with things like this every day.
What we have here is indeed a hardware issue, in that the radio interference is coming in through the radio hardware.
However things like this can be fix fairly easily in software. It's called debounce.
When you monitor an electronic input like the buttons on a phone there is always noise and flutter even when you just press the button. If testing by Google has shown that they just need to turn up the debounce time (the time which an input must exceed for it to be determined to be a genuine press) then it will more than likely just work and no one will ever see ti again.
Like I said I deal with this kind of thing every day, it's not a big deal as long as your debounce time is not excessive. But noise happens down on the order of 1 to 40 ms, real inputs when you press a button last from 100 or 200ms if you tap the button, up to seconds if you hold it down.
This is nothing like Apple and the iPhone 4 antennae problems that could not be fixed in software. I'm sure everyone will see in due time, the problem will be fixed, and the dust will blow over.
And people will be saying "wow, I was wrong, Google rocks
Cheers,
Lee
Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!
Yeah, and for further proof, he does it in the bootloader screen of the GNex
http://www.youtube.com/watch?v=y_mO_K7OYR0
This seems like it's a hardware fault entirely.
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
well you're mistaken then. the test is not inconclusive at all.
martonikaj said:
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
Click to expand...
Click to collapse
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
no software patch can fix this. the phone has inadequate RF shielding.
My bionic which I know is a different device does something similar. When I put it next to my corded work phone and the bionic switches to 4g it causes the speaker on my work phone to male a distortion noise even when it is hung up. So I can see where the radios cause some sort of interference on these 4g phones
Sent from my DROID BIONIC using Tapatalk
TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Would that have anything to do with the nfc chip?
DammitCubs said:
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
please read this post
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
dadsterflip said:
Would that have anything to do with the nfc chip?
Click to expand...
Click to collapse
it has nothing to do with the NFC chip or aerial
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
chandlerweb said:
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
Click to expand...
Click to collapse
yes, exactly - the internal radio on the Galaxy Nexus is causing the problem. that is why those of us who have been affected by this hardware defect have been so vocal about it.
vash1053 said:
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Click to expand...
Click to collapse
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
This is why I effing hate Samsung they always screw something up... Looks like the g-nex us going to be a big failure.. Hint hint goggle you should of stick with HTC to make your nexus line phones
Danrarbc said:
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
Click to expand...
Click to collapse
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
oscillik said:
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
Click to expand...
Click to collapse
Yeah, figured it was. And trying to work around it by analyzing radio signals to detect if it is a real button press or interference would be very hard too, they're going to have to do something about the phones already sold - this is a huge issue.
This is indeed bad. I guess this makes my decision easier about getting one from Hantec. Hopefully the Verizon version doen't have this issue since it uses different frequencies however, this may be the reason they haven't released it yet.
Nexus exchange?
The fact that Samsung have begun replying to peoples comments on their UK Facebook page asking for an email to be sent to technical support including their home address suggest they intend to replace the phone. It`s a great phone and it should never have happened but it`s how Samsung/Google deal with it.
For those who haven’t read the Facebook comment from Samsung :
Samsung UK Hi *, to ensure we investigate thoroughly could you please send the following details to [email protected]: Serial Number, IMEI number, date of purchase, place of purchase, details of issue
your name, address and phone number. We will get in touch as soon as we have more information.
I purchased a Samsung Galaxy Note 3 about a month ago. Last week I began having a problem with the phone. When a call comes in, whether I make it or if its incoming, I can hear the person on the other end fine but they can’t hear me. I turned the volume all the way up and that hasn’t worked. It is not the area I’m in, because it has happened in different areas.
Do you have any solutions to this?
Wifi calling? Are you rooted and non stock?
Sent from my SM-N900T using Tapatalk
I had the same issue. I was never able to fixed or the tmobile store. We change the mic several times and nothing. So I got an ear blue tooth and forgot about it. If you put it on Speaker works perfectly.
Sent from my SM-N900T using Tapatalk
I had an issue that was similar, but not the same. When I was at home on wifi and answered calls, I could hear the caller but they couldn't hear me (said there was weird squeaking noise or something). Answering calls when not on wifi gave me no issues, but my apartment is a total dead-zone so I really need wifi calling.
I just fixed it today actually by doing two things: turning OFF power saving mode, and turning off the voice control that deals with answering calls and such. I'm not sure if just one or both of those steps were necessary, but wow, F power saving mode! I thought my phone was pretty fast before, but w/ power saving mode off it just absolutely blazes. I've had pretty awesome battery life on 4.3 Tweaked ROM w/ Saber kernel, so I don't think I'll mind a battery hit in exchange for the ridiculous performance I'm seeing.
Back to your problem, I've heard of people solving issues by cleaning the microphone with a toothpick or something. Are you able to use the mic for voice recording or voice commands or anything? If you're having a hardware problem with the mic, an exchange might be necessary.
jeaniturrizaga said:
I had the same issue. I was never able to fixed or the tmobile store. We change the mic several times and nothing. So I got an ear blue tooth and forgot about it. If you put it on Speaker works perfectly.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thanks for your Info but I don't like using ear bluetooth all time. I want to another solution if you have. Thanks
Compusmurf said:
Wifi calling? Are you rooted and non stock?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Its happend all kind of calling. Yes I am rooted
If it's a hardware defect, you could get a replacement for that.
Lorettaa said:
If it's a hardware defect, you could get a replacement for that.
Click to expand...
Click to collapse
I think so. It should replace. Thanks
The only problem that I have with this phone is that callers keep complaining that they can't hear me. It seems like its only an issue when I receive calls and not when I make the calls. The weird part is that people will complain that they can't hear me at all or they will say I sound like I am really far away. they are like " hello, hello, HELLO!!!" so out of frustration I will move the phone away from my face and be like WTF! The screen will then turn back on and as soon as I talk again people hear me again just fine. So it definitely seems like an issue with the software. I went and replaced the phone at Verizon and since got a new one and the problem STILL exists. Anyone else have this issue at all? It's beyond frustrating!
Case
Sent from my SM-N910V using Tapatalk
---------- Post added at 04:28 AM ---------- Previous post was at 04:27 AM ----------
Verizon note 4 have the mics in different locations. I had to drill a hole for mine. Look at the bottom of the phone and your cas2
Sent from my SM-N910V using Tapatalk
I don't have a case for my phone
Sent from my SM-N910V using XDA Free mobile app
Don't have this issue at all.
If you don't have a case, maybe bluetooth is connecting to something?
I'd start troubleshooting it, try with speaker, see if some app is taking over your mics, obviously your mic works since its only on incoming calls and you've replaced your phone already.
Try booting into safe mode and testing.
Does it happen everywhere? Or only when you're in a certain area? Make sure you're not accidently muting it somehow?
Do all your testing in safe mode so you'll know if it's app taking your mic.
|> transmitted from deep inside a Verizon Note 4 <|
kerimh40 said:
The only problem that I have with this phone is that callers keep complaining that they can't hear me. It seems like its only an issue when I receive calls and not when I make the calls. The weird part is that people will complain that they can't hear me at all or they will say I sound like I am really far away. they are like " hello, hello, HELLO!!!" so out of frustration I will move the phone away from my face and be like WTF! The screen will then turn back on and as soon as I talk again people hear me again just fine. So it definitely seems like an issue with the software. I went and replaced the phone at Verizon and since got a new one and the problem STILL exists. Anyone else have this issue at all? It's beyond frustrating!
Click to expand...
Click to collapse
Does the other person hear static? Or nothing at all? For me I can hear then but they hear static.
I've called verizon about this for the past 4 weeks and now they have me doing something every time it happens. After it happens I have to hang up and dial ### and then after it tells me its a wrong number, hang up.
Apparently this is to mark the calls that were bad so they can further diagnose the issue.
I've been through 2 note 4s already and I am actually about to exchange this one today because I'm having other issues on top of the caller issues.
I'd recommend calling verizon and complain about call quality issues and ask them to put you on the monitoring service so they can further diagnose the issue.
-Wizzle
Same Issue on T-Mobile
I've had my phone a few days and it's constantly doing this. I first noticed it while using headphones. Then, I noticed it while on speakerphone. Most of the time, the people on the other end can't hear me. However, once today, I couldn't hear the other line but they could hear me. SO frustrating, because I use my phone for work!
I have the Verizon XL and I'm having some issues with others not being able to hear me during calls. I'm not connected to WiFi calling, have good reception and it doesn't happen all the time. During the call it's as if I'm putting them on mute. I hear them fine, but they can't hear me. Doesn't matter if it's Bluetooth or not and there's no set time-frame for when it happens. Anyone else having this issue?
Sent from my Pixel XL using Tapatalk
People tell me that I sound very quiet, or muffled, during calls on my XL.
I've read elsewhere about there being a microphone problem.
Has anyone else had this?
Do you have a case on your phone?
TechBSwift said:
Do you have a case on your phone?
Click to expand...
Click to collapse
No case.
Sent from my Pixel XL using Tapatalk
I am having the exact issue you describe. I reset the device. Same issue. Now trying it in safe mode. No answer yet.
So I finally got my phone after waiting on back order since November and I'm having the same problem with mid conversation the person on the other end can't hear me but I can hear them. I've had the phone for 2 days and it's happened maybe 4 times. Tech guy at V had me do a factory reset and he switched me off the HD network but I don't think that is going to solve the problem. I have 12 days left to return the phone for something else or get back on the waiting list probably tool March at least if not June. What do you all end up doing with them did you exchange? Have you had issues since with new phone? Google really needs to come up with a patch.
I have pixel XL, and no issues here, maybe get a replacement? It might be bad manufacturing?
I have to wonder how much of this is signal/network related . Really curious what the breakdown of user base is and how the modems are faring across various bands. I haven't had any call quality issues in my area on AT&T with my Google store variant, but this isn't the only call issue thread that I have seen out there, Verizon or otherwise.
Microphone issue. Only way to solve the problem is to send it to warranty and get it exchanged. I had the same issue.
Sent from my Pixel XL using Tapatalk
My wife and I are with Verizon and her S7 is bad about that problem. Occasionally, not often with both my N6 and Pixel but her S7 is horrible.
Sent from my Nexus 6 using XDA-Developers Legacy app
MichaelMcC said:
My wife and I are with Verizon and her S7 is bad about that problem. Occasionally, not often with both my N6 and Pixel but her S7 is horrible.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have this same problem also with Verizon. With me, though, I have determined the situation is unique to several persons I speak with often. I went to the support tab in the settings and spoke with google. I still have the problem, but it is better. The surprise is they had me remove the verizon app. Apparently neither Verizon nor Google have a clue what to do here.
my verizon pixel xl is doing the same thing. it seems when im on the phone with a caller and i switch out to check something it will mute my voice to the caller. i can hear them but they can't hear me. when i get by to the call screen though they all of a sudden can hear me again. never had this problem with my droid max 2. could leave the call screen go into my notes app and back with no problem..
I have the same issue. Have not found any information on it. I have to hang up and then call back. Not sure if it has to do with HD voice or not.
I'm not sure if I'm the only one with this issue, but here goes. My Razer Phone is extremely slow to make any call that is outgoing - full bars, Wi-Fi calling, etc - it doesn't make any difference. Is there any solution for this, or should I just attribute it to T-Mobile? My Pixel 2 XL did not have any of these issues, and frankly, and it's extremely frustrating when I'm in a hurry to make a call. Any help would be greatly appreciated...
are you using the stock dialer or something like hangouts?
aknotts415 said:
are you using the stock dialer or something like hangouts?
Click to expand...
Click to collapse
The stock dialer
Running mine on 3UK which so far I can't say I've had issue with call quality but as it's Three branded I'd hope not
Grumpycat62 said:
I'm not sure if I'm the only one with this issue, but here goes. My Razer Phone is extremely slow to make any call that is outgoing - full bars, Wi-Fi calling, etc - it doesn't make any difference. Is there any solution for this, or should I just attribute it to T-Mobile? My Pixel 2 XL did not have any of these issues, and frankly, and it's extremely frustrating when I'm in a hurry to make a call. Any help would be greatly appreciated...
Click to expand...
Click to collapse
I'm having the same issue after switching from AT&T. In addition, video calling to other TMobile users doesn't work at all. Tried messing with a bunch of different apn settings and nothing makes a difference.
Combined with the fact that my lte will drop to edge network randomly when other tmobile devices do not, Bluetooth sounds like absolute garbage when calling in my Toyota and contact pictures are all ****ed up on the same vehicles display I am really starting to not care about my 120 hz display anymore. So many little things on this phone that are bad add up to a really rough experience and when combined with a large problem like the apparent network issues on certain carriers make it really hard to keep.
This seems like a terrible time to be in the market for a new phone so I'm gonna hold out for a bit. If I figure out anything with the calls I'll report back here.
Grumpycat62 said:
I'm not sure if I'm the only one with this issue, but here goes. My Razer Phone is extremely slow to make any call that is outgoing - full bars, Wi-Fi calling, etc - it doesn't make any difference. Is there any solution for this, or should I just attribute it to T-Mobile? My Pixel 2 XL did not have any of these issues, and frankly, and it's extremely frustrating when I'm in a hurry to make a call. Any help would be greatly appreciated...
Click to expand...
Click to collapse
Just out of curiosity, why did switch to the razer from the pixel 2?
lessthanzach said:
I'm having the same issue after switching from AT&T. In addition, video calling to other TMobile users doesn't work at all. Tried messing with a bunch of different apn settings and nothing makes a difference.
Combined with the fact that my lte will drop to edge network randomly when other tmobile devices do not, Bluetooth sounds like absolute garbage when calling in my Toyota and contact pictures are all ****ed up on the same vehicles display I am really starting to not care about my 120 hz display anymore. So many little things on this phone that are bad add up to a really rough experience and when combined with a large problem like the apparent network issues on certain carriers make it really hard to keep.
This seems like a terrible time to be in the market for a new phone so I'm gonna hold out for a bit. If I figure out anything with the calls I'll report back here.
Click to expand...
Click to collapse
Good to know I'm not the only one. I'm in the same boat regarding new phones too :crying:. I'll most likely hold out until the Pixel 3 comes out as I have $400 left in Google Play credit, lol.
Heavyweightgd6 said:
Just out of curiosity, why did switch to the razer from the pixel 2?
Click to expand...
Click to collapse
Really wondering that myself right about now... I got two units of which both had really odd displays. I knew they all were plagued with similar issues, but the shift on the two I got was literally unusable.
Interesting. I have not had any issues regarding my call making being delayed, however my first razer phone (before RMA for speaker issue) did have issues when on speaker phone. The party on the other side has a hard time hearing me.