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
Related
I have a problem that more people seem to have, according to the search. I couldn’t find the “audio” tab in my Bluetooth-settings, so that didn’t help me.
The problem is as follows. After 1 day the sound on my compact III mutes, including vibration. Sometimes it's after 12 hours, sometimes after 2 days, there's no distinct pattern to be recognized. Also, it doesn't seem to matter if you use the phone or not, since it sometimes is alright at night and the sound is muted the next morning. This is for all sound-events (warnings, incoming call notifications, messages, mp3 etc), however, you can make a call without any problems and hear what the other person is saying. Once you’ve hard-reset the device everything is back to normal.
It does get annoying however, since I regularly miss calls due to this bug.
I had the same problem on my Vario in the past. So I’m guessing it’s somewhere in the software I use, but apart from Total Commander and TomTom6 I haven’t installed any third-party apps.
Yup i've been having a slight problem with the sound. I thought it was like the endless knackered M500's that orange used to send me which had speaker failure after about 10minuites! (Swear they kept sending me the same 2 faulty phones - I had 5 in 5 days once!) But a play in the bluetooth seems to get it working again.
The other annoying thing is that if you leave the power management at the default settings then occasionally the screen blanks without being able to get the backlight on again - so now I have to manually turn of the screen. Stil aint much of a problem - ive had a normal days use, 2 hours of radio play, bluetooth and wi-fi on all day and still have 35% battery - wehay!
Hopefully there'll be a patch soon to sort out he glitches.
I forgot to mention I had the exact same problem on my mda Vario also. I always thought it was a problem with that specific piece, but apparantly not.
Could it be the vibrate.cab that I'm using to produce vibrations when you use the phonepad? Or should I really do some further research in the bluetooth-department?
Same problem here.
Phone becomes completely silent after 9 hours in standby mode.
I need to reset it to get back sound
Does someone know what is going on here ?
Please advise. Thank you.
I seem to experience no problems the past couple of days (fingers crossed). I used the 'speed up your WM5' tweak where you set the Glyphcache to 32768. After I reduced it to 16something the problems seem to have disappeared.
I noticed that this problem happens when for example email is automatically checked during night. If email comes in (and is not read immediately) the phone will start notifying in background.
Notifications are kept and only a program like "check notifications" will delete them manually. But still if you delete them, the phone then needs a reset
to work properly again.
This is not a memory issue, it has to do with the notifications.
I do not know how to solve it.
I've been having a weird issue with my phone muting the mic during calls. This mute seems to be independent of the mute softkey on the phone (when it gets muted, the softkey is not lit, nor does toggling the softkey unmute the mic). This is incredibly annoying as once it mutes, the only way to continue the conversation is to hang up and redial. This issue occurs both using the phone normally (phone to ear), with a wired headset (so no possibility of cheek activating softkey), and with a bluetooth headset. In all 3 scenarios the mute will toggle on its own, seemingly randomly. I can go through a 40 minute call with no problems, yet sometimes it seems to mute right after I make the call.
Has anyone else had this issue?
This is what I have done to troubleshoot the issue:
1) With the original phone that I bought, I reset that phone back to factory settings and set it back up. Issue still persists.
2) Had the phone swapped out at the same Verizon store that I bought it at. Issue still persists.
3) Reset the new phone back to factory defaults. Issue still persists.
I will try the following:
Reset phone back to factory defaults and not install any apps whatsoever (running only apps that came with the phone, won't disable anything such as VZW Backup Assistant, etc either). Something tells me that this won't fix the problem either.
Does anybody know what I can do? This is a great phone but I'm a little miffed about not actually being able to make calls with it. I called VZW tech support and they are willing to replace the phone, but I basically have to go from a NEW phone to a certified like-new device (which VZW allows up to a maximum of 2 blemishes on the back, which I am not ok with) through no fault of my own.
See this thread on the Google Code bugtracker: (Hm.. I can't seem to post a link as a new forum member.. well its bug ID 24019 on the android bugtracker off of code.google.com) Don't want to munge up a link and piss off a mod or anything.. sorry guys :/
That im affraid is a nasty bug that is yet to be fixed.
Have you experienced this bug? I'd like to hear from members of this forum on if they have this issue, and how they resolved it (if at all). I was surprised that something so blaring isn't on the list of known GNex/ICS bugs (at least not on the one I saw on androidforums.com). I'm just uncomfortable with how the Verizon reps are pretending to not know about this issue...
//Edit: Oops. Found the other thread in this forum on this issue. It seems that I'm describing this as a mic muting issue, whereas other people are describing it with "mic cutting out" so I can never find their posts. Post ID 1403051 in Galaxy Nexus General.
Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
erickh0 said:
Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
Click to expand...
Click to collapse
Maybe a theme issue?
Nope. Just reformatted the phone and did not install any theme/launcher apps
Same issue
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
same here
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Me too. Bumping in hopes of a fix.
Same. I'm running a custom ROM and haven't upgraded to 8.0 yet. Does the issue persist with 8.0? Google told me today to revert to stock and upgrade to see if that fixes it.
Sent from my Pixel using Tapatalk
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Having the same issue on a regular Google Pixel. Also Google Assistant is not working using the "Ok Google" voice command and the phone app - answering and ending calls lag - same issue mic and speaker do not work. In Safe work, they work but on rebooting same issue persists.
xbiggyl said:
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Click to expand...
Click to collapse
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
me too
jasona08 said:
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
Click to expand...
Click to collapse
stock O, Rogers.
bump - hoping someone has heard something somewhere.
Same here for my regular pixel, this is really annoyed. It just starts happening after almost 12 months since I got it.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
I have been having these same issues with my phone. I noticed it happened after I downloaded the what's call app to make a WiFi call. I noticed another user had the problem after installing what's app to her phone. Could this somehow be the problem? I am not super tech savvy but I am convinced it is related to my downloading the what's call app. I have uninstalled the app. Still the problem remains. Any ideas? Thanks.
Has anyone that posted in this thread was able to resolve this issue? I also have this problem, I'm currently waiting for it to happen again so I can pull logcat but no idea what I should be looking for since I have no idea what can cause not being able to hear the caller so randomly.
I was originally suspecting V4A, but last night I flashed stock system img, did not install V4A and same issue occurred.
Pixel 2XL, Bought from Google UK running on EE.
For the passed week do not disturb is just not working at all on my phone, either when I turn it on manually or when my rule kicks in.
Notifications don't pop up on the screen like I have always had set up, but every single notification pings the phone. Instagram likes, Strava, WhatsApp and messages, the lot all make a noise on full volume regardless of the do not disturb.
Oddly, every notification makes the same noise while on DND, none of the app specific sounds you'd expect.
Any ideas? Partner has an identical phone and works as it should.
Narom88 said:
Pixel 2XL, Bought from Google UK running on EE.
For the passed week do not disturb is just not working at all on my phone, either when I turn it on manually or when my rule kicks in.
Notifications don't pop up on the screen like I have always had set up, but every single notification pings the phone. Instagram likes, Strava, WhatsApp and messages, the lot all make a noise on full volume regardless of the do not disturb.
Oddly, every notification makes the same noise while on DND, none of the app specific sounds you'd expect.
Any ideas? Partner has an identical phone and works as it should.
Click to expand...
Click to collapse
You have a screenshot of your Do Not Disturb settings? I know once in a while, I've had times when it clears and defaults to sounds on. I think it's usually after an update.
Sent from my Pixel 2 XL using Tapatalk
It's an issue that has existed since March or April update. Saw a few posts about it, myself facing the same problem. It's really trial and error now to get DnD working properly
I've had the same problem on and off for the past few months. Usually setting it manually always works for me. It's just the auto rules aren't activating. I haven't noticed any difference in the notification sounds.
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.