Jump to content

Network Vision/LTE - Puerto Rico/Virgin Islands Market


Gab2012

Recommended Posts

Sprint will not have data and voice simultaneously until VoLTE. Sprint is not going to able to deploy VoLTE for some time. It would be crazy for you to want Sprint not to deploy B41 to increase LTE speeds and capacity now in PR to wait for VoLTE in a year or two.

So it's not stupid. You're confused on your technologies. And adding VoLTE service can happen with the existing equipment that's already in place at sites.

Using Nexus 6 on Tapatalk

Thanx for the much needed clarification....

 

Ok and now that you mention devices....

 

Im up for upgrade... And the G4 just got released....

Is it a good way to go or not....?

Link to comment
Share on other sites

Thanx for the much needed clarification....

 

Ok and now that you mention devices....

 

Im up for upgrade... And the G4 just got released....

Is it a good way to go or not....?

A great article written about the new G4

http://s4gru.com/index.php?/blog/1/entry-385-updated-use-the-4th-lg-may-the-4th-be-with-you/

Link to comment
Share on other sites

WELL I AM BACK.. .QUESTION IF THEY USE 2.5 GHZ  AND ADD  SMALL CELLS HOW FAR CAN THEY GET?

 

WHO ARE THEY?  RF PROPAGATES INFINITELY FAR.  AND WHY ARE WE SHOUTING?

 

AJ

  • Like 4
Link to comment
Share on other sites

I mean if puerto rico won't see lte 800 , band 41 plus small cells can reach rural areas?

 

Not likely.  Small cells are mostly for capacity in urban areas.

 

AJ

Link to comment
Share on other sites

I think sprint need to add a few more antennas for 1900mhz/2.5ghz in order to increase coverage in

rural areas

 

That may or may not be a priority for Sprint in Puerto Rico, as it already has several hundred sites there.  Not everywhere is destined to have Sprint service.

 

AJ

Link to comment
Share on other sites

Sprint have a 6% of the market said Marcelo Claure when he visited PR,in order to increase that they need to increase coverage

They likely will wait to do any expansion in PR after they resolve licensing in 800 SMR band. There are a lot of squatters on that spectrum who have not met build out requirements. The FCC needs to boot them.

 

Using Nexus 6 on Tapatalk

  • Like 2
Link to comment
Share on other sites

Sprint have a 6% of the market said Marcelo Claure when he visited PR,in order to increase that they need to increase coverage

 

Again, Puerto Rico and coverage expansion there just may not be a priority for Sprint -- especially if Sprint has such a meager market share.  Sprint has more pressing concerns where it has more customers.  From the data that we have seen, a 6% share would be by far the lowest for Sprint in any major market.

 

AJ

Link to comment
Share on other sites

I think that is not what Marcelo intends for this market. He said that a 6% is unacceptable...

 

6% is unacceptable in every market for basically any Tier 1 carrier with a built out network and yet Sprint is sub 10% market share in many markets alongside PR. It's more of a demographic appeal IMHO considering his background and focus on central / south america + carribeans. . 

  • Like 1
Link to comment
Share on other sites

Anyone know whats up with the signal going on and off for the past couple of days in the west side of the island....mayagüez specifically... ?

Link to comment
Share on other sites

Nobody knows if they (sprint) started testing 2.5 ghz?

 

Testing?  We don't know if they even started deploying 2.5GHz in PR.

  • Like 1
Link to comment
Share on other sites

I called the airave cs number regarding aweird issue i had and the rep told me that in my area there was some work done about 3 or 4 days ago.... With antennas..... Anything new that you can elaborate on?....

Link to comment
Share on other sites

This thread needs some active site hunters.

Yes. But that never was very popular in PR. Even in the early deployment. Lots of members, not much reporting.

 

Using Nexus 6 on Tapatalk

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

    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
  • Recently Browsing

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