Been there done that. Don't kill my app.com isn't anything special it just details the steps that anybody would probably get into their system and find out anyway. Nothing magical there. Thanks though.Follow steps at dontkillmyapp.com. Also see the Github for dontkillmyapp.com as there are suggestions.there on fixes.
It's a REVVL 4 5007W running Android 10.What device are you using ?
For some weird reason macrodroid shuts down out of the blue
Thank you. I tried that also. It doesn't help. I know it's probably my phone that's just a POS... But at the same time I've noticed through multiple phones that macrodroid isn't a very good program when it comes to things being thrown at it that it's not used to dealing with, for lack of a better way to put it. Definitely not a program I would call mature or robust.If MacroDroid is forcefully closed in the background you should try setting it as device administrator app. That may or may not help.
MacroDroid has pretty much everything to ask the system "keep me alive and relaunch me ASAP if you kill me" so it's really your phone wanting you to not lose battery.Thank you. I tried that also. It doesn't help. I know it's probably my phone that's just a POS... But at the same time I've noticed through multiple phones that macrodroid isn't a very good program when it comes to things being thrown at it that it's not used to dealing with, for lack of a better way to put it. Definitely not a program I would call mature or robust.
All battery optimizations that I have available to me in the system UI are disabled. If there was anything available to me through ADB I'd gladly try it. I'd root it in a second if it wasn't my only phone. But I have macrodroid running as high priority as I can...MacroDroid has pretty much everything to ask the system "keep me alive and relaunch me ASAP if you kill me" so it's really your phone wanting you to not lose battery.
If you can't disable these optimizations you'll need root or another phone.
And another thing, there's no relaunch. Period. If there's a checkbox in settings of macrodroid that said if under any circumstances macrodroid is not running (verify this every second I will take the performance hit) restart me ASAP! It's a user choice and a smart piece of code for macrodroids reliability... And for a program that's meant to continually run so we can run tasks on the machine... Am I wrong on this? That's the first thing I would do as a programmer. I've written thousands of lines of code myself. Perl, mind you, but complex code running home automation tasks. So I have an idea of what programmers are working with. Just put in the code!! Above All Else keep macrodroid running even if you have to start a whole new process and a whole new part of the memory system whatever I'm not THAT into programming. But you get what I mean.MacroDroid has pretty much everything to ask the system "keep me alive and relaunch me ASAP if you kill me" so it's really your phone wanting you to not lose battery.
If you can't disable these optimizations you'll need root or another phone.
And another thing, there's no relaunch. Period. If there's a checkbox in settings of macrodroid that said if under any circumstances macrodroid is not running (verify this every second I will take the performance hit) restart me ASAP! It's a user choice and a smart piece of code for macrodroids reliability... And for a program that's meant to continually run so we can run tasks on the machine... Am I wrong on this? That's the first thing I would do as a programmer. I've written thousands of lines of code myself. Perl, mind you, but complex code running home automation tasks. So I have an idea of what programmers are working with. Just put in the code!! Above All Else keep macrodroid running even if you have to start a whole new process and a whole new part of the memory system whatever I'm not THAT into programming. But you get what I mean.
adb shell dumpsys activity exit-info *macrodroid package name*
from adb to find out who is responsible for killing Macrodroid.I'm not a software developer, but I think if the app was killed (it doesn't run!) it can't relaunch itself, maybe...And another thing, there's no relaunch. Period. If there's a checkbox in settings of macrodroid that said if under any circumstances macrodroid is not running (verify this every second I will take the performance hit) restart me ASAP! It's a user choice and a smart piece of code for macrodroids reliability... And for a program that's meant to continually run so we can run tasks on the machine... Am I wrong on this? That's the first thing I would do as a programmer. I've written thousands of lines of code myself. Perl, mind you, but complex code running home automation tasks. So I have an idea of what programmers are working with. Just put in the code!! Above All Else keep macrodroid running even if you have to start a whole new process and a whole new part of the memory system whatever I'm not THAT into programming. But you get what I mean.
From what I remember there are both. There are flags MacroDroid has to try and stay in background and autostart which can be effective for most device but sometimes for example with Xiaomi you need to set the autostart permission yourself (although the app won't launch unless it has a flag to autostart).The property also can't be set by the app themselves, it should be done by the user manually for any 3rd party app
From what I remember there are both. There are flags MacroDroid has to try and stay in background and autostart which can be effective for most device
macrodroid isn't a very good program