Related
My Desire has a huge problem with determining my location in my home. I only use wireless networks to determine the location (I wouldn't have a GPS signal inside anyway). Sometimes my location is being incorrectly determined as Hamburg, Germany - and this was only a minor annoyance until it started changing the time zone to that of Germany. So, I would go to bed in the evening after setting my alarm, and I would wake up in Hamburg's timezone (or even in both timezones - the alarm going off twice). I enabled obtaining the time from the network (this could mean GSM or NTP or both).
The problem must be my wi-fi because:
- I used Google Maps with cellular location on wi-fi-less phone before, without problems
- The Desire's IP address is in the 192.168.*.* family, I doubt they would use that for geo-location
- The external IP address of my wireless router has always been located correctly (e.g. Google.com redirects me to the local website)
- The only explanation is that the SSID of my WiFi is registered in Hamburg and Andoid ignores all the previous reliable clues for location and sets the location based only on a completely unreliable SSID database.
I've been reading forums, and people say there is no way to submit or correct entries in this database. Does anybody know of a workaround or a solution to this?
I don't think it uses the SSID,but some one else asked about it and was refered to this
http://standards.ieee.org/regauth/oui/index.shtml
I think it's more likly to be by ip,anyway here's a link for that too
http://www.maxmind.com/app/city_accuracy
Thank you for the reply. You are right, it's not the SSID, as changing it has no effect. Also, my IP has always been correctly located, including in maxmind's database.
I now think the cause could be the MAC of the router... I can't change that (unless I get a new router) and I can't find any reference about a public database that Google is using. I need to find a solution to this and fast, because it's a deal-breaker and I would have to return the phone.
This is not an issue with your phone. It is a problem with Google maps and Google's location service. Google use the MAC address of the surrounding access points. I had an issue where my location was determined to be 200 miles away when using wifi in a rural area with only one access point in range. I was being placed at my previous address as that is where Google had catalogued the access point (possibly when doing the Street View survey). The only way that I'm aware of to improve this is to submit a bug report to Google on:
https: //services.google.com/fb/forms/wifibugs/
I'm surprised that Google don't collect data directly from Google maps when your phone can see GPS and WiFi signals in order to automatically update their system.
Sorry about the space in the above URL. The rules here didn't allow me to post a URL so I had to post it that way.
Through Google location and online IP trackers, I get placed as 60-300 miles away from my home since a year now- seems pretty random. Doesn't bother me really.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
60-300 miles away wouldn't bother me either. For my location, it gets it wrong by over 1000 miles, while online trackers always get it right. And even that wouldn't be a problem if the phone wouldn't switch the timezone and mess my alarms and calendar.
I mean, what the hell? Cellphone towers and IP addresses are not precise, wifi can position you more accurately, but when these's a 1000 miles distance between the location returned with these methods, which one do you trust? I believe cellphone towers and IP addresses are always more reliable, because they are assigned in a controlled manner.
Been having some issues with callers not hearing me. I tried swapping out the modems (can't remember exactly which ones but can figure it out if necessary), tried different kernels (while I was on TeamSonic rom), and switched from Sonic to FrostyJB and still happening.
I am on wifi calling at my home (crappy signal). It happened on all calls this morning. I made all the above saps and changes this morning as well. I tried a call when I left and was outside of wifi and call worked fine.
This sound like a defect or setting thing? Don't see a lot of settings in the Wifi Calling menu.
Thanks!
There are a few things that could be the problem. You need to determine if it is the phone or the wifi.
What kind of signal are you getting? Are you able to test your wifi for internet? Is this all of a sudden, meaning were you able to use wifi calling without problems prior to this recent problem?
I always had problems with wifi calling so I never use it on my HTC one s and this one too
Sent from my SGH-T999 using Tapatalk 2
pytyper483 said:
There are a few things that could be the problem. You need to determine if it is the phone or the wifi.
What kind of signal are you getting? Are you able to test your wifi for internet? Is this all of a sudden, meaning were you able to use wifi calling without problems prior to this recent problem?
Click to expand...
Click to collapse
It has been happening more frequently lately but I am not really sure on a time frame. I don't make gobs of calls. I have had the phone for about a month or so and didn't have any problems early on. I have tried a few different ROMs but I wouldn't call myself a flashaholic.
My wifi signal at home is pretty decent. My speeds are usually around the 18 - 19 range. No problems with internet. The calls connect pretty quickly.
I do have a cell-fi (sp?) unit on the way from t-mobile which my help but I would just like to try and figure out if something is off with the device.
Thanks!
Information update:
I just made a call from my office (same no cell signal and decent wifi) and call worked fine. Wifi speeds here are a bit slower, usually around 8-9.
Haven't changed router or modem at home. Time Warner Cable is the provider.
Will check my son's phone tonight. He also has the S3 but being a teenager, I am not entirely sure he knows how to make an actual phone call...
Does the problem seem to happen at the same times of day? Depending on how your isp is set up, heavy network traffic can cause the issue. Also remember that your voice going out is like uploading a file on that upstream data is going to be slower than downstream.
Is your cable modem or router kind of outdated? Last year I upgraded my modem and saw a huge improvement. The DOCSYS 3.0 tech is a lot faster than a DOCSYS 1.0 rated modem can handle.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Does the problem seem to happen at the same times of day? Depending on how your isp is set up, heavy network traffic can cause the issue. Also remember that your voice going out is like uploading a file on that upstream data is going to be slower than downstream.
Is your cable modem or router kind of outdated? Last year I upgraded my modem and saw a huge improvement. The DOCSYS 3.0 tech is a lot faster than a DOCSYS 1.0 rated modem can handle.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Today it happened around 8:00 am (EST) and again around noon. I'll check the upload speeds as well.
I swapped out the modem about 4-5 months ago. Not sure of the make. It is the one Time Warner provides. Haven't noticed any major problems with our PC though.
Router does have a few years on it.
I suspect that you're getting one way voice translation... the router is forwarding the incoming voice traffic to your phone but failing to do the same for your outbound traffic. I have a Cisco enterprise class router at my house (I'm an IT geek so I *play* with it) and until I opened up a bunch of ports to a bunch of sites I saw being blocked in the router logs I was having the same issue.
I asked T-Mobile for a list of voice gateway IP addresses at their end but none of the tier 1/2 techs were ever able to give me any useful info regarding IP addresses or ports... The phone keeps finding new IP addresses it wants to connect to so in the end I gave up on getting wifi calling working reliably and have mine set to prefer cellular.
A SOHO or Home router ought to automatically open up the necessary ports but I would suggest looking at the manufacturers web page to see if there's a firmware update for your router. If there is, apply it and see if that fixes the problem. Else buy another one and see if that resolves it. If it doesn't then you can always take it back.
Hope this helps
I thought it was just me that had a wifi problem
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling. It's possible the signal is so weak it's dropping once you have the phone up to your face and it's moving around and stuff. Try using speakerphone with the phone on the desk or wherever you have some signal. You should also try to get a signal booster from tmo.
Definately check to see if there's any firmware updates for your router like ronin said.
Is it a G or N router? If it is N, check your other devices that connect to it as well. If anything connects to it at 802.11G then all connections with the router can be throttled down to G speeds. If so disconnect the G device, reconnect your S3 and try it again.
Also have you restarted the modem and router recently? Unplug them both from power for about 15-30 seconds. Then plug back in and give it a minute or two for everything to reconnect.
Sent from my SGH-T999 using xda app-developers app
I've been having the same problem all day today. I couldn't quite determine if it's my service or wi-fi, until then, I have it off for now.
Please read forum rules before posting
Questions go in Q&A
Thread Moved
Friendly Neighborhood Moderator
psykhotic said:
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling. It's possible the signal is so weak it's dropping once you have the phone up to your face and it's moving around and stuff. Try using speakerphone with the phone on the desk or wherever you have some signal. You should also try to get a signal booster from tmo.
Click to expand...
Click to collapse
Didn't have to do all of this with V2
psykhotic said:
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling. It's possible the signal is so weak it's dropping once you have the phone up to your face and it's moving around and stuff. Try using speakerphone with the phone on the desk or wherever you have some signal. You should also try to get a signal booster from tmo.
Click to expand...
Click to collapse
I didn't know about the cell connection requirement. The cell signal at my house is far north of crappy but the signal in my office is bad as well and no issues. I do have the tmo booster (cell-fi?) on the way. Hopefully that will fix it.
Thanks!
J_Bone said:
I didn't know about the cell connection requirement. The cell signal at my house is far north of crappy but the signal in my office is bad as well and no issues. I do have the tmo booster (cell-fi?) on the way. Hopefully that will fix it.
Thanks!
Click to expand...
Click to collapse
Someone told me once they'll send you one for free if you have lousy coverage at your home. Is that true?
Sent from my SGH-T999 using xda app-developers app
J_Bone said:
I didn't know about the cell connection requirement. The cell signal at my house is far north of crappy but the signal in my office is bad as well and no issues. I do have the tmo booster (cell-fi?) on the way. Hopefully that will fix it.
Thanks!
Click to expand...
Click to collapse
Woah.. holding my phone landscape killed my WiFi calling. WiFi went from 3 bars to 1 and WiFi calling disappeared. Holding the phone the other way fixed it.....I just had an iPhone 4 problem
DocHoliday77 said:
Someone told me once they'll send you one for free if you have lousy coverage at your home. Is that true?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you had good credit they will and you have to have SOME service. Like 1 bar or w.e.
ronin4740 said:
I suspect that you're getting one way voice translation... the router is forwarding the incoming voice traffic to your phone but failing to do the same for your outbound traffic. I have a Cisco enterprise class router at my house (I'm an IT geek so I *play* with it) and until I opened up a bunch of ports to a bunch of sites I saw being blocked in the router logs I was having the same issue.
I asked T-Mobile for a list of voice gateway IP addresses at their end but none of the tier 1/2 techs were ever able to give me any useful info regarding IP addresses or ports... The phone keeps finding new IP addresses it wants to connect to so in the end I gave up on getting wifi calling working reliably and have mine set to prefer cellular.
A SOHO or Home router ought to automatically open up the necessary ports but I would suggest looking at the manufacturers web page to see if there's a firmware update for your router. If there is, apply it and see if that fixes the problem. Else buy another one and see if that resolves it. If it doesn't then you can always take it back.
Hope this helps
Click to expand...
Click to collapse
I believe you are right on. I could not get my Wifi Calling to function properly at work. Text works great, sending and receiving. My phone rings when I receive a call, but I cannot hear anything, neither does the caller. Similarly, when I dial a number, the other phone rings, but no audio is heard on either end. I called TMobile Tech Support and they read me a memo from Samsung that this is a "Known Issue" with "one-way audio" on wifi calling. A salesperson in the store read to me the same memo. Interesting thing is when I got home, everything works, both voice and text. I tried it at another wifi location and everything works also. But not at work. I am convinced it is a problem with the network at work. Puzzle is that Wifi Calling works great on my HD2 with Custom Rom at work using the same enterprise network. But I would hate to keep swapping the micro sim from the S3 into a sim adapter into the HD2 just to get reception at work. I was hoping the upcoming JB upgrade will solve the problem, but reading the above explanation makes me worried now. Anybody out there with any work around?
isaywedoit said:
I believe you are right on. I could not get my Wifi Calling to function properly at work. Text works great, sending and receiving. My phone rings when I receive a call, but I cannot hear anything, neither does the caller. Similarly, when I dial a number, the other phone rings, but no audio is heard on either end. I called TMobile Tech Support and they read me a memo from Samsung that this is a "Known Issue" with "one-way audio" on wifi calling. A salesperson in the store read to me the same memo. Interesting thing is when I got home, everything works, both voice and text. I tried it at another wifi location and everything works also. But not at work. I am convinced it is a problem with the network at work. Puzzle is that Wifi Calling works great on my HD2 with Custom Rom at work using the same enterprise network. But I would hate to keep swapping the micro sim from the S3 into a sim adapter into the HD2 just to get reception at work. I was hoping the upcoming JB upgrade will solve the problem, but reading the above explanation makes me worried now. Anybody out there with any work around?
Click to expand...
Click to collapse
You'd have to have access to the networking equipment at your work to really know the answer why... Short version is that Home routers/firewalls reflexively open ports when a device inside the network tries to access an IP address. UPnP is an example of this... Enterprise class routers/firewalls don't do this as it's considered insecure. So, you have to know what ports the traffic is coming from/going to and allow traffic on those ports. You also want to know what outside IP address it's destined for so you can lock down that traffic to just certain destinations, not the whole internet...
So, if it doesn't work at your office then there's likely very little you can do to fix it unless you're in the IT department or have a really good relationship with the Network Administrator of your IT department.
psykhotic said:
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling.
Click to expand...
Click to collapse
Lol, really? Show me evidence of this.
What would be the point of Wifi calling if you have a cell connection? I've used Wifi calling since my MT4G and that's a total crock of BS
There would be NO POINT to Wifi calling if you have a cell signal.. common sense...
Hi, all.
I'm down in Mexico on TelMex Infinitum internet service with their really lousy Thomson T585v8 DSL router using WPA2/AES security, on, I think, an n signal (router only runs n on a b/g/n or b/g setting, I have it set to b/g/n). My SGS3 firmware is stock unrooted LJ4.
When the wifi connection isn't strong, or the internet speed isn't fast enough, the WiFi Calling icon turns red and gives me an "09" error code saying I need to register a 911 address before I can use WiFi Calling. When I move back into range with full bars on the WiFi signal, sometimes it corrects itself....but other times I need to reboot my phone. It's a pain in the butt and I do have a (US) 911 address registered.
Not really asking for advice....just wanted to make a post about it so that others can be aware (include T-Mobile) of this pesky problem and post their similar experiences (if they are having them). Give me a "weak signal" error, but an incorrect "911 address missing" error and a failure to automatically reconnect is a problem.
Heads up if you are planning on using WiFi Calling on a weak or slow international connection.
I will say that my WiFi Calling voice/call quality has been amazingly good when WiFi Calling is connected down here.
Tldr trying to help anyway. If there is a 911 error then you need to address something within the T-Mobile website and your login. Google search it.
Sent from my SGH-T999 using xda premium
mt3g said:
Tldr trying to help anyway. If there is a 911 error then you need to address something within the T-Mobile website and your login. Google search it.
Click to expand...
Click to collapse
Already went there a few days ago when I first experienced the problem, re-entered and re-saved 911 address information. No change in behavior.
Didn't have this problem on my old Vibrant which I used down here on same setup (our house) as recently as last May.
Can you call T-Mobile from a landline?
Sent from my SGH-T999 using xda premium
mt3g said:
Can you call T-Mobile from a landline?
Click to expand...
Click to collapse
I think maybe you misread my original post.
I have intermittent connection problems with WiFi Calling. I can get it to work, it's just picky and sometimes requires a reboot. I can call 611 via WiFi Calling, but really don't want to bother, as this falls into the "nitpicking" category right now. As long as I can get it to work, get my voicemail, etc., I'm good. No landline here anyway.
I do, however, appreciate your attempts to help.
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
im having an issue with Wifi calling after a while i get an error saying ER081 unable to connect.
i reached out tmo today and they claim its an issue with samsung.
Anyone else experiencing this?
lileddy305 said:
im having an issue with Wifi calling after a while i get an error saying ER081 unable to connect.
i reached out tmo today and they claim its an issue with samsung.
Anyone else experiencing this?
Click to expand...
Click to collapse
Nope. I rely heavy on WiFi calling as the tmo signal is not strong enough at my house.
I believe the error is when the phone doesn't think the WiFi signal is strong enough which can happen even with 5 bars. Get the free VoIP router from T-Mobile and you won't have the problem anymore at home ;o)
This is generally related to your WiFi network, not the phone. It's usually from the AP changing channels, device switching bands, encryption rekey, or some other normally imperceptible change on the network side. The quickest solution is to turn WiFi off and then back on on your phone.
ER081 on G6 at work
I can't connect to the wi-fi calling here at work at all. I have TERRIBLE service with T-mobile here and can't even receive any messages or calls on my phone with the wi-fi calling not working. My G4 worked great....this G6, not at all. SO frustrating.
lileddy305 said:
im having an issue with Wifi calling after a while i get an error saying ER081 unable to connect.
i reached out tmo today and they claim its an issue with samsung.
Anyone else experiencing this?
Click to expand...
Click to collapse
It's not Samsung, it's whatever software T-Mobile is using. I have no cell reception whatsoever where I live and no landline either and have been using wifi just fine for my calls. And yesterday out of nowhere, I started getting instant disconnects on calls the moment they were dialed while the internet worked fine.
And today after a patch, I am getting the er081 error. Did the same thing at a local wifi network as well so the next time I am in town, I'll check the T-Mobile store and then either have them replace my phone or get a refund even though I would rather not have to since I have the 128gb version and have been pretty much using it for everything I used to do on my laptop..
er081 error galaxy s6 edge
I received the Jan 2017 patch and my wifi calling won't connect. I also had to have my frontier router replaced the next day. Any suggestions? Is there a setting in the router dashboard I should know abou
on wifi router add ports forward
4500 udp
5060-5061 tcp
reboot router/phone
should be fixed
raven2099 said:
on wifi router add ports forward
4500 udp
5060-5061 tcp
reboot router/phone
should be fixed
Click to expand...
Click to collapse
Thanks to raven2099
your hint solved my problem on my Oukitel K5000. I had the same errormessage with error 081
obiwan2 said:
Thanks to raven2099
your hint solved my problem on my Oukitel K5000. I had the same errormessage with error 081
Click to expand...
Click to collapse
raven2099 said:
on wifi router add ports forward
4500 udp
5060-5061 tcp
reboot router/phone
should be fixed
Click to expand...
Click to collapse
I know this thread is old, but this fixed my WiFi calling issue. The problem is I need more than one phone to be able to use WiFi calling and my router only allows port forwarding to individual internal IP addresses. Therefore, once I assign the port numbers you have given to one phone's IP, I can't assign them to another phone's IP because it will not allow me to create a conflicting service. Any idea how to tackle this?
My router is Netgear Orbi mesh router RBR50 and also have one mesh satellite RBS50
Phones are all OnePlus 7T Pro 5G
Internet Service Provider is Charter Spectrum
Phone Service Provider is T-Mobile