Jump to content

SoftBank is lighting a fire under Sprint


jamisonshaw125

Recommended Posts

Yeah But Softbank knows it will take time to see a return. Once 800LTE and TDD-LTE is more widespread and More Tri-band devices are in customers hands, then It will work it self out. People do have a bad taste in their mouth, but once they see NV in the real world, More subscribers will come. But I hope Softbank has patience. I am Sure they do

 

I agree. I'm sure SoftBank is patient but I'm sure they will not tolerate any delays.

 

I would think most of sprint smartphone customers will have a Triband phone by 2016 and onward considering all smartphones released in 2014 and onward will be triband. I just hope they have 2.5 somewhat nationwide by then

  • Like 1
Link to comment
Share on other sites

I think y'all are missing the boat in that smartphone subscribers are just one of piece of a rapidly expanding pie. Millions of automobiles will soon be equipped with 4G LTE radios, and owners/passengers naturally want to connect their cars to the internet, especially if they want Netflix in the backseat TV screens.

  • Like 1
Link to comment
Share on other sites

Sorry to bring this back up but I support your decision. I have self identified as working for a competer and have at times been critical of sprint. I have never felt unfairly treat in any thread or by any member of the staff even when they have disagreed with me.

We definitely don't see eye to eye on every issue. But I appreciate that you mention the good things with the bad. It's not a one sided discussion, every time.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

I think y'all are missing the boat in that smartphone subscribers are just one of piece of a rapidly expanding pie. Millions of automobiles will soon be equipped with 4G LTE radios, and owners/passengers naturally want to connect their cars to the internet, especially if they want Netflix in the backseat TV screens.

 

I've been thinking about this a lot.  I know AT&T has been getting in bed with Onstar, GM and Tesla.  Google and Audi are now hooking up:  http://www.engadget.com/2013/12/30/google-audi-to-announce-android-in-car/

  • Like 1
Link to comment
Share on other sites

I agree. I'm sure SoftBank is patient but I'm sure they will not tolerate any delays.

 

I would think most of sprint smartphone customers will have a Triband phone by 2016 and onward considering all smartphones released in 2014 and onward will be triband. I just hope they have 2.5 somewhat nationwide by then

 

Is the goal right now to have 100 million POPS covered by LTE on the 2.5 GHz band by the end of next year?

  • Like 1
Link to comment
Share on other sites

I think y'all are missing the boat in that smartphone subscribers are just one of piece of a rapidly expanding pie. Millions of automobiles will soon be equipped with 4G LTE radios, and owners/passengers naturally want to connect their cars to the internet, especially if they want Netflix in the backseat TV screens.

yes but that is why there will probably be added highway sites, with coverage meant for those users. And I believe I read there is tech out there to help reduce the strain of those added devices.
Link to comment
Share on other sites

Is the goal right now to have 100 million POPS covered by LTE on the 2.5 GHz band by the end of next year?

I'm most likely wrong. But I don't see SB resting with 2.5 roll outs. If NV's contracts were too late to be effected with SofBank (which makes total timeline sense) I've got a feeling NV 2.0 will be quicker not to mention all the hard work is done.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

I'm most likely wrong. But I don't see SB resting with 2.5 roll outs. If NV's contracts were too late to be effected with SofBank (which makes total timeline sense) I've got a feeling NV 2.0 will be quicker not to mention all the hard work is done.

 

 

Sent from my iPhone using Tapatalk

The problem with 2.0 getting faster roll out is all these carrier's are upgrading to. There is not the people to do the work,plus bad weather will slow everybody down.

Link to comment
Share on other sites

If there's any fire needing to be lit, it needs to be lit on the backhaul side of things.  NV 1.0 isn't completed and a lot of sites are left with new equipment but lacking new backhaul.  If Sprint can't get fiber from these bigger ISPs they need to start looking at smaller municipal owned ISPs.

  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

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

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • 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.
  • Recently Browsing

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