HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Can i upgrade from weekly 1.0.24.7.28 to stable 2.0.6.0 without data loss? If no which steps should I follow? Since 1.0.7.0 is not exist anymore I don't know how to do without data loss.
You can upgrade without data loss as stated in opening post if you read it carefully. 1.0.7.0 was the minimum version that could be used.

And don't ask are you sure...
 
  • Like
Reactions: fikide
Xiaomi.eu Still has the weather forecast after the alarm in the morning? The last version i used was miui 14.0.9 on my redmi note 10 pro. Im gonna unlock my xiaomi 14 bootloader within a week, and i love that function and I am interested if its still in the rom?
 
Yes, with root everything is possible. I have it like this but you need a valid keybox
Root is no option for me. Valid keynote neither. Locking the bootloader would hinder further updates here. So no interconnectivity between devices I guess. What a pity.
 
  • Like
Reactions: Pelayo
There are 3 modem files in latest xuanyuan Rom. Does the script decide which one to install or we can chose? The reason I am asking is that I have high battery discharge with latest rom. Is it possible that modem is responsible for high battery drain?

Also, since my trip to China last month, some apps not working anymore and some apps show notification with wrong time (China time zone). I tried everything and I cant get them to work. Apps are stuck on loading screen.
 
There are 3 modem files in latest xuanyuan Rom. Does the script decide which one to install or we can chose? The reason I am asking is that I have high battery discharge with latest rom. Is it possible that modem is responsible for high battery drain?

Also, since my trip to China last month, some apps not working anymore and some apps show notification with wrong time (China time zone). I tried everything and I cant get them to work. Apps are stuck on loading screen.
No, don't touch what you clearly don't understand.
 
How can i completely remove the watermark from the MiCamera? I can't uncheck both options :( i have to keep at least one of them :(
 
I was able to sort this out by extracting the MiMediaEditor.apk from the XUANYUAN ROM and installing it manually.
That's great that you've managed to do that, but how can I do it? Maybe a version will be available soon where it works again. It's been more than a month since the last update.
 
Hello everyone, will there be a new version for the Xiaomi 15(dada) soon? I'm on the current version and can't use any AI stuff and the Gallery Editor doesn't work.
Do you use an alternative DNS services or VPN (pihole etc..) If yes disable it, ive also a DADA with 116 installed. everyting is okay ( T-mobile.de..)
 
  • Like
Reactions: Pelayo
The issue we fixed was with AI features in normal gallery editor, for images.
What is "the beautify option in the video editing section of the Gallery application"?
EDIT: I see, it's only available for specific devices. Tried it on my POCO X7 Pro and it also crashes, but it has nothing to do with the issue we fixed.
In fact, it's not our issue at all. The libraries provided from Xiaomi's cloud server are causing the crash.

Also, I don't know what you mean by "the gallery app is still an old version", 4.2.0.15-global is the latest Global Gallery app.
Hi @Igor Eisberg,

I am also experiencing this issue and decided to investigate. So, I found out that the issue is this.

Code:
NativeLog@release-dev2.25.3.28:  BeautyWapper [/Users/xingdaming/AndroidStudioProjects/VideoSDK/videosdk/src/main/cpp/modules/plugin/beauty/BeautyWapper.cpp](18) dlopen get error: dlopen failed: library "/product/app/MiMediaEditor/lib/arm64/libFaceBeautyWrapper.so" not found

And upon checking, the issue is not from Xiaomi but from your end. The problem is that you made MiMediaEditor a system app. That app is meant to be a data app only as data apps have a behavior to extract their library outside the APK whenever you install it. But this does not happen to a system app. So, that CPP function could not find the library file as it is still inside the APK.

I modified my copy of the xiaomi.eu ROM and I was able to fix this by moving MiMediaEditor to product_a/product/data-app. If you want to really make MiMediaEditor a system app for some reason then you can still fix this by extracting the lib folder outside the APK and rename arm64-v8 folder to arm64.
 
Sounds like related to this:
I initially thought it was just a ROM version issue, until I just updated to 2.0.112 (shennong) and still encountered the problem of reboot twice. I came back to the forum and searched again and found that it was just as you said.After executing the ADB command,It can boot normally.

thank you a lot!
 
Hi @Igor Eisberg,

I am also experiencing this issue and decided to investigate. So, I found out that the issue is this.

Code:
NativeLog@release-dev2.25.3.28:  BeautyWapper [/Users/xingdaming/AndroidStudioProjects/VideoSDK/videosdk/src/main/cpp/modules/plugin/beauty/BeautyWapper.cpp](18) dlopen get error: dlopen failed: library "/product/app/MiMediaEditor/lib/arm64/libFaceBeautyWrapper.so" not found

And upon checking, the issue is not from Xiaomi but from your end. The problem is that you made MiMediaEditor a system app. That app is meant to be a data app only as data apps have a behavior to extract their library outside the APK whenever you install it. But this does not happen to a system app. So, that CPP function could not find the library file as it is still inside the APK.

I modified my copy of the xiaomi.eu ROM and I was able to fix this by moving MiMediaEditor to product_a/product/data-app. If you want to really make MiMediaEditor a system app for some reason then you can still fix this by extracting the lib folder outside the APK and rename arm64-v8 folder to arm64.
Normally system apps load native libs directly from the APK, but they implemented it poorly so it's looking for it in nativeLibraryDir (/product/app/MiMediaEditor/lib/arm64/libFaceBeautyWrapper.so) instead of letting Android resolve the correct path automatically (which then would be /product/app/MiMediaEditor/MiMediaEditor.apk!/lib/arm64-v8a/libFaceBeautyWrapper.so).
There's an easy fix for that, will take care of it. It doesn't have to be a data app.

EDIT: Should be fixed in DADA OS2.0.118.0.VOCCNXM.
 
Last edited:
Normally system apps load native libs directly from the APK, but they implemented it poorly so it's looking for it in nativeLibraryDir (/product/app/MiMediaEditor/lib/arm64/libFaceBeautyWrapper.so) instead of letting Android resolve the correct path automatically (which then would be /product/app/MiMediaEditor/MiMediaEditor.apk!/lib/arm64-v8a/libFaceBeautyWrapper.so).
There's an easy fix for that, will take care of it. It doesn't have to be a data app.

EDIT: Should be fixed in DADA OS2.0.118.0.VOCCNXM.
Thank you very much for the thorough explanation Igor! I learned something new again. And another thank you for the DADA update
 
Normally system apps load native libs directly from the APK, but they implemented it poorly so it's looking for it in nativeLibraryDir (/product/app/MiMediaEditor/lib/arm64/libFaceBeautyWrapper.so) instead of letting Android resolve the correct path automatically (which then would be /product/app/MiMediaEditor/MiMediaEditor.apk!/lib/arm64-v8a/libFaceBeautyWrapper.so).
There's an easy fix for that, will take care of it. It doesn't have to be a data app.

EDIT: Should be fixed in DADA OS2.0.118.0.VOCCNXM.
When will the same fix be released for Xiaomi 15 Ultra Xianyuan?
 
  • Angry
Reactions: NXTwoThou
I noticed significant heating on my 15U ROM 2.0.122.0 after about twenty minutes on PVZ 1.

Has anyone else observed this problem?
 
  • Like
Reactions: amibumping
I have not noticed that behaviour. But I have a different way of opening my phone:
I have Settings / Lock screen / Raise to wake switched on and also Settings / Fingerprints, face data, and screen lock / Face unlock activiated. I also have Stay on lock screen after unlocking switched off. That means that when I pick up the phone and look at it, it automatically switches on and unlocks.

If the light it bad, or for some reason it does not recognise me (!), which is quite rare, I then use the finigerprint unlock. If for whatever reason that does not work, I then use my gesture unlock. If you put Battery saver on, you may have to re-check some of the above settings.
As i edited my oryginal post .... All gone after clean downgrade to MiUi 14 (14.0.28.0 EU)
 

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
52K
Replies
51
Views
66K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
99K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
42K