Xiaomi Support Thread

dhj49er

Well-known member
I am using the latest MD 5.52.5 from the Google Play Store.
I am using the latest 2.0.101.0 from HyperOS.
Poco X7 Pro has been on HyperOS 2.0 since purchase and will not work over time.

It works fine immediately after restarting the smartphone, but after 10 to 20 hours of
restarting, the {battery} value is no longer updated.
Charging and Discharging statuses will also stop updating.

I believe this is similar to what is posted in #194, #181, #180, and #179 of this thread.
I believe the problem is caused by a combination of HyperOS 2.0 and MD.

The app Device Info HW shows the wrong value as well as MD 5.52.5 when I check the battery status after starting the app, but it changes to the correct value after about 2 seconds.
Also, Battery Guru works fine.
So I am wondering if this is a problem that can be corrected on the MD side?

If v5.53 will be released after April 21 after the developer's vacation, I would like to try it.
5.53.11 is available from the Play store
 

SiElyes

New member
Not sure if this is a bug, but Macrodroid appears to be capped at 90fps on my Xiaomi 14 and dips to 60fps when scrolling. Could it be due to me having over 100 macros? Can anyone else test it out? (You can enable the refresh rate overlay in the developper settings).
 

4896

New member
Current battery percentage and power connect triggers not working on Redmi Note 13 Pro+ running Xiaomi HyperOS 2.0.x.0

The Current Battery Percentage i.e. {battery} is no longer working in Macrodoid Version 5.51 on Xiaomi HyperOS 2.0.6.0 (Redmi Note 13 Pro+ 5G). The Power Connect/Disconnect triggers are also not working. Connect is always false and Disconnect is always true even with a charger connected. Strangely enough, sometimes if I reset my phone, everything works again for around 12/24 hours and then {battery} gets stuck at 53% and the Power Connect trigger no longer fires. Even killing and restarting Macrodroid does not resolve the issue. Works fine on previous HyperOS 1.0.x.0 version on MacroDroid 5.51; Automate 1.45.1 also returns correct battery percentage levels.

Hoping someone is able to provide a fix for this. Thank you.
I am happy to report that upgrading to 5.53.11 (as suggested by dhj49er) fixes the {battery} problem I've been seeing (thank you MD developersand and dhj49er!) However, the Power Connected action and constraint functions still always returns false even with a charger connected. The Power Connected and Power Disconnected triggers are all working. Hoping this will be fix in the next release - many thanks.
 

Shiffo

Active member
I am happy to report that upgrading to 5.53.11 (as suggested by dhj49er) fixes the {battery} problem I've been seeing (thank you MD developersand and dhj49er!) However, the Power Connected action and constraint functions still always returns false even with a charger connected. The Power Connected and Power Disconnected triggers are all working. Hoping this will be fix in the next release - many thanks.
Did you submit a bug report through the troubleshooting section of the app?
 

dhj49er

Well-known member
I am happy to report that upgrading to 5.53.11 (as suggested by dhj49er) fixes the {battery} problem I've been seeing (thank you MD developersand and dhj49er!) However, the Power Connected action and constraint functions still always returns false even with a charger connected. The Power Connected and Power Disconnected triggers are all working. Hoping this will be fix in the next release - many thanks.
Where are the Power Connected actions?

I've looked and couldn't find any such actions.
 

4896

New member
Where are the Power Connected actions?

I've looked and couldn't find any such actions.
Apologies for the late reply.

The Power Connected condition or "function" is actually a "...condition to be satisfied in order to run the actions within an <If clause> action". I should have used the term, Power Connected condition instead of action as in my previous post - sorry for the confusion. Anyway, it can be accessed as follows:

Add action -> Conditions/Loops -> If clause -> [ADD CONDITION] -> Battery/Power -> Power Connected

Similarly to use it as a constraint for an action:

Add constraint -> Battery/Power -> Power Connected

Hope that helps.
 
Last edited:

sofofiwa

New member
5.53.11 is available from the Play store
I have updated my MD to 5.53.18 from the Google Play Store.
Like 4896, the power connection is always False in POCO X7 PRO under Triggers→Power Connected→Any.
{battery} is now fixed and returns normal values.
 

4896

New member
I have updated my MD to 5.53.18 from the Google Play Store.
Like 4896, the power connection is always False in POCO X7 PRO under Triggers→Power Connected→Any.
{battery} is now fixed and returns normal values.
Like you, I have just updated MD to 5.53.18 only yesterday - my preliminary testing shows that the Power Connected condition is working fine on my Redmi Note 13 Pro+. The only difference is that I updated my MD though the Beta channel and not from the Play Store.
 
Last edited:

sofofiwa

New member
Like you, I have just updated MD to 5.53.18 only yesterday - my preliminary testing shows that the Power Connected condition is working fine on my Redmi Note 13 Pro+. The only difference is that I updated my MD though the Beta channel and not from the Play Store.
The previous version also works fine immediately after rebooting the smartphone, but 10-20 hours after rebooting, the charging/discharging status is also not updated.
I did not reboot after updating MD to 5.53.18. I have rebooted and will report back tomorrow.
 

4896

New member
The previous version also works fine immediately after rebooting the smartphone, but 10-20 hours after rebooting, the charging/discharging status is also not updated.
I did not reboot after updating MD to 5.53.18. I have rebooted and will report back tomorrow.
I also did not reboot my phone after updating to 5.53.18 - and I will also keep an eye out to see if eveyrhing still works tomorrow. Fingers crossed!
 

sofofiwa

New member
I also did not reboot my phone after updating to 5.53.18 - and I will also keep an eye out to see if eveyrhing still works tomorrow. Fingers crossed!
I have booted up my smart phone after shutting it down and it has worked fine for over 24 hours.
Thanks dhj49er and 4896!
 

4896

New member
I have booted up my smart phone after shutting it down and it has worked fine for over 24 hours.
Thanks dhj49er and
Glad to hear that everything is good for you, sofofiwa. It has been over 72 hours since I'd updated to MD 5.53.18 and the Power Connected condition is still working well for me too. Hope it continues that way!
 

sofofiwa

New member
Android uptime was no longer working properly at 1days 19 hours.😭
 

Attachments

  • Screenshot_2025-05-08-20-08-20-253_com.arlosoft.macrodroid.jpg
    Screenshot_2025-05-08-20-08-20-253_com.arlosoft.macrodroid.jpg
    325.1 KB · Views: 6

4896

New member
Android uptime was no longer working properly at 1days 19 hours.😭
Hello sofofiwa,

Sorry to hear that it is still not working for you but no worries; I may have a solution which might bring back the smile to your face. I have been using this workaround/fix right up until I installed 5.53.18. Just follow these steps:

1. Remove the Power Connected constraint in your Battery Level trigger
2. Add this instead -> Add constraint -> Macrodroid Specific -> Compare Values
3. Assign type to Decimal
4. Assign {battery_current_now} to Value 1
5. Select < (less than) as operator
6 Assign 0 to Value 2
7. Click OK and save the changes

Clipboard_05-09-2025_01.jpg

Some explanation : {battery_current_now} is the value of the current the phone battery supplies or receives. It always return a negative value when the battery is receiving charge; otherwise, current flow will be positive when the battery is supplying charge to the phone. So, if the current value is below zero (i.e. a negative value) we can logically and safely assume that the phone is connected to the charger (i.e. same like the Power Connected condition or constraint). Thank goodness that MD has the {battery_current_flow} magic text and it is totally working fine in MD.

Let me know how it works out for you.
 

sofofiwa

New member
Hello sofofiwa,

Sorry to hear that it is still not working for you but no worries; I may have a solution which might bring back the smile to your face. I have been using this workaround/fix right up until I installed 5.53.18. Just follow these steps:

1. Remove the Power Connected constraint in your Battery Level trigger
2. Add this instead -> Add constraint -> Macrodroid Specific -> Compare Values
3. Assign type to Decimal
4. Assign {battery_current_now} to Value 1
5. Select < (less than) as operator
6 Assign 0 to Value 2
7. Click OK and save the changes

Some explanation : {battery_current_now} is the value of the current the phone battery supplies or receives. It always return a negative value when the battery is receiving charge; otherwise, current flow will be positive when the battery is supplying charge to the phone. So, if the current value is below zero (i.e. a negative value) we can logically and safely assume that the phone is connected to the charger (i.e. same like the Power Connected condition or constraint). Thank goodness that MD has the {battery_current_flow} magic text and it is totally working fine in MD.

Let me know how it works out for you.
Hello 4896,

Thanks for your good ideas.
I was able to do it successfully using {battery_current_now}.
 

4896

New member
Hello 4896,

Thanks for your good ideas.
I was able to do it successfully using {battery_current_now}.
No worries and happy to hear that the workaround is working for you. Hope that will keep you going until MD releases a new version to fix the issue.
 
Top