OnePlus Two joins Snapdragon 810 delay roster


by |


Share:


Oneplus One



Adding fuel to the fire of Qualcomm’s woe-laden Snapdragon 810 overheating fiasco is news that the OnePlus Two might also be delayed thanks to the chip issues too.


That’s right – the latest entrant to the Snapdragon 810-blaming delay fray is the OnePlus One’s upcoming successor.


Forbes reports that ‘sources’ have confirmed that the OnePlus Two has been ‘forced back into the third quarter of 2015’ because of ‘manufacturing challenges with the Snapdragon 810.


It’s not the only one either – both the Samsung Galaxy S6 and LG G4 have reportedly been affected by the alleged overheating issues on Qualcomm’s flagship chipset.


Fortunately, rumours point to Samsung snubbing Snapdragon for its own custom-built Exynos series, likely to keep production of the Galaxy S6 on track.


Less fortunate however is the suggestion that Qualcomm might be less than keen to fix its chip for 2015 smartphones after reports emerged suggesting LG might file a lawsuit against the chip-manufacturing firm.


This is because it’s already announced the LG G Flex 2, Snapdragon 810 in tow. A second and, more importantly, better Snapdragon 810 landing on other smartphones would most definitely be a thorn in LG’s handset heel.


All the while, Qualcomm has been flat-out denying any suggestion of delays or overheating issues with the Snapdragon 810, despite the ever-mounting evidence pointing to the contrary.


Related: MWC 2015: What to expect from the Barcelona expo


So what’s actually wrong with the Snapdragon 810? Here’s how it goes…


The Snapdragon 810 is built with ARM’s big.LITTLE chip configuration. This means that of the eight cores, four are dedicated to less demanding tasks, and four are dedicated to more demanding tasks.


The former are Cortex A-53 processor cores, while the latter are Cortex A-57 processor cores. Therein lies the problem.


Apparently, the A-57 cores are overheating and throttling the clock rate once the frequency passes 1.2-1.4GHz, which is now proving to be a big old PR disaster for Qualcomm, if nothing else.