Xiaomi begins official testing of HyperOS 2.0

There have been some leaked information about HyperOS 2.0 released in recent weeks, but have not been confirmed. It wasn't until now that the XiaomiTime team actually found important information confirming that HyperOS 2.0 is being tested, and is expected to officially launch in October.

Recently, Xiaomi has quietly accelerated the deployment of HyperOS 2.0. A new extension named [OSBigversion] has been discovered on the Xiaomi OTA server. This new extension specifies HyperOS versions. For example, if you are using HyperOS 1.0, this extension will be displayed as [OSBigversion] => 1.0. Or assuming you are using HyperOS 2.0, this extension will be shown as [OSBigversion] => 2.0.

Previously there was no OSBigversion extension, but only [Bigversion] for major MIUI versions. This Bigversion extension has specified major MIUI versions. For example, if you are using MIUI 14, it will show as '[bigversion] => 14'. Xiaomi has been using this type of extension for many years. Now we see that there is a new special 'OSBigversion' extension used for HyperOS.

This extension is added to the OTA server to differentiate between new HyperOS versions. With the new extension, subsequent HyperOS versions will be delivered to users' devices safely without any problems. This shows that HyperOS 2.0 development has officially begun.

Additionally, HyperOS versions have build numbers starting with V816. MIUI was first released on August 16, 2010. Therefore, Xiaomi has set the build number as V816. In fact, there are many different factors involved in this build number.

Before HyperOS 1.0 was released, this new version had build number V15. That suggests HyperOS 1.0 is a rebranded MIUI 15. Some people speculate that Xiaomi is trying to build a new operating system, but this is not true.

HyperOS 2.0 is expected to be announced alongside the Xiaomi 15 series in October. Xiaomi usually introduces new UI with quite a bit of fanfare, then gradually starts rolling out new updates. All we have to do now is wait patiently for HyperOS 2.0.