JWMaloney

Alltel EV-DO roaming is still in the stock PRL in some areas. I am on the 55019 PRL and I roam on Alltel every time I cross the state border.

Not for the reason you're insinuating, no. I think that because they have a business relationship, they probably have a direct interconnect, which would give you better results. Yes, because you've now altered the route your speed test follows, taking you outside of TWC's network.

According to Android Central, this is not the case -- "The Ookla Speedtest.net application is designed to measure true network speed--not show that a customer has exceeded their high-speed data bucket. Other speed test providers are also whitelisted." That has nothing to do with "preferential treatment" and everything to do with peering interconnects. Try speed testing to a server located near the data centers of "ANY other website" that you're referring to.

It's a bug with selinux permissions. You'll run into it if you've ever restored a data partition backup before. Run this from a root shell and reboot: restorecon -R -v /data/misc

The same thing happened to me this week. I had the charge zeroed out but the SOC still shows on my line.

Remove the page number from the end of the URL.

If you had asked me a year ago if Apple would ever support carrier-specific Wi-Fi calling on iPhone, I would have said you were crazy. Let's hope Google follows suit.

That was my point. An air conditioner in a thick hut won't have to run 24/7, but ambient cooling on thin metal boxes in a hot climate will. EDIT: I'm going under the assumption that when you say ambient cooling, you mean fans blowing, and that you would have said passive cooling otherwise. Who knows what they have inside though?

Surely they would be better insulated and thus more energy-efficient when it comes to air conditioning than a thin metal cabinet?

I just wish they would cover everything Nextel used to cover. I spent all day yesterday in a spot covered only by Alltel and decommissioned (but still standing) Nextel sites.

Pinpoint is useless for eCSFB issues. You have to get a ticket open. And no, even most of the advanced support team is clueless about eCSFB. Some of them are aware that tri-band devices have specific issues, but generally they aren't any more knowledgeable than that.

Yes, Ericsson tiger team has been very busy.

I do have debug options and test messages enabled, and I have indeed received test messages, but I've never received any legitimate ones. I think digiblur has though.

Probably a security fix for Towelroot http://forum.xda-developers.com/showthread.php?t=2780568

https://community.sprint.com/baw/thread/163896 http://support.sprint.com/support/article/Find_and_update_the_software_version_on_your_Google_Nexus_5/WServiceAdvisory_542_GKB61196?INTNAV=SU:DP:OV:UG:GoogleNexus5:FindAndUpdateTheSoftwareVersionOnYourGoogleNexus5

Sprint set out to cover 250 million POPs with LTE by the end of 2013. They only reached 80% of that number. We all know that there are numerous reasons for this, many of which are outside of their control, but they still did not do what they set out to do. Hopefully the event on the 23rd has something to do with their more recent ambition to reach 250 million POPs by mid-year. We know they were well on track with 225 million in April. I just hope they don't pad the numbers with their alliance partners like T-Mobile padded their customer gain numbers with MetroPCS.

https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&calledFromFrame=Y&application_id=929407&fcc_id=TA8AKRC118159-1 Sprint will be swapping some of their old RRUs for the "RRUS 31 B25" in some locations now.

Try the phone number in the link that you just quoted.

I just got the forced update. Nothing changed from the defaults in the profile. Only thing it did was put me on band 25.

That's exactly what I said Sprint should have done at their last event.

Some time this year. There were posts when it happened. I don't remember when it was.

http://s4gru.com/index.php?/topic/5001-breaking-band-tri-band-lte-ecsfb-issues-thread/page-36&do=findComment&comment=327652

Band 26 is the 800 MHz LTE band. What you have likely experienced is that eCSFB is not enabled on band 26 LTE sites in your area.

All of the 1900 MHz CDMA traffic is being consolidated to the old regional switches. All of the LTE and 800 MHz traffic is on brand new switches that don't have regional designations -- only numbers, and you aren't geographically limited to certain ones anymore. Remember that day when LTE latency practically halved overnight? That was when the non-regional switches came online. Then Google Voice integration makes it even weirder, because it causes your calls to go through one of 3 (with a fourth possibly coming online in the future) Google Voice switches directly to the cell sites. In other words, my calls never hit the local MSC at all. I'm beginning to wonder if Google Voice integration is the cause of the failed handoffs.

The ticket is now open, but I've been told that inter-frequency handoffs may be impossible for a while because 800 MHz is being handled on a different switch now.