Hey...so here's an interesting problem...
I have a Pixel XL 128GB running on T-Mobile. Wifi calling is turned on. Whenever anyone on my contact list calls, the phone rings through normally. If the caller is not in my contact list, the phone will ring for 1-2 seconds, then the notification disappears and the phone goes silent, and after another 1-2 seconds, it starts again. If I just let the call play out, it will go to VM after the 3rd or 4th loop. My call log shows that there were 3-4 calls from the caller. This is consistent - it happens literally every time a non-contact tries to call me.
I thought it might have something to do with the call blocker app, so I uninstalled that - no change.
I changed wifi calling to Cellular preferred and then to off - no change on either.
Factory reset and sign in to account with no install of additional apps (other than updates to stock apps) - no change.
Changed to my wife's SIM still using my Google account - no change.
I am stumped. It seems like it is T-Mobile, but then how do they know who is a contact and who is not? This does not happen on the S7 Edge I came from (put the SIM back into that phone and no problems). Does anything else leap out to anyone to check or set or...?
Related
This is like my third thread in this forum. There are a lot of bugs on my device that are literally driving me crazy!
I've had this device since december and I was so impressed. I rooted and themed my phone completely about 2 months ago and everything has been golden.
Recently I've had these bugs/issues and its really annoying.
1.) Call drops as soon as I go to make a call. Usually happens at the worst times when I really need to use the phone. Also sometimes when I make a call it says please turn off airplane mode when I NEVER turned off airplane mode to begin with. Its like 50/50 as to which problem occurs.
2.) Call forwarding automatically turns on randomly. Phone is in my pocket, I look at it and it has the call forwarding icon in the notification bar. I go to turn it off and it allows me to, but it will not let me disable it forever. Says my carrier does not allow it or something. (this never happened before)
3.) Forgets voicemail number. I get a voicemail and in the notification is says "voicemail number unknown". I change it manually in the settings and its fine for a few days, then happens again.
Does anyone have any clue wtf is going on and how to fix these bugs?
Use a stock rom
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
I have been experiencing this problem with making some phone calls where it connects to the line I am calling, but it goes silent. They can hear me, but I can't hear them. I have found that it usually depends on who you are calling. I just did a test with a friend's cell phone and a land line. I called the land line 10 times in a row and there is never a problem. But when calling my friend's cell phone, it is random. Would go silent the first time, then be ok the next 2 times, then silent again, and so forth. Also, my friend's cell phone is set so that it only rings one time, and then the voice mail picks up. I know this from looking at the top right of the phone screen where it says "Dialing", and when the call connects, you will see a time counter. When the time counter is running, it is still silent.
I wiped the phone app cache and system caches, but the problem still occurs.
Any ideas why this is happening?
Hey! My wife has a t-mobile G3, stock non-rooted. It's running 6.0. She's had it for a year, and it's been fine (other than some wifi issues here and there). But in the last few weeks, she can no longer make calls.
The weird thing is the calls do "connect", but there's no sound either direction. For example, if she calls me, my phone will ring, but when I answer there is no sound either direction. Both of our phones show the call timer counting the seconds, as if they are both connected. If one of us hangs up, the other phone gets disconnected immediately---so the 2 phones are DO connect with each other, but no sound can pass. This happens with every number she calls.
I would have thought it might be a network problem, but she did a factory reset and it worked fine---until a few days later when it broke again. So I'm thinking it's software. Sometimes her phone will work for a few hours, but then it will stop working for a few days.
I've tried turning ON/OFF bluetooth, wifi, data, & wifi calling. I've tried changing to 2G network. I've tried different sound/noise settings. No change.
Any ideas?? Thanks
Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
*Copy/pasted from the Pixel 2 forum. Whoops!*
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
I have noticed a similar problem that has cropped up recently - I cant make consecutive calls. If I hang up from a call and then try to make another the phone sits there. The phone button animates but doesn't do anything. If I try 20 seconds later it will sit there for about 10 seconds and then make the call. If I wait about two or so minutes it will work. Incoming calls are different.. if I am in that "period" of time, the phone will ring and if I am not in the phone app - meaning the incoming call screen pops up - I can answer it. If its a heads up incoming call I cant answer it. I must turn the screen off and then back on to get to the full screen to answer it. I am on 17.0.186697879 which I believe is the latest.
I've had the delayed calling problem for almost 2 months. The problem also includes sometimes not being able to answer a call from the notification shade when the screen was already on. Toggling airplane mode alleviates the problem temporarily.
There's a lengthy thread in the OG pixel threads with the many users with the problem. Also a lengthy thread on one of the Google support threads. Someone there suggested it had something to do with the mlb at bat app. I think that has since been debunked. I haven't found a solution yet and Google hasn't made an official acknowledgement yet.
This issue suddenly appeared on my Pixel 2 couple of days ago. Tried all the hacks and solution, but even turning off all the knobs in the phone permissions screen didn't help.
I have android 8.1.0
Build OPM1.171019.021
Has anyone else had this issue where you can hear the phone ring but it takes 5 to 10 second to see the display in order to answer?
Yes, had the same, no idea
Had this before,
Do you have more than two Google accounts on the phone? Try to remove one and see if it solves it.
No only one G-account
I have seen this issue. I think for me turning off adaptive battery for apps solved this for me. What annoys me the most is trying to hang up calls, where it takes over 3-5 seconds for the phone to respond to hang up, and multiple presses on hang up before it does, 9 times out of 10 the other end hangs up
danw_oz said:
What annoys me the most is trying to hang up calls, where it takes over 3-5 seconds for the phone to respond to hang up, and multiple presses on hang up before it does, 9 times out of 10 the other end hangs up
Click to expand...
Click to collapse
Have this as well, I've got my power button set to end calls and even that doesn't work
I've had this problem with my Note 4 a few times but I believe I had Power Saving mode turned on.
Is the call screening feature enabled?
I have the same issue ONLY when I have more than one Business Google accounts on the phone.
If I have multiple simple Google accounts and one Business G account then No Issues.
Adding one more Business G account triggers the delay.
Actually to be honest, you should try enabling the VoLTE on your phone. Pixel phone needs internet to be working for all services and apps to run smoothly. When an incoming call appears, it usually tries to grab the info from internet if the caller is a known profile. It used to happen with me, until I rooted and enabled VoLTE using magisk module because unfortunately my country is not supported for voice over LTE services on Google Pixel handsets.