The Samsung Galaxy Note7 (S820) Review
by Joshua Ho on August 16, 2016 9:00 AM ESTVideo Performance
For this portion of the review we can take a look at video performance, which provides an extra test of encode block performance in addition to ISP, sensor, and optic performance. In the interest of not wasting time on retreading topics that are basically unchanged relative to the Galaxy S7, I would redirect readers interested in an in-depth exploration of this subject and comparisons to other devices to the Galaxy S7 Part 2 review as this part of the review will be almost entirely focused on just comparing the Note7 to the Galaxy S7 to see what’s changed.
| Samsung Galaxy Note7 Video Encode Settings | ||||
| Video | Audio | |||
| 1080p30 | 17 Mbps H.264 High Profile | 256 Kbps, 48 KHz AAC | ||
| 1080p60 | 28 Mbps H.264 High Profile | 256 Kbps, 48 KHz AAC | ||
| 4K30 | 48 Mbps H.264 High Profile | 256 Kbps, 48 KHz AAC | ||
| 720p240 | 76 Mbps H.264 Baseline | 256 Kbps, 48 KHz AAC | ||
Starting with encode settings, we can see that the Note7 retains the same exact encode settings as the Galaxy S7 and S7 edge, which probably isn’t a surprise given that we’re probably seeing the limits of what the Snapdragon 820’s encode blocks can handle in cases like slow motion video, although 1080p30 is likely not encode-limited at this point.
Galaxy Note7
Galaxy S7
In 1080p30 video the Galaxy Note7 and Galaxy S7 look basically identical save for some slight differences in color rendition. The Note7 seems to be slightly more accurate here as the sky is closer to the color of blue that it should be but detail and most other colors look fairly comparable and both still have some jerky OIS reset behavior.
Galaxy Note7
Galaxy S7
In slow motion video the Galaxy Note7 again seems to have slightly improved color rendition but detail and pretty much everything else is identical. I don’t think this is a reason to go out and buy the Note7, but hopefully these improvements to color rendition come to future OTAs for the Galaxy S7.
Overall I don’t think video results appreciably change the Galaxy Note7’s results here. The camera is great from a speed perspective and it’s good for video but in a lot of cases HTC really does have them beat with the camera on the HTC 10. I think the major win for the Note7 continues to be speed and consistency as the one major weakness of the HTC 10’s camera relative to the Note7 is somewhat unreliable contrast AF in low light, although in better conditions PDAF has no issues achieving perfect focus.
Facebook
Twitter
RSS
202 Comments
View All Comments
lilmoe - Tuesday, August 16, 2016 - link
SD820 has the power more fluidly? Yes. Better than Exynos? Ummm... No.If you want smoother UI and better touch response, root and change the governor to Performance, or Ondemand.
lilmoe - Tuesday, August 16, 2016 - link
I've dug a little deeper into this after I bought my GS7e (Exynos). Looks like Exynos (and it's higher count of cores) plays better than the Snapdragon with the Conservative Governor that Samsung employs to save battery life. You can manually switch it to Ondemand, Interactive, or even better, Performance (eliminating most of the UI performance differences, and increase the responsiveness of the device drastically). But battery life would take a major hit, just like every other Android device with a 1440p screen.What needs to fixed and optimized is ANDROID. Google still insists on doing a crappy job with their OS, just like with their browser.
lilmoe - Tuesday, August 16, 2016 - link
"What needs to fixed and optimized is ANDROID. Google still insists on doing a crappy job with their OS, just like with their browser."What also needs to be fixed is the "higher resolutions screen is better" mentality. No smartphone should have more than a 1080p panel for optimal performance and efficiency.
There's absolutely no mention of the new power saving features that the new version of TouchWiz employs; like scaling down the resolution and how much more battery life you get out of that. Guess I'll have to test it myself when my GS7 gets the update. I'm soooooooooooooooooooooo scaling back the resolution to 1080p while leaving processing power intact.
InspectHerGadget - Wednesday, August 17, 2016 - link
Yes. The extra screen resolution is not worth the hit on battery life. Android and Samsung are also both to blame for poor optimisations. I had the Nokia 1520 which had great battery life, then the Note 5 which had only so so battery life, now the iPhone 6S Plus which has great battery life. On the Note 5 if I left the hotspot on it would get hot and drain the battery even when my Microsoft Pro 4 was in its case. I just felt too many rough edges on Samsung phones I had.jospoortvliet - Thursday, August 18, 2016 - link
Remember, guys, amoled isn't hit by lower efficiency on higher resolution, that is only an LCD problem. Now granted the gpu and cpu have to work a little harder but 1080P wouldn't look nice with pentile and Samsung does pentile to get a better endurance/longevity and brightness out of AMOLED. I don't think they made the wrong choice here. And yes, 1440P on an LCD is stupid.lilmoe - Tuesday, August 16, 2016 - link
Sorry, the governor they use is Interactive, not conservative...jospoortvliet - Thursday, August 18, 2016 - link
Then it shouldn't be an issue and if it is - they shold fix the governor not switch to performance. The performance governor is barely faster at big costs.lilmoe - Thursday, August 18, 2016 - link
It doesn't act like an Interactive governor would act at all, it's very slow to ramp up clock speed, and most ramps up the little cores. It's a good thing for battery life, but not as good for fluidity.jospoortvliet - Thursday, August 18, 2016 - link
IMHO the on demand governor should really not be costing battery life. It was designed to be a good balance and it generally is, at least on desktop.Then again with such an outdated kernel with patches who knows what is in there... wish the android vendors would get their stuff up streamed more timely...
grayson_carr - Tuesday, August 16, 2016 - link
It's a conscious decision happening at Samsung. They could tweak the kernel / governor configuration so that there are almost no frame drops and slowdowns, but it would come at the cost of battery life. Samsung is aiming for the minimum performance they think their users won't be annoyed with in order to maximize battery life, which Samsung assumes is more important to the average user. Google on the other hand configures their devices so that they maintain 60 fps in most scenarios, and their battery life suffers for it. I personally prefer Google's approach because I value a smoother and stutter free UI more than a little extra battery life, but I think a lot of people who buy Nexus devices are baffled as to why the battery life isn't as good as their Samsung phone even though the battery is just as large. Those people may prefer battery life over the smoothest UI possible.