TaskService is stopping even with service running in the foreground. How do I fix this?

417 views
Skip to first unread message

Matthew Lozy

unread,
Oct 27, 2016, 12:00:53 PM10/27/16
to Tasker
Hi all,

So I have noticed in the Run Log that TaskService is stopping during the night almost nearly every hour. It doesn't seem to affect anything because it starts up again in time for a profile to trigger again (which is my weather profile that runs once an hour). However I'd still like to get to the bottom of this. I have a Galaxy S7 unrooted. I have Tasker to Run in the Foreground, reliable alarms set to When Off, and in the battery settings I have Tasker set to not be optimized so Doze should not be affecting it (plus my phone is always charging at night).

Does anyone have any insight in this? Before I go to bed I always end all apps and restart my phone so RAM isn't low so I see no reason why Android should be killing the service. Is there a system or Tasker system that I'm not aware of? Thanks.

Pent

unread,
Oct 27, 2016, 1:17:05 PM10/27/16
to Tasker
It always shuts down when it has nothing to do, saves resources.

Pent

Matthew Lozy

unread,
Oct 27, 2016, 1:20:03 PM10/27/16
to Tasker
Thank you so much! Finally I understand why it's happening. That explains why it only does it at night. I thought Android was killing the service because in the userguide it states that unexpected Monitor starts indicates that the Android system is killing the process. 

Pent

unread,
Oct 27, 2016, 3:29:48 PM10/27/16
to Tasker
Monitor service is not the same as Execution service, just to be clear.

Pent

Matthew Lozy

unread,
Oct 28, 2016, 9:09:39 AM10/28/16
to Tasker
Well then let me ask. Is it normal to see TaskService stopping, then Monitor starting, then TaskService starting (in that order with profiles activating in between the monitor start and task service start) nearly every hour during the night?

Pent

unread,
Oct 28, 2016, 10:42:07 AM10/28/16
to Tasker



Well then let me ask. Is it normal to see TaskService stopping, then Monitor starting, then TaskService starting (in that order with profiles activating in between the monitor start and task service start) nearly every hour during the night?

No, the monitor should not be restarting, should stay running, that's probably the 'being killed by Android' thing
you quoted previously.

http://tasker.dinglisch.net/userguide/en/androidpowermanagement.html

Pent

Matthew Lozy

unread,
Oct 28, 2016, 1:15:55 PM10/28/16
to Tasker
Okay then I need your help fixing it. I read your Android Power Management write up a long time ago and followed everything months ago, yet the Monitor still restarts. Any ideas?

Pent

unread,
Oct 28, 2016, 3:28:18 PM10/28/16
to Tasker


Okay then I need your help fixing it. I read your Android Power Management write up a long time ago and followed everything months ago, yet the Monitor still restarts. Any ideas?
 
Device ? Android version ? Custom ROM ? Rooted ?

Pent

Rich D

unread,
Oct 28, 2016, 4:01:24 PM10/28/16
to Tasker Google Groups Post


yet the Monitor still restarts. Any ideas?

It is my understanding that a monitor "restart"  is expected an occurs whenever a context is changed and saved or a profile is enabled or disabled. 

A monitor "start" occurs when Tasker is killed and restarted.

Rich.....   

Matthew Lozy

unread,
Oct 29, 2016, 12:23:04 AM10/29/16
to Tasker
Galaxy S7 6.0.1 stock, not rooted.

Matthew Lozy

unread,
Oct 29, 2016, 12:26:52 AM10/29/16
to Tasker
Rich, I meant start not restart. I'm aware the monitor restarts after a change. I'm seeing monitor starts in the middle of the night.

Also Pent, before I go to bed I end all apps and restart my phone. Nothing is running that would use up so much RAM that Android would need to kill Tasker.

Matthew Lozy

unread,
Nov 2, 2016, 12:41:36 PM11/2/16
to Tasker
Any update Pent?

Matthew Lozy

unread,
Jul 24, 2017, 2:51:16 PM7/24/17
to Tasker
On Wednesday, November 2, 2016 at 12:41:36 PM UTC-4, Matthew Lozy wrote:
> Any update Pent?

I know this is old, but if anyone stumble upon this, this resolved itself when TMobile updated my S7 to Android 7.0

Reply all
Reply to author
Forward
0 new messages