Related
I notice sometimes that my wifi will disconnect, and when I go to view the network list my home network will say "disabled" under it. I can connect easily by clicking it again, and it doesn't happen that often, but it can be a real battery killer if I don't catch it due to poor service at my house.
yep! same issue here. Every single version so far including RC1.
Yay. Someone else has the same problem as me!
I don't have this issue, I flash the nightlies (well, nightly). I only have my phone associated with one WiFi spot and that's at my house. I use JuiceDefender so that WiFi is automatically disabled when I leave, and enabled when I'm home (location based).
Bump! I'm still getting this problem with my school's wifi network, and it's a necessity that this works for me becuase I have terrible coverage in my apartment.
I have this issue as well. When the phone sleeps, WiFi will disconnect and the connection will show as "disabled." I, too, am using CM 6.1 and I have the WiFi sleep policy set to "never."
I get this issue a lot at work. I always assumed it did it because I'm usually on the edge of the WiFi network, and so after jumping on-and-off enough, it just disables the network.
EDIT: Here's the word from #CyanogenMod on Freenode:
[11:09] <DrMacinyasha> http://forum.xda-developers.com/showthread.php?t=740773 <--Can anyone/any dev comment on this? WiFi networks get marked as "disabled" sometimes on 6.1RC and Nightlies.
[11:11] <@pb> DrMacinyasha: happens when the phone can't register on the wifi network - for instance, you walk into range just enough for it to try, and then in the middle of it trying to get an IP address, you walk out of range again...
[11:11] <DrMacinyasha> Does it re-enable after a certain period of time?
[11:12] <@pb> DrMacinyasha: generally speaking, no
Click to expand...
Click to collapse
I'm glad someone actually figured this out. I don't have the problem as much on CM6.1, but it does happen occasionally. I usually just disable and re-enable wifi, but sometimes I have to completely forget the network and re-add it.
This morning I decided to do the lollipop update, everything seemed to go well and im pretty sure my wifi calling was working after I did the update, now later on this afternoon I cant get it to connect its showing a wifi calling symbol on my notification bar with a slash through it and keeps telling me Wifi Calling connection error, anyone have any idea how to fix this? Thanks!!
Yep, I'm getting the same thing today. It happened the other day and I restarted my phone and it resolved itself. Today a restart hasn't fixed it. No idea why it's not working. Nothing has changed with my phone's software. Doesn't make any sense.
cody_cummins said:
This morning I decided to do the lollipop update, everything seemed to go well and im pretty sure my wifi calling was working after I did the update, now later on this afternoon I cant get it to connect its showing a wifi calling symbol on my notification bar with a slash through it and keeps telling me Wifi Calling connection error, anyone have any idea how to fix this? Thanks!!
Click to expand...
Click to collapse
I didn't try WiFi calling since the update last week, and sure enough, I had the same issue. I even went as far as doing packet captures on my network to see what the issue was. I found a few "fixes" on the Sprint forums but none worked. So, I have two SSID's at my house, one is 2.4Ghz and one is 5Ghz (a new access point) I always connect to the 5ghz here at the house (but I don't use wifi calling at my house). So, for the heck of it, I switched my connection to the 2.4Ghz and turned on Wifi calling and BAM! It worked(I had previously used wifi calling on this network when I was testing it out when I first got my phone last year)! I switched back to the 5Ghz, didn't work. What I did to get it working: While I switched back to the 2.4ghz AP, i went into SETTINGS-WIFI CALLING, pressed and held on the 5Ghz network and tapped "remove", then re-added that SSID to wifi calling and now it works.
Please note I also have "Wi-fi Range Alert" and "Update address Notification" selected in Wi-Fi Calling settings (three dots on the upper right hand) and it did ask me to update my address information (and I saved the information). Not sure if this is critical, but I can only say this fixed the issue I had. Also note that I had previously tried:
1) Clearing the cache from APPLICATION MANAGER-ALL-> WFC SETTINGS and WI-FI CALLING
2) Dialing ##72786#
I can't say for sure doing the above two things actually did anything to help.
Earlier I tried reprovisioning my phone and it didn't fix it, also tried other things, so decided to give sprint a phone call a little bit ago and they had me go through the provision process again but they were refreshing it on they're end and it fixed the issue, hope the same works for you!!
Edit: Maybe that's what I didn't do was clear the cache before provision, I did it after wards!
MrSickle said:
I didn't try WiFi calling since the update last week, and sure enough, I had the same issue. I even went as far as doing packet captures on my network to see what the issue was. I found a few "fixes" on the Sprint forums but none worked. So, I have two SSID's at my house, one is 2.4Ghz and one is 5Ghz (a new access point) I always connect to the 5ghz here at the house (but I don't use wifi calling at my house). So, for the heck of it, I switched my connection to the 2.4Ghz and turned on Wifi calling and BAM! It worked(I had previously used wifi calling on this network when I was testing it out when I first got my phone last year)! I switched back to the 5Ghz, didn't work. What I did to get it working: While I switched back to the 2.4ghz AP, i went into SETTINGS-WIFI CALLING, pressed and held on the 5Ghz network and tapped "remove", then re-added that SSID to wifi calling and now it works.
Please note I also have "Wi-fi Range Alert" and "Update address Notification" selected in Wi-Fi Calling settings (three dots on the upper right hand) and it did ask me to update my address information (and I saved the information). Not sure if this is critical, but I can only say this fixed the issue I had. Also note that I had previously tried:
1) Clearing the cache from APPLICATION MANAGER-ALL-> WFC SETTINGS and WI-FI CALLING
2) Dialing ##72786#
I can't say for sure doing the above two things actually did anything to help.
Click to expand...
Click to collapse
It was fixed, now its doing it again, I bet its this sweet modem that im renting from Comcast, what a joke of a company
Having the same issue sperradically. Literally just before clicking on this thread I went to my phone and it had the symbol with the exclamation mark, pulled it down said "Connection Erro..." tapped on it, made a 'boop' sound then nothing) which is what I had since I got home around 5:30 today... and by the time Ifinished reading these posts, it went back to "WiFi Calling is Ready"
today I wonder if they were doing maintenence or something since a lot of ppl had the problem, (for me I first turned it on day-before-yesterday and it worked great till today though I might just have been lucky) I tried turning it off and on, I tried forcing stop and restarting, re-setting my location, etc and I still got the same error till just now, so... yeah... Sprint WiFi Calling seems flakey... (I have a skype in/out account I've been using for calls since I dont get decent reception and was hoping to replace it with this, but...)
Same here, decided to update this morning and WIFI calling is dead Jim. Tried reprovisioning after a cache clear, no change. Still dead, which sucks because I depend on it due to my in house signal being so poor.
Anyone have any other ideas?
If your desperate you can do what I did to solve my lack-of-reception...
Set up Skype
Add a skype-in number (~$4/month iirc)
Add skype out subscription (~$4/month iirc)
Activate "Google Voice Integration" on your sprint account
Add the skype-in number to google voice
turn off voice to the sprint mobile device (inside google voice)
Now when people call your number it gets routed through google-voice to skype, which will ring on your phone like normal. (just dont plan on getting a Gear because so far I've found NO way to accept/place skype calls using the gear)
Follow up that has fixed my issue with WFC after the 5.01 update on my Note 4.
Contacted Sprint via Chat.
updated Profile and PRL under system update in settings.
Pulled the battery for 30 sec and restarted. Turned on location and updated E911 settings and I'm back up and going.
Update:
For the last two days I've had no issues with wifi calling except when I went to town (where I dont need it anyway) it even reconnected and worked when I got back home. Dont know if it was a fluke or I've just been lucky, but it seems to have stabilized for me (at least for now) will report back it if acts up again.
UPDATE 2:
welp, looks like I jinxed myself. not been able to use wifi calling all day now...
Noticed a pattern though, last time it did this was when it rained, I wonder if wifi calling requires the GPS to be connected so rain kills it. (or it might be a coincidence, just something to think about)
cody_cummins said:
It was fixed, now its doing it again, I bet its this sweet modem that im renting from Comcast, what a joke of a company
Click to expand...
Click to collapse
Don't rent modems from the cable company. Usually its a cheap piece of crap. For what they charge you to rent the modem you can buy one on anazin/newegg and it'll pay for itself in less then a year
Sent from my SM-N910P using XDA Free mobile app
Both my wife and I have pixel 3's, I have the XL and she has the regular. Both were preordered and delivered at the same time, and we are both on AT&T. Since the beginning we have experienced random issues such as the phone dropping mobile data completely even though the signal shows LTE , and having to cycle airplane mode off and then on again to get data back. The other issue is that we both experienced call issues where our end would drop and we could not hear the other party, but they could hear us fine.
I think I may have traced these issues to WiFi causing the problems. When the data drops, I notice that my wifi is on and occurs when I am not connected to wifi (such as an unidentified network) and on LTE, or when I leave a connected WiFi area (like my house) and keep wifi on. We would have to cycle airplane mode to fix this.
For the calls, I had a call drop yesterday and when I looked at the notification bar it showed connected to wifi. I immediately turned off wifi and the call came right back. I thought this was an AT&T wifi calling issue, so I turned off wifi calling. Today, I was at the post office and had to make a call. Soon after connecting, the call dropped. I checked wifi and it showed unidentified network (not connected), so I turned off wifi. The call immediately came back.
So now, wifi is completely useless to my wife and I. Assuming I don't experience any more dropped data or calls, I cant use wifi to ensure good call quality and constant data.
Anyone else experience this? Could this be an RMA issue? Seems weird that it is happening to both phones. Is there a setting we should turn off that could be causing this?
i have a similar problem where if i am on wifi, when i get off wifi my lte or h+ will show bars but have a small x in the bars. i have to cycle airplane mode to get data back after i switch wifi off. i may just make a tasker task to do this.
i had a call from an s9 yesterday where i could hear them but they couldnt hear me. i think i was on wifi. we tried 2-3 times but he couldnt hear me. when i switched to my google voice phone number and called him, he was able to hear me fine.
there is another thread around here about similar issues. i might try to get a new sim card since this one is almost 9 years old.
dipstik said:
i have a similar problem where if i am on wifi, when i get off wifi my lte or h+ will show bars but have a small x in the bars. i have to cycle airplane mode to get data back after i switch wifi off. i may just make a tasker task to do this.
i had a call from an s9 yesterday where i could hear them but they couldnt hear me. i think i was on wifi. we tried 2-3 times but he couldnt hear me. when i switched to my google voice phone number and called him, he was able to hear me fine.
there is another thread around here about similar issues. i might try to get a new sim card since this one is almost 9 years old.
Click to expand...
Click to collapse
I may have started that original thread a while ago, but since it was more focused on the data drop thing I created a new thread to help narrow the conversation towards the wifi issue. I went to ATT when I first had the data drop issue and got a brand new sim so it is definitely not that.
Just curious if anyone else has had any issues with WiFi calling on their S20 variants. I have a stock S20 Ultra on Verizon. I recently noticed my wifi calling would simply just not connect at all. It was also failing on sending some text messages, problems that I surmised might have been a recent wonky app installed. I then factory-refreshed the phone from scratch, and installed from scratch, manually picking and choosing my apps to avoid the same fate. But even so, my WiFI calling is sporadic at best. Incoming calls will ring in mostly, but if I answer the call, I get no sound at all and no one can hear me. Outgoing almost never works, unless I restart the phone, then toggle wifi calling off, wait a minute, turn it back on, and then wait for the icon to display as WiFi Calling able. Then I can get one call out. I can immediately hang up and try again, any number, and it'll just sit there waiting to connect. I have only been able to test it while on my home network. I did also recently upgrade to 50m Fiber internet, though everything is routed through a Google OnHub router for wireless so I can monitor devices in the home. I'm still connecting to the same band that I was prior, and that my other phones (my S105G and S9+) have had no issues connecting and calling from. I do not have a strong enough signal inside the house for calls to connect over the network, so that's out. All other data on the phone works fine from wifi. Texts work more reliably but still suffer from the occasional Sending Error where it times out and I have to resend. Or it'll take an extra 20-30 seconds before it sends. I get the same results if I connect directly to the modem's Instead.
Are there any other suggestions on settings or checks I can look at between phone and network that anyone can think of? This only seemed to happen within the last couple months, too. When the phone was brand new, everything seemed fine.
Edit: Workaround / half solution found, post #6.
Howdy. I just got the S20+ 5G from Verizon. I noticed my mobile data connection going in and out fairly often and texts getting stuck sending. I also noticed wifi calling draining the battery. I've disabled wifi calling for now. I'm a little peeved a $1200 phone has an issue like this.
I know it's been a bunch of months, but I just wanted to follow-up with this. I haven't found a solution but I've all but ruled out the phone as the culprit. As it turns out, all the other phones suffer from the same issues. I even bought a Verizon LTE Network Extender, which has at least solved my text issue - they work reliably now. But voice calling is still a one-way street. Calls can come in, I can hear the other person all day long but nothing can be said back. Since it happens the same way on all the phones, and since it happens even with the network extender, I can only assume the issue lies somewhere either in the modem settings somewhere that I haven't found, or in the ISP backbone itself. Sadly, they're pretty worthless when it comes to tech support (and I should know - I work for them...). I've tried most things I can think of in the modem/router itself, took out my Google OnHub altogether, and still nothing. I've heard ports opened up being a common issue but for some reason, the ports that most people suggest are already showing in use and unable to be set aside. I revisit the issue every few months, but if I ever do find a solution for my case, I'll post back then.
CharlzO_2000 said:
I know it's been a bunch of months, but I just wanted to follow-up with this. I haven't found a solution but I've all but ruled out the phone as the culprit. As it turns out, all the other phones suffer from the same issues. I even bought a Verizon LTE Network Extender, which has at least solved my text issue - they work reliably now. But voice calling is still a one-way street. Calls can come in, I can hear the other person all day long but nothing can be said back. Since it happens the same way on all the phones, and since it happens even with the network extender, I can only assume the issue lies somewhere either in the modem settings somewhere that I haven't found, or in the ISP backbone itself. Sadly, they're pretty worthless when it comes to tech support (and I should know - I work for them...). I've tried most things I can think of in the modem/router itself, took out my Google OnHub altogether, and still nothing. I've heard ports opened up being a common issue but for some reason, the ports that most people suggest are already showing in use and unable to be set aside. I revisit the issue every few months, but if I ever do find a solution for my case, I'll post back then.
Click to expand...
Click to collapse
From what you've shared the connection issues would point to your ISP. If you haven't already done so request Verizon do a reset on the fiber connection or switch to DSL if they offer it. At times a COLO, the actual distribution point closest to your home isn't properly maintained or the equipment is in need of upgrades or repair. The only other consideration might be a firmware defect. If your S20 Ultra is operating on Unlocked FW you might want to flash Verizon's latest FW to your device. ATT/Verizon are notorious for compatibility issues with non-native FW.
I actually just came back to add more confusion to my post, but I'll answer above as best as I can:
I don't have Verizon for home service, but Verizon Wireless for my cell. My S20 Ultra was purchased directly through the store, with all Verizon updates installed and current. My home internet is new 50/50 Fiber internet, which was just deployed to the area about 8-9 months ago. I was the first person on the loop to be installed, and it runs fine. I could up the speed if I wanted, but have no need for more. It's new cable from the unit in the field, up to the road, and new drop to the house and new equipment. From that standpoint, everything has been rock solid and works fine. I certainly am not letting them off the hook (or, wasn't until five minutes ago) for what might be a setting somewhere between points.
However, during some more testing, someone mentioned they had an issue with WiFi calling not working. So I did more testing with my S20 Ultra. Turns out, WiFi calling isn't even working at all on my device. I can place it in airplane mode (so it doesn't see my Network Extender), enable wifi, and no matter what I try to do, it will not recognize WiFi for calling purposes. I can enable it fine, it shows enabled, I can restart and toggle all day long. But the moment I try to make a call that way, it tells me I must turn off Airplane mode to make a call. This is in spite of the phone having wifi calling enabled, with WiFi set as the preferred call type in it's settings. This is full wifi from within feet of the router. On a whim though, I took out my SIM card and put it back in my S10 5G sitting in it's box. Calling works perfectly, on both wifi calling, and the network extender. So all that did was confuse me more.
I have an S9+ that doesn't work. I have an iPhone 11 Max that doesn't work. I have an S20 Ultra that doesn't work. But an S10 5G that does. It's the only phone I've found in the house so far that I can make or receive calls from/to, and be heard on the other end. All the other phones, connected to the same wifi and the same network extender all suffer from the same thing. At this point, I've basically hit a wall and am ready to throw in the towel. I was ready to spend another evening messing with the modem until my S10 worked perfectly. It worked on the extender fine. I put it to Airplane mode, enabled wifi calling, and within twenty seconds it registered an outgoing call to my house as a wifi call, completed, and could hear fine. A bunch of coincidences all at once. My fiber internet came with a new modem, though the same model that my regular DSL used prior - when everything worked fine. This new one is configured exactly the same, I kept the wifi configuration exactly the same as before to eliminate having to set a dozen devices back up. So I thought that change still somehow did the phones in, as it was shortly after that I realized that they weren't working right. But then the S10 connected just fine, using the same new modem and everything.
Pretty sure I just live in the bermuda triangle of befuddlement here. I'm just going to abandon trying to figure it out, and go back to just calling back anyone that tries calling, from my home phone instead.
A workaround /semi-solution has presented itself:
The reason my S10 worked was because it was connecting to the 2.4GHz radio instead of the 5GHz one (my router is set up with both configured through what is called "Total Control Wireless" where it configures both under one umbrella with the same SSID, security and password and then lets the devices pull whichever it prefers). But my S10 still had my 2.4 guest wifi in it, and connected to that without me realizing it.
By switching my S20 to Airplane mode, and connecting to my 2.4GHz guest wifi, it works. It does NOT work though, if I don't enable airplane mode. I believe this is due in part to some others I've seen posted where the Samsung phones will automatically attempt to use cellular signal regardless of wifi calling enabled or set as preferred. Noting that the preferred call type is under 'roaming' and likely not subjected to just always using it. So it sees a signal at all, be it from the extender or from even a small signal seeping through the wall, and I guess it tries to use that instead of the wifi. Airplane mode on, 2.4Ghz radio, and I can make and receive calls all day, with no issues with voice.
I still have some more to play with, like disabling the 5GHz band altogether, and so on, but for now at least, I seem to have narrowed it down. Even though this router is set up exactly as before, my guess is something in there isn't liking it. I even set up the 5GHz guest radio, which did nothing either. But for now, I at least have a workaround, even if it means having to remember to disable airplane mode when I leave the house. I think there's rules I can make for that somewhere...
Last follow-up. I don't know if this is really a solution, but for future reference:
I disabled the 5GHz radio in my modem/router. For records, it's an Arris NVG448BQ. I'm not sure what would've changed from the old modem to the new, but I guess it's possible that I didn't have both bands enabled on that one.
However, changing to strictly a 2.4 GHz radio has eliminated the issues altogether with my S20. I will be able to test the other phones later but I suspect the same thing. I don't think it's so much the phones as much as it is something somewhere in the 5 GHz side of the router, despite being unable to find any difference in the way they were set up. I even left it enabled as a separate SSID, and still nothing.
I also was able to disconnect my Network Extender (glad I spent money on that...) and thus eliminate the need to toggle airplane mode on and off. I was worried that the phone would still see a trace amount of cellular signal and prevent things from working, but I made a 30 minute test call on wi-fi calling (which now shows enabled reliably and available, no funky restarting or toggling needed), and repeated testing with sending and receiving text and SMS messages are all working as they should once again.
As far as phone-related though, I'm calling this one solved finally. I do suspect that with a better router and advanced band filtering, I could make things work somehow, but I really don't have any need to do so at this time.
Case closed.
Confirm carrier setting. Or re install carrier setting.
Go to setting / general / about.
Network must be Verizon 4G LTE. Network is good all the time.
HD Voice is activated/
Charlz0_2000 gives 2.4 GHz setting is the best solution here available.
As a follow-up to my last follow-up, and I promise after this one, I'm done. The ultimate cause of all this, was a faulty modem - which I half-suspected at times anyway as there should be no reason an S20 shouldn't be able to use the 5GHz band for Wifi calling. My Modem started completely rebooting at random a week ago, and I finally was able to get a replacement today from my ISP. As soon as I had it installed and configured, I connected to the 5GHz band with my phone and was able to make and receive calls over WiFi with no issues at all. I will keep the bands separate as I do have some smart devices that have a hard time with the "smart" umbrella that the modem defaulted to.
But just for future trouble-shooting for others with WiFi calling issues, it's worth a shot to try one band or the other specifically as a work-around.
Cheers all.
Hello Folks,
In summary, the WiFi stack on OnePlus 11 is quite unstable compared to other smartphones (that are also based on Qualcomm SoC with built-in modems).
First off, I've two 802.11 AC (WiFi 5) routers. Compared to my Asus (ROG 5) and Motorola (Moto G 5G Plus) phones, I've noticed that my new OnePlus has better reception for both mobile and WiFi networks. E.g., at the same location where ASUS has say -30db signal, OnePlus 11 shows -27 or -28db. So performance wise, it's fantastic, however, stability of WiFi connectivity is subpar. Between performance and stability, obviously I always prefer stability. I've up-to-date OnePlus 11 CPH2449 device (CPH2449_11_A.08).
I've been using the phone for about 5 days & these are the three distinctive WiFi problems with OnePlus 11 that I've observed in that duration:
1. WiFi dieing silently:
I've seen many times that all of a sudden the WiFi symbol will disappear. Then checking the status of the connectivity will show that it had silently dropped/died. Sometimes, it'll reconnect on its own within 10 odd seconds. When it doesn't, then toggling WiFi off and then on may help. When even that doesn't help, then toggling airplane mode on and then off becomes necessary/only-way to re-establish the connection. During these episodes, the phone is barely 2 metres away from the routers with a clear/unobstructed line of sight with them. Needless to say, neither ASUS nor Moto exhibit this problem while these episodes are playing out with OnePlus 11.
2. VoWiFi dieing silently:
While operating the phone (non-phone-call situations), a number of times I've seen that the VoWiFi logo would drop and VoLTE logo would appear. Interestingly enough, within a matter of 10+ odd seconds, it'd re-establish the VoWiFi connectivity on its own.
3. WiFi not roaming efficiently:
When moving faraway from one router and close to another, it doesn't roam to the closest one, instead holding onto the furthest one. But putting the phone down for say a minute with the screen off, triggers the roaming to the closest router! WiFi assistant neither helps nor hinders this behaviour.
In short, it'd seem the whole WiFi stack is riddled with stability issues. I've done "Reset Network settings", which didn't help with those issues.
Am I the only one facing these issues?
Thanks for any help/guidance.
Wifi Issue
Anyone have wifi dropping off and reconnecting after flashing to oxygen os? I seem to keep experiencing this. Anyone have any fix?
forum.xda-developers.com
No issues with Wifi.
Just downloaded over 130GB over Wifi and ftp server on the phone without a single interruption. Took over 3 hours and no problem.
I have similar issues. My wifi will randomly drop out and then pick up again in that time sometimes it will say internet offline. I've been noticing it the last week or so when that happens.
I've escalated my problems to OnePlus support. After a number of discussions, I think we got the winner: Disabling ipv6 in my WiFi network seems to stabilise it!
I've been trying this only for the past few hours, but it's proving positive so far. Still I'd prefer to test this over at least a day or two.
I've had WiFi just stop working finds no networks. Even turning the toggle off and back on again doesn't work. But after a reboot works fine again. Mines a euro model on fw09
sutt359 said:
I've had WiFi just stop working finds no networks. Even turning the toggle off and back on again doesn't work. But after a reboot works fine again. Mines a euro model on fw09
Click to expand...
Click to collapse
I've seen similar behaviour. Turning flight mode on and then off helped me on those circumstances. Mine too EU version CPH2449.
Now, if the root cause is identified and addressed, then it ought not to even regularly disconnect from WiFi in the first place, so subsequent problems like reconnection issues can be avoided then.
Disabling ipv6 has proven to be a good workaround for vastly improving my phone's WiFi stability. Of course, they need to identify and resolve the problem that's making WiFi & ipv6 incompatible though.