HyperOS 1.0 HyperOS 1.0 STABLE RELEASE

[fkin_lizard]

Hi there, I can note also on Aurora 1.0.9.0 high battery drain compared to 1.0.8.0.

 

[victor0801x]

@victor0801x could you revive your network?

Sent from my Mi 11 Ultra.

sadly no, I reset to default eventually

I tried to flash moden & modenfirwmare with TW version (original where I bought the phone) & global & china. none of them work

btw, have you tried flash without the SIM card inside?

 

[Karpfenhai]

sadly no, I reset to default eventually

I tried to flash moden & modenfirwmare with TW version (original where I bought the phone) & global & china. none of them work

btw, have you tried flash without the SIM card inside?

Not sure, but I'll try again later tonight, after reset it worked again I guess?

Sent from my Mi 11 Ultra.

 

[Sean Jee]

Flashed the hyperOS for Alioth a few days ago and all work very perfectly! Thanks a lot

 

[MiBoi9000]

Mi 11 5G speed 333mbps T-Mobile USA. 5G definitely working for sure. Too bad they took the bands out after Mi 12S Ultra.

 

[Jacometto]

I did a Clean Install of the latest HyperOS Stable for Poco F5 Pro (mondrian) and notice an issue.
When installing or updating in the Google Play Store the System UI or Home Screen' restarts and I have to insert my PIN again in the System Lock Screen.
How to handle it?

 

[Antidote03]

is there any way to add auto dark mode its missing in latest version of hyperOS
ROM : Xiaomi.eu
Device : POCO F5 (MARBLE)
VERSION : OS1.0.2.0.UMRCNXM_os1-14

 

[gogocar62]

If you mean to schedule "dark mode" for a specific time, you can create an automatic task.

app Security > automatic tasks > in the lower right corner click + > create the desired task

 

[Karpfenhai]

I managed to grad a full logcat this time from boot to system I see plenty of errors relates to user 0 locked and SELINUX, can someone with more insight have another look? I also tried flashing modem again w/o simcard to slot b etc, nothing helps, I think its probably just one adb command away from a solution ;(

Here are some suspicious lines:

04-26 13:07:08.680 2656 2656 I wificond: wificond is starting up...
04-26 13:07:08.685 2656 2656 E HidlServiceManagement: Service android.system.wifi.keystore@1.0::IKeystore/default must be in VINTF manifest in order to register/get.
04-26 13:07:08.685 2656 2656 I wificond: Did not register wifi keystore HIDL HAL service: -2147483648

going to add more findings..

04-26 13:07:17.509 6661 6661 E MQSEventManagerDelegate: failed to get MQSService. 04-26 13:07:17.509 6661 6661 W ActivityThread: registerApplicationScoutThread result:false 04-26 13:07:17.529 2233 2282 I WindowManager: wms.showSurfaceRobustly mWin:Window{ee6f85b u0 RoundCornerTop} 04-26 13:07:17.535 2233 2262 D CoreBackPreview: Window{74e36d4 u0 RoundCornerBottom}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@882e4fc, mPriority=0, mIsAnimationCallback=false} 04-26 13:07:17.537 2233 3967 I ActivityManager: Flag disabled. Ignoring finishAttachApplication from uid: 1001. pid: 6661 04-26 13:07:17.549 2233 2263 I StatusBarManagerService: registerStatusBar bar=com.android.internal.statusbar.IStatusBar$Stub$Proxy@64177e 04-26 13:07:17.550 2233 2282 I WindowManager: wms.showSurfaceRobustly mWin:Window{74e36d4 u0 RoundCornerBottom} 04-26 13:07:17.565 2233 3990 E NativeTombstoneManager: Tombstone's UID (1073) not an app, ignoring 04-26 13:07:17.566 2233 3990 E NativeTombstoneManager: Tombstone's UID (1073) not an app, ignoring 04-26 13:07:17.575 2233 5088 I ActivityManager: Process com.android.networkstack.process (pid 6531) has died: pers PER 04-26 13:07:17.575 2233 2233 E ConnectivityModuleConnector: Lost network stack. This is not the root cause of any issue, it is a side effect of a crash that happened earlier. Earlier logs should point to the actual issue. 04-26 13:07:17.576 2233 5088 W ActivityManager: Scheduling restart of crashed service com.android.networkstack/com.android.server.NetworkStackService in 0ms for persistent 04-26 13:07:17.576 2233 5088 W ActivityManager: Scheduling restart of crashed service com.android.networkstack.tethering/.TetheringService in 0ms for persistent 04-26 13:07:17.576 2233 2279 D DisplayManagerService: Drop pending events for gone uid 1073 04-26 13:07:17.576 2233 5088 W ActivityManager: Re-adding persistent process ProcessRecord{617cd51 6531:com.android.networkstack.process/1073} 04-26 13:07:17.577 2233 5088 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 1073; state: DISABLED 04-26 13:07:17.577 2233 5088 D CompatibilityChangeReporter: Compat change id reported: 177438394; UID 1073; state: DISABLED 04-26 13:07:17.577 2233 5088 D CompatibilityChangeReporter: Compat change id reported: 135772972; UID 1073; state: DISABLED 04-26 13:07:17.577 2233 5088 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 1073; state: ENABLED 04-26 13:07:17.577 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.585 2233 2339 I ActivityManager: Start proc 6716:com.android.networkstack.process/1073 for restart com.android.networkstack.process caller=android 04-26 13:07:17.585 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.604 2233 5088 I SmartPower: com.android.networkstack.process/1073(6716): died->background(29ms) R(process start ) adj=-10000. 04-26 13:07:17.604 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.606 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.607 6716 6716 E MQSEventManagerDelegate: failed to get MQSService. 04-26 13:07:17.607 6716 6716 W ActivityThread: registerApplicationScoutThread result:false 04-26 13:07:17.610 2233 5088 D CompatibilityChangeReporter: Compat change id reported: 182478738; UID 1000; state: ENABLED 04-26 13:07:17.628 2233 5088 I ActivityManager: Flag disabled. Ignoring finishAttachApplication from uid: 1073. pid: 6716 04-26 13:07:17.668 2233 3990 E NativeTombstoneManager: Tombstone has invalid selinux label (u:r:vendor_qtelephony:s0:c219,c256,c512,c768À€), ignoring 04-26 13:07:17.669 2233 3990 E NativeTombstoneManager: Tombstone has invalid selinux label (u:r:vendor_qtelephony:s0:c219,c256,c512,c768À€), ignoring 04-26 13:07:17.676 2233 3967 I ActivityManager: Process com.qti.phone (pid 6609) has died: pers PER 04-26 13:07:17.677 2233 3967 W ActivityManager: Scheduling restart of crashed service com.qti.phone/.ExtTelephonyService in 0ms for persistent 04-26 13:07:17.677 2233 3967 W ActivityManager: Scheduling restart of crashed service com.qualcomm.qcrilmsgtunnel/.QcrilMsgTunnelService in 0ms for persistent 04-26 13:07:17.678 2233 3967 W ActivityManager: Re-adding persistent process ProcessRecord{324da33 6609:com.qti.phone/u0a219} 04-26 13:07:17.678 2233 2279 D DisplayManagerService: Drop pending events for gone uid 10219 04-26 13:07:17.678 2233 3967 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10219; state: DISABLED 04-26 13:07:17.678 2233 3967 D CompatibilityChangeReporter: Compat change id reported: 177438394; UID 10219; state: DISABLED 04-26 13:07:17.678 2233 3967 D CompatibilityChangeReporter: Compat change id reported: 135772972; UID 10219; state: DISABLED 04-26 13:07:17.678 2233 3967 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10219; state: ENABLED 04-26 13:07:17.679 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.679 2233 2339 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10219; state: ENABLED 04-26 13:07:17.687 2233 2339 I ActivityManager: Start proc 6751:com.qti.phone/u0a219 for restart com.qti.phone caller=android 04-26 13:07:17.687 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.702 5499 5499 E FaceManager: No sensors 04-26 13:07:17.707 2233 3967 I SmartPower: com.qti.phone/10219(6751): died->background(30ms) R(process start ) adj=-10000. 04-26 13:07:17.707 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.709 2233 4644 W UsageStatsService: Failed to query usage stats for locked user 0 04-26 13:07:17.712 6751 6751 E MQSEventManagerDelegate: failed to get MQSService. 04-26 13:07:17.712 6751 6751 W ActivityThread: registerApplicationScoutThread result:false 04-26 13:07:17.743 2233 3966 I ActivityManager: Flag disabled. Ignoring finishAttachApplication from uid: 10219. pid: 6751 04-26 13:07:17.772 2233 2279 D MiuiScreenOnProximityLock: far from the screen for a certain time, release proximity sensor... 04-26 13:07:17.788 2233 3990 E NativeTombstoneManager: Tombstone's UID (1001) not an app, ignoring 04-26 13:07:17.792 2233 3990 E NativeTombstoneManager: Tombstone's UID (1001) not an app, ignoring 04-26 13:07:17.803 2233 2281 W DisplayManagerService: Failed to notify process 5476 that displays changed, assuming it died. 04-26 13:07:17.803 2233 2281 W DisplayManagerService: android.os.DeadObjectException 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.os.BinderProxy.transactNative(Native Method) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.os.BinderProxy.transact(Unknown Source:174) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.hardware.display.IDisplayManagerCallback$Stub$Proxy.onDisplayEvent(Unknown Source:23) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at com.android.server.display.DisplayManagerService$CallbackRecord.notifyDisplayEventAsync(Unknown Source:25) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at com.android.server.display.DisplayManagerService.deliverDisplayEvent(Unknown Source:179) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at com.android.server.display.DisplayManagerService.-$$Nest$mdeliverDisplayEvent(Unknown Source:0) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at com.android.server.display.DisplayManagerService$DisplayManagerHandler.handleMessage(Unknown Source:196) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.os.Handler.dispatchMessage(Unknown Source:19) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.os.Looper.loopOnce(Unknown Source:198) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.os.Looper.loop(Unknown Source:83) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at android.os.HandlerThread.run(Unknown Source:28) 04-26 13:07:17.803 2233 2281 W DisplayManagerService: at com.android.server.ServiceThread.run(Unknown Source:12) 04-26 13:07:17.804 2233 3967 I ActivityTaskManager: Config changes=20000500 {1.0 ?mcc0mnc [en_GB] ldltr sw411dp w411dp h825dp 560dpi nrml long hdr widecg port night finger -keyb/v/h -nav/h winConfig={ mBounds=Rect(0, 0 - 1440, 3200) mAppBounds=Rect(0, 147 - 1440, 3035) mMaxBounds=Rect(0, 0 - 1440, 3200) mDisplayRotation=ROTATION_0 mWindowingMode=fullscreen mDisplayWindowingMode=fullscreen mActivityType=undefined mAlwaysOnTop=undefined mRotation=ROTATION_0 mInSplitScreen=false letterBoxed=false foScaledfalse} s.12 fontWeightAdjustment=0/d/o themeChanged=0 themeChangedFlags=0 extraData = Bundle[{}] screenType=0} ImeAppBounds:null ;isMultiWindowMode:false 04-26 13:07:17.805 2233 5964 I ActivityManager: Process com.android.phone (pid 5476) has died: pers PER

Log is full with things like that..

After Boot we see this:


04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: Unable to read /sys/devices/platform/soc/soc:spf_core_platform/soc:spf_core_platform:lpass-cdc/wcd939x-codec/extcon/extcon3/cable.2/name. This probably means the selinux policies need to be changed.
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: java.io.FileNotFoundException: /sys/class/extcon/extcon3/cable.2/name: open failed: EACCES (Permission denied)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at libcore.io.IoBridge.open(IoBridge.java:574)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at java.io.FileInputStream.<init>(FileInputStream.java:160)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.FileUtils.readTextFile(Unknown Source:2)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.ExtconUEventObserver$ExtconInfo.<init>(Unknown Source:91)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.ExtconUEventObserver$ExtconInfo.initExtconInfos(Unknown Source:100)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.ExtconUEventObserver$ExtconInfo.getExtconInfoForTypes(Unknown Source:3)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.policy.PhoneWindowManager.initializeHdmiStateInternal(Unknown Source:158)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.policy.PhoneWindowManager.initializeHdmiState(Unknown Source:4)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.policy.PhoneWindowManager.init(Unknown Source:1117)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.policy.PhoneWindowManager.init(Unknown Source:5)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.policy.MiuiPhoneWindowManager.init(Unknown Source:0)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.wm.WindowManagerService$5.run(Unknown Source:21)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.Handler$BlockingRunnable.run(Unknown Source:3)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.Handler.handleCallback(Unknown Source:2)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.Handler.dispatchMessage(Unknown Source:4)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.Looper.loopOnce(Unknown Source:198)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.Looper.loop(Unknown Source:83)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.HandlerThread.run(Unknown Source:28)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.ServiceThread.run(Unknown Source:12)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at com.android.server.UiThread.run(Unknown Source:8)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: Caused by: android.system.ErrnoException: open failed: EACCES (Permission denied)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at libcore.io.Linux.open(Native Method)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at libcore.io.IoBridge.open(IoBridge.java:560)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: ... 19 more
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: Unable to read /sys/devices/platform/soc/soc:spf_core_platform/soc:spf_core_platform:lpass-cdc/wcd939x-codec/extcon/extcon3/cable.0/name. This probably means the selinux policies need to be changed.
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: java.io.FileNotFoundException: /sys/class/extcon/extcon3/cable.0/name: open failed: EACCES (Permission denied)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at libcore.io.IoBridge.open(IoBridge.java:574)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at java.io.FileInputStream.<init>(FileInputStream.java:160)
04-26 13:07:24.955 8235 8256 W ExtconUEventObserver: at android.os.FileUtils.readTextFile(Unknown Source:2)


Wifi wont work because of:


04-26 13:07:25.728 8235 8235 D SystemServerTiming: StartPermissionPolicyService
04-26 13:07:25.728 8235 8235 I SystemServiceManager: Starting com.android.server.policy.PermissionPolicyService
04-26 13:07:25.730 8235 8539 W BroadcastLoopers: Found previously unknown looper Thread[WifiHandlerThread,5,main]
04-26 13:07:25.735 8235 8235 D SystemServerTiming: MakePackageManagerServiceReady
04-26 13:07:25.745 1516 1572 E android.hardware.wifi-service: Failed to open directory: Permission denied
04-26 13:07:25.745 1516 1572 E android.hardware.wifi-service: Error occurred while deleting old tombstone files
04-26 13:07:25.745 1516 1572 E android.hardware.wifi-service: Error writing files to flash
04-26 13:07:25.745 1516 1572 D android.hardware.wifi-service: Stopping legacy HAL
04-26 13:07:25.746 1516 5717 I android.hardware.wifi-service: Legacy HAL stop complete callback received
04-26 13:07:25.747 8235 8235 I PermissionManager: Permission ownership changed. Updating all permissions.
04-26 13:07:25.801 1516 5717 D android.hardware.wifi-service: Legacy HAL event loop terminated
04-26 13:07:25.802 1516 1572 D android.hardware.wifi-service: Legacy HAL stop complete
04-26 13:07:25.802 1516 1572 I android.hardware.wifi-service: Wifi HAL stopped
04-26 13:07:25.803 1516 1572 W android.hardware.wifi-service: Duplicate death notification registration
04-26 13:07:25.812 8235 8539 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
04-26 13:07:25.872 8235 8299 E DefaultPermGrantPolicy: Package not found: com.google.android.apps.assistant
04-26 13:07:25.872 8235 8299 E DefaultPermGrantPolicy: Package not found: com.google.android.apps.actionsservice
04-26 13:07:25.874 1516 1572 D android.hardware.wifi-service: Initialize legacy HAL
04-26 13:07:25.874 1516 1572 I android.hardware.wifi-service: Wifi HAL started
04-26 13:07:25.875 1516 1572 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
04-26 13:07:25.875 1516 1572 E android.hardware.wifi-service: Unknown iface name: wlan0
04-26 13:07:25.875 1516 1572 E android.hardware.wifi-service: Unknown iface name: wlan0
04-26 13:07:25.877 1516 1572 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
04-26 13:07:25.877 1516 1572 E android.hardware.wifi-service: Unknown iface name: wlan0
04-26 13:07:25.877 1516 1572 E android.hardware.wifi-service: Unknown iface name: wlan0
04-26 13:07:25.877 8235 8235 D SystemServerTiming: MakeDisplayManagerServiceReady
04-26 13:07:25.877 1516 1572 D android.hardware.wifi-service: Waiting for the driver ready
04-26 13:07:25.878 8235 8318 W PackageManager: Not removing package com.google.android.trichromelibrary.beta hosting lib com.google.android.trichromelibrary.beta version 642200333 used by [VersionedPackage[com.chrome.beta/642200333]] for user 0
04-26 13:07:25.878 8235 8258 E DisplayModeDirector: Asked about unknown display, returning empty display mode specs!(id=0)
04-26 13:07:25.878 8235 8318 W PackageManager: Not removing package com.google.android.trichromelibrary hosting lib com.google.android.trichromelibrary version 631209933 used by [VersionedPackage[com.google.android.webview/631209933]] for user 0
04-26 13:07:25.878 8235 8258 E DisplayModeDirector: Asked about unknown display, returning empty display mode specs!(id=0)
04-26 13:07:25.878 8235 8318 W PackageManager: Not removing package com.google.android.trichromelibrary hosting lib com.google.android.trichromelibrary version 636705433 used by [VersionedPackage[com.android.chrome/636705433]] for user 0
04-26 13:07:25.880 1516 1572 D android.hardware.wifi-service: Starting legacy HAL
04-26 13:07:25.881 8235 8258 I DisplayModeDirectorImpl: onDesiredDisplayModeSpecsChanged:baseModeId=2 allowGroupSwitching=false primary=physical: (0.0 Infinity) render: (0.0 120.0) appRequest=physical: (0.0 Infinity) render: (0.0 120.0) noVotes=false
04-26 13:07:25.882 1516 8924 D android.hardware.wifi-service: Starting legacy HAL event loop
04-26 13:07:25.882 1516 1572 I android.hardware.wifi-service: Adding interface handle for p2p0
04-26 13:07:25.882 1516 1572 I android.hardware.wifi-service: Adding interface handle for wlan0
04-26 13:07:25.882 1516 1572 I android.hardware.wifi-service: Adding interface handle for wifi-aware0
04-26 13:07:25.882 1516 1572 D android.hardware.wifi-service: Legacy HAL start complete
04-26 13:07:25.882 1516 1572 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
04-26 13:07:25.882 1516 1572 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
04-26 13:07:25.882 8235 8235 I BrightnessSynchronizer: Initial brightness readings: 29(int), 0.10831682(float)
04-26 13:07:25.883 1516 1572 I android.hardware.wifi-service: Configured chip in mode 3
04-26 13:07:25.883 1516 1572 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
04-26 13:07:25.883 8235 8235 D SystemServerTiming: StartDeviceSpecificServices
04-26 13:07:25.883 8235 8235 D SystemServerTiming: StartDeviceSpecificServices com.miui.me.server.auto_install.InstallService
04-26 13:07:25.883 8235 8235 I SystemServiceManager: Starting com.miui.me.server.auto_install.InstallService
04-26 13:07:25.884 8235 8235 D SystemServerTiming: GameManagerService
04-26 13:07:25.884 8235 8235 I SystemServiceManager: Starting com.android.server.app.GameManagerService$Lifecycle
04-26 13:07:25.884 1516 1572 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
04-26 13:07:25.884 8235 8235 D PreCacheUtilStubImpl: registerContentObserver
04-26 13:07:25.884 8235 8235 D GameManagerServiceStub: downscale register
04-26 13:07:25.885 1516 1572 I android.hardware.wifi-service: Adding interface handle for p2p0
04-26 13:07:25.885 1516 1572 I android.hardware.wifi-service: Adding interface handle for wlan0
04-26 13:07:25.885 1516 1572 I android.hardware.wifi-service: Adding interface handle for wifi-aware0
04-26 13:07:25.887 1516 1572 E android.hardware.wifi-service: Failed to get chip capabilities from legacy HAL: NOT_SUPPORTED


Conclusion, the network stack is dying:

04-26 13:07:32.743 8235 10898 I SmartPower: com.android.networkstack.process/1073(11556): died->background(38ms) R(process start ) adj=-10000.

Phone is dying, Dataservice and wlan are dying, possible reason User 0 is locked.

04-26 13:07:40.368 8235 10096 I SmartPower: .qtidataservices/10104(14040): died->background(39ms) R(process start ) adj=-10000.
04-26 13:07:40.368 8235 8715 W UsageStatsService: Failed to query usage stats for locked user 0
04-26 13:07:40.371 8235 8715 W UsageStatsService: Failed to query usage stats for locked user 0
04-26 13:07:40.372 14040 14040 E MQSEventManagerDelegate: failed to get MQSService.

MQS Service not responsive, whatever that means.

User 0 issue couls also explain why i cant no longer open developer options ;(

The Question is why...

I hope someone can help / assist.

please remove .zip from filename and use 7zip to unpack, thx!

Thx in advance!

 

[Konfetti030]

The system launcher is what uses all the battery power. Also mine is locked at 120fps. I toggle between 60hz and 120hz and now it is acting better. Drops to 60fps after some delay.

I also want to upgrade from MIUI 14 to HyperOS but the battery drain is holding me back.
I am using a 3rd party launcher. So do you think I won't be facing this drain?

Mi 11 Pro

 

[Silvio1953]

I also want to upgrade from MIUI 14 to HyperOS but the battery drain is holding me back.
I am using a 3rd party launcher. So do you think I won't be facing this drain?

Mi 11 Pro

I have HyperOseu on Redwood and the battery is awesome, 10-11 hours of SOT (no game). I use Nova launcher

 

[Supermechf]

Just found out that there's no Sapphire download on the website. Only Sapphiren. Am I blind or has this been reported before?

 

[snow1]

I also want to upgrade from MIUI 14 to HyperOS but the battery drain is holding me back.
I am using a 3rd party launcher. So do you think I won't be facing this drain?

Mi 11 Pro

Mi 11 here I tested nova launcher made no difference still same high battery drain

 

[gogocar62]

Just found out that there's no Sapphire download on the website. Only Sapphiren. Am I blind or has this been reported before?

See the table in the first post of this thread.
Sapphiren ROM is shared by Sapphiren and Sapphire.

 

[tarkan37]

Hi guys, even with a format data, the battery drain, hope that future update will be better and will resolve the drain problem

 

[Supermechf]

Sapphiren ROM is shared by Sapphiren and Sapphire.

Oh, sorry. Many thanks then.

 

[victor0801x]

Not sure, but I'll try again later tonight, after reset it worked again I guess?

Sent from my Mi 11 Ultra.

yep, reset to default work again.

not sure related or not (2 major changes/improvements might not be compatible with the global version
in 1.0.9 release note (china version)
System

• New: Tiantong Satellite communications
• New: 5G-A capabilities for better 5G connectivity (available when provided by your carrier)
• Updated the security patch to April 2024. Increased system security

global version does not have Satellite communications capability.

 

[pajser92]

I saw on Reddit that HyperOS is now available for Poco F3 (alioth). Does that mean it will soon be available here as well?

 

[snow1]

I saw on Reddit that HyperOS is now available for Poco F3 (alioth). Does that mean it will soon be available here as well?

It's already available look at the first page

 

[MiBoi9000]

I also want to upgrade from MIUI 14 to HyperOS but the battery drain is holding me back.
I am using a 3rd party launcher. So do you think I won't be facing this drain?

Mi 11 Pro

Use Microsoft Launcher very nice. So far work ok.

 

[pajser92]

It's already available look at the first page

Jesus I looked at the table and for some reason looked for F3 somewhere in the middle, completely missed the very first row. Thanks!

 

[MiBoi9000]

Mi 11 here I tested nova launcher made no difference still same high battery drain

Same I tried Microsoft Launcher, still uses 18% per hour of SOT. So 5 hours SOT is 3500mAh for me. I have new battery in mail. Should be 4500mAh new.

 

[xMarvin732]

An update has been released for Xiaomi 11T Pro (vili), to HyperOS.

we will get HyperOS Xiaomi.EU as soon as UKDMIXM released.
"sadly" the mi pilot is UKDEUXM
Xiaomi.EU only uses MIXM or CNXM roms

 

[joseph-veux*user]

Deleted

 

[GodSir]

xiaomi.eu_multi_UNICORN_OS1.0.4.0.ULECNXM_os1-14 not work in magisk_patched boot.img, who worked boot magisk_patched file?