Xiaomi launched its latest flagship device, the Xiaomi Mi 6, in China just last month. As has always been the case with Xiaomi's smartphones, the device packs best-in-class hardware at an attractive price point. The device is already on sale in its home country, with a release expected in other markets in the coming months. Early reports suggest the device has been well received in China, with flash sales resulting in units flying off the shelves just seconds after the device goes on sale.
However, it appears that the device is facing a supply shortage. According to a report from MyDrivers, the Xiaomi Mi 6 is facing a supply shortage of the Qualcomm Snapdragon 835 chips as well as Ceramic shells which the company has used on a special edition of the Mi 6.
Shortage of the Snapdragon 835 chipsets shouldn't come as a surprise as we already know that Samsung reportedly has the first claim on the Qualcomm's latest chip for its Galaxy S8 and Galaxy S8+ devices. Qualcomm's Snapdragon 835 SoC is built on Samsung's 10nm Fin FET process, so it's hard not to see why when the South Korean smartphone giant has first dibs over the supply of Snapdragon 835 chips.
Apart from chip shortage, Xiaomi is also facing a shortage for the Ceramic body, which the company is using on a special edition of the Mi 6. There is an increasingly high demand for the Ceramic variant of the Xiaomi Mi 6. The Ceramic edition comes with 128 GBs of internal storage and costs RMB 2999 ($435), which is $15 more compared to the standard 128 GB edition ($420). Ceramic has the feel and glossiness of glass and the heaviness of metal, but it's also incredibly scratch resistant. So it's understandable that for such a small price increase, many consumers would probably be happy to shell out little extra to get a better build for their smartphone.
With the Mi 6 already facing tight supply in its home country, it's unclear if this will also delay its release in other markets such as India.
Source: MyDrivers Via: Android Authority
from xda-developers http://ift.tt/2q3m5BZ
via IFTTT
No comments:
Post a Comment