Tasker Wakelocks

[Hassan Siddiqi]

I have a question or a bug report related to tasker wakelocks

If you have a tasker profile with a time context like my profile which is to do a task from 20:00 to 24:00 every hour if a variable NewFile is set to 1(2 contexts, the variable state is second context) , should tasker cause wakelocks all day long and set alarms? because from what i read on the forums is that tasker doesnt care about times that its profiles arnt active. But in my case its causing lot of wakelocks and the attached log shows tasker is setting alrams a lot. 

I disabled the profile at night and the wakelocks stopped. i turned it back on in the morning.

I have another profile that launches an app at 5, but i didnt cause any wakelocks.

So is this normal or a bug?

Thanks

[Pent]

If you have a tasker profile with a time context like my profile which is to do a task from 20:00 to 24:00 every hour if a variable NewFile is set to 1(2 contexts, the variable state is second context) , should tasker cause wakelocks all day long and set alarms?

What if you remove the %NewFile context ? Perhaps the variable is changing a lot.

Pent

[Hassan Siddiqi]

its basically a profile for automated backups of downloaded tv shows to my pc. and nowadays it changes once a week and goes back to 0 once backup is done. and it didnt change the day i posted the message.
so basically variable state will be checked before the time context causing the 25 wakelocks per hour? altbough im not sure how battery consuming the constant variable check is compared to time events.
im fine with the wakelocks, just want to make sure there is no unusual behaviour.

[Pent]

I don't think you answered my question ?

Pent

[Hassan Siddiqi]

sorry that profile was dependant on the variable, i made another profile for testing, will let you know in a couple of hours

[Hassan Siddiqi]

On Monday, 5 September 2016 12:32:33 UTC+5, Hassan Siddiqi wrote:
> sorry that profile was dependant on the variable, i made another profile for testing, will let you know in a couple of hours

so i set up a profile at ~12 to run a task from 15:00 to 24:00 every 30 min. The wakelocks happened even before 3 and after that at a rate of 25 wakelocks/hr.
and tasker is still setting a lot of alarms, more than 18 alarms required for the profile. no other profile was active during this time.
And i also saw tasker log mentioning the NewFile variable and some other states, but other profiles were off so why check that. (maybe its nothing)
Thanks

[Hassan Siddiqi]

@Pent did you find any problem?

[Pent]

> sorry that profile was dependant on the variable, i made another profile for testing, will let you know in a couple of hours

so i set up a profile at ~12 to run a task from 15:00 to 24:00 every 30 min. The wakelocks happened even before 3 and after that at a rate of 25 wakelocks/hr.
and tasker is still setting a lot of alarms, more than 18 alarms required for the profile. no other profile was active during this time.

And i also saw tasker log mentioning the NewFile variable and some other states, but other profiles were off so why check that. (maybe its nothing)

I think you would need to clear all the other profiles before testing. I doubt it's this particular profile which is causing
the device to wake. Note also: when a profile activates, other wakelocks will be set to e.g. ensure the task which
is running can complete without the device going off. What are the names of the wakelocks ?

Pent

[Hassan Siddiqi]

i knew that other profiles might cause problems so i disabled them all during my testing. You meant disable other profiles by "clear all other profiles" or remove them too?
i used betterbattery stats, it doesnt show wakelock names. Wakelock detector can get the names i think. do u need them?

[Pent]

i knew that other profiles might cause problems so i disabled them all during my testing. You meant disable other profiles by "clear all other profiles" or remove them too?

Most sure is to backup all, then delete all except the interesting one.
 

i used betterbattery stats, it doesnt show wakelock names.

Surprised, thought it did.

Wakelock detector can get the names i think. do u need them?

If you're still interested in where they're coming from :-)

Pent

[Hassan Siddiqi]

sorry betterbatterystats did give your tasker wakelock names...screenshots attached for the M and *alarm* wakelocks and tasker alarms. consistent with the logs...
ill remove everything and do the testing again and report back...