HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Yes, with the last version (101) for vermeer the errors stop with mi-connect. All good now and the safety date is 1-1-25. Will check the battery life now for some days.
 
LucasFC said:
be able to log in to the part where it asks you to block by pin and just skip the option
Click to expand...
I don't even see this option, I confirm the phone number and I get the message that the app isn't official.
 

Attachments

  • Screenshot_2025-01-08-13-25-40-111_com.whatsapp.jpg
    Screenshot_2025-01-08-13-25-40-111_com.whatsapp.jpg
    323.6 KB · Views: 133
  • Like
Reactions: Pakino2004
groxFR said:
Yes, with the last version (101) for vermeer the errors stop with mi-connect. All good now and the safety date is 1-1-25. Will check the battery life now for some days.
Click to expand...
Yes, but mi connect is still searching for devices in background even when turned off, and it is draining battery
 
Last edited:
heryssrique said:
I'm having the same problem with Whatsapp
Click to expand...
Are you rooted. maybe changes in the builtprop like the name of the phone itself gonna help. I'm not rooted because of a failure with twrp. Mine is not touchresponsive. Never worked with my phone. Doesn't matter which kind of twrp. I don't no why...
 
Pakino2004 said:
Are you rooted. maybe changes in the builtprop like the name of the phone itself gonna help. I'm not rooted because of a failure with twrp. Mine is not touchresponsive. Never worked with my phone. Doesn't matter which kind of twrp. I don't no why...
Click to expand...
I'm not rooted, I did a clean installation without root
 
groxFR said:
Ok, didn't know this..
Can you tell me how to stop mi-connect or even delete it?
Click to expand...
Remove with exa system app remover

Disable with ice box or hail



I choose to disable it, because you never know with system apps

There is also problem with Interconectivity system app
You can check in settings>notifications>history
 
  • Like
Reactions: groxFR
ptkruz said:
Just upgraded Peridot to 2.0.6, everything ok. Just have one problem that has been around for years: the games are at 60hz. Searched a lot online, and the only solution is to wipe data of "battery and performance". Is there any other workaround to make it permantly stick to 120hz? Didn't have this problem on global ROM btw. Thank you for the constant updates!
Click to expand...
Does anybody know anything about this? Thanks
 
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
 
punk0437 said:
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
Click to expand...
After booting, wait for a while, then have someone call your phone. This might help in completing the boot process.
Although the phone has likely already finished booting, the screen might be stuck due to some bugs. If you connect your phone to a computer and run ADB commands, it works, indicating that the booting is complete.
Some overlay actions like an alarm or phone call might help getting out of the infinite boot screen as I tested.
 
  • Like
Reactions: floyd168
punk0437 said:
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
Click to expand...
JisungKim said:
After booting, wait for a while, then have someone call your phone. This might help in completing the boot process.
Although the phone has likely already finished booting, the screen might be stuck due to some bugs. If you connect your phone to a computer and run ADB commands, it works, indicating that the booting is complete.
Some overlay actions like an alarm or phone call might help getting out of the infinite boot screen as I tested.
Click to expand...
Make a log guys.
xiaomi.eu

Logging with ADB Logcat

Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...
xiaomi.eu xiaomi.eu
 
  • Like
Reactions: katerpanne and banie01
Igor Eisberg said:
Make a log guys.
xiaomi.eu

Logging with ADB Logcat

Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...
xiaomi.eu xiaomi.eu
Click to expand...
I flashed back to HO1 enabled adb and flashed HO2 over TWRP.
Here is the log
I waited 10 minutes with the boot logo.

Thank you
 
  • Like
Reactions: Igor Eisberg
mattzildjian said:
Theres an option within developer options
"Disable default frame rate for games - Disable limiting the maximum frame rate for games at 60hz"

Have you tried this?
Click to expand...
Thanks for the reply, never tried that. Now tried this for 1 day and all the games are still stuck at 60hz... It's so annoying
 
punk0437 said:
I updated my TWRP to A15 and flashed the HyperOS 2.0 rom 12S Pro (unicorn).
I got a lot of "skip copying super image avb footer due to sparse image" errors and my phone only shows Xiaomi HyperOS. I tried to flash the rom via windows and over TWRP.
Anyone an idea how to fix it ?

Thank you
Click to expand...
Same problem，stuck on boot logo，now flashed back to old rom
 
I bought the Poco F6 a few days ago and since I've been using Xiaomi devices for over 9 years, I unlocked the bootloader straight away.

My question at this point is whether it would be better to flash "xiaomi.eu_PERIDOT_OS2.0.4.0.VNPCNXM_15" because of the "Wi-Fi Battery Drain Bug" in the latest version, or should I rather flash the current "xiaomi.eu_PERIDOT_OS2.0.6.0.VNPCNXM_15" despite the bug?

I would like to thank you at this point for your help.
 
You must log in or register to reply here.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
374K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
45K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
49K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
60K
HyperOS
KGVER
KGVER
ingbrzy
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
35K
HyperOS
emre_66
E
Top Bottom
Back