HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Ah, yes, Nova.
I use Nova and witness this issue, it's because System Launcher doesn't initialise fully because of default launcher being Nova (if it's just Nova that has this issue)

Go switch your Launcher app to System, go to recents menu, switch launcher back to Nova.

Restarting will clear this and you will need to repeat (use apps like Links to make quick shortcuts)
 
  • Like
Reactions: mattzildjian
I use Nova and witness this issue, it's because System Launcher doesn't initialise fully because of default launcher being Nova (if it's just Nova that has this issue)

Go switch your Launcher app to System, go to recents menu, switch launcher back to Nova.

Restarting will clear this and you will need to repeat (use apps like Links to make quick shortcuts)
Thanks for the tip, for some reason I had to completely uninstall nova just to get back to System launcher, as it wasnt letting me switch any other way...
After reinstalling nova I am able to switch between them and get the app switcher functionality back temporarily, thanks.

I wonder if you also have a solution to the "Chain Start" message that pops up for every app that is launched via Nova? Even after "remembering" the choice it eventually pops up again. Thanks.
 
Updated to latest on Vermeer. Facing System Launcher crashing. Screen freeze. Massive power drain by "Android System"
 

Attachments

  • Screenshot_2025-03-31-23-31-52-075_com.miui.securitycenter.jpg
    Screenshot_2025-03-31-23-31-52-075_com.miui.securitycenter.jpg
    279.8 KB · Views: 75
Lisa user here. Managed to find the official HyperOS 2.0.1.0 CN ROM for this device and also got the Xiaomi.EU version (which has been deleted). I've extracted the payload.bin and found some img files missing from the original:
- cust.img 86236kb

The Xiaomi.EU one misses these (maybe they are in the super.img's):
- mi_ext.img 147456kb
- odm.img 17694720kb
- system.img 715182080kb
- system_ext.img 578744320kb
- vendor.img 1536798720kb

Could this mean Xiaomi changed the partition layout with HyperOS2?

Also could confirm, after the update process the phone reboots to the Android loading screen and after that to Fastboot. Unfortunately as far as I know ADB doesn't work before the system loads so I couldn't get a Logcat, and I don't know if there is any way to log what happens during boot. Sorry if this is offtopic here.
 
Are you facing these issues also on Vermeer?

Facing System Launcher crashing. Screen freeze. Massive power drain by "Android System"
I'd like to have it ( this is cool feature ) :) but unfortunately NO. Everything work in the Atomic level without a problem :cool:
 
  • Like
Reactions: groxFR
Lisa user here. Managed to find the official HyperOS 2.0.1.0 CN ROM for this device and also got the Xiaomi.EU version (which has been deleted). I've extracted the payload.bin and found some img files missing from the original:
- cust.img 86236kb

The Xiaomi.EU one misses these (maybe they are in the super.img's):
- mi_ext.img 147456kb
- odm.img 17694720kb
- system.img 715182080kb
- system_ext.img 578744320kb
- vendor.img 1536798720kb

Could this mean Xiaomi changed the partition layout with HyperOS2?

Also could confirm, after the update process the phone reboots to the Android loading screen and after that to Fastboot. Unfortunately as far as I know ADB doesn't work before the system loads so I couldn't get a Logcat, and I don't know if there is any way to log what happens during boot. Sorry if this is offtopic here.
Nothing has changed in the partition layout, in fact it never changes after a device has been released.
Yes, those logical partitions are part of super partition, we don't use the payload format.
 
Here to report vermeer, no freeze like others mention, but android system is now at the top of draining in the battery page.first pick is before update second is after.
 

Attachments

  • Screenshot_2025-04-01-07-56-02-873_com.miui.securitycenter.jpg
    Screenshot_2025-04-01-07-56-02-873_com.miui.securitycenter.jpg
    384.1 KB · Views: 58
  • Screenshot_2025-04-01-07-56-12-921_com.miui.securitycenter.jpg
    Screenshot_2025-04-01-07-56-12-921_com.miui.securitycenter.jpg
    412.7 KB · Views: 59
  • Like
Reactions: miccio
Here to report vermeer, no freeze like others mention, but android system is now at the top of draining in the battery page.first pick is before update second is after.
I have the very same issue on Xiaomi 15 ultra. Even after updating it 2 times with never system version (110 and currently 113), android system is on top of the list in battery management. Didn't find any solution for that yet. Phone can hardly survive till the evening.
 

Attachments

  • Screenshot_2025-04-01-06-44-02-517_com.miui.securitycenter.jpg
    Screenshot_2025-04-01-06-44-02-517_com.miui.securitycenter.jpg
    256.7 KB · Views: 71
  • Screenshot_2025-04-01-06-48-03-423_com.android.settings.png
    Screenshot_2025-04-01-06-48-03-423_com.android.settings.png
    789 KB · Views: 70
  • Like
Reactions: miccio
I have the very same issue on Xiaomi 15 ultra. Even after updating it 2 times with never system version (110 and currently 113), android system is on top of the list in battery management. Didn't find any solution for that yet. Phone can hardly survive till the evening.
14U has the same problem
Battery drain is quite good
Probably waiting for update
 
1st off thanks to the development team for the Marble release.

I installed it this morning and functionally, everything is good.
The only issue I've encountered so far is my storage/data partition not being mounted when I boot to recovery.

I have tried the wipe>advanced wipe>Data>repair file system fix suggested across the web and it fails out with an error message.

I have also tried deleting and readding my screen pin with same result.

TWRP is booting straight into its menu without asking for unlock code.

I'm guessing I will need to reformat and with that in mind, I just want to ask what's the preferred/best back up solution to ensure I get back up and running with nothing lost?

Thanks
 
The only issue I've encountered so far is my storage/data partition not being mounted when I boot to recovery.
That's TWRP issue. Check if there's newer TWRP for your device.
 
  • Like
Reactions: banie01
1st off thanks to the development team for the Marble release.

I installed it this morning and functionally, everything is good.
The only issue I've encountered so far is my storage/data partition not being mounted when I boot to recovery.

I have tried the wipe>advanced wipe>Data>repair file system fix suggested across the web and it fails out with an error message.

I have also tried deleting and readding my screen pin with same result.

TWRP is booting straight into its menu without asking for unlock code.

I'm guessing I will need to reformat and with that in mind, I just want to ask what's the preferred/best back up solution to ensure I get back up and running with nothing lost?

Thanks
Yes I think you are using old twrp. It happened to me too. Use the latest android 15 version
 
  • Like
Reactions: banie01
That's TWRP issue. Check if there's newer TWRP for your device.
Yes I think you are using old twrp. It happened to me too. Use the latest android 15 version
Thanks for the tips guys.
I've just tried flashing Orangefox TWRP via fastboot and it failed as its detectting the target volume as full.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (131072 KB)...
OKAY [ 3.773s]
writing 'recovery'...
FAILED (remote: Error flashing partition : Volume Full)
finished. total time: 3.796s

Any tips on what to try next will be much appreciated.
 

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
49K
Replies
51
Views
58K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
81K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
39K