Initial Conclusions

Even though we’re just barely scratching the surface of what we can test, the results we already have show quite a bit about the Samsung Galaxy S7. The Galaxy S line remains one of the most popular Android smartphones, and if history is any indication we can get a pretty good idea about what to expect for 2016 just by looking at the Galaxy S7 and S7 edge.

The first place we can start is design, and here we can see that the Galaxy S7 is decidedly an evolution of the Galaxy S6’s ID. However, pretty much every sharp edge has been rounded out to make the device more comfortable in the hand. The device has also been thickened in order to handle the larger battery and reduce the apparent z-height of the camera. The display size of the Galaxy S7 (non-edge) stays at 5.1 inches, and given how long Samsung has stuck to this display size it’s likely that they will be staying at this size for quite some time for their flagship.

In general, it feels like the industry has settled upon a display size somewhere between 5 to 5.5 inches for their flagship devices as going further probably won’t make a lot of sense for ergonomic reasons. I suspect Samsung and many other Android OEMs are settling into an Apple-like 2 year cadence for industrial and material design as replacement cycles lengthen, especially in the United States where subsidized phones have been almost entirely eliminated.

Meanwhile, though we haven’t had the time to run our full suite of battery life benchmarks, the data that we do have is quite interesting. At the very least, it looks like the Galaxy S7 will be a solid upgrade for those coming from the Galaxy S6 and earlier with a 15% bump in battery life or so. Anyone using a phone with an SoC not on a FinFET node will see even bigger gains to battery life, which is impressive to say the least. If you have any device with a Snapdragon 810 or 808 SoC, you’re definitely going to see major gains if you move to any device with a SoC fabricated on a FinFET node.

In terms of SoC performance, the Snapdragon 820 doesn't disappoint. In the time since testing the MDP it seems that between Qualcomm, Samsung, and Google, the trio has finally been able to optimize Snapdragon 820 for Chrome, so performance there is quite acceptable now and a pretty solid uplift over something like the Exynos 7420 or Snapdragon 810. GPU performance is also pretty much right where the Snapdragon 820 MDP was, so performance should be a good step above the A9's GT7600 GPU. Of course, we have yet to consider the power efficiency or sustainability of this performance, but turbo/overdrive performance is always relevant in the mobile space considering just how bursty almost every mobile workload is. It's pretty safe to say that Qualcomm has at least regained their footing in the SoC space, and with future SoCs they may well come to dominate the high end for performance and power once again. For now, it's looking like the race between Exynos 8890, Snapdragon 820, and Kirin 950 will be quite close.

For storage performance, to some extent it seems that the performance gains are relatively small, as the UFS 2.0 storage solutions on the Galaxy S6 and S7 are relatively similar. It’s interesting to see here that despite the now-mandatory use of FDE, the delta in performance between the Galaxy S6 and S7 in storage performance doesn’t seem to exist. This is welcome news as it wasn’t all that long ago that FDE for Android had a noticeable effect on storage performance.

On the display side, again we can see that the Galaxy S7 has a relatively similar display to the Galaxy S6. Calibration should be relatively good across the board, and AMOLED retains all of its traditional advantages including high contrast, support for wide color gamuts, low transition time, and improved power efficiency at lower average picture levels. Peak brightness is the only noticeable area where things seem to change, but I suspect that this will vary noticeably depending upon the unit. The one issue that I continue to notice here is that the edge display on the Galaxy S7 edge has a green tint at the edges, likely due to the diamond PenTile subpixel arrangement.

On the software side, Samsung’s TouchWiz UI continues to be more of the same when compared to the Galaxy Note5. The edge features continue to be somewhat interesting, but I continue to find myself thinking that there would be no difference if the same feature was implemented on the non-edge variant. Thankfully, the lag that I noticed last month in my initial hands-on time with the device seems to just have been a function of pre-release software, as the Galaxy S7 is relatively performant here. Although I’m not sure I’d go as far as to say that the Galaxy S7 is entirely free of lag. I suspect that Samsung has to balance power efficiency and responsiveness to some extent here, as while devices like the Nexus 5 can feel incredibly smooth and responsive there are very real knock-on effects in terms of practical battery life.

I’m also looking forward to testing features like Samsung Pay that are finally being deployed to the extent that I can use my personal credit card with Samsung Pay on my phone. However, out of the box TouchWiz still has some issues with an overly-neon theme, and in general things like Always-On Display already feel like they aren’t quite executed as well as they should be. I also noticed that the fingerprint scanner performance is strongly influenced by initial setup if I didn’t scan some areas on initial setup they never seemed to work very well unless I retrained the finger.

As for making a choice between the Galaxy S7 edge and Galaxy S7, there basically aren't any outside of size for the most part. There is the edge display, but by and large it feels like that's more of an aesthetic choice than a functional one. As we have seen you do get better battery life in the Galaxy S7 edge, but I don't feel like it makes sense to cross-shop the two. If you want one-handed usability, the Galaxy S7 is the only choice that makes sense. If you want a phablet, the Galaxy S7 edge is the only choice that makes sense.

Overall, I think the Galaxy S7 is looking to be one of the better devices of the year. Of course, there’s still a lot more to test, but the initial indications are already looking quite good. If you absolutely want the Galaxy S7 now, I don’t think there will be any major showstoppers present in this phone. However, if you’re looking to buy the best phone possible available this year I think it’s still too early to say where the chips will fall as Samsung's eager competitors have their own flagship phones right around the corner.

Software UX
Comments Locked

202 Comments

View All Comments

  • jjj - Wednesday, March 9, 2016 - link

    One last time , these apps due to the different core configs can change the rankings. The one that gets 20h could go to 12 and the one with 16 to 14h.That was the main point here.Because the vast majority of users have such apps, you can't reach relevant results without factoring them in.A phone can get good results in the current test and poor in actual usage.
  • retrospooty - Wednesday, March 9, 2016 - link

    That is an extremely unlikely example. In real world usage, Octa cores have had very little difference in any area (performance or efficiency) vs. their quad core counterparts unless there is an issue with the ROM where it's simple bleeding power. Whatever though, if you feel so strongly about it, by all means, do some testing on various phones and submit to a few sites and see how worthwhile it is.
  • jospoortvliet - Friday, March 11, 2016 - link

    I'm no fan of the hitching at the AND team but he has a point with the background tasks - an average modern phone has a lot of them and testing endurance with them all disabled isn't realistic. Moreover, indeed a dual core would probably perform worse with more background tasks than a quad-core or octacore as they can spread the load and keep their cores at an energy-efficient optimal speed.

    A repeatable, fixed background load would be good to have. Also hard to write, certainly across ios and Android due to their different capabilities and limitations with regards to background tasks. So I get why it hasn't been done and if jjj is up for writing a tool that does it I bet the anandtech team would take it... Yeah.
  • leexgx - Monday, March 14, 2016 - link

    the only thing i find with anandtech is battery tests is that they do not follow real world battery use (to get correct results divide it by about 2 or 2.5 and there is your real battery use, when you look at anandtech reviews, all other tests are good, most phones last around 4 hours Screen on time (max tends to be 4 hours but can be as low as 1.5 hours)

    the only exception to that rule tends to be the
    Motorola RAZR MAXX phones (Low end CPU with 3200 battery),
    CUBOT H1 1Ghz Quad core, 720p screen {basicly Samsung Note 2 spec} with Massive 5200 battery, (i own and love, and only costs £110 !!) still miss not having the HTC ONE stereo speakers but i take 8 hours over 2 hours (without having to use an external battery case that turns it into a brick)
    and the Huawei Mate 8 (4000 battery)
  • Andrei Frumusanu - Tuesday, March 8, 2016 - link

    GFXBench long term performance is currently not useful to anybody as it hits Vsync in the current T-Rex test. In the full review we'll have a proper test which will be of use for users.
  • jjj - Tuesday, March 8, 2016 - link

    Seems that you might be wrong Andrei. I am guessing you got the MI5 but that's 1080p and you forgot to factor that in? Here at 1440p you don't hit the 60FPS wall even in the first run.
    If the MI5 doesn't fall bellow 60FPS with the 1080p, it would be relatively good news, as it means less than 33%-ish throttling with a 1080p display and no heatpipe.
  • hansmuff - Tuesday, March 8, 2016 - link

    This German review posted some GFXbench results you might be interested in, however ofc their phone uses Exynos. Hard to say that Snapdragon would behave the same way, but it's also clear that having a heatpipe alone in the phone doesn't mean it won't throttle.. significantly at some points.

    http://www.computerbase.de/2016-03/samsung-galaxy-...
  • jjj - Tuesday, March 8, 2016 - link

    Thanks a lot, ofc has nothing to do with SD820 but having this for the Exynos is nice too.
    Digitimes was claiming that only the SD820 models have the heatpipe, no clue if true or not, guess it's something else that has to be verified.
  • jjj - Tuesday, March 8, 2016 - link

    The Exynos models do have the heatpipe too.
  • tuxRoller - Tuesday, March 8, 2016 - link

    Is that what you do with your phone? Run continuous benchmarks all day?
    I understand we want an idea about throttling but using those benchmarks as proxy for expected performance won't get you that info about day to day usage.

Log in

Don't have an account? Sign up now