by Jeff Foster
Sprint 4G Rollout Updates Tuesday, January 31, 2012 - 7:46 PM MST
Since last fall, there had been talk of a Samsung Galaxy Nexus launching on American carriers other than Big Red. Sprint has finally announced several weeks ago that it is the another vendor slated for release in the U.S. Suffice to say, many of us out there, especially those adverse to heading to Verizon and paying its premium prices, are excited about the impending release.
The good news is that Google could be working on an updated version of the Galaxy Nexus. It has unofficially been dubbed the Galaxy Nexus Plus. There is much anticipation that it will be released before Sprint turns on LTE this summer. It’s not the first time an OEM has refreshed a device and re-released it to the market place, which works to our advantage. It’s rumored that the new Galaxy Nexus will have either a 1.5 or 1.8 GHz Texas Instrument OMAP4670 dual core processor. This would be a significant upgrade from the 1.2 GHz dual core processor found in the current Verizon version.
We don’t know anything about official specs, but it’s also rumored to have an 8 MP camera. This is a noteworthy upgrade to the 5 MP shooter on the Verizon model (which has been lauded by many techies). We already know that the Sprint model will come installed with Google Wallet, per previous announcements. Some rumors also point to a beefier battery as well. The phone should have all the other features that’s on the current Galaxy Nexus, so now all we have to do is wait.
Try to make this as short and simple as possible. I have three devices; 2 of which are on the same plan and the third on a separate plan.
The third device is my tab 4 which is picking up SprintB41 site 310120 just great. I get 3 bars downstairs.
My other two devices; Galaxy Note 4 & Galaxy Note Edge for some reason will not pick up this tower. I have tried PRL updates, Profile updates, restarted the phones and all I can get them to connect to is a ClearwireB41 site.
More background info...all devices have same Sim card as when purchased, tablet stays off 3/4 of the day and my phones are on when I wake up and turn them off at night. No matter where I go inside or out my phones won't connect to the Sprint site.
Anybody have any ideas before I call Sprint trying to figure something out? I'm not sure how long the tablet has been able to connect to this site so I'm not sure what to think of it besides agitated that the tablet of all things is connecting. I posted two photos; one of the tablet connected to the Sprint site; second of the Clear wire site my phones connect to.
Samsung Network Vision equipment are highly distinct and fairly easy to spot compared to the equipment that other vendors are deploying. Sprint is Samsung's first extremely massive American contract (baring Clearwire) so there should be no issues in confusing these equipment for another carrier which happens often with Ericsson NV equipment.
Below are images of Samsung equipment which includes antennas, remote radio units, base stations, and their mounting configurations.
Samsung antenna with eSMR 800 RRU & PCS 1900 RRU
A close look at a Samsung setup
A narrow beam setup
High Capacity Site with 2 Antennas & 3 RRUs (2x PCS & 1x SMR).
Second antenna is PCS only for now.
Canadian IBEZ (NO SMR)
Special Case PCS Only Setup for Canadian IBEZ
Close up of standard antenna connectors
Powerpoint slides from Samsung / Sprint
*disclaimer - all powerpoint diagrams and images were found through public municipality online databases and is by no means misappropriated through malicious means*
*Credit goes to those whom took pictures of these equipment. You know who you are*
On my iPhone XS Max, Bands 2 & 4 LTE shows up as Sprint native service on the device, but in Field Test Mode you know it's T-Mobile because the MCC MNC is 310 260. So it never actually states that it's T-Mobile except for the MCC MNC.
And yes, my phone kept jumping 5 hours behind and back.
I replied to your Reddit post. But so others here know, it's an issue with eCSFB and IMS on the Airave. Devices which maintain SRLTE don't have the issue, since calls and texts go over CDMA instead of LTE. I have a ticket open about it, but so far they can't find anything wrong. Been a problem that has been ongoing for months, and I know other people in different markets with different devices and accounts have the exact same issue. It affects all phones that rely on eCSFB and IMS instead if SRLTE.
A "solution" is to block the LTE ipsec tunnel on your router's firewall. In my experience, blocking access to 184.108.40.206 and rebooting the Airave resulted in just CDMA and no LTE. That being said, if your non-SRLTE phone can pick up the macro LTE signal at all, it will almost certainly never use the Airave. I don't believe that macro eCSFB will setup a call via the Airave.
Sent from my Pixel 2 XL using Tapatalk