milan03
-
Posts
607 -
Joined
-
Last visited
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Everything posted by milan03
-
Yup, also Sievert far right lol -
Can you spot Marcelo?
-
Small correction. iPhone 6 with MDM9625 is capable of aggregating two component carriers of unequal size, for example 10MHz + 5MHz. There are quite a few commercial AT&T units with the same chipset already aggregating 10+5 in selected markets. As you've already mentioned, what's not possible is aggregating more than 20MHz in total, and considering that Sprint's B41 in it's current deployment is a single 20MHz channel, adding a secondary TDD 20MHz channel wouldn't increase peak throughput for iPhone 6 users, as the phone isn't capable of aggregating two 20MHz carriers. If Sprint deploys a secondary 20MHz B41 carrier this year, subscribers will still benefit as the load would be balanced between two different capacity channels. Only the peak throughput wouldn't be doubled for iPhone 6 users.
-
"Unsupported SIM" error.
-
Their existing unlocking policy still prohibits the device use on domestic operators. Verified it on iPhone 5s and iPhone 5c. Also, all third party unlock services point that unlocking Sprint's iPhone won't get it to work on US operators.
-
Sprint's unlock policy allows foreign SIM cards, but it's always been locked out of domestic non Sprint SIMs. So popping in Verizon/AT&T/T-Mobile SIM into Sprint's iPhone 5s/c for instance will give you "Incompatible SIM" error, and bring you back to the activation screen, even after you've successfully went through the process of unlocking the iOS device. On the other hand, Verizon's variant when bought outright at the Apple store is unlocked out of the box, and will accept AT&T/T-Mobile SIM just fine. I'm using one right now on T-Mobile and iOS 8, and WiFi Calling and other T-Mobile features have been working all along. Point is, even though Sprint's variant in theory should be able to work on every single operator known to men, it doesn't due to Sprint's firmware lockdown/database whitelist.
-
27-11 Astoria blvd
-
Remember this: Huawei probed for security, espionage risk http://www.cbsnews.com/news/huawei-probed-for-security-espionage-risk/
-
That makes me wonder if Sprint or in your case AT&T even have local offices deciding on the build outs, or all of the decisions blindly come out of Kansas City/Dallas?
-
Ya it's a B41 site with no proper backhaul. All I know that I wouldn't wanna live in that building, ever.
-
That side of the building doesn't even have windows. Straight up concrete
-
Gotta love Sprint/Clear panel placement here in Astoria... Absolutely ridiculous, blasting straight at the facade in front!
-
Keep in mind that XLTE in NYC never had full 150Mbps backhaul bandwidth provisioned for that capacity layer. It used to max out at ~80Mbps since day one, as they were pooling 150Mbps between 20MHz B4 and 10MHz B13... So, they could easily re-provision the backhaul for more bandwidth per sector, and that alone will double the existing peak rates. Not sure if they will any time soon, because they only guarantee 5-12Mbps on the downlink.
-
This rendered your previous post invalid, didn't it? Point is, T-Mobile is giving consumers every right to leave the carrier at any point, and as you've stated Sprint will also gladly buy your existing contract if needed. There are quite a few options for T-Mobile subscribers.
-
Yup, about 15 Million pops in EDGE Only areas will be covered by LTE by the end of 2014, which btw is not 50% of the remaining EDGE footprint, it's more like 27%. Majority of the upgrades will happen in H1 2015. Their goal is to cover 250 Million pops with LTE by the end of 2014. Currently they're at the 233 Million mark as of the last official announcement a few weeks ago. Entire footprint covers 284 Million pops. You can find more info and reports on that progress on other T-Mobile Forums.
-
Wait... Is that a Download Booster turned on in the notification bar?
-
This 100%
-
You mean after T-Mobile
-
They actually do, Shammo or Lowell (can't remember) was talking about Verizon's LTE issues a few quarters ago during the conference call. In theory some will tell you that there isn't an issue, but on a fully loaded cell the issue is real.
-
My local contact have mentioned Air 32's and the deployment in Long Island market starting in September, but considering that AT&T and Verizon have been deploying taller AIR21's for 700MHz, I wouldn't be surprised to see those as well. The main issue is the weight of taller AIR21's as many NYC rooftop sites would fail the load. AIR32's are way heavier so that's why they'll be starting with suburban monopoles in LI area and Westchester.
-
Haha I hear ya! I am certainly glad that Sprint's subs are getting happier as they've stuck with the operator through thick and thin. Much respect. I am offering my own personal experience from my own market, fully respecting your site and it's nature. There wasn't any trolling involved in my posts, but I'm sorry that you've felt that way.
-
Robert, with all due respect, I've been comparing all 4 wireless operators myself for the past 2 years in New York City market. I'm telling you how it is here. I do appreciate his 7-day TestDrive comparison, it is one opinion testing the portion of the market, but keep in mind NYC is a huge urban area, and the operators without ubiquitous low band blanket need to deploy dense on PCS/AWS/BRS to tackle the capacity demand. Sprint is definitely getting better as more B41 sites are coming on air, but due to inadequate cell density at the moment, that airlink just isn't able to provide consistent user experience across the market. Often times users are camping on G block which as you know is oversold, and now further loaded with all those MVNO subs. That also further shrinks the cell and forces subs onto EVDO, etc. T-Mobile on the other hand still hasn't upgraded the bandwidth to many of their NYC cell sites, many of them capped at 50Mbps some of them at 100Mbps. Once that's re-provisioned, and MetroPCS CDMA shut down, 15MHz FDD LTE will provide even more capacity, and MetroPCS significant DAS deployment will further densify already very dense grid. Obviously I'd love to see Sprint get their stuff together and get serious about all that 2.5GHz spectrum, and there isn't a more perfect market to test the TDD tech than NYC. It simply just isn't up to par YET.
-
Not so sure about that NYC comparison since T-Mobile currently has way more MHz/pop deployed, less subs, has three competent data layers 75Mbps LTE -> HSPA+42 -> HSPA+21, cell density is second to none in this market with ~99% cell sites modernized with active fiber backhaul in place. I wouldn't compare Sprint's experience to T-Mobile's, at least not in New York City. On the brighter side, here is the T-Mobile 700MHz deployment in Silver Spring, MA: http://imgur.com/a/rz9SQ
-
My understanding is that they were deploying Band 2 and Band 4 flexis to urban sites since day one, even though they're only using 1900MhHz licenses for HSPA+/GSM in those markets.
-
Band 2 LTE is right now being deployed in rural areas where PCS's already been used for 2G services. For now, they're not deploying AWS to those areas at all, it's purely PCS LTE/2G, plus 700MHz where possible. This type of rollout allows them to rapidly deploy LTE using the least amount of resources. In many cases they're reusing the existing 1900MHz panels, only replacing the cabinets and adding RRUs. This also makes it much easier for their engineers to tune those PCS LTE sites, as they already have a pretty good idea how 1900MHz spreads and propagates around those 2G sites. The backhaul seems to be in place as well: https://twitter.com/unforgiven512/status/502493782299123713/photo/1
