Jump to content

Snapdragon 820 Modem details released


EvanA

Recommended Posts

https://www.qualcomm.com/news/snapdragon/2015/09/14/snapdragon-820-countdown-breakthrough-lte-and-wi-fi-x12-lte-modem

 

 

https://www.qualcomm.com/news/releases/2015/09/14/qualcomm-announces-breakthrough-connectivity-features-snapdragon-820

 

The new X12 LTE modem supports the following:

 

3 carrier downlink aggregation (CAT12 600Mbps)

2 carrier uplink aggregation (CAT13 150Mbps)

Up to 256QAM modulation on downlink

4x4MIMO for a single downlink carrier

LTE-U

 

LWA (LTE-WiFi aggregation)

802.11ac 2x2 MU-MIMO

802.11ad

 

It also has built it handling of WiFi and LTE connections to automatically pick the best connection based on current network conditions.

  • Like 5
Link to comment
Share on other sites

Yep, Qualcomm has revamped its baseband modem page, adding the Snapdragon X12 LTE and reversing the order from right to left.

 

https://www.qualcomm.com/products/snapdragon/4g-lte-connectivity/comparison

 

Now, before everyone gets giddy about the Snapdragon 820 with 3x CA, the Snapdragon 808 and Snapdragon 810 already support 3x CA.  But they require multiple RF transceivers to implement anything beyond 2x CA.  That is why basically all of the current handsets utilizing those chipsets are 2x CA.

 

Unless Qualcomm also has unveiled a next generation RF transceiver or the Snapdragon 820 incorporates it, the situation will not change.  Most/all handsets will stick to 2x CA.  And uplink CA is a real question mark, since that will suck additional handset battery power.

 

AJ

  • Like 3
Link to comment
Share on other sites

I also hope the energy efficiency is far better on this set of Snapdragons. This year, it seemed like Samsung won the war for best Android power with the Exynos 7420. It killed the 810 on efficiency and total power. Hopefully the 820 is far more competitive.

 

The modem enhancements, which will include 3x CA from the looks of it, will aid even the next generation of devices from Sprint and Verizon, though I could also see T-Mobile joining in on the MDM9645 party if Samsung can't support LAA, leaving AT&T alone to support the Shannon RF competitor to Qualcomm.

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

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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