|
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Yea I wouldn't believe the September date they told you. This is due to the slow speed issues I was having last year, they told me several resolution dates and didn't deliver on any of them and the towers are still messed up despite what the network.sprint.com site says. I would wait it out first but after that then begin to shop around for another carrier.
|
This post has been thanked 1 times. |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Try the maintenance map here:
https://network.sprint.com/ If the problem is only at your house, make them give you a free airave.
__________________
Earn some spare cash and get cash back at stores like NewEgg and more:
http://quickrewards.net/?r=!F94VXV35D5MV2 (My shameless referral link) ![]() ![]() |
This post has been thanked 1 times. |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Quote:
it simply isn't right. |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
sorry I missed what you said, I was kind of busy while doing it and didn't see it :/
|
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Hi, thanks for responding to my question.
I'm not satisfied with Sprint's explanation either, since they can't provide any information that correlates with the start of my problems, and it doesn't explain why I get the same bad reception when Roaming Only. I'm in a well populated area with excellent Verizon and AT&T coverage, so I expected to get good reception on Roaming. Anyone have any ideas to figure out where the problem is actually originating? Any ideas how to tell which network I'm connecting to on Roaming Only? . |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Quote:
You might have better luck with roaming reception if you try a different radio. |
This post has been thanked 1 times. |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
I could call and ask Sprint what partner network they think I should be connecting to, but I guess I wanted to be able to see it for myself. (The completely different tech you're talking about is Sprint and Verizon being CDMA and AT&T being GSM, right? I had forgotten about that.)
Thanks for the suggestion about changing the radio. I'm curious about all things about modifying my TP2s, but I've been having a hard time finding a starting place. I use PHM Regedit for some enabling some hidden settings, but that's it so far. Is changing the radio an advanced task and is it easily reversible? My knowledge level right now is I don't understand unlocking or know how to flash a ROM. I've tried looking for tutorials from time to time but keep getting overwhelmed by unfamiliar terminology. That's probably a question for the WM Legacy Devices area, though. I feel like Sprint should theoretically be able to come out here with some kind of high-tech dowsing rod and walk around following the beeps until they yell, "there's yer problem!" . |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Quote:
If the roaming party allows data roaming and not only voice. you can get your ip address in the browser and based off ip address tell who it is. Also if you trace the tower your connecting to, based on tower code you can tell who it is. There might be other methods available via EPST but those are the 2 I can think off the top of my head. Radios and information can be found here: http://forum.ppcgeeks.com/cdma-tp2-d...-included.html Flashing a radio is reversible, just make sure you don't flash any radio thats not on the list I gave. Unless you are in need of a new paperweight. |
This post has been thanked 1 times. |
|
||||
Re: Perplexed: troubleshooting dropped calls at home
Thanks - though now I'm even more perplexed. I couldn't find out how to trace the cell tower I'm connecting to, but I tried the IP address lookup you suggested, using Tracemyip/Maxmind/Whatismyip. Results:
Sprint Automatic: 246.23.244.x - Sprint PCS, no other data found Roaming Only: 184.215.140.x - Sprint PCS, location Wichita KS (I'm in California!) Sprint Only: 107.37.164.x - Sprint PCS, location Concord, CA (60 mi away but makes more sense than Wichita) Roaming Only: 183.140.38.x - Sprint PCS, location Mission, KS (near Kansas City, KS) Roaming only:173.140.38.x - Sprint PCS, Mission, KS Roaming only:174.154.32.x - Sprint PCS, Wichita, KS Sprint only: 107.39.83.84 - Sprint PCS, Vallejo, CA (70 mi away) Sprint only: 107.32.58.x - Sprint PCS, Oakland, CA (40 mi away) Roaming only: 173.154.182.x - Sprint PCS, Overland Park, KS Sprint (automatic): 107.38.131.x - Sprint PCS, San Francisco, CA (50 miles away) Is the "location" referring to a specific tower that I'm connected to, or the physical location of a server somewhere or something like that? And does it make any sense that when I force Roaming, I still always get a Sprint IP address? Does it make sense that on Roaming, the "locations" are in Kansas, when I'm in California? Maybe these tables are not kept up to date? . Last edited by k8e; 08-06-2012 at 07:58 PM. |
![]() |
|
Tags |
dropped calls, interference, roaming, sprint |
|
|