![]() If you use a shift modifier you have to wait for the macro to go over the line for the mod button, and also the macro wont interrupt a fireball cast.īest solution for me is to use a manual button with a /stopcasting /cast Pyroblast button. I think the issue that makes it slightly less effecient is that once you have hot streak you should be IMMEDIATELY casting Pyro and this takes priority over everything else and I don’t think the macro can realistically do this. In my opinion, modern Google location service is improved enough intelligent,reducing the frequency just still on the same places, turning off unreliable GPS inside the buildings, so don't care about it.I think the main issue isn’t the macro it’s fire itself in nature.įire is probably the only spec where you actively cast things over one another and it’s encouraged to clip casts. So, Wifi only might be good option for you. If you still worry about it, you can turn on airplane mode to make sure all location sources such as GPS, Cell, and WiFi are NOT working, however it is not realistic. That's why you don't need to be sensitive It was proceeded before each macro calling and only when MD main getting location change event from OS service, and then triggers are called as the conditions. ![]() It means the trigger handler of MD main process is working correctly and well filtering effectively. You don't get outside while working, the geofence trigger is never fired. If you have timer base triggers such as interval, stopwatch and longer wait(above 5 seconds when ticked depending on alarm option), they consume battery at the same level. On the others hand, the checking frequency of MD location/geofence is still a factor of battery draining, but it's very small. The mechanism is similar to alarm, based on system tick as my understandings. MD is just waiting the renewal events via receivers, so if no data coming, no waking up and no processing, even though you set it up every 30 seconds MD main process never calls the triggers as you know. These are managed by the location service by itself, so its refresh rate is out of MD concerns. Now all apps can just make receivers to get a specific location data, and couldn't initiate to work of GPS, Cell towers, Wifi and looking up the Google stored data via Internet connection. OP might recognize the differences of the frequency between OS location service and MD location/geofence. Yes, I know that reducing screen brightness will lower battery drain, but I don't see how lowering my screen brightness is going to lower battery drain which is caused by Macrodroid's "Location Updating". ![]() Meanwhile, Macrodroid would continue to use Location Services for all OTHER macros which require Location Services. I was hoping that if I DISABLE the "At_Work" macro (when I am home) it will tell Macrodroid to stop updating my location UNTIL the next morning when I RE-ENABLE the "At_Work" macro. When I arrive home, there is no need for Macrodroid to continue to constantly update my location (until the next morning). Obviously, this constant location updating causes a certain amount of battery drain. In order for Macrodroid to know when to run the macro, it must must constantly update where my phone is located. Now, when I physically ENTER this geofence, the geofence trigger (in the "At_Work" macro) will cause my "At_Work" macro to run which will then send an SMS message to my wife telling her I have arrived at my workplace. ![]() Next, I created a Macrodroid macro called "At_Work" which uses this geofence as a Trigger. In Macrodroid, I created a "geofence" around my workplace. Click to expand.Yes, I know that reducing screen brightness will lower battery drain, but I don't see how lowering my screen brightness is going to lower battery drain which is caused by Macrodroid's "Location Updating".Ĭan I FURTHER minimize the battery drain - which is caused by Macrodroid's "Location Updating" - by DISABLING my macros which use a Geofence trigger?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |