[Updated] Google Pixel 3 & Pixel 3 XL users reporting "No response, timed out" issue after latest update (workarounds inside)

New updates are being added to the bottom of the story…

Original story (from November 17) follows:

Google Pixel 3 series users are reporting random call drop issues wherein the call disconnects post the 30-second mark with an ambiguous “No response, timed out” error message.

Users are frustrated. And their frustration is justified given that such issues should be non-existent on a function as basic as making calls.

As a result, there have been plenty of complaints on Pixel Phone forums as well as Twitter regarding the same.

Pixel 3 is dropping outgoing calls at the 30 second mark. This is new since the latest update a few days ago. It only happens on outgoing calls. I’m on verizon. It says ‘no response, timed out’….it is extremely unsafe for google to do this. you would think they would test something as simple as making calls?
Source

Same here! My phone performed an update which lead to this issue. I can talk to everyone but my brother who has an iPhone also on Verizon. Called my parents on a landline twice and had no issue. Please fix this Google ASAP!!!
Source

As apparent from the above complaints, this annoying bug seems to prevail only on Pixels making use of the Verizon carrier network.

The problem doesn’t occur on all calls though, and several users have stated that it arises only when calling other Verizon phones. Also, the issue is limited to outgoing calls only.

Therefore, users are now having to request call-backs or use alternative apps to call certain people.

A 30 seconds call time window is good for nothing, unless of course if you just want to dictate a shopping list of only two items, which rarely happens.

The issue also seems to have emerged quite recently – since the past 4 or 5 days. Hence, it is quite possible that it is related to the latest November Android update.

However, it is unclear if the problem is actually related to Pixels or Verizon. It could be some kind of compatibility issue between the two. Either way, you can try the workarounds given below.

1. Turn off advanced calling: This has reportedly fixed the issue for several users and is the first thing you need to try. You can do the same via “Settings > Network & internet > Mobile network > Advanced calling.”

2. Reset app preferences: For some odd reason, doing the following has also fixed the problem for a couple of users.

Go to apps and notifications, see all apps, click the dots on upper right reset app preferences. Resetting all app preferences worked for us.
Source

3. Reset network settings: If nothing else has worked for you, then this could be your last resort. To perform the same, open up your settings app and head over to “System > Reset options > Reset Wi-Fi, mobile & Bluetooth.”

And that’s all for now. Be sure to also check out our dedicated Android 11 bug tracker for further coverage on similar issues. Hopefully, Google/Verizon will fix this crucial bug soon.

IST 20:15: At least one affected user is confirming that a Verizon tech support told them the issue is on the carrier’s end. Here’s the exact comment they posted on the Google support forum:

VZW tech support said that it’s a known network issue and that they are working on it

Since the user didn’t provide any supporting proof for this, so we’d ask our readers to take this info with a pinch of salt. We’ll update our story as and when any other newsworthy development comes to our sight.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.