I have noticed that my Verizon SGS3 will randomly turn WiFi on. It will be off completely and just turn itself on then make a connection with whatever WiFi spot I have previously connected to.
Was wondering if anyone else is having an issue like this?
JsinLegacy said:
I have noticed that my Verizon SGS3 will randomly turn WiFi on. It will be off completely and just turn itself on then make a connection with whatever WiFi spot I have previously connected to.
Was wondering if anyone else is having an issue like this?
Click to expand...
Click to collapse
Chances are you won't get a response on this issue, since there are about a dozen other threads about it. I think it has something to do with a conneciton optimizer, however, Verizon didn't give users the ability to disable it.
Has anyone experienced any issues with missed calls (no notifications) or delayed text messages with their Nexus 5?
I've had the phone since 5 November and it seems when the phone goes into deep sleep the only notifications I can consistently get are ones that are data based (Gmail, email, hangout chat, etc.). At first I thought it only happened while I was on WiFi, but I tested this out by turning off WiFi and using only LTE and then only 3G, but the issue remained.
I've noticed with SMS and voicemails that once I unlock the screen and make a call or send a text I'll receive a deluge of notifications and messages at once, and I've been told that phone calls ring twice as if my phone is off but I never see any notification of a missed call unless there is a voicemail (again, like SMS, doesn't show up until I unlock and use my phone). It feels like the phone drops the connection with a cell tower while in deep sleep or something.
The short list of troubleshooting I've tried is turning off WiFi battery optimization, toggling between LTE to 3G only, and a factory reset. I haven't loaded the stock image from Google yet. I use Textra as my default messaging app, but the messages come in fine when I'm active on the device so I don't believe it's app related. Same goes for phone calls; everything is fine as long as the phone is relatively active.
I saw on the Google support forums that people have reported issues with the WiFi turning off when in deep sleep; at least they are unable to ping the device after a while so I wonder if could have something to do with battery saving optimizations in KitKat.
Anyone have similar issues, or ideas on what I could do to try to fix it?
---EDIT: 2013-12-09---
Here are some links to the Google Product Forum threads that this issue is being talked about.
https://productforums.google.com/forum/#!msg/nexus/eOToYgJXdrw/OLpSbSfPoIQJ
https://productforums.google.com/forum/#!msg/nexus/3gVF5Dm-yG0/R761PwahTxkJ
The first one is the most recent thread, but I'd suggest that anyone that is experiencing the problem and comes across this XDA thread go post in both of the Google Forums to show Google how many are really having this issue. So far nobody from Google has acknowledged there being problem.
I have that same issue, also on TMO. It seems like the phone forgets it's connected to a cell network until you remind it. However, I noticed it first on my HTC one when I installed the stock 4.3 update.
I called TMO support and they reset my line or something. It *seemed* to fix the problem, but I'm not entirely sure because I got my N5 very shortly thereafter. I'm now experiencing the same issue on my N5.
Of particular note is that it always happens in the evening. Even if I toggle airplane mode around 6pm, by 8pm I'll have missed texts. I've just started periodically calling my voicemail to reestablish cell connection.
muffinhunter said:
Of particular note is that it always happens in the evening. Even if I toggle airplane mode around 6pm, by 8pm I'll have missed texts. I've just started periodically calling my voicemail to reestablish cell connection.
Click to expand...
Click to collapse
Airplane mode turns off everything and you will not receive anything until it is back on. Only wifi works.
muffinhunter said:
I have that same issue, also on TMO. It seems like the phone forgets it's connected to a cell network until you remind it. However, I noticed it first on my HTC one when I installed the stock 4.3 update.
I called TMO support and they reset my line or something. It *seemed* to fix the problem, but I'm not entirely sure because I got my N5 very shortly thereafter. I'm now experiencing the same issue on my N5.
Of particular note is that it always happens in the evening. Even if I toggle airplane mode around 6pm, by 8pm I'll have missed texts. I've just started periodically calling my voicemail to reestablish cell connection.
Click to expand...
Click to collapse
Hmm, I'll give T-Mobile a call then and see what they have to say as well. I'm glad I'm not the only one, but it sure is a pain in the ass to have to micro-manage the actual phone aspect of a smartphone, heh.
mistahseller said:
Airplane mode turns off everything and you will not receive anything until it is back on. Only wifi works.
Click to expand...
Click to collapse
I think he meant that he toggles Airplane mode on and off in order to try and re-establish the connection to the cell tower; not that he's expecting messages while Airplane mode is on.
Just to update anyone that comes across this thread, I flashed the stock 4.4 images and still have the delayed texts and missed calls after the phone goes into deep sleep. I currently have a conversation with a Google support tech, but I'm not encouraged by their suggestions at this point.
This just happened to me as well, I'm on Vodafone Romania. I only have the N5 since yesterday, and it's on 3G only, wifi always on. Wifi connects fine, today I actualy got an email from a friend who's been trying to call me unsuccesfuly for 1 hour. I just hope this is sw related, as the warranty is not valid in Romania
Sent from my Nexus 5 using Tapatalk
I just got my n5 yesterday.
I'm in Toronto, Canada on Fido network and twice in 24 hrs I have had the cell network not available, displaying message " emergency calls only."
If I restart the phone it will see the network a minute after it restarts.
What's up with that?
Any help would be appreciated, thanks.
I experienced this problem on every single android phone I've ever had. I dont think its a carrier problem. I think its a OS problem. I've used T-Mobile, AT&T, Straight Talk and Sprint. All of my phones have done it. HTC Evo, evo3d, galaxy s2 epic 4g touch, nexus4 and nexus5.
To me it seems like it happens more often with games. I may be playing a game of Navy Wars (a battleship game) or words with friends. I pick my phone up to do something and as soon as I turn it on I get a notification saying its my turn when actuality my opponent made their move a long time ago. Its also an issue with IM apps like hangouts and whatsapp.
happens on carrier data and wifi.
If anyone has a fix for it I'd love to know what it is.
I have exactly the same issue with my N5 sometimes i get massages 5 or 6 h after they sent. And some missed calls. It never happened to me on my N4 so i believe its phone issue.
I'm glad that I'm not the only one experiencing this issue. I do believe this is a software/OS problem as well, but I find it strange that I couldn't find more about it on Google's support forums or even more threads about it on XDA.
I wanted to update everybody and let them know that Google support put in an RMA for my phone in order to try to resolve the issue. I explained to the support tech that I tried resetting the phone to defaults and reloading the latest images that were posted (KRT16M) and could still produce the same issue without fail; I even took a video with my Galaxy Nexus and sent it to them.
And I gave up on being connected to WiFi all the time. Once I connect to WiFi and let the phone go idle all the issues begin, and then I'll have the problem on 3G/LTE when I turn off WiFi. Rebooting with WiFi off will get me back to normal, but this is obviously very inconvenient and putting a serious cramp in my monthly data usage.
I have absolutely 0 confidence that this is a hardware issue, but at this point I'll try anything so my fingers are crossed that the RMA/new device does the trick since it seems such a small percentage of people seem to be talking about this particular issue.
I'll post an update once I get the new phone and test.
I just wanted to chime in and say I've got the Nexus 5 on Tmo's $30 plan and I haven't experienced this at all. All my calls come through exactly as they should...maybe it is a hardware issue or even a Tmo issue.
I had this problem on Sprint. On one of the Sprint forums (S4GRU), I was told about a Sprint LTE issue. You can read more if you want, but net-net, the recommendation was to switch to 3g in areas where the LTE issue is occurring. Yes, it is a pain in the rear, but it seems to help me at least get the calls that I need. (data is available for me over wifi at this location).
Again, this is specific to Sprint, and only in some impacted areas.
(I did have Google send me a replacement phone - that didn't solve this issue)
There is 2 posts about the same issue on google forum
i can't post link i am to fresh on this forum
but google "Nexus 5 Hangouts SMS messages are delayed" 1st on top
and "Unreliable texting" 2nd
If this is the problem with software why it started like few days ago before everything worked fine
---------- Post added at 10:56 PM ---------- Previous post was at 10:50 PM ----------
Another post on androidcentral
google "Google Nexus 5 - Missed Calls, Anyone Else?"
And i am with T-Mobile by the way
I have zero issues on my N5 with Tmo, texts and calls come through right away. I've had many Android phones and have never had any issues.
Are you guys running any apps like Greenify or anything that is preventing the radio from waking the phone properly>
Having the same issue on different carriers with the same OS where all that they have in common is a Google account, I can see one app having an ill effect on the basic phone functionality.
Sprint does have a known delay with incoming calls, it's a CDMA thing they enable on their end, but it usually only adds a couple of seconds delay.
It happens to me and when it does I realize that the phone is locked onto LTE, when a call comes in it is supposed to switch to 1x. The fall back switching on the phone's software is probably the issue on Sprint.
having the same issues. had to reinsert the sim card. tmobile.
I turned off wifi and restart the phone two days ago so far no problem just not using wifi. Hope google will fix it soon
Did any one report it to google already ??
I had an issue with sms not sending until I would reboot phone. I was only able to fix by getting a new sim card. No issues since.
For the people with issues, are you using a lte compatible sim card, and have you tried resetting the device and using it without any 3rd party apps installed (absolutely none)?
Sent from my Nexus 5 using Tapatalk
Is anyone else having an issue with WiFi calling disconnecting itself, especially overnight? I'm using T-Mobile and when the WiFi calling will stay connected, it works as it should. But often it either won't connect to WiFi calling when reconnecting to my home network, or most often, by the time I get up in the morning, it has fallen off WiFi calling and either has "no service" or is trying to use the virtually non existent T-Mobile signal in my home. I see no indication that it's losing the WiFi connection overnight as it's not reconnecting when I wake the phone up in the morning. I've tried prioritizing the device through my Netgear R7000 router, updating the T-Mobile account settings including the e911 address, making sure my WiFi calling settings on the phone are on and set to WiFi preferred, and rebooting into Safe Mode to make sure a third party app wasn't somehow causing the issue. (The same issue occurred in Safe Mode)
Any ideas?
Thank you all for any assistance you can provide.
Wish I had an idea. All I can tell you is I share in your misery as Wi-Fi Calling is inconsistent for me as well. While it works most of the time, sometimes it’ll drop off for no apparent reason. When it does, I can usually force Wi-Fi Calling to reestablish by putting the phone in and out of airplane mode.
FWIW, I use high-end Wi-Fi gear at home and a custom-built firewall.
Not sure if this applies to you but take a look here:
http://www.androidpolice.com/2017/10/24/google-inexplicably-removed-keep-wifi-sleep-toggle-pixel-2/
It's been my experience that Google's implementation is poor at best for WiFi calling. Constant disconnects are common and sometimes reboots are the only thing that will get it working again. It's been this way since it's inception on the Nexus devices back in the day.
On other devices such as Samsung and OnePlus WiFi calling just works. But it's always been hit or miss on Nexus/Pixel deives.
Thank you all for chiming on the matter. It does make it a little less maddening to know it's not unique to my particular device or network setup as Google customer service would imply. Their solution was to have me send in my several week old "defective" device and get a refurbished one from them instead. Besides offering no explanation as to what kind of hardware fault could possibly cause this issue, I think it's ridiculous that someone making a warranty claim on a device less than a month old for a manufacturer defect would be sent a used replacement, particularly a device at this price point.
If it helps anyone, I've found if I switch the phone to airplane mode, and turn on WiFi while leaving airplane mode on, WiFi calling has been a bit more stable so far.
Hello,
I have a carrier unlocked Pixel 2 walleye that is rooted (magisk, no custom recovery) and on Verizon
android version 8.1.0
build #OPM1.171019.021
when I try to activate wifi calling, i get the spinning circle for a long time, and then it finally says "unable to activate wi-fi calling. please try again later"
I have HD voice activated on my verizon wireless account.
I tried the VoEnabler module in Magisk
Wifi calling is turned on in the phone info screen (*#*#4636#*#*)
The only thing i guess i haven't tried is installing a Verizon ROM instead of the stock Google ROM.
Before I went that route, I wanted to check here and see if anyone else was able to get it to work for them.
Thanks in advance.
ok so i had this issue twice on the same phone and i am rooted as well. i think the only way to get it to work is to disable root, activate wifi calling, then reactivate root.
I have enabled this feature while rooted on 2 different PIxel 2's.
This sounds silly but turn off wifi and try to activate it. I've been unable to input my address during the activation process multiple times unless I am on cellular.
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I don't think your problem is related to root unless it's a Magisk module of some kind that's the problem. I'm on Verizon, rooted with Magisk. I haven't had wireless calling turned on but after seeing your post I thought I'd check and see if it works on mine. It connected without any problems for me.
Did you ever figure this out?
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I'm having a similar issue, except that I can enable wifi calling but always get the "Turn off airplane mode or connect to a wireless network" message when attempting to place a wifi call. Everything with regard to wifi calling is set up correctly. I thought I had this narrowed down to Oreo version and patch level, but I honestly can't come up with a repeatable scenario that breaks it. About all I can say for sure is it seems like when I flash back to bone stock, OPM1.171019.021, wifi calling works as expected. However, it seems to break after a while, even without applying any updates. My gut says it's related to root, but I've also seen it work with root. I also have a suspicion it has something to do with the type of authentication on the wifi network, as the first time I ever saw wifi calling work was when I connected to an open SSID. The problem is, right after that, it worked fine on a WPA2 network on which it never worked before. This is on Verizon with a Pixel 2 from the Google Store. I have a hard time believing it's a Verizon issue, though. It's more like the phone does a check for wifi connectivity and returns "false" for some reason.
*** I should add all my testing has been done by turning on airplane mode (thus disabling LTE/3G) and then enabling wifi. My office at work has horrendous cell coverage, but I haven't gotten it down to zero bars without airplane mode to see if it works then.
Hi,
I'm using a Sony Xperia Z5 Dual Android 7.0 facing that issue making me unable to use my WLAN hotspot (which it pretty anoying cause it doesn't only dissallow me to share my internet connection but also I can't do other network stuff between devices I'd use that hotspot for).
So when I try to turn on my the hotspot it simply turns itself off again after small amount of seconds. When I got to WLAN hotspot in settings then I have the active button to switch the hotspot on while it shows me tbat it's of at the moment. Doing that it says "Activating hotspot..." (pretty exactly that) until it's going off again with a quick "Deactivating hotspot" and you could activate it again but it will do nothing again than say "activating" and go off again. While it is "activating" it already shows the active hotspot icon in the top bar of the phone and the hotspot settings are as well already active and no more inactive greyed out. But only for nk idea, 3 seconds probably. Within that short period of time my laptop didn't find my phones hotspot but that might just be down to an to high delay in scanning and finding so I don't know wether it would shortly pop up seeable for other devices.
Earlier that day I had my hotspot working actively (nobody actually joined) but it worked and would have if somebody joined because that issues is not new to me on my phone and when the hotspot activates, then it also works. But half of the time it seems when I want to use it, it doesn't work. I haven't changed any settings inbetween or restarted my phone. It was probably on for one week, but after then trying a restart it still didn't help.
I already changing some one-click stuff like just turning out WLAN, turning off or on data save mode (which stops background data for all apps in mobile internet and WLANs marked as hotspots), turning off or on mobile data. But well, I don't know anything else and earlier it worked with all the same settings so what could be the problem behind that?? Besides that my phone always just works completely normally without any issues, WLAN always works without problems, only Bluetooth sometimes doesn't want to activate and then I see it active after some minutes or hours later, but that can always be fixed with a restart if I needed it instantly. If you just wait and it is active then tough, it is kinda awoken and works instantly then again shutting it off and on.
Phone is not rooted btw.
Ok long text, but please if you have any ideas tell me..
Greetings, HelpsToMes