|
||||
Re: TP reception sucks
|
|
||||
Re: TP reception sucks
Haha....yea well its good to see it does make some difference, still no proof on the battery life however.
|
|
||||
Re: TP reception sucks
my buddy has a vogue on sprint i tweaked for him-kept the stock sprint radio though
last wknd he was gonna call my other buddy but didn't have signal, busted out my phone and made the call standing right next to him using the telus radio...
__________________
If someone (like me) helps you out, press !! only takes a second... !
Mogul -> Vogue -> TP -> TP2 -> Snap -> Evo -> 3D |
|
||||
Re: TP reception sucks
I don't really have a basis for comparison, since I was previously on a 700w on Verizon and I never missed a call anywhere, but now on my TP on Sprint I miss calls all the time, even when I have a bar of signal. The problem is ESPECIALLY bad if my phone is in my pocket (where I keep it most of the time, unfortunately).
I can't tell if it is a Touch Pro problem, or a Sprint problem, except that if I force roaming I still miss calls (which makes me think the TP just has ****ty reception, at least in respect to any other phone I've ever had). Because I was getting sick of counting on the inaccurate, and fluctuating "bars", I did some tests using ##DEBUG# I don't know exactly how the dbm correlates to the "bars", but it seems to be about (when I say "less" I mean smaller absolute value): less than -85 = 5 bars less than -90 = 4 bars less than -95 = 3 bars less than -100 = 2 bars less than -105 = 1 bar greater than -105 = 0 bars Anyway, I've noticed a few things. 1) When on Sprint network, if it is worse than -100 dbm then the calls won't come through. What is more annoying is that even when I drop down to less than (absolute value) -100 I still won't be able to receive calls, even when it goes down to -90 or even better. Sometimes when doing this, even when my Power reads ~-90 dbm my "bars" will turn to the "searching for signal" icon". Usually when this happens, though, my Rx Ex/Io values have gotten pretty high (this is the signal noise?). The phone can be in the exact spot I usually get "good" signal with, but if I had just come from "bad" signal, then it takes upwards of a minute or so of being in "good" signal before a call will be able to come through. 2) if I set it to roaming only, then I can sometimes get calls when my signal is worse than -100 (in my tests, I recieved 3/4 of my calls at -101 to -103), and as soon as I get back into "good" coverage, the calls still come through. 3) if I have it set to "Automatic", then it basically acts like I'm on Sprint, where if the signal is worse than -100 then it screws everything up for a while. I don't have similar numbers for my 700w on Verizon, but I do know that I pretty much never missed a call. I got the TP on Sprint figuring that I could always just force roaming to use Verizon network when I needed, but even then I'm still not getting great reception, which again I attribute to worse reception. I've debated trying to replace it, but I'm just worried this is as good as it will be. I've even changed to the Telus 1.04 radio, which "seemed" to give better results (slightly fewer missed calls) but I haven't done any scientific tests to check this out, and I'm hesitant to flash radios back and forth. |
|
||||
Re: TP reception sucks
Same issues here. Missed calls, late text messages, late voicemail notification. Had a Mogul before and I rarely missed a call, if I did miss a call voicemail was instant.
I hard reset my touch pro, advanced tech support tried resetting my account, I took it to a Sprint store they tested it and said it was fine. I finally just got a new Touch Pro yesterday to try. So far texting is still unreliable on my new Touch Pro, but I'm pretty sure that's at least partially a network issue because even outgoing ones are getting to my friend late on ATT. In my limited tests I haven't missed a call yet but it's early so time will tell. I love this phone otherwise, but this issue is totally unacceptable. |
|
|
|