Go into safe mode. When I called last week about this issue, Samsung said they had just discovered it when people started calling in about the problem. The tech I spoke with said if you can access the security settings in safe mode, then the problem might be an application that you downloaded. Only problem with that theory is you would literally have to spend a lot of time, probably multiple hours, uninstalling and reinstalling your apps and also checking the settings to see if they work. I was told Samsung tech support would investigate further and call back about further troubleshooting, but have not done so yet!
Hi,
I'm not sure what this post is about.... But if you have an actual question.... I need your device make and model to point you towards help.
Thanks! ?
Thank you. Thread closed.
My Pixel suddenly stopped being able to make and receive phone calls a few days ago. The Phone app is extremely sluggish trying to make a call, will usually finally "connect" and look like the call is open, but I hear nothing but silence on the other side, and the other person can't hear me. It's slow to try and hang up, too. I see calls coming in, and can try and answer, but with the same result. Missed calls are registered. Voicemail also does not work. I can see there is a message, but can't play it.
Running 8.1 with February 5 security patch. Carrier is Verizon. I've gone in the store, and they switched out the SIM card. I've also tried a hard factory reset, all with no difference to the problem. The phone is over a year old, so I think a replacement is not possible...
If anyone can help me or has any ideas, I would greatly appreciate it! Thanks!
It's a hardware problem, Google is aware of the problem, they should replace your device. Contact Google, even if you are out of warranty they will replace the device for you!
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPOPRT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH, is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issue. I really DOUBT its a 3rd party app.
Thanks for your replies. I've contacted Google, and they didn't seem to think it was justification for replacing the phone out of warranty. They said I could either take it to a repair place to fix it or trade it in for the new Pixel 2 and get some money for it.
The workaround for answering calls works to connect the call and start the timer, but I still can't hear the caller and they can't hear me...
I still after much troubleshooting have found no way in which calls are functional. In addition to the attempts made above, I've since tried to uninstall and reinstall the phone app, and also to install a different phone app. No change to the problem. Even more curious, the problem still persists in Safe Mode.
If anyone has any more ideas, I'm all ears! Thanks!
So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou
It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.
Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon
I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.
The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.
Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.
Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!
Recently I've been getting a notification on my watch about Samsung's Terms and Conditions being updated and that I needed to accept the new ones. The notification didn't provide anything clickable and just gave a link to account.samsung.com, which doesn't prompt me with anything. This same issue would pop up if the watch reconnected to my phone, or if I tried to use SmartThings or S Voice.
Then I saw a thread about this same issue on Samsung's help forum in which the top suggestion was a factory reset. Well, after doing that I was gifted with "Couldn't unlock, try again?" during setup. I tried unlocking with my Note 9 and with a spare OnePlus One, and neither worked.
Lastly I tried to unlock the device by using it in standalone mode, connecting to wi-fi on the watch, and signing into my Samsung Account on the watch, which greets me with: "The Terms and Conditions and the Privacy Policy have been updated. Use the link below to read and accept the legal information, then sign in again. http://account.samsung.com/" before kicking me back to the login screen.
Has anyone run in this before? This watch is a brick
This also only popped up recently. I've factory reset this watch and unlocked it many times before.
I have a Verizon Gear S3 Classic if it matters.
Update: I spoke with Samsung support and they declined to repair this as apparently an Amazon.com receipt is not a valid proof of purchase. I called Amazon and told them all of this and they let me return it for a full refund. That's the last Gear watch for me.
I have this issue also... Has anyone found a fix?
so after 6mounth using this watch suddenly watch disappeared from wearable app and it wouldn't connect again always stuck on 80% or 90% of the process i searched many people faced this issue and had to reset the watch to connect it again and i'm using it on huawei phone (as before i was using) so wearable wont let you connect and you need to force it by samsung and now that i'm connected i cant signing my google account to my watch to restore my apps and watch faces now this google signing problem is there for all wearos users and many people face this problem i tried resetting the phone and watch several times using different google accounts and even tried to do this in a samsung device still the same result any one have any experience or idea about this? me and many others cant use their watches
FIXED!!!
UPDATE : After search for a long time and couple of factory resets and every single way that ppl said it fixed it for them it didnt worked for me until i saw someone had the same problem like me and only connecting to a Canada vpn fixed it for it sounded too random but i tried and it worked so if you have the same problem and other ways dont fix it try this first connect to a canada vpn then start copy account from wearable app on phone
I have a Samsung Galaxy S22 Ultra but ran into this issue when I first bought my Galaxy Watch4 Classic. What I ended up having to do is delete the Google account from my phone all together. Then setup the watch. Once I got the watch setup on the Galaxy Wear app, I reloaded my Google account on the phone, and all worked fine.
dalepl said:
I have a Samsung Galaxy S22 Ultra but ran into this issue when I first bought my Galaxy Watch4 Classic. What I ended up having to do is delete the Google account from my phone all together. Then setup the watch. Once I got the watch setup on the Galaxy Wear app, I reloaded my Google account on the phone, and all worked fine.
Click to expand...
Click to collapse
i tried almost all the ways that fixed some people problems like redoing multiple times disabling screen locks turning wifi off clearing data and caches removing g accounts almost everything out there but still there is too many people with the issue remaining idk why they make it so hard to do this when i could just put in my gmail and password in my watch simply
bhello same problem for 3 days, it annoys me crazy!!! I so regret having bought it, autonomy level is zero and now this bug with Google Frankly is too much
Hello. I had the same problem. After googling for longe time i found out it was a dns related issue.
Link (unfortunately only in german)
Long story short, as i could not figure out how to set up my router, i got it running by simply using mobile data instead of WIFI.
EDIT: I am not sure if i disabled "Private DNS" setting in Android as well
tu Still no response from Samsung? Does anyone know how to fix the problem? Me, I've tried all of them and I'm at the end of it
ste27.jah said:
tu Still no response from Samsung? Does anyone know how to fix the problem? Me, I've tried all of them and I'm at the end of it
Click to expand...
Click to collapse
frankly me too i stopped using the watch couple of days now im gonna redo all the processes that i found in the internet if no luck im just gonna get rid of it cuz it was all working and suddenly stopped connecting to phone and wearable app so it will happen again someday
Did you try using Google DNS 8.8.8.8 while copying?
david.siebauer said:
Did you try using Google DNS 8.8.8.8 while copying?
Click to expand...
Click to collapse
yes still no luck. i noticed after many reset factories my watch still connects to my wifi ap without required password and most of the people who cant solve this problem are using android 9 even on samsung s8 and s9 series
oh yes exactly, very strange the fact that the watch automatically reconnects itself to the wifi and that without any passwords and all that without any restoration!!
JI really hate against Samsung, because no solution is offered anyway went crazy. As usual, the customers remain in a dead end without any help from the manufacturer.
ste27.jah said:
oh yes exactly, very strange the fact that the watch automatically reconnects itself to the wifi and that without any passwords and all that without any restoration!!
Click to expand...
Click to collapse
ste27.jah said:
JI really hate against Samsung, because no solution is offered anyway went crazy. As usual, the customers remain in a dead end without any help from the manufacturer.
Click to expand...
Click to collapse
its either the watch is not wiping the data completely and the issue still remains or they are aware of this problem and cant solve it and even worse they wanna force ppl to upgrade their phones cuz all the new devices can fix the issue but the older devices running android 9 cant fix this and i searched lots of posts on samsung and google forums no official staff answering to the ppl only other ppl trying to help out. i mean why you should need to copy google account from the phone? why not just log into it with your freakin watch
It's not just Android 9. My OnePlus 10 Pro can't sign in. The Samsung sign in send you to a web browser to press continue to sign and just puts you in a death loop of continue button until failure. If you skip this part it fails to log in to Google account and then the wearable app has a bleeping seizure. I've tried resetting the device, restarting both phone and watch, wiping data from app uninstalling and reinstalling all needed apps and plugins.... I think this is a server side issue from Samsung bc when I go to Samsung website after creating my account I'm unable to to link my Google acct just a non functional set up button on the screen... At least my OnePlus watch can tell time this is just a useless wearable until patch is released
RickCambio34 said:
It's not just Android 9. My OnePlus 10 Pro can't sign in. The Samsung sign in send you to a web browser to press continue to sign and just puts you in a death loop of continue button until failure. If you skip this part it fails to log in to Google account and then the wearable app has a bleeping seizure. I've tried resetting the device, restarting both phone and watch, wiping data from app uninstalling and reinstalling all needed apps and plugins.... I think this is a server side issue from Samsung bc when I go to Samsung website after creating my account I'm unable to to link my Google acct just a non functional set up button on the screen... At least my OnePlus watch can tell time this is just a useless wearable until patch is released
Click to expand...
Click to collapse
i updated the first post check it out it fixed it for me i hope it helps you aswell
I have the same proble, VPN no works, I cant copy account google to watch... It is ....
found solution. downgrading gms to 23.05.14 worked for me