ImmerStark

I've been hearing a lot of news lately about the drought in California being past the critical stage and the likelihood of a large chunk of the population being forced to relocate when the ground water is exhausted next year. It occurred to me that this would throw a major wrench in network planning and the allocation of resources. So, any speculation or insight on the how that will be handled?

Of course you never have zero bars, at&t has the "strongest" network. Like back when they had more bars in more places. What I really want to know is: how many of those bars were topples? *topless

Seems like even after the lollipop update this is still an issue.

I really hope the screen is flat. I recently put a glass screen protector on my S5 and am kicking myself for not using one much sooner, it is freaking fantastic. Since Samsung has betrayed me with their iPhone clone S6 I will be looking at other options for my next upgrade.

Duplicate post

I have a first generation galaxy gear and while I love it that big curved display on the gear s is just so damn sexy. I just can't bring my self to spend the money on it though because I can't wear it at work :-(

I frequently work in the NE part of Harrah up to Hefner Rd and out to 3360 Rd. A t-Mobile phone is a paperweight in much of that area and I don't mean because it is only EDGE coverage, there is no service at all.

It seems like there are no good options here. At&t and Verizon have horrible voice quality but good coverage where as Sprint and T-Mobile have great voice quality but coverage/network issues. Sent from my SM-G900P using Tapatalk

My data works pretty reliably most places but I've been having issues with incoming calls not ringing my phone when on LTE or Wi-Fi calling. Is anyone else experiencing that? Sent from my SM-G900P using Tapatalk

Verizon and at&t are notorious for using low encoding rates on voice calls. Sprint has always sounded better than Verizon and T-Mobile has always sounded better than at&t. A big part of why I left Verizon was because of the voice quality, it was especially bad when calling someone on at&t. Conversions were so muffled and garbled as to be unintelligible. The outrageous price was the other big factor. Sent from my Nexus 7 using Tapatalk

This is starting to sound like a case of vocoder mismatch. Most call centers use VoIP as does google voice, if they are both using the same vocoder things will be peachy keen. If however you the calling party(you) and the receiving party(call center) are using different vocoders things get rough. Each vocoder has a unique way of determining what information is acceptable to lose when compressing the voice information. To grossly simplify it we can say a voice frame consists of information A, B, C , and D. Vocoder 1 may drop A to achieve required compression and vocoder 2 may drop C to achieve the same goal. If both parties are using the same vocoder then only either A or C is dropped. However if you have one party using vocoder 1 and the vocoder 2 then both A and C are lost which greatly diminishes the integrity of the information. Since this effect is less noticeable when compression is less lossy newer codecs should theoretically improve it. Since the primary improvement with HD voice is improved frequency range and to a lesser extent improved encoding efficiency it may help. The real question is if network operators are willing to sacrifice the network resources to pass all calls as HD for what may end up being a negligible benefit. My guess is that they have tested it and determining that the gains do not justify the cost. Sent from my Nexus 7 using Tapatalk

Is the Google voice call being routed over Wi-Fi or CDMA? Sent from my Nexus 7 using Tapatalk

It wouldn't help, the issue is most likely in the call centers phone system or the pots link. A call to a local landline might be better though.

I don't see this being an issue, Sprint and Verizon devices diverged several years ago. Almost all current devices are custom radios tailored to the carrier with the exception of devices like the Nexus 5. Sent from my SM-G900P using Tapatalk

I think Verizon and Sprint are taking the right approach. Voice service is far too important to risk messing it up with a network or technology that isn't ready. I for one hope that Sprint doesn't stop selling CDMA capable handsets for the foreseeable future. The 15db advantage CDMA has over LTE at the same frequency means that it is unlikely LTE coverage will ever be equal, unless of course we see some 400MHz spectrum cleared and auctioned for LTE.

I'm curious about this Korea mode as well, please allow us to learn from your actions so as that we may not be doomed to repeat them.

I do not have one.

Forced CDMA only and got this. Sent from my SM-G900P using Tapatalk

Data roaming is enabled, but even with native sprint coverage I get no data. The phone kicks out an error code. I think it was 67, I'll have to pay closer attention next time it happens. Sent from my SM-G900P using Tapatalk

Since upgrading to my Galaxy S5 I have noticed that when I fall back to 1xrtt I have no data connection available. The same thing happens when I'm roaming on U.S. Cellular. 1xrtt worked for data on my single band S4. Is anyone else experiencing this on tri-band handsets?

There have been two new sites added in the OKC market in the past month. One at 59th and S. Shields which I'm thinking might have been added for capacity more than coverage. Another at SW 74th and Council which is 3 miles away from two other towers so I think it may have been for coverage reasons. Sadly a good deal of SW OKC that has been growing rapidly for the past 20 years is still lacking in much needed sites. The worst thing is that there are a couple of former Nextel sites that have been decommissioned that would have been ideal for conversion or at least close to it.

If the tower got 800MHz LTE at the same time it got 800MHz CDMA then it could very well be the issue. I don't know how Samsung and ALU do it but after Ericsson lights up Band 26 they take their sweet a** time coming back and enabling eCSFB. I had to disable band 26 on my phone for a while until eCSFB was enabled on the majority of sites.

Not quite as good as pcs evdo but it's much improved over pcs lte. Sent from my SM-G900P using Tapatalk

I haven't been in Norman recently but I can tell you that in many parts of the metro I have almost seamless lte now. Band 26 has been improving rapidly. Give Ericsson some time to finish the optimization and I bet it will really knock the socks off T-Mobile coverage wise. You might want to consider upgrading to a better supported device too. It's my understanding that the nexus 5 is the red headed stepchild of triband devices. Sent from my SPH-L720 using Tapatalk

I figured I would throw this out there just in case it is the culprit but when band 26 started rolling out in my market band 25 reception decreased by about 8db which made a pretty big difference. Many of the places where I used to get LTE I was banished to 3g land. This was on my single band GS4. I've since upgraded to a GS5 which is tri-band and now have band 26 coverage at levels similar to if not slightly better than my former band 25 coverage. I'm hoping all this improves after optimization is done on the network.