Related
Sprint Samsung Galaxy S6 G920P.02
Android 5.1.1
Rooted, No ROMS
I am very, VERY confused. This makes absolutely no sense to me. I believe my phone is just fried but I will find out when I take it into the sprint store tomorrow. I will most likely get a new/replacement phone but they will have no idea what caused the problem and I need to figure out how this happened so it won't happen again. I'm also very curious as I don't understand at all.
The problem: It started with me not being able to connect to the internet on ANY of my apps. No crashes or anything, just no connectivity to the internet. Calls and SMS still worked like normal. After calling sprint support they told me dial ##72786#, which then just simply broke calls and SMS. Now NOTHING works.
What caused the problem: This is where I am most confused. I was trying to setup a VPN (purevpn, to be exact) on my Xbox One. In the process of this, I was modifying my router settings on my Windows 8 PC, plugged in a 2nd router, and constantly turned the wifi off and on. I was using my phone to test if the wifi was still working. (e.g. going to google.com on firefox or launching clash of clans...literally that was it) The only thing that I can think may have messed it up was a step in settings up the VPN. On my computer, after I installed the purevpn software I located myself to "Network and Sharing Center", then clicked "Adapter Settings", then clicked on "Pure VPN", then "Sharing", then checked the box "Allow other network users to connect through this computer's internet connection", and lastly from the drop down menu, selected "Local Area Network." This allowed all devices on my network to use the VPN. Somehow this messed up my phone that hard?
See image below for clarification:
i.imgur DOT COM /cnAmC6h DOT PNG
Steps I have taken to fix this: I tried rebooting my times a million times. Then I cleared DNS cache in firefox and tried to connect. Then I tried hard rebooting my phone to flush DNS cache. Then I called sprint support, who told me dial ##72786#. After dialing this, calling and SMS DO NOT WORK. "Hands free activation" starting running after dialing that number and fails to work everytime. When I wasn't able to call the phone rep back, I used the sprint online chat support. I told the online rep what happened, and they assured me the only way to fix this was to factory reset my phone. As frustrated as I was, I did it. After the factory reboot, my phone STILL CAN'T CONNECT TO ****. Exactly how it was before the reboot, except I lost all of my stuff. I have done countless google searches and am clueless and need help.
Google will push all your stuff back to the phone after you log into your account. But you'll need the internet for that.
How did you get root?
quatzar said:
Google will push all your stuff back to the phone after you log into your account. But you'll need the internet for that.
How did you get root?
Click to expand...
Click to collapse
I really don't remember, It was months ago. I paid $30 for it though and have never had issues with it.
Just brought it into a sprint tech store and they fixed by putting in a fresh sim card, reseting the phone, cache, dns, and everything they could reset. After that did not work they flashed an updated version of my phones software on the phone, which removed the root , and fixed the issue.
I explained what I did to all of the employees in the store (I was the only one there) and they were all as clueless as me.
Does anyone know what could have possibly caused this?
So, this is bit of a new issue, one I've not had before. I wish Hangouts/Messenger still had the Service Center ID in the settings in order to fix this, but, in the long/short run...
I unboxed my pixel and put my SIM in, started the phone. LTE/UMTS work perfect, locked right on, good signal/speeds, can place/receive calls, all is right in the world? I noticed after an hour I hadn't received any texts, and after feeling very unimportant, I sent a SMS to a friend, and got an immediate error. Out of curiosity, I went into the INFO settings (*#*#3646#*#*) and went into the SMSC settings. pressed refresh, which, populated an error. I manually typed mine, hit update, went back to hangouts, and voila!
The next day, I restarted the phone ( I like to do this often. I am also this user who actually turns their phone off from time to time ) and noticed upon restart, the problem resurfaced, like as if I never updated it to begin with.
Is this occurring with anyone else? I've yet to see a phone completely dump it. I'd prefer not to download another SMS application really, but, it's just inconvenient those few times I do restart it that I lose that SMSC number...
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
I'm having this same issue. I've contacted support about it, but haven't gotten a response yet (they said I would have an update yesterday).
If I manually put the SMSC in, and then Update, I can send texts briefly, but eventually I start getting an error 38 instead. A reboot and then manually entering the SMSC again allows me to send texts again.
vagosto said:
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
Click to expand...
Click to collapse
I'm curious if setting your mobile data to always-on would be a functional workaround to help until they can get this fixed for real. Have you tried that?
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!
Hello, I've had the unlocked Note 10+ for a few weeks and have had chronic issues since day one and not really sure what to do about it. A lot of the issues seem to get worse over time. Not sure if the problems are related, but it feels like it.
First, I have MMS issues mostly with any other app but the built in messaging app and even that one isn't perfect. Using Textra for instance will get me MMS timeouts sending and receiving and sometimes messages don't send or come in. This seems to happen with or without wifi enabled.
Next, I'm getting delayed notifications on many if not all apps. Notifications will some in here or there, then all of a sudden I'll get all the notifications for the day all at once. So suddenly my phone is going crazy receiving 50 notifications from different apps all at once. Related to that, if I get a notification and click on it to open the related app, often nothing happens. Then like an hour or more later the app I clicked on for the notification will pop open in the middle of doing something else. It will also get hung up installing or updating apps. A reboot will usually clear this but at some point it get's stuck again and will take hours to install an app if it does at all.
I've done all the usual things like disabling battery optimization for the apps in question, set the phone to high performance mode. Uninstalled and reinstalled things, cleared the cache partition, reset network settings, checked APN settings, even now have factory reset the phone, twice, got a new SIM card. Talked to Samsung and they tell me I need to mail it to their repair depot in Texas if I think it's hardware.
So no idea where to go with this. Seems hard to believe it's a hardware problem and sending the phone away for a week or more doesn't seem like a great option, especially when they might just send it back as it works OK for awhile after a reboot.
Any ideas would be appreciated. Thanks
After you reset the phone, did you install apps manually from store or let it go off a backup?
Also, just an idea but maybe the tower servicing you is acting up.. Unless it's been happening in multiple areas.
Sent from my SM-N950U using Tapatalk
That is a good point, I did let it install automatically from the Google backup. It wasn't a true restore the way I would generally think of it as everything was installed from scratch, but maybe some settings are getting put back that are messed up. It happens out of the are as well, but I did talk to my carrier and they claimed the did some stuff at the tower that might help. I usually think that means they go get coffee then tell me to reboot the phone. Maybe this evening I'll try a fresh install with no restore. Sort of sucks of course as that's a lot more work to get going, but what the hell at this point. Thanks.
willp2 said:
That is a good point, I did let it install automatically from the Google backup. It wasn't a true restore the way I would generally think of it as everything was installed from scratch, but maybe some settings are getting put back that are messed up. It happens out of the are as well, but I did talk to my carrier and they claimed the did some stuff at the tower that might help. I usually think that means they go get coffee then tell me to reboot the phone. Maybe this evening I'll try a fresh install with no restore. Sort of sucks of course as that's a lot more work to get going, but what the hell at this point. Thanks.
Click to expand...
Click to collapse
Sorry for the late reply. I have a note 10+ myself now unlocked and seeing some texting issues where I don't receive text or mms from Apple phones. Hasn't happened with Android to Android though.
Sent from my SM-N975U1 using Tapatalk
So none of that reinstall stuff helped me. On texting I finally tried the Google Messages app with chat features enabled when it was leaked. Messages alone didn't work, but enabling RCS did and now it actually works better than ever. I hate giving up on textra, but I like the sheer speed of sending giant MMS messages now.
On the notifications thing, the thing that finally got that working right was disabling the Google app. As soon as I did that, all is working as expected. Of course that breaks some Google stuff, but at the moment that's what I have to do to make this work. Even upgrading to Android 10 betas didn't allow me to turn that back on.