So, after searching all sites about tasker I found, and read a couple of threads without answer to this very problem, I think I need to ask.
I notice a couple of days that profiles were not starting when conditions are accomplished. I run a log and I found a lot of Start TaskService, Stop TaskService that I don´t remember have seen before. I checked all the options to keep Tasker running (battery optimization, accessibility, etc) and they are just as before, when profiles worked ok. I set the popup error option, but it does not give me any information of what is killing the service. I don't use boosters, task killers, memory cleaners, etc. I set the monitor notification icon to show, to see if tasker is running or not, but the icon is always there, no matter the Stop TaskService message
Today I have a couple of moments where the service started and stopped like 20 times in a lapse of 3 minutes, with a "Restart Monitor" message in between some stop start.
Every time I manually disable Tasker, and start it again, all the active profiles run just fine, all the tasks are executed without unexpected errors, they ExitOK, but the log ends with a Stop TaskService, and it stays like that until I manually do something that start it again.
I have a BT near profile, and I read is giving some problems, but I've no idea if this is related, because Tasker worked ok before, even with that profile. The only change I remember is to add a second BT device to the profile (Dev1/Dev2). I updated to the last version on google play, but the service keeps stopping TaskService when all the tasks end the execution.
So, is the start stop TaskService sequence normal? If it is, then, What could be causing the profiles no to change status?
Thanks in advance.