HyperOS 1.0 HyperOS 1.0 STABLE RELEASE


dentistgev said:
Clean install, still doesn't work for me. Device Thor HyperOs 1.0.8.0. Shutting down or restarting, no any confirmation.
Click to expand...
Then read the description. "Require confirming screen lock if your device is powered off while locked".
Locked here means the device is on the lock screen + the lock screen has security applied.
 
  • Like
Reactions: banie01
Einar said:
Anyone updated Lisa to 1.0.6?
Went through the regular way line the updates before, installed fine, but went into some kind of bootloop. Pressing Power + Vol get's me into TWRP 3.7.0_A12 instead of HOS Recovery?!??
Click to expand...
Apply power down for fast boot. Power up for twrp. I always get it mixed up.
 
MiBoi9000 said:
Apply power down for fast boot. Power up for twrp. I always get it mixed up.
Click to expand...
Got me wrong, mate. The + didn't meant volume up, I know how to enter recovery/fastboot with the buttons.
What got me off is the fact, that I had TWRP on HOS. No custom recovery is working on Lisa with HOS, neither TWRP nor OF.
And since the phone got a bootloop I couldn't enter fastboot to re-install 1.0.5., vol up and vol down got me into TWRP.

In the end I made a sideload through TWRP and installed 1.0.6 again. Afterwards the recovery was again the usual of HOS, no TWRP available.

So no big deal at all, was just curious that a TWRP made for A12 was working ion a device with A14 installed.
 
Hello friends, I have a question, I believe it is simple for you who understand better. I'm using the latest version of the weekly beta, I'd like to know when it's worth switching to the "current" stable version. My question is more or less the following, which version would be more "up to date" than the beta, my cell phone is a Poco F4 GT, current stable version at 0.6, is it worth exchanging the latest beta for the current stable?
 
gogocar62 said:
I assume you know that this feature only works from the lock screen.
Click to expand...

Actually, it doesn't work for me either, unless I misunderstood what it is supposed to do.
I have the option of not showing the reboot/shut down nor the notification shade while on lock screen, so keeping the power pressed gives a short vibration, but does nothing.
Keeping it pressed for longer (like 10 seconds maybe?) it restarts the phone.
As I fear time will come when I will need my device to be forced off by keeping the power button pressed, I leave the option disabled, but, as already said, it doesn't seem to work (or maybe it actually does a slightly different thing?)

Edit: I'm on Ishtar, 1.0.16
 
Liiuknup said:
Hello friends, I have a question, I believe it is simple for you who understand better. I'm using the latest version of the weekly beta, I'd like to know when it's worth switching to the "current" stable version. My question is more or less the following, which version would be more "up to date" than the beta, my cell phone is a Poco F4 GT, current stable version at 0.6, is it worth exchanging the latest beta for the current stable?
Click to expand...
OS1.0.4.0 and later for Poco F4 GT (Ingres) is newer than the latest weekly rom.
As mentioned in the post
xiaomi.eu

HyperOS 1.0 - 24.7.28 (Final)

Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu xiaomi.eu
 
Last edited:
Schnapsbrenner said:
Did anybody ever try bluetooth connection to a Dual App? It worked on MiUI 13 on my Mi10Pro. The dual app was pokemon go, and there is a little catching bluetooth device, that the game itself is doing to pairing with (you don't pair it like a normal BT device in the BT menu). Now the dual app finds the device, but pairing just times out.
Don't even know, how I would log that to get any idea what's happening.
Click to expand...
I managed to get a log of the error:
"Error receiving broadcast intent"
a lot of "Unknown Source" and "Illegal state: own package not found"

That's what Xiaomi came up with by a pop-up saying the pogo app was crashing frequently (the app itself was running fine)

Can someone advise me how to properly trace the dual app connection. If it helps I could also trace a function connection attempt by the non-dual version.
 

Attachments

  • Screenshot_2024-10-15-11-42-06-006_com.miui.bugreport.jpg
    Screenshot_2024-10-15-11-42-06-006_com.miui.bugreport.jpg
    572.4 KB · Views: 186
  • Screenshot_2024-10-15-11-42-13-096_com.miui.bugreport.jpg
    Screenshot_2024-10-15-11-42-13-096_com.miui.bugreport.jpg
    499.1 KB · Views: 177
Last edited by a moderator:
Hi every one I'm encounter an issue in hyperos 1.0.16.0.UMACNXM (ishtar) when using a USB dac to 3.5 jack adapter and listening to music when i use the prev next buttons the screen turns on and when my Device is in pocket the prev button doesn't work at all, I've tested several adapters and always occurs when the adapter is recognized as USB DAC USB to 3.5 adapter, this happens in every music player not poweramp only, this doesn't happens with another adapter that is recognized as wired headphones/aux and works just fine the problems is that I need the usb dac to work normally
Maybe this can be fixed in hyperos 2 release
 

Attachments

  • Screenshot_2024-10-21-15-31-23-162_com.maxmpz.audioplayer.jpg
    Screenshot_2024-10-21-15-31-23-162_com.maxmpz.audioplayer.jpg
    158.4 KB · Views: 90
Last edited:
Original cable (and charger)?
And when you turn off screen and plug the charger in? What do you see then? Can be, when screen is on, the speed is lower to prevent heating?
 
Hello I can't add Widgets does anyone knows how to fix? Poco F3 here

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Click to expand...
 
Last edited by a moderator:
Not sure wether this is a Bug or not, so, sorry if I'm wrong, but the last Update for Houji (Xiaomi 14 Global) made my "SnowyMountain" super wallpaper stop working. However, if you deinstall the wallpaper and install an earlier version it's fixed again.

Don't know wether it has something to do with the wallpaper update or the last system update. Also I don't know wether this is good cause I know it's stated to not manually download official xiaomi apps since you guys mentioned that you modify them aswell.

Anyways, cheers
 
anybody test psyche 12x version 1.0.10 with Work Profile and Intune?

Does it fix the issue with Outlook and Teams (Work Profile) on 1.0.10 for 12x?

I need it for my work and it is a must-have function.

Appreciate your response.
 
Last edited:
gogocar62 said:
Try reinstalling the ROM via fastboot.
If you are using root and mods, remove them before installing the ROM.
Click to expand...
That was only solution. After reinstalling ROM to 1.0.6.0 everything works like it should. That is really strange.. Next time I will do full backup before update. I was not avare, that something like that can occure. It never happened to me before. It's another experience. Luckily I was able to backup all my data trough TWRP.
 
anybody test psyche 12x version 1.0.10 with Work Profile and Intune?

Does it fix the issue with Outlook and Teams (Work Profile) on 1.0.10 for 12x?

I need it for my work and it is a must-have function.

Appreciate your response.
 
Google app is permanently using my location. I already told the app to only use it when asking for location, but it still used this service. What I can do for it?
 
Hello, everyone.

I made a mistake when updating the ROM on my Xiaomi 12.

I had already updated my phone with the stable version. The updater kept saying that an update was available, but it never downloaded.

So I searched for the version number it was reporting (1.0.9) and believed that there would be no other ROM with the same version. I ended up finding this one: https://hyperosupdates.com/hyperos/cupid/version/OS1.0.13.0.ULCEUXM, which would be more up-to-date, by the way.

The update was done via FASTBOOT, but the device no longer started. So I went back to the stable version available here on the forum and the device started again, but extremely slowly and with some bugs. That's when I formatted the DATA partition, to try to get it back to normal. Almost everything went back to normal, but the camera, for example, no longer works.

I cleared CACHE and DALVIK, but it didn't work. What else can I try to do to fix this?
 
You must log in or register to reply here.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
952
Views
391K
HyperOS
PervizMikail
PervizMikail
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
340K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
45K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
44K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
54K
HyperOS
KGVER
KGVER
Top Bottom
Back