If S810 with watercooing can take on 4k screen, even if batterylife is bad, S820 cannot be worse if its more powerfull and energy efficient. I just hope phones get bigger batteries and will last at least as long as Z3compact with its snapdragon.
.alpha, 29 Oct 2015Qualcomm also say 810 v2.1 fixed the overheating problem until people find out all 810 are v2.... moreYour bang on the money, A Qualcomm spokesperson even admitted that the Apple 64-bit announcement caught them by surprise.
As far as I am aware, the only company to have successfully fielded a 'heat' issue free device using the 810 is Oneplus, and they did this by limiting the maximum clock speed to 1.8ghz (down from the 2.0ghz the rest of the industry have gone with). Sony went with the original speed but tried to offset this by using a special thermal gel and dual heat pipes, this appears to have helped to a degree, but not completely banished the issue.
In short this has been a reactionary year for Qualcomm, and not a very good one as far as the high end of the market goes, it's hard to argue that the 410 and 615 have been disappointments as they both do what is required of them trouble free, and the 808 is solid, just not the highest performer.
The 810 is represents a black mark for Qualcomm (it's first real one), and I really hope the 820 is fine from performance point of view.
Qualcomm also say 810 v2.1 fixed the overheating problem until people find out all 810 are v2.1 and they all overheats. Qualcomm made it sounds like the overheating problem were limited to HTC One M9 by saying a version number as if One M9 isn't using v2.1.
Qualcomm were simply caught off guard when Apple whack it with 64-bit and it has lost its footing ever since.
If samsung don't use the chip on their next flagship, then we know that it does have issues. And bye2x to profits for qualcomm.
These are just rumours at this stage, though it appears everyone is already drawing conclusions.
For me the first major indication that there is an issue with the 820 will be if Samsung again drop it form their upcoming Galaxy S7, based on the apparently correct decision to leave the 810 out of this years Samsung line up.
Considering the momentum they have achieved this year with the impressive Exynos 7420, and the fact that they now have their own brand new custom core designs that they must be eager to put to the test. If after you take these factors into consideration, Samsung still choose to utilise the 820 in their 2016 line up, then I'll be more convinced this is all just rumour.
Did you smell what Qualcomm is cooking?? *The Rock likes this lol
Grey1213, 29 Oct 2015But that's the point, they're using custom cores now, plus its not going to be 20nm.The problem is not whether they're using custom or not. Exynos 5433 was/is a mirror of SD810 (at 20nm no less!) but it hardly had any serious throttling/overheating issues. They're just bad engineers because with the same resources they make worse products.
Like I wrote above, here's hoping that SD820 would prove me wrong.
They told this about Snapdragon 810 last year, we can't believe a proven liar!
Oh god, not this again, another terrible year? if this is true i'll just buy nexus 6p i guess!
"the SoC currently meets its design specifications, and will continue to be enhanced"
"Yes it runs hot, we are desperately trying to fix it"
Why is Samsung even bothering with Snapdragon? They apparently have production capacity since they are manufacturing the Snapdragon. So why not just stick with proven tech - the Exynos 7422 or whatever the latest is?
Anonymous, 29 Oct 2015Applogists of bad engineers are so funny. Qualcomm has held back the evolution of ARM SoCs for... moreBut that's the point, they're using custom cores now, plus its not going to be 20nm.
mas39, 29 Oct 2015Jealous people won't leave Qualcomm alone, the s820 should be awesome and I can't wait for the... moreApplogists of bad engineers are so funny. Qualcomm has held back the evolution of ARM SoCs for years now. Up until late 2014 they were using a modified Cortex-A9 core (krait), seriously! Their 64bit "jump" was disastrous. I really don't trust anything this company says anymore. Here's hoping that they will prove me wrong...