adhrty

Comparing the abuse of a human being to too much data being used on the network of a non-entity corporation is deeply disturbing.

AJ, I completely understand where you are coming from, wireless spectrum, unlike fiber or other wired networks we use, is a physically limited resource. I ask you though, is Sprint selling it to their customers as such when they have ads like this? http://www.youtube.com/watch?v=frKZyFYxQCY I think it is understandable that people are frustrated when they've been sold a certain idea ("a billion roaming photo journalists uploading the human experience"). Obviously, they were not sold the dog crapping in the park paradigm, accurate as it might be.

Of course, there is a big exception here. All these people are talking about the Exynos SoC. It appears that there will again be a split, with the North American version containing a Qualacomm SoC while the international version ships with the Exynos 5. Qualacomm, through Code Aurora Forum, provides excellent support (and GPLed code) that makes the NA GS3 one of the best supported CM devices. Too bad Sony dosen't make CDMA phones though...

Thought I would chime in here with some thoughts, since I'm in a 1st round market that has seen much work. The network is unquestionably better from where it was last fall. 3G was truly unusable, especially near any major highway or road. 4G penetration is pretty good in the south KS suburbs (OP, Leawood, etc), but not ubiquitous. Downtown and Midtown KC are better covered by 4G in my experience. Things have stalled a bit in the past month or so, owing to weather. The one thing I would note is that I feel like they need to tackle some of the building mounted sites. It seems as though they are responsible for covering some very busy areas (Metcalf, Town Center and the ever increasing offices around it) and it would patch many of the holes that remain. In summary, I think Sprint needs to put the pedal to the metal in April, May and June to keep up with their own timelines and solidify their NV work, which I'm guessing might be patchy in other round 1 markets outside of Chicago. Once the 'Kansas' market is up to about 85% completion or so, I do think the Sprint network will be a solid presence ready to take the fight to AT&T and Verizon. Also, I guess 800Mhz LTE and voice will be cool, but I feel that the 1900Mhz cell spacing is so tight in KC I rarely if ever don't have voice and 3G coverage. Guess I'll have uber coverage (for voice and 1x that is).

That's the thing though, the number is perfectly valid (it is listed on their website) so it would've have to been spoofed. Second, it was the lamest social engineering I've ever seen. I guess they established that the phone number is live, but other than that they were perfectly content to end the conversation when it was clear I had no idea why they were calling. As for why they "let" me disconnect, I would guess they have to make some judgement call on calling back 911 disconnects and I think it was clear that I was not someone in imminent danger. Edit: With the vast amount of telco knowledge we have around here, someone must have some experience with 911 systems. There is no way they have to manually enter a number to call it back right?

I was not calling 911, they were calling me. The number does match with the Leavenworth PD, although I supposed it could have been spoofed.

Wanted to see if the collective talents of S4GRU might be able to shed some light on an interesting situation I just encountered. Around 15 minutes ago I received a call claiming to be from the Leavenworth, KS 911 dispatch, saying they were responding to a 911 disconnect from my number. I live in south suburban KC, roughly forty miles away. My phone log does not show a call to 911, nor does Google Voice or Sprint billing. What say you? A misdial on their part? Some kind of phantom call? A network issue? Anyone else ever ran into this?

Yeah, I believe Google finally integrated an API for LTE strength in Android 4.2. Of course, I don't think anyone is shipping 4.2 besides CM and Google on Nexus phones. More here: http://developer.android.com/reference/android/telephony/CellSignalStrengthLte.html

As a proud denizen of flyover country, I love to hear people from SoCal mention non-important areas. Either way, the rollout schedule and the updates that have taken place were/are influenced by so much more than population size. Spectrum constrains (Chicago!), contractor and backhaul availability are just a few that come to mind. That said, I believe the first of the third round markets have begun to see full installations start (Phoenix + Vegas), so Colorado should be seeing NV work soon.

Yea, no @ sign for me Sprint to Sprint on SGIII. But I do receive the text after the missing sign.

It goes to the MSC, which you can determine by clicking on the sites pin, and from there it is routed out to the larger internet. Not sure if a VPN is strictly necessary as they have their own backhaul to the MSC. AFAIK, there is no central NOC in Overland Park/Kansas City, except for the respective MSCs for that market. Perhaps they have some kind of warroom at the campus. Also, this is for data, I do not know the ins and outs of how they route voice. Now Robert and AJ, let us know if that is all wrong.

While we're on the topic of Dillons, the new one on Mass. in Lawrence is nice, but is missing so much of the character that Dirty Dillons/'illons had. Who knows what I'm talking about?

CM10 devs for the Sprint Galaxy S3 have noted this same behavior with that phone as well, but only for a small subset of users. They argue that it is an isolated Sprint network issue and introduced a custom messaging APK to manually split the messages. So, as others have recommended, a different messaging app is probably what you need.

I'll be staying right at the Hawes St. Green line station (right on Beacon St. really). Any suggestions for seafood?