Just saw this, its a speed test between the Pixel and iPhone 7. I know this is the S7 thread, the point is that the way the pixel began reloading apps in the second is very reminiscent of how Samsung phones have done in this same test, resulting in a lot of flack for touchwiz, but here is Googles version and it does the same thing. It's weird because I've seen tests with HTC phones and past Nexuses that haven't done this. Could this be a result of using the faster on board storage that Samsung has been using for a while?
It was last years Samsung devices with their aggressive ram management that exhibited same, the S7/S7e didn't suffer as much from the issue (especially the exynos variants which outperformed the Snapdragon).
But yeah, I'd like to see the same test against the Nexus 6P so we can see if it's a software issue on the Pixel.
The 6P previous Phonebuff tests didn't do this.
So why ?
Two possible scenarios.
1) Android 7.1 on the pixel still has bugs / chinks that need to fixed
2) The underclocked Snapdragon 821 could point to the fact they are also aggressively killing ram as a way to extend battery life.
We have seen the OP3 do a similar thing where it's 6gb ram on arrival only performed like a 2gb device, and even with the update to fix the issue, the build.prop limited adjustment OP changed to means it still only uses around 3 tops of the 6gb available. (Meaning unless you circumvent the issue and adjust build.prop yourself you will never benefit from 6gb).
Anyway so there are your two scenarios.
1. Buggy software
2. An artificial ram limiter which expunges stored data early in order to preserve battery.
If it's the latter, that would truly suck. A €750 pixel shouldn't perform like a €250 Nexus 5X memory wise.
However I hope it's the former and it's simply buggy software.
Time will tell, what we need is a Pixel Vs Nexus 6P running 7.0 to see a comparison in behaviours.
