Develop Bugs

Problem with Data Connection

I replaced my galaxy s 2 because it was acting up and now i have rooted one and also put stock rom bloat free and i recently noticed that sometimes my phone have hard time connecting to data. i can see the uplink sign go green but the downlink arrow doesnt blink and phone keeps me waiting waiting and waiting and i have to restart the phone or leave it for good 5 or 10 minutes to be able to start working. can anyone please tell me if thats a hardware issue or the software? do i need to have my phone replaced?, i dont know if tmobile store would exchange phone now because i purchased phone on 12th and its been 12 days if the reffer me to customer service then they will send me a refurbished phone which i do not want because i paid full price for phone.
any help will be appreciated.

Data connection problem
If you haven't already tried, go to Settings/Wireless and network/Mobile networks/Access Point Names and if there is an option to reset, select it. I had a similar problem with data connections - up and down lights blinked but no connection - and T-mobile support helped me out. Also, make sure Use packet data and Data roaming are checked.

mtmikey said:
If you haven't already tried, go to Settings/Wireless and network/Mobile networks/Access Point Names and if there is an option to reset, select it. I had a similar problem with data connections - up and down lights blinked but no connection - and T-mobile support helped me out. Also, make sure Use packet data and Data roaming are checked.
Click to expand...
Click to collapse
I've had the problem too, both on 4G and WiFi. There is a warning on the data roaming option about incurring extra charges. Is this true? I know that my plan says free domestic roaming, but I'm not sure that applies to data?

The T-mobile rep allowed that this was confusing. They stated that there are no additional charges within the US. Roaming is required because TM uses other providers' (i.e. Verizon) towers in some locations.

I have this same problem, Im wondering if the update coming out next month for wi-fi calling will address this, or what about using the new sim card??? Its pretty annoying but i didnt want to really exchange my phone b/c this is the only problem im having as well as the vertical lines which i have pretty much learned to live with.

K_esco said:
I have this same problem, Im wondering if the update coming out next month for wi-fi calling will address this, or what about using the new sim card??? Its pretty annoying but i didnt want to really exchange my phone b/c this is the only problem im having as well as the vertical lines which i have pretty much learned to live with.
Click to expand...
Click to collapse
i am using the new sim card already... i dont know if the problem is with new sim card or the phone itself but it gets annoying sometimes when i need internet and it doesnt wanna work.

Has anyone had any luck fixing this?
I noticed this problem sometime after rooting and flashing roms. Now I'm on the stock rom released in the dev channel. I've talked with customer servie for an hour and none of their solutions fixed anything for me.
I don't have a good backup - is there anything I can do?

I haven't been bitten by this again. It has been a couple days and I've since replaced my phone (today). But I haven't been on 4G much. Wifi has been working fine for the last couple days.

WiFi Calling

My WiFi Calling has never worked properly, and attempts to get support from Sprint have only ended in frustration. It works fine on incoming calls, but almost always (its worked once or twice) within 10 seconds of initiating an outgoing call the call is disconnected and my WiFi Calling is disabled for about 30-50 seconds, after that WiFi Calling turns back on. I assume that something is causing me to be disconnected from the WiFi Calling server. Sprint can't even tell me who runs the server if its them or a third party). They have told me it was related to my geographic location, but I've demonstrated it having the same behavior in multiple Sprint stores on their Wifi networks. The latest is that they are telling me to upgrade to Lollipop (which I haven't tried yet). Can anyone enlighten me or anything?

I've noticed that wifi calling is flaky. Sometimes it doesn't work, most of the time it does. Sprint support was able to help me fix it one time. If you've tried to go into Sprint stores for help and called Sprint support, maybe turn it off and wait a week or so and then turn it back on....i know it sounds like a crappy answer but that's what I had to do.

DarkManX4lf said:
I've noticed that wifi calling is flaky. Sometimes it doesn't work, most of the time it does. Sprint support was able to help me fix it one time. If you've tried to go into Sprint stores for help and called Sprint support, maybe turn it off and wait a week or so and then turn it back on....i know it sounds like a crappy answer but that's what I had to do.
Click to expand...
Click to collapse
I appreciate the answer, however this problem has been going on for months and it has not been "flaky" for me. All incoming calls work. All outgoing calls (with two exceptions) have been experienced what I previously described. This has been going on for many months. This problem isn't going to fix itself. Now, Sprint claims that the Lollipop release includes "enhancements" to WiFi Calling, so perhaps that might fix something. I doubt it though.

Wifi Calling issue

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

WiFi Calling dropping calls...

Ok, it seems for me the issue with wifi calling not working at all is resolved (I always have the "Wifi calling is ready!" notification) but when I receive a WiFi call it will randomly disconnect after a few minutes. Might be 5 min, might be 20, and after that if I or they call back it might disconnect in as little as 2-3 minutes! Doesn't seem to matter if I answer on my handset or my GearS, still always drops in <20 min.
It's not my internet connection dropping, I also have Skype with In/Out running and can place/receive calls on it without any interruptions (on both my N4 and my PC).
Any suggestions?
Phone is 100% stock, not rooted, Android 4.4.4.

Wi-Fi calling was a PITA on KitKat with my Netgear router. Netgear support and DD-WRT forums for my router were both saying to disable the firewall. Forward porting and setting my phone as DMZ with static address didn't help with UDP packets and maintaining a connection.
Lollipop its better and the reason I'm not going back to KitKat but hardly tolerable without root.
I know this doesn't apply to you but with Adaway, I monitored the DNS requests for Wi-Fi calling and whitelisted them. That seemed to help with the Wi-Fi connection list issues. There's webservicesgateway and vowifi dns requests to look for. Didn't post for security concerns.

Yeah, I'm scared to make the jump to lollipop because right now my GearS is working perfectly and I'm scared to change anything major (spent 2 weeks fighting in on the "compatible" SGN2, finally said "screw it, I'm due for an upgrade" and got the SGN4) as Is aid I've not even rooted my SGN4 for fear of 'breaking' my smartwatch...
Router could be the issue, since it's a brand I've never heard of before ("ComTrend") but It's a router/modem combination that my ISP requires so I cant swap it out... may try the suggestions you mentioned, just in case, but not going to hold my breath...
If anyone else has suggestions, please post them. Right now I'm in a situation where I need VoIP (I literally get 0-1 bars reception, so bad that if I answer a call it drops) and to get Skype to work I have to turn off calls comming to my handset (otherwise the Phone App overtakes skype, then drops the instant I answer) which means I miss calls when NOT at home thanks to skype playing poorly with my cellular data... >.<

Off topic: did you consider asking Sprint for an Airave unit? Bad cell signal.
Mine was free to use and got exchanged/upgraded for newer model a couple of times.
I let mine go with Wi-Fi calling because it conflicts. Had to pick one.

I've had two actually. Back when it was amde by Samsung it worked GREAT, (thought they charged me soemthing like $5/month for it) but now the new "Airvana" version has stopped getting a GPS signal... why I cant program it in I dont get (since WiFi calling works with out constant GPS) It's been sitting around gathering dust for a while, I might get it out and try to make it work again, maybe they upgraded their system enough that it wont turn off... or maybe I'll try sticking it in the attic or something... thanks for the suggestion!

Not connected to Mobile Network after being on Wifi?

This has been a frustrating issue I've been having pretty much since starting up my T-mobile service about a month ago.
To start off, my G3 is unrooted and on the latest stock software version, 20e.
I use Wifi calling often because I get 0-1 bars of reception at work. All seems to work well until I go outside and try to make a phonecall over the voice network. I'll have plenty of signal bars, be connected to 4G even, yet when I try to use the phone dialer to make a call it will say "Not connected to Mobile Network." or something along those lines.
I haven't done extensive testing, but I believe the other day I toggled the "Mobile Data" off then back on and was able to make calls.
Has anyone else had this trouble? Is it something possibly to do with Wifi and/or Wifi calling?
I believe I could make a phonecall using Hangouts when I was off of wifi, which tells me that the data part is working, but not the voice network.
I contacted T-mobile support, but they just had me do the "typical" things, like shut down the phone, remove the battery/SIM, start everything back up. And sure enough, it worked after that, but I'd rather not have to restart my phone or toggle stuff to get it to work as it should without any hassle.
Thanks!

My wife has the same problem after the 20E update. Her mobile is stock as well. It did not happen on 20B.

thewalkingdude said:
My wife has the same problem after the 20E update. Her mobile is stock as well. It did not happen on 20B.
Click to expand...
Click to collapse
Interesting.... so is there a known solution for it?

rubejb said:
Interesting.... so is there a known solution for it?
Click to expand...
Click to collapse
Off the top of my head no. I'll dig around a bit and see what if anything I come up with.,

From the digging I did I can't seem to find any help. The only thing I can think of is to factory reset it thing and see if it helps. I am going to do do it on my wifes phone tonight.

Yeah, that's what I was thinking too... I'm not really in the mood to deal with restoring all of my apps and whatnot, so I'll hold off on the factory reset for now.
If you remember, could you let me know the results? If I know for fair certainty that a wipe will fix the issue, I might do it.
Thanks!

It's a network problem and it is worst on Samsung phones. I recently went and got a new sim card and it seems to have fixed it. I read it is because if you live in a area where there is poor coverage it causes your sim to where out fast.

punkhawaiian said:
It's a network problem and it is worst on Samsung phones. I recently went and got a new sim card and it seems to have fixed it. I read it is because if you live in a area where there is poor coverage it causes your sim to where out fast.
Click to expand...
Click to collapse
This started happening before my first month of T-mobile service was even up with a brand new SIM. I'm not saying that it's definitely not a SIM issue, just would seem unlikely that it's worn out that fast.

Mobile out of Network-Tmobile - Android
I;m having the same issue, turned phone off and on, checked Network connections everything looks fine, but now able to receive and send texts or make calls.
rubejb said:
This has been a frustrating issue I've been having pretty much since starting up my T-mobile service about a month ago.
To start off, my G3 is unrooted and on the latest stock software version, 20e.
I use Wifi calling often because I get 0-1 bars of reception at work. All seems to work well until I go outside and try to make a phonecall over the voice network. I'll have plenty of signal bars, be connected to 4G even, yet when I try to use the phone dialer to make a call it will say "Not connected to Mobile Network." or something along those lines.
I haven't done extensive testing, but I believe the other day I toggled the "Mobile Data" off then back on and was able to make calls.
Has anyone else had this trouble? Is it something possibly to do with Wifi and/or Wifi calling?
I believe I could make a phonecall using Hangouts when I was off of wifi, which tells me that the data part is working, but not the voice network.
I contacted T-mobile support, but they just had me do the "typical" things, like shut down the phone, remove the battery/SIM, start everything back up. And sure enough, it worked after that, but I'd rather not have to restart my phone or toggle stuff to get it to work as it should without any hassle.
Thanks!
Click to expand...
Click to collapse