MacroDroid can't change battery settings and other similar settings but SetEdit SettingsDatabaseEditor can

[Creeper]

As the title says, can someone please explain to me why MacroDroid can't change battery/power saver and other similar settings while SetEdit SettingsDatabaseEditor from Play Store can change it without any ADB hack or root?

MacroDroid has 108 permissions
SetEdit has only 4 permissions (screenshots added)

I am trying to create a battery saver macro so when I go to bed it turns on battery saver mode but the "Action Trigger" in MacroDroid doesn't do anything, and while some settings like brightness works from the System Table, not all of them works with MacroDroid. I have even tried with the MacoDroid Helper App.

SetEdit SettingsDatabaseEditor on the other hand works flawlessly without any ADB hack or root and can change any settings under the System Table and only requires the ADB hack when I want to change from the Secure or Global Table.

Can the developer please look into this issue? It looks like a problem with MacroDroid to me, not having proper permissions.

The post below may no longer apply since it's working with SetEdit SettingsDatabaseEditor

Battery saver mode (on/off/toggle) doesn't work

I have Macrodroid on my phone and it works flawlessly. I now wanted to install it on my tablet (Huawei MediaPad M5 lite 10. I went through the steps of installing ADB and all and the ADB actions in Marcrodroid seem to work (e.g. change keyboard). But I actually wanted Macrodroid to manage my...

www.macrodroidforum.com

Is it the 4th permission "ACCESS" from the screenshot that's letting me change the battery settings in SetEdit or do I have to give ADB permissions for WRITE_SETTINGS but I guess its not needed? I'm trying to confirm it with the experts since I don't want to mess up my phone as I recently formatted it and don't want to factory reset it again as it take days for me to set everything up.

Can the developer please fix this in the new update or will just giving the permission for MacroDroid work? Thanks!

 

[Endercraft]

The only thing that would matter would be the target API version and the permissions for both apps, I know the helper uses target API 21 but I'm not sure about SetEdit.
You should check the helper has the write settings permission allowed (if you can't fine it just allow using adb). In this case the adb hack shouldn't matter.

 

[Creeper]

The only thing that would matter would be the target API version and the permissions for both apps, I know the helper uses target API 21 but I'm not sure about SetEdit.
You should check the helper has the write settings permission allowed (if you can't fine it just allow using adb). In this case the adb hack shouldn't matter.

Ok, so I was wrong. I'm still unable to change the battery/power saver settings through MacroDroid and SetEdit. It only changes the battery icon to orange but doesn't actually turn on the battery/power saver mode. I was trying the new Setting Key which I thought was the Key to turn on/off battery saver mode but it only affects the visual.

SetEdit however was able to turn on other settings except for the battery saver while MacroDroid requires the Helper App. I think SetEdit worked because it hasn't been updated since October 31, 2018 and using the older API.

I still wish if there was a way to turn on or off battery saver

 

[Endercraft]

Are you using MIUI?
Also try the battery saver action.

 

[Creeper]

Are you using MIUI?
Also try the battery saver action.

No, I am using a Red Magic gaming phone, it's using the Red Magic OS 6.0.
I have already tried the Battery Saver Action, it just toggles between Light and Dark Mode.

The Setting Key which affects the battery saving mode is "power_saving_mode" but adding the action to MacroDroid doesn't do anything even with the Helper App and SetEdit, the value stays "0" unless I turn it on through the quick settings or going to Settings > Battery > Toggle Power Saving Mode. It seems other apps isn't able to change the value of battery saver or doesn't have the permission to do it.

 

[dhj49er]

No, I am using a Red Magic gaming phone, it's using the Red Magic OS 6.0.
I have already tried the Battery Saver Action, it just toggles between Light and Dark Mode.

The Setting Key which affects the battery saving mode is "power_saving_mode" but adding the action to MacroDroid doesn't do anything even with the Helper App and SetEdit, the value stays "0" unless I turn it on through the quick settings or going to Settings > Battery > Toggle Power Saving Mode. It seems other apps isn't able to change the value of battery saver or doesn't have the permission to do it.

I have a Galaxy S23 and the battery saver actions toggles the power saving setting....so is working as expected.

Strange that on your phone battery saver toggles between light and dark modes...looks like the OS might be the issue.

 

[hino22]

1. Permissions:
   • While MacroDroid has more permissions (108) compared to SetEdit SettingsDatabaseEditor (4), the number of permissions alone does not necessarily determine an app's ability to perform specific actions. The crucial point is whether the necessary permissions related to the specific functionality (changing battery/power saver settings in this case) are granted.
2. Design Choices:
   • Apps may have different design philosophies and strategies for interacting with the Android system. Some developers may choose to request many permissions to cover a broad range of potential functionalities, while others may prefer to request only the permissions absolutely necessary for their app's core features.
3. System Table Access:
   • The ability to modify certain settings may be dependent on how an app interacts with the Android system's settings database. If MacroDroid is using a different approach or if there's a limitation in its current implementation, it might explain why it's not working as expected.
4. ADB and Root Access:
   • The mention of ADB hack or root for SetEdit SettingsDatabaseEditor suggests that it might be using more privileged methods to modify system settings. Apps that require root access or ADB permissions generally have greater control over system-level changes.
5. MacroDroid Development:
   • It's possible that the MacroDroid app has certain limitations or bugs in its current version that affect its ability to modify specific settings. Development teams regularly release updates to address such issues, so it might be worth checking for the latest version of MacroDroid.
6. Community Feedback:
   • It's common for users to share their experiences and workarounds on forums or community boards. Checking for user discussions or contacting the MacroDroid community might provide insights or solutions.
7. Compatibility and Android Versions:
   • Compatibility issues or differences in how apps interact with the Android system may vary across different Android versions. Ensure that both apps are tested on the same Android version, and check if there are any known compatibility issues.

In conclusion, the issue may be multifaceted and involve the app's design, permissions, and system interaction methods. To address the problem, it's recommended to reach out to the MacroDroid developer or community for assistance. Additionally, checking for app updates and exploring community forums may provide valuable information and potential solutions.

 

[Qarboz]

1. Permissions:
   • While MacroDroid has more permissions (108) compared to SetEdit SettingsDatabaseEditor (4), the number of permissions alone does not necessarily determine an app's ability to perform specific actions. The crucial point is whether the necessary permissions related to the specific functionality (changing battery/power saver settings in this case) are granted.
2. Design Choices:
   • Apps may have different design philosophies and strategies for interacting with the Android system. Some developers may choose to request many permissions to cover a broad range of potential functionalities, while others may prefer to request only the permissions absolutely necessary for their app's core features.
3. System Table Access:
   • The ability to modify certain settings may be dependent on how an app interacts with the Android system's settings database. If MacroDroid is using a different approach or if there's a limitation in its current implementation, it might explain why it's not working as expected.
4. ADB and Root Access:
   • The mention of ADB hack or root for SetEdit SettingsDatabaseEditor suggests that it might be using more privileged methods to modify system settings. Apps that require root access or ADB permissions generally have greater control over system-level changes.
5. MacroDroid Development:
   • It's possible that the MacroDroid app has certain limitations or bugs in its current version that affect its ability to modify specific settings. Development teams regularly release updates to address such issues, so it might be worth checking for the latest version of MacroDroid.
6. Community Feedback:
   • It's common for users to share their experiences and workarounds on forums or community boards. Checking for user discussions or contacting the MacroDroid community might provide insights or solutions.
7. Compatibility and Android Versions:
   • Compatibility issues or differences in how apps interact with the Android system may vary across different Android versions. Ensure that both apps are tested on the same Android version, and check if there are any known compatibility issues.

In conclusion, the issue may be multifaceted and involve the app's design, permissions, and system interaction methods. To address the problem, it's recommended to reach out to the MacroDroid developer or community for assistance. Additionally, checking for app updates and exploring community forums may provide valuable information and potential solutions.

It is of no help to ask ChatGPT (or similar) and paste the answer into the forum, especially phrases like "To address the problem, it's recommended to reach out to the MacroDroid developer or community for assistance."
IMHO

 

[Endercraft]

It is of no help to ask ChatGPT (or similar) and paste the answer into the forum, especially phrases like "To address the problem, it's recommended to reach out to the MacroDroid developer or community for assistance."
IMHO

If they do that it's 99% to come back and edit the post to put some spam link (I they haven't already).

 

[lonely.myp]

I have the same problem, I can change any parameters through the SetEdit , but the macrodroid cannot do that.
issuing a permit through the ADB does not help

 

[Endercraft]

I have the same problem, I can change any parameters through the SetEdit , but the macrodroid cannot do that.
issuing a permit through the ADB does not help

Try with the helper app instead.

 

[lonely.myp]

Try with the helper app instead.

I can’t, the helper app is not running in the background. The only macros that work for me are those that can work in a macrodroid.