Jump to content

Samsung Galaxy S7 Rumors thread


bitslizer

Recommended Posts

Most current rumors says that Samsung will be switching back to the Quaulcomm for USA, Exynos elsewhere strategy for the S7

 

Qualcomm have formally announced the SnapDragon 820, which support 3x20mhz CA download and 2x20mhz CA upload

 

https://www.qualcomm.com/products/snapdragon/processors/820

 

 

This will probably be the first phone on Sprint to support 3x B41 CA

  • Like 1
Link to comment
Share on other sites

I guess Samsung decided against Never Going Back Again to Qualcomm and would break The Chain of Exynos only powered phones.

I say both parties should just Go Your Own Way.

 

0xjTeTB.jpg?1

  • Like 1
Link to comment
Share on other sites

Had no idea where to post this! but 3x20...

 

 

Both the Snapdragon 808 and 810 already supported 3x CA aggregated 60 MHz FDD/TDD.  The Snapdragon X10 LTE baseband was not the limiting factor.  However, 2x CA used only one RF transceiver, while 3x CA required a second RF transceiver.  Unless that requirement has changed, then the Snapdragon 820 with Snapdragon X12 LTE baseband is little different from its predecessors on the 3x CA front.  So, do not get overly excited.

 

AJ

Link to comment
Share on other sites

Both the Snapdragon 808 and 810 already supported 3x CA aggregated 60 MHz FDD/TDD.  The Snapdragon X10 LTE baseband was not the limiting factor.  However, 2x CA used only one RF transceiver, while 3x CA required a second RF transceiver.  Unless that requirement has changed, then the Snapdragon 820 with Snapdragon X12 LTE baseband is little different from its predecessors on the 3x CA front.  So, do not get overly excited.

 

AJ

To add to this, Qualcomm has implemented a number of new technologies to their modems, but Sprint's complex setup with triband often leaves them limited.  For example, Envelope Tracking hasn't been in a Sprint device yet, but it came out back in I believe 2013.

  • Like 1
Link to comment
Share on other sites

Wonder if the screen size will stay the same.  Probably since Samsung released a Note-like S6+ Edge.

 

The G4 for example is about the size of a Note.

 

I think Samsung is smart to leave things the way they are and not try to experiment with larger sizes of the regular Galaxy series.  Samsung realized that the 5.7 inch size is the absolute maximum screen size for the Note series and anything bigger than 5.7 inch doesn't tend to do that well (ex: LG G Pro 2, Nexus 6, etc).

 

Samsung wants to maintain that 3 devices difference between the Galaxy, Galaxy Note and Edge series.  Making the Galaxy phone bigger in screen size would just close the gap between the Note and Edge devices making the Note and Edge less relevant.  Perhaps Samsung could bump it to 5.2 inches to be similar to the Nexus 5P and LG G2 but I doubt it.

Link to comment
Share on other sites

Samsung announcing that Exynos now will have an LTE 12/13 modem built into their SoC.  Maybe they will stay in house.

 

If exclusively so, then there will be no Sprint variant Samsung Galaxy S7.  Sprint will be left out.  VZW, AT&T, and T-Mobile will get their variant(s) -- with VZW voice service VoLTE only, as in the HTC One A9.

 

AJ

Link to comment
Share on other sites

SamMobile rumor report CDMA carriers to use Qualcomm, everybody else use Exynos.

 

http://www.sammobile.com/2015/11/16/rumored-model-numbers-for-snapdragon-820-and-exynos-8890-powered-galaxy-s7-and-galaxy-s7-edge/

 

Snapdragon 820

 
Verizon - SM-G930V and SM-G935V
Sprint - SM-G930P and SM-G935P
US Cellular - SM-G930R4 and SM-G935R4
China - SM-G9300 and SM-G9350 models
 

Exynos 8890

 
International unlocked - SM-G930F and SM-G935F
T-Mobile - SM-G930T and SM-G935T
AT&T - SM-G930A and SM-G935A
Canada - SM-G930W8 and SM-G935W8
Korean versions - SM-G930 S/K/L and SM-G935 S/K/L, depending on the carrier
  • Like 1
Link to comment
Share on other sites

I bet Samsung will use Qualcomm modems anyways.  Unless the specified cat 13 modem in the Exynos is a Samsung one?  Doubtful.

 

it is a samsung modem call shannon

Link to comment
Share on other sites

  • 3 weeks later...

Samsung announcing that Exynos now will have an LTE 12/13 modem built into their SoC.  Maybe they will stay in house.

 

I think Samsung using the Exynos chip in for the US variants was just a one off situation due to the initial batch of Snapdragon 810 chips that had power consumption issues.  By the time the Snapdragon v2.1 was available for general release it was already too late for them.  I expect Samsung to rejoin with Qualcomm just because the US still uses CDMA on 2 of its big 4 carriers.

  • Like 1
Link to comment
Share on other sites

I think Samsung using the Exynos chip in for the US variants was just a one off situation due to the initial batch of Snapdragon 810 chips that had power consumption issues. By the time the Snapdragon v2.1 was available for general release it was already too late for them. I expect Samsung to rejoin with Qualcomm just because the US still uses CDMA on 2 of its big 4 carriers.

I expect Exynos SoC and Qualcomm MDM9645. That is my bet.

 

Sent from my SM-N920V using Tapatalk

Link to comment
Share on other sites

I expect Exynos SoC and Qualcomm MDM9645. That is my bet.

 

I will join that bet for VZW and Sprint, not for AT&T and T-Mobile.

 

AJ

Link to comment
Share on other sites

I will join that bet for VZW and Sprint, not for AT&T and T-Mobile.

 

AJ

Come think of it, you're right, given Shannon 333 was the AT&T and T-Mobile baseband for the S6 class of devices.

 

Sent from my SM-N920V using Tapatalk

Link to comment
Share on other sites

Come think of it, you're right, given Shannon 333 was the AT&T and T-Mobile baseband for the S6 class of devices.

 

Little known fact, the Shannon baseband was named after Shannon Doherty. Or maybe it was Shannon Tweed.  Shannon Sharpe?

 

AJ

  • Like 1
Link to comment
Share on other sites

So, when does everybody think the GS7 will be released?  From rumors I've read on the web, I'm thinking Feb.

 

Sounding like March based on current latest rumor/news

Link to comment
Share on other sites

  • 2 weeks later...
Guest
This topic is now closed to further replies.

  • 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...