Qualcomm is currently working on the design of a new smart for connected watches. Based on a new architecture, this chipset would be much more powerful than what the Californian giant proposed so far.
This is what we learn from a WinFuture report. According to the German site, Qualcomm is working on a heavily modified version of the Snapdragon 429, which is suitable for connected watches. This new chip would be based on the ARM Cortex-A-53 architecture. A potentially interesting evolution vis-à-vis the solutions proposed to date by Qualcomm.
Towards a real renewal for the Snapdragon Wear range?
In the SoC market for smartwatches, Qualcomm is content for the time of its Snapdragon Wear 3100. This is an evolution of Snapdragon Wear 2100, created especially for the connected watch market to replace the Snapdragon 400, proposed at the beginning of what was still called Android Wear. The common point between these three generations of chips is to be based on an ARM Cortex-A7 architecture; the Snapdragon Wear 2100 and 3100 both include an Adreno 304 graphic part.
Clearly, since the entry of Qualcomm in this market, no scale renewal has been undertaken for these chipsets. But that could change.
A faster chip for future Android smartwatches
By switching to the Cortex-A53 architecture, Qualcomm's new Snapdragon Wear chip would benefit from significantly higher performance compared to the brand's existing offering. Good news for Wear OS, which could, therefore, be more responsive. This renewal would also allow Qualcomm to add support for Bluetooth 5.0 to its next chip.
If we lack additional technical information, WinFuture believes that this new generation processor would be marketed under the name Snapdragon Wear 2700(and not 3700, still according to the German media). It would still benefit from some similarities with the Snapdragon Wear 3100 and would currently be tested with 1GB of LPDDR3 RAM and 8GB of eMMC memory.
No launch slot is currently being discussed. And for good reason, said the chip is still in the " trial and verification " phase.
0 Comments