Related
My s3 randomly loses connection to the network. Today I picked up my phone to make a call and noticed it was not connected to the network and displayed Emergency call only message.
This happened a few times before too. Initially, I thought it could be a buggy sim so I got a brand new sim from telus. But its still does it. Randomly though. Any thoughts guys?
Anyone?
I haven't really noticed any issues, but I'm on AT&T. What ROM/firmware/modem?
I had similar problems till i disabled LTE. It was trying to connect to it all the time plus it was killing battery.
me and my brother have had the issue in dowtown ottawa on rogers. seems fine in my apt in the market but on a patio and at a restaurant it just wouldnt work!! couldnt send texts, or receive, couldnt call, sometimes it showed i had full bars and lte but couldnt do anything. my brother complained about this the day before. i will try disabling lte next time
Hey I'm a 1st to T-Mobile i'm testing it out before I switch all my lines from Verizon. The question I have is that both the Note II and the GS3 that I have seem to drop the Wifi calling feature randomly. I thought at 1st it may have been some sort of power saving option but it seems to happen in frequently. (Doesnt matter if I'm close to the Router or not)
Is this common? Or am I the only one that has had this happen?
Thanks for any input!
-Scoob
Mine does the same thing I just turned off the wi fi calling app and it now works fine
Sent from my SGH-T889 using xda app-developers app
somethinboutpat said:
Mine does the same thing I just turned off the wi fi calling app and it now works fine
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what you mean by turning the App off? When turning the WIFI calling app off does that not mean you are unable to use the feature?? LOL- I have to have this as I have zero reception at my home.
Thanks for letting me know!
-Scoob
scooby-snack said:
Hey I'm a 1st to T-Mobile i'm testing it out before I switch all my lines from Verizon. The question I have is that both the Note II and the GS3 that I have seem to drop the Wifi calling feature randomly. I thought at 1st it may have been some sort of power saving option but it seems to happen in frequently. (Doesnt matter if I'm close to the Router or not)
Is this common? Or am I the only one that has had this happen?
Thanks for any input!
-Scoob
Click to expand...
Click to collapse
Same here
Sent from my SGH-T889 using xda app-developers app
This is happening to me as well.
@ scoob go to setting, more setting, deselect the wifi calling app and it should work for you my coverage at my place is between 0 and 1 bar so this should help
Sent from my SGH-T889 using xda app-developers app
mine goes on and off on both my new note 2 and my wife's new galaxy s3. really aggravating. worse on my phone, when in wifi calling, it only answered calls like 1 out of every 10 times, otherwise they went to voicemail. I took the sim out of mine, then put it back in and pushed it in and out and in the holder a few times and now it seems to receive calls in wifi mode but still always in and out and error to connect and such.
My experience with Wifi-Calling has been nothing but troublesome. It's really not reliable at all, sometimes calls comes through sometimes don't.. and when it does come through I can hear the caller but caller cannot hear me. This is quite common problem with wifi-calling and i given up.
If you get even a 1bar of reception near by the window, I suggest calling T-Mobile and getting their Cel-Fi device (Free of charge but has to return when you leave T-Mobile). 1~2 bar by the window will give you full 4bar reception throughout the house on 4G. Only requirement is that you must be living in single house, can't ship out to house that are connected by or close by. I live in townhouse and I just told them I live in single house and got the device in 3 days. =)
Wi-Fi calling is a disaster. For me, incoming audio drops constantly, but the party I am calling can hear me fine. On other occasions, the call will just randomly drop. Came from a Sensation where Wi-Fi calling was perfect. There does not seem to be any resolution... I have spent hours talking to tech support and they have replaced the device with no improvement. I have also had my ISP out and they have verified that my connection is fine. I have even changed the router out... same issues.
With my wifi calling, as soon as I turn kt kn my bars at home would drop where I would hardly get any service. As soon as I turn wifi calling off I magically get bars. So I leave it off and now I get bars pretty much everywhere I go....almost
from my Galaxy Note 2 using Tapatalk 2
Nellyinda803 said:
With my wifi calling, as soon as I turn kt kn my bars at home would drop where I would hardly get any service. As soon as I turn wifi calling off I magically get bars. So I leave it off and now I get bars pretty much everywhere I go....almost
from my Galaxy Note 2 using Tapatalk 2
Click to expand...
Click to collapse
With wifi calling on, it's suppose to drop signal bars to nothing. You have to go by the wifi bars instead.
Wifi also greatly depends on your network conditions. Cause I have the same problem but it doesnt happen to me that often after some tweaking.
Wifi Issue
I have that problem quite a bit but the signal strength on my router is good. Yesterday i had my internet company reset the cable modem and my wifi problems have decreased a lot but it is still happing. It has to deal with the wifi certificate problems on the Note 2 (Samsung). It is the same problem that I had on the GS3.
Oh well
ghost_231 said:
Wifi also greatly depends on your network conditions. Cause I have the same problem but it doesnt happen to me that often after some tweaking.
Click to expand...
Click to collapse
what tweaking did you do?
my internet is rock solid. only good thing about uverse service, yet this wifi calling is in and out and in and out all the time.
robl45 said:
what tweaking did you do?
my internet is rock solid. only good thing about uverse service, yet this wifi calling is in and out and in and out all the time.
Click to expand...
Click to collapse
not much for me, just very little. tried to set up QoS and worked pretty good. until my bro starts playing on his xbox, then im screwed on it lol
No issues here with wifi calling.
Nellyinda803 said:
With my wifi calling, as soon as I turn kt kn my bars at home would drop where I would hardly get any service. As soon as I turn wifi calling off I magically get bars. So I leave it off and now I get bars pretty much everywhere I go....almost
from my Galaxy Note 2 using Tapatalk 2
Click to expand...
Click to collapse
Uhh, that's the point of wifi calling, to make calls over WiFi and disable your cellular radio. If you turn on Wifi Calling, you should get a blue phone icon on the top left and your "bars" should drop to nothing as your phone turns off the cellular radio. You can still make/recieve calls/sms/mms.
I've been getting an ER01 error lately with invalid certificate, but it seems to be a T-Mobile backend problem? It happens, about 10% of the time and only on my school's network (I have a feeling, it might have to do with the sign in process there).Otherwise, it works well at my apartment.
achusaysblessyou said:
Uhh, that's the point of wifi calling, to make calls over WiFi and disable your cellular radio. If you turn on Wifi Calling, you should get a blue phone icon on the top left and your "bars" should drop to nothing as your phone turns off the cellular radio. You can still make/recieve calls/sms/mms.
I've been getting an ER01 error lately with invalid certificate, but it seems to be a T-Mobile backend problem? It happens, about 10% of the time and only on my school's network (I have a feeling, it might have to do with the sign in process there).Otherwise, it works well at my apartment.
Click to expand...
Click to collapse
i get that certificate problem at my house, not too much anymore, but I still see it. and the wifi calling does drop in and out at various times. not a huge deal for me, but the average person wouldn't deal with that.
achusaysblessyou said:
I've been getting an ER01 error lately with invalid certificate, but it seems to be a T-Mobile backend problem?
Click to expand...
Click to collapse
I've been noticing more & more problems with my service in the last two months. I called T-Mobile to fix it and whatever they did seemed to only help a little. I get times where I get frequent ER01 errors with WiFi & duplicated text messages (same text message gets received by my phone 2-3 times) for an hour or two. I used to also get errors sending texts around that time, but that appears to have gotten better.
Someone else mentioned Uverse, and my WiFi calling problems are at home & work, both of which have AT&T for internet... When I switched from their DSL to Uverse I expected less problems, but got more.
anyadike said:
I've been noticing more & more problems with my service in the last two months. I called T-Mobile to fix it and whatever they did seemed to only help a little. I get times where I get frequent ER01 errors with WiFi & duplicated text messages (same text message gets received by my phone 2-3 times) for an hour or two. I used to also get errors sending texts around that time, but that appears to have gotten better.
Someone else mentioned Uverse, and my WiFi calling problems are at home & work, both of which have AT&T for internet... When I switched from their DSL to Uverse I expected less problems, but got more.
Click to expand...
Click to collapse
Seems to be a problem that a lot of people are experiencing. Just did a quick Google search and some indication points to a possible T-Mobile back-end problem. I wonder if i call up T-Mobile and ask for wifi calling to be explicitly added to my plan if that'll change anything.
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
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.
When I woke up today, I saw that my phone was on No Service and it wasn't just flipping between full bars and no service for a second like it too often does (including dropping calls a couple of times). I tried to fix it by turning Airplane Mode on and back off, but it did nothing. I went to try to manually choose a tower to connect to mostly to see if the T-mobile tower near me was working or not, and there instead of a tower name it said "Emergency Calls Only". It did let me pick from the list and a disappearing pop-up said it connected, but it never changed to signal and stayed on Emergency Calls Only. So, I restarted my phone. Once it was back on, I had signal, but strangely I also got a Gmail notification about an e-mail that had arrived an hour prior, so I guess even my WiFi wasn't working! Bluetooth did connect fine to my Apollo Neuro anti-anxiety device, but the app was messed up showing it at 100% strength on two different settings instead of the strength they were saved at (and were sent to the device at), which was weird. Everything was fixed after the phone restart.
Anyone else had this happen? The signal issues on this phone are really starting to annoy me! Flipping to no service for a second too often, not connecting manually to any other tower (my plan includes unlimited roaming for talk and data) [I'm not sure if auto roaming works since I haven't been where it would be needed], dropping a couple of calls, not sending texts at times, Chat texting dots turning off often (usually fixed by going into Airplane Mode and back), and now this! I love the phone, but they need to fix it whether it is Samsung or T-mobile!
i thought i was the only one. suddenly no service to any calls but data intact. only way to fix is by cycle flight mode.
jemfalor said:
i thought i was the only one. suddenly no service to any calls but data intact. only way to fix is by cycle flight mode.
Click to expand...
Click to collapse
That sucks. They really need to fix this basic function of this phone!
I've had that issue when getting in areas where coverage is spotty, but never been able to see it go into Roaming..........just "emergency calls only".
ycats said:
I've had that issue when getting in areas where coverage is spotty, but never been able to see it go into Roaming..........just "emergency calls only".
Click to expand...
Click to collapse
It seems that is the issue, that the phone won't roam. That is a mega problem.
My phone was just sitting on the wireless charger all night, and I get full bars (occasionally minus one) here at home, so .