Jump to content

Samsung Galaxy S6 Preview Thread (was "Samsung Galaxy S6 Edge pre-order page up.")


twospirits

Recommended Posts

True, the battery has less capacity, but the screen technology and chipset power consumption has been vastly improved.  I wouldn't be surprised if the GS6 has better battery than the GS5.

As long as the edge has the same or similar battery life as my m8 then I will be very happy.  

 

 

Damn, I still can't believe I am this excited for a samsung device.  I feel like I need to go and take a shower after saying that.

  • Like 2
Link to comment
Share on other sites

If Samsung ends up using their own chips for the US versions, do we know who will make the modem? I'm guessing probably Samsung's in house version but I kind of would like to see an Intel one.

Link to comment
Share on other sites

If Samsung ends up using their own chips for the US versions, do we know who will make the modem? I'm guessing probably Samsung's in house version but I kind of would like to see an Intel one.

 

 

It could be the MDM9635M, or the MDM9645 (which is what the 810 has integrated inside it as far as baseband goes.) 

 

Personally I want Exnyos to be inside the Sprint version as far as SoC goes simply due to the fact that Qualcomm has become increasingly fat and lazy due to their baseband dominance. The problem is that the 810 sucks, it has thermal issues on the G Flex 2 that some have detected, and then when you compare AnTuTu between the Exynos in the S6 and the 810 in the One M9 it's pretty clear who's ahead here. 

 

Anything that further breaks down the Qualcomm Empire is good in my book. Apple already pawned Qualcomm with the A8 now I'm guessing it's Samsung's turn. 

Link to comment
Share on other sites

It could be the MDM9635M, or the MDM9645 (which is what the 810 has integrated inside it as far as baseband goes.) 

 

Personally I want Exnyos to be inside the Sprint version as far as SoC goes simply due to the fact that Qualcomm has become increasingly fat and lazy due to their baseband dominance. The problem is that the 810 sucks, it has thermal issues on the G Flex 2 that some have detected, and then when you compare AnTuTu between the Exynos in the S6 and the 810 in the One M9 it's pretty clear who's ahead here. 

 

Anything that further breaks down the Qualcomm Empire is good in my book. Apple already pawned Qualcomm with the A8 now I'm guessing it's Samsung's turn. 

You know better than to compare using AnTuTu. I guess I forgot that even if they use their own SoC that they can still have a Qualcomm modem.

Link to comment
Share on other sites

You know better than to compare using AnTuTu. I guess I forgot that even if they use their own SoC that they can still have a Qualcomm modem.

I know benchmarks can be manipulated, but by 20,000 points? I doubt that sort of gap is due to simple manipulation. Besides, all Android vendors are in on the manipulation game at this point.

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Link to comment
Share on other sites

I know benchmarks can be manipulated, but by 20,000 points? I doubt that sort of gap is due to simple manipulation. Besides, all Android vendors are in on the manipulation game at this point.

 

 

Sent from my iPhone using Tapatalk

My problem is not that it could be manipulated, it's that it was never a good benchmark. Unless things have changed, it's basically just an arbitrary number.

Link to comment
Share on other sites

My problem is not that it could be manipulated, it's that it was never a good benchmark. Unless things have changed, it's basically just an arbitrary number.

I'd have to look deeper once Anandtech does a structural compare of Exynos 7 series to the 810, but I'm guessing that there's structural advantages with Samsung implementing BIG.little.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

I'd have to look deeper once Anandtech does a structural compare of Exynos 7 series to the 810, but I'm guessing that there's structural advantages with Samsung implementing BIG.little.

 

 

Sent from my iPhone using Tapatalk

Yeah, AT should pretty definitely conclude if Samsung made the right choice in ditching Qualcomm (for now). 

Link to comment
Share on other sites

It could be the MDM9635M, or the MDM9645 (which is what the 810 has integrated inside it as far as baseband goes.) 

 

Personally I want Exnyos to be inside the Sprint version as far as SoC goes simply due to the fact that Qualcomm has become increasingly fat and lazy due to their baseband dominance. The problem is that the 810 sucks, it has thermal issues on the G Flex 2 that some have detected, and then when you compare AnTuTu between the Exynos in the S6 and the 810 in the One M9 it's pretty clear who's ahead here. 

 

Anything that further breaks down the Qualcomm Empire is good in my book. Apple already pawned Qualcomm with the A8 now I'm guessing it's Samsung's turn. 

Not sure what the issues are with the flex 2 but the m9, based on what I know, hasn't been experiencing those issues at all.

 

I just came across this article a few minutes ago:

 

http://www.gsmarena.com/htc_mwc_2015-review-1215p3.php

 

 

I know benchmarks can be manipulated, but by 20,000 points? I doubt that sort of gap is due to simple manipulation. Besides, all Android vendors are in on the manipulation game at this point.

 

 

Sent from my iPhone using Tapatalk

Yeah, benchmarks are so 2010.  Look at galaxy s devices versus one devices over the last few years.  On average the s devices in most cases would easily have better benchmark scores compared to the One device of that same year yet when it came to real world use the One devices blew the galaxy s devices out of the water when it came to responsiveness.  So I could care less who has extremely high scores or not, its all about real world use. 

  • Like 2
Link to comment
Share on other sites

@ascertion and the lack of waterproofing and the fact that the phone actually has less battery than before and...

 

I'm massively dissapointed as well. Ive been a Samsung smartphone user since my first one, but this looks like it might be the end of the line for me.

Link to comment
Share on other sites

I'm massively dissapointed as well. Ive been a Samsung smartphone user since my first one, but this looks like it might be the end of the line for me.

I'm disappointed that they are still making carrier specific models, especially with the new unlocking policies. Why would anyone buy a six hundred dollar phone that can only be used on a certain carrier's LTE network. All manufacturers should be following the iPhone 6 and Nexus 6 and support all domestic LTE bands.
  • Like 4
Link to comment
Share on other sites

I'm disappointed that they are still making carrier specific models, especially with the new unlocking policies. Why would anyone buy a six hundred dollar phone that can only be used on a certain carrier's LTE network. All manufacturers should be following the iPhone 6 and Nexus 6 and support all domestic LTE bands.

Well, the at least the good thing about the Sprint variant is that it is essentially fully compatible with AT&T and T-Mobile's networks (except a couple of minor things: the lack of UMTS1700 which I would no longer consider a concern and VoLTE which hopefully Sprint will some day enable in the S6 via a firmware update).

Edited by GoWireless
Link to comment
Share on other sites

Well, the at least the good thing about the Sprint variant is that it is essentially fully compatible with AT&T and T-Mobile's networks (except a couple of minor things: the lack of UMTS1700 which I would no longer consider a concern and VoLTE which hopefully Sprint will some day enable in the S6 via a firmware update).

No band 17 on the Sprint variant. Not compatible with AT&T.
Link to comment
Share on other sites

I'm disappointed that they are still making carrier specific models, especially with the new unlocking policies. Why would anyone buy a six hundred dollar phone that can only be used on a certain carrier's LTE network. All manufacturers should be following the iPhone 6 and Nexus 6 and support all domestic LTE bands.

 

No, that last statement is not true.

 

The iPhone 6, for example, is not compatible with Lower 700 MHz band 12 nor WCS 2300 MHz band 30 -- both of which are included in the just recently disclosed AT&T variant Samsung Galaxy S6.  And the Nexus 6 supports band 12 but not band 30.  Additionally, both the iPhone 6 and the Nexus 6 lack BRS/EBS 2600 MHz band 41 carrier aggregation -- though they support carrier aggregation for other bands.

 

In the end, there are simply too many bands and too many carrier aggregation combinations in use -- and continually expanding -- for a single SKU to rule them all.  Maybe that will happen someday, just do not expect it for several years.  So, an unlocked handset may possess base capabilities for use on any domestic network, but it probably will not be truly a jack of all trades.  It will be missing certain bands or carrier aggregation capabilities that are needed for an optimal network experience.

 

AJ

  • Like 1
Link to comment
Share on other sites

No, that last statement is not true.

 

The iPhone 6, for example, is not compatible with Lower 700 MHz band 12 nor WCS 2300 MHz band 30 -- both of which are included in the just recently disclosed AT&T variant Samsung Galaxy S6. And the Nexus 6 supports band 12 but not band 30. Additionally, both the iPhone 6 and the Nexus 6 lack BRS/EBS 2600 MHz band 41 carrier aggregation -- though they support carrier aggregation for other bands.

 

In the end, there are simply too many bands and too many carrier aggregation combinations in use -- and continually expanding -- for a single SKU to rule them all. Maybe that will happen someday, just do not expect it for several years. So, an unlocked handset may possess base capabilities for use on any domestic network, but it probably will not be truly a jack of all trades. It will be missing certain bands or carrier aggregation capabilities that are needed for an optimal network experience.

 

AJ

The iPhone 6 and Nexus 6 do leave out what you mentioned but they do however, support the current core technologies of all domestic carriers which allows you to take your phone to any domestic carrier and have a pleasant experience.
Link to comment
Share on other sites

The iPhone 6 and Nexus 6 do leave out what you mentioned but they do however, support the current core technologies of all domestic carriers which allows you to take your phone to any domestic carrier and have a pleasant experience.

 

And that experience evolves and morphs every quarter.  The crux of his point.  Right now AT&T customers have a good experience without B29 and B30, but that will not be true in another quarter or two.  And new AT&T devices support them.  Also, there will come a time that B41 CA will be quite necessary on the Sprint network.

Link to comment
Share on other sites

So, an unlocked handset may possess base capabilities for use on any domestic network, but it probably will not be truly a jack of all trades.  It will be missing certain bands or carrier aggregation capabilities that are needed for an optimal network experience.

 

AJ

 

I wonder how marketing and PR teams from each carrier are going to handle customers who want to take thier unlocked phones from carrier to carrier.

I can see that being a big mess leaving the customer confused and angry - most definately placing the blame on their current carrier rather than on thier phone.

  • Like 1
Link to comment
Share on other sites

The iPhone 6 and Nexus 6 do leave out what you mentioned but they do however, support the current core technologies of all domestic carriers which allows you to take your phone to any domestic carrier and have a pleasant experience.

 

A "pleasant experience" is an ambiguous term.  It has variable meanings to different people at different times, present and future.

 

Also, the unlocked handset street tends to be one way -- away from Sprint.  A Sprint handset may provide a "pleasant experience" for some on other operators.  But another operator's handset generally provides a zero experience or notably compromised experience on Sprint.

 

AJ

  • Like 1
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

    • I think it is likely that T-Mobile will be forced to honor any existing US cellular roaming agreements in those areas as a condition of them taking over the spectrum.  In that case, there would be no improvement of service unless T-Mobile improves the service offering in those areas.
    • My understanding is the MNO carriers are the one who have objected to the use of cell phones in commercial planes.  I understand that it ties down too many cell phones at once, thus I can not see this changing. However this depends on how it is structured. Use of a different plmn for satellite service might make it possible for planes only to connect with satellite. Private pilots have been using cellphones in planes for many decades. Far fewer phones at a lower altitude.
    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
  • Recently Browsing

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