Jump to content

Qualcomm X55 5G modem


dkyeager
 Share

Recommended Posts

There's a few big deals, there's now compatibility for FDD networks meaning this one can likely be used on n71 for T-Mobile. There is also support for 4G/5G spectrum sharing which seems like a big deal for Sprint given what Ericsson said about the technology.

Quote

Spectrum Sharing enables Ericsson’s 4G radio hardware to dynamically and simultaneously service both 4G and 5G devices rather than being dedicated to just one standard. As a result, if a new 5G smartphone includes the ability to transmit on 2.5GHz radio frequencies that were previously used for 4G, it could use the same spectrum for a superior connection — when connected to a compatible radio. There should be quite a few of those: Ericsson says that Spectrum Sharing can be installed remotely via software on Ericsson Radio System radios shipped since 2015.

As the company notes, this software upgrade is standards-compliant, and it will let carriers quickly upgrade their nationwide networks to 5G coverage without completely dedicating existing 4G towers to 5G, a decision that would reduce 4G availability. Carriers using the new software will also be able to remotely allocate additional 5G capacity to their networks as demand shifts from 4G, a strategy Sprint said earlier this year it would employ in 2019.

 

  • Like 1
Link to comment
Share on other sites

18 minutes ago, Paynefanbro said:

There's a few big deals, there's now compatibility for FDD networks meaning this one can likely be used on n71 for T-Mobile. There is also support for 4G/5G spectrum sharing which seems like a big deal for Sprint given what Ericsson said about the technology.

 

My guess is the first generation of 5G phones will accomplish the spectrum sharing with two chipsets and a larger battery to handle it.

Link to comment
Share on other sites

3 hours ago, Paynefanbro said:

There is also support for 4G/5G spectrum sharing which seems like a big deal for Sprint given what Ericsson said about the technology.

I did not know about this. I wonder if that means Sprint will be able to software upgrade other older Ericsson equipment to NR...

More research is definitely needed. 

Link to comment
Share on other sites

Basically what this means is you skip the first generation phones powered by the X50 chipset and go for phones with the X55 in them. Which means waiting for 2020. Which is OK since the 5G networks in this country will have minuscule coverage in 2019.

Link to comment
Share on other sites

3 hours ago, bigsnake49 said:

Basically what this means is you skip the first generation phones powered by the X50 chipset and go for phones with the X55 in them. Which means waiting for 2020. Which is OK since the 5G networks in this country will have minuscule coverage in 2019.

It all depends on whether Sprint has its act together.  If they have some clusters of Massive MIMOs deployed in their initial 5G markets and the firmware upgrades for 5G are ready and other precursors, and the LG 5G phone is available soon, that could be quite helpful to them.  Of course some marketing would also be good.

For most of us I agree that waiting is the rational choice.

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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Let me take a look tonight. 
    • Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked. Robert
    • I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung. EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.
    • I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.
    • I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.
  • Recently Browsing

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