What you need to know
- After rolling it out to users in China, Huawei is now pushing the stable EMUI 10 update for the P30 Pro in Europe.
- Based on Android 10, the EMUI 10 update comes with a new dark mode, magazine-style UI layout, upgraded GPU Turbo, performance improvements, and more.
- You can check for the update by going to Settings > System > Software updates.
Huawei began pushing the stable EMUI 10 update based on Android 10 to the P30 Pro smartphones in Chine earlier this week. Now, the update has started rolling out (via HuaweiCentral) in parts of Europe as well.
The update arrives as EMUI 10.0.0.168 and weighs in at a whopping 4.47GB. Just as you would expect, the update is being pushed in stages currently. This means it will take at least a few weeks before it becomes widely available.
Apart from Europe, the EMUI 10 update is expected to soon begin rolling out in other regions as well. As per P30 Pro users on Reddit, the update is currently being pushed in Serbia, Portugal, and a few other regions in mainland Europe.
In addition to all the standard Android 10 goodies, the EMUI update also brings a few other exciting new features. It comes with a new UI design with a magazine-style layout, an enhanced dark mode, one-touch screen sharing, GPU Turbo upgrades, faster system performance, improved security, and more.
Huawei is expected to push the stable EMUI 10 update for the Mate 20 X, Mate 20 RS Porsche Design, Honor 20 series, as well as the Honor Magic 2 before the end of the month in China. The global variants of these devices, however, may have to wait until next month to receive the stable update.
My P30 PRO just got the update. I was reading the update logs and read the following under security: "Huawei's own self-developed microkernel design, certified as the most secure OS kernel for commercial use" does anyone know any more info on this?
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.