Jump to content

Network Vision/LTE - Tampa Market


Feech

Recommended Posts

It shouldn't fail unless of course the 3G is overloaded where it can't stream it. Or maybe Netflix's app can't handle the different in speed change between 4G and 3G.

 

Its failing because LTE and 3g have different IPs until they turn the NV cluster on

Link to comment
Share on other sites

I was at dale Mabry and northdale inside a restaurant and had great lte signal.

 

I have an evo lte: 12mbps down 6 mbps up.signal: 96db

My gf with an S3 : 28mbps down 8 mbps up signal: 92db

 

It's pretty crazy how the S3 can get choose better speeds with only a 4db signal difference

Link to comment
Share on other sites

I was at dale Mabry and northdale inside a restaurant and had great lte signal.

 

I have an evo lte: 12mbps down 6 mbps up.signal: 96db

My gf with an S3 : 28mbps down 8 mbps up signal: 92db

 

It's pretty crazy how the S3 can get choose better speeds with only a 4db signal difference

 

4db is not small by any means.

 

Sent from my little Note2

 

 

Link to comment
Share on other sites

I was at dale Mabry and northdale inside a restaurant and had great lte signal.

 

I have an evo lte: 12mbps down 6 mbps up.signal: 96db

My gf with an S3 : 28mbps down 8 mbps up signal: 92db

 

It's pretty crazy how the S3 can get choose better speeds with only a 4db signal difference

 

How many test did you run to determine that?

Link to comment
Share on other sites

 

4 test with the phones side by side and test started after the other phone finished so they don't compete for bandwidth

 

Very interesting. Can you tell me if the S3 has a stronger 1x signal as well?

 

Sent from my Nexus 7 using Tapatalk HD

Link to comment
Share on other sites

 

 

Ehrpd is on at every site.

 

Sent from my little Note2

 

I know that, but apparently ehrpd is running through the legacy back haul with a different IP until a while cluster get turned on. See post on previous page

Link to comment
Share on other sites

 

I know that, but apparently ehrpd is running through the legacy back haul with a different IP until a while cluster get turned on. See post on previous page

 

Backhaul doesn't matter it is still Sprint's network. Last mile doesn't matter.

 

They didn't go through the effort of ehrpd on every market for nothing before LTE launched.

 

Sent from my little Note2

 

 

Link to comment
Share on other sites

Hey Guys haven't been around lately. Just catching up on things. So I noticed that the Osprey and Eagles are back. tells me we are going to see a slowdown in new progress, like any towers that still haven't been rigged. The one that comes to mind for me is the tower closest to my work on 301 between MLK and 60.

Link to comment
Share on other sites

I had no problems in Wichita Falls testing to go back and forth between LTE and eHRPD on legacy sites. The backhaul type in irrelevant. Each type of backhaul is provisioned like a VPN direct to the Sprint network core at an MSC. The backhaul is just a conduit, whether legacy or NV. Legacy NV backhaul is just bandwidth/throughput limited, but pointed to the same place.

 

That being said, Sprint's network is still not mature and can have hand off problems between LTE and eHRPD. It does occur. And this may be exarcebated by dissimilar vendors.

 

Robert via Nexus 7 with Tapatalk HD

Link to comment
Share on other sites

I had no problems in Wichita Falls testing to go back and forth between LTE and eHRPD on legacy sites. The backhaul type in irrelevant. Each type of backhaul is provisioned like a VPN direct to the Sprint network core at an MSC. The backhaul is just a conduit, whether legacy or NV. Legacy NV backhaul is just bandwidth/throughput limited, but pointed to the same place.

 

That being said, Sprint's network is still not mature and can have hand off problems between LTE and eHRPD. It does occur. And this may be exarcebated by dissimilar vendors.

 

Robert via Nexus 7 with Tapatalk HD

it seems completely fine on anything but Netflix.
Link to comment
Share on other sites

LTE can still be really slow still. I am pretty sure my LTE signal was low didn't get a chance to look at the engineering screen.

 

this was done at my office in sable park.

 

http://db.tt/XPykqRXC

 

just fyi sensorly shows dbm under the more details screen. also the CDMA Field Test app shows db in app and in the status bar. Looking at your speeds, i would guess you had about 118-120 dbm signal, which is bare minimum

Link to comment
Share on other sites

LTE can still be really slow still. I am pretty sure my LTE signal was low didn't get a chance to look at the engineering screen.

 

this was done at my office in sable park.

 

http://db.tt/XPykqRXC

 

Could you try again using the Tampa server? The Columbia server is notoriously slow.

 

Sent from my Nexus 7 using Tapatalk HD

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...