Latest rumor says to expect a fingerprint scanner and the Snapdragon 820 SoC for the Xiaomi Mi 5
We've characterized China's Weibo micro-blogging site as being like the Wild, Wild West. Information is constantly being posted on the site, and unless a specific post comes from a verified account, it is always a good idea to take the rumors and speculation originating from Weibo with the proverbial grain of salt.
Take this morning's rumor. According to a Weibo-er @MochaRQ, who claims to have knowledge of what is going on inside Xiaomi HQ, things are progressing well with the Xiaomi Mi 5. By today's standards, the sequel to the Xiaomi Mi 4 flagship is overdue. And according to the leak, Xiaomi will be stuffing the phone with the Snapdragon 820 SoC, which means the company is being held hostage by Qualcomm's own production schedule for the chip. The Snapdragon 820 chipset might not be available to manufacturers until early next year. If this is legit, it means that Xiaomi is not turning to MediaTek. Nor is it going to settle for the Snapdragon 810 to power the Mi 5.
Even if Qualcomm picks up the pace, the Xiaomi Mi 5 appears to be a 2016 model. In the meantime, we have seen variations of the Mi 4 (Xiaomi Mi 4i, Xiaomi Mi 4c) offered. If you're waiting on Xiaomi's new flagship, you probably have a few more months left before you can truly get excited about the phone.
source: MyDrivers (translated) via XiaomiToday
The Weibo post also includes word that the Xiaomi Mi 5 will include a fingerprint scanner, although just about every new flagship is offering one these days. Earlier speculation that the Mi 5 would be part of a Xiaomi media event to be held on Monday, was shot down by Xiaomi co-founder Lin Bin.
Even if Qualcomm picks up the pace, the Xiaomi Mi 5 appears to be a 2016 model. In the meantime, we have seen variations of the Mi 4 (Xiaomi Mi 4i, Xiaomi Mi 4c) offered. If you're waiting on Xiaomi's new flagship, you probably have a few more months left before you can truly get excited about the phone.
Things that are NOT allowed: