This post has been thanked 1 times. |
|
||||
Re: Common NAM Performance Tweaks.
Quote:
I'm gonna test this out, cause mine came defaulted to 5 and I notice beter connect-call times now that I set it to 2. I'm willing to beleive it's a placebo. but I'll post my findings/placebo effects.
__________________
Kitchen:Calkulin's VK for WVGA (Updated with Touch Pro 2 Collaboration)
ROM:Custom6.5.x(ScubaGear) My Files: Mediafire Folder When it's deserved, click |
|
||||
Re: Common NAM Performance Tweaks.
I did a quick search for Canada's wireless priority
Quote:
As I'm on Telus, and Telus already offers WPS, and my ACCOLC is already '9' (my phone # ends in that too), I think I'm set |
|
||||
Re: Common NAM Performance Tweaks.
Quote:
so i dont think is something to be with the nphone # |
|
||||
Re: Common NAM Performance Tweaks.
I'm on Sprint. Just read this whole thread... Pretty Confused if either 0-1 is the best or 9 is the best to set it to. A while back I set it to 2 from 9. Since then i've noticed it takes like 5 secs for my phone to connect to the network before it places the call. Most of the time ...
Just now changed it to 9, which I think is my default value being my last digit is also a 9. Wow...my calls are placed awhole lot faster, and more successful then before at the 2. Thats my experience. I think this thread needs hard proof evidence, not people going back and forth saying this and that. Lets see some real evidence. Sorry just being truthful, not trying to step on anybodies toes or hurt anyones feelings. |
|
||||
Re: Common NAM Performance Tweaks.
Uh, yea... too many seasoned industry professionals claiming contradictory information. Don't get me wrong, I completely respect each person's background and input formed from that background--but it's frustrating and confusing.
Anyway, I had that same error another user had with the first MSL program: "Check Unlock code failed. Please input again." This was after inputing the MSL generated from my DECIMAL MEID. After checking and rechecking that I entered the correct Dec MEID, I tried the HEX one, and got a different MSL, which I guess makes sense... but BOTH MSLs give me that "Check unlock code failed" error. I then downloaded that BAF MSL Grabber, and I get an error each time that says "MissingMethodException This application requires a newer version of the Microsoft .NET Compact Framework than the version installed on this device". Ha, my luck! |
|
|
|