Hi guys,
as the title says, is there any way to restart Tasker service from a task in Tasker itself?
Situation: sometimes Tasker suddenly freezes up, tasks are not carried out fully, and I received rejected copy or queue maxed out error. In such cases, I have to restart Tasker.
The procedure is: holding tasker symbol on the top part of the screen until it turns grey. Back out of tasker, go back in, and hold that symbol again until it turn colored.
Is there a way to force Tasker to do this, via a task maybe?
thanks
No. You can create a task to disable, but not enable. Besides once you disable, it would stop the task from running to re-enable it.
alienyd said:
and I received rejected copy or queue maxed out error.
Click to expand...
Click to collapse
You should just fix your runaway task. That's what the max queue limit is for...to let you know one of your tasks is being called in a recursive loop.
Sent from my g928c powered by RiverRom RR5 and SkyHigh 5.7
thanks for the replies. That's exactly the problem, after disabling, there's no way to re-enable itself.
Have you tried clear cache and re-install Tasker? I had problems with time based contexts that wouldn't trigger when it was supposed to, after clear cache/re-install everything worked like a charm.
I, like you, would like this because my time lapse, cloud sync task, seems to be blocked from the lg camera after a random number of hours.
I have tried everything, and the only thing to try next is to kill tasker and restart it, somehow with an external app.
I have tasker checking the email for the time lapse interval (1,3,5,15 minutes), then then choose the appropriate loop (5 minute default if no email), then upload the compressed as webp photos to Google drive at minute 12. I run the 12 to 14 minute script, every 15 minutes. Overnight, 9pm to 6:59am, it takes a picture every half hour. 7am,8am,7pm,8pm, it takes 4 photos per hour. Saturday and Sunday are one photo every 15 minutes. These are my jobsite cameras and remote eyeballs, and honesty boxes, as I call them, which document all work and contract fulfillment with no opportunity to skip steps or take risks, in a time lapse manner.
Unfortunately, the Android 10, LG g8 phones seem to running into weird snags every xx hours and a 0b jpg is all I get in the dcim/tasker folder. The moment I physically touch the phone, the script starts taking regular photos. I do not know it the problem is hardware, android 10, or tasker beta.
I could not find out how to clear the media store. I doubt if tasker can clear its own cache or if that would help.
There is now. Newer action called "Restart Tasker".
Related
Greetings,
When the phone is idle and I get a text message the sound stutters. Are more people experiencing this problem?
Regards,
Xionax
Do you have anything running in the background that may have a higher priority than sound playback?
Mine works fine but there's nothing run in the background.
Just a thought.
I've noticed mine does the same thing.
It starts, then pauses for a few split seconds and then finishes.
How long is your message tone? I seem to remember this is a windows mobile thing, something to do with waking up out of standby and having to bring all the drivers up. There's an MSDN post somewhere.
[EDIT] Found it here, the important part is:
"The issue is that it takes a "long" time to go to sleep and a similarly long time to wake back up. When a PocketPC goes to sleep, we have to notify every device driver so that they can each save any important information (their "state") and shut off the hardware they're controlling. Then, on wake up, we need to notify every driver again and have them turn all their hardware on. This process can take up to three seconds in each direction."
AND
"Imagine that your device receives a SMS message. The sleeping PocketPC will need to run the CPU for around six seconds to handle it. The Smartphone will do the same task in a few milliseconds. Waking up is much more efficient on a device that doesn't sleep. It turns on only the devices necessary, uses them for the minimum amount of time needed, and then immediately shuts them back off."
I could be wrong of course, but interesting non the less!
G
galvinize said:
How long is your message tone? I seem to remember this is a windows mobile thing, something to do with waking up out of standby and having to bring all the drivers up. There's an MSDN post somewhere.
[EDIT] Found it here, the important part is:
"The issue is that it takes a "long" time to go to sleep and a similarly long time to wake back up. When a PocketPC goes to sleep, we have to notify every device driver so that they can each save any important information (their "state") and shut off the hardware they're controlling. Then, on wake up, we need to notify every driver again and have them turn all their hardware on. This process can take up to three seconds in each direction."
AND
"Imagine that your device receives a SMS message. The sleeping PocketPC will need to run the CPU for around six seconds to handle it. The Smartphone will do the same task in a few milliseconds. Waking up is much more efficient on a device that doesn't sleep. It turns on only the devices necessary, uses them for the minimum amount of time needed, and then immediately shuts them back off."
I could be wrong of course, but interesting non the less!
G
Click to expand...
Click to collapse
Interesting but still "s*cks". I mean... thats not my problem that they have issues with the way drivers are handled. The phone should do its job and not stutter or anything. If so.. change it. (IMHO)
I was thinking about this last night, what type of file are you using (mp3, WAV) as a message tone and where is it stored?
galvinize said:
I was thinking about this last night, what type of file are you using (mp3, WAV) as a message tone and where is it stored?
Click to expand...
Click to collapse
I agree that its a windows mobile thing... i have got this stutter problem too.. FYI, i am using .wav file (245kb). and for the sms notification sound, i put the file under \windows folder
joseph.sapri said:
I agree that its a windows mobile thing... i have got this stutter problem too.. FYI, i am using .wav file (245kb). and for the sms notification sound, i put the file under \windows folder
Click to expand...
Click to collapse
After rom upgrade seems to run better
I am finding that my apps that send notifications, specifically that I send through LIghtflow, are either not notifying, or doing so 30 min. to an hour late.
I am also finding that installing as well as uninstalling apps are quite slow.
POwer saver is not on; battery optimization is not on for the offending apps; they are set to run in the background.
Anyone else experiencing this? Or any suggestions?
Regarding the slow downloads, I am finding the download finishes (according to the status bars, etc), but it then goes into a state of Install Pending. Can't find anything on that.
For anyone who cares, I have it resolved for the time being.
After 2 factory resets, I remembered back to the days i used to root my phones, and remembered that one strongly recommended task in that process was to delete cache.
So I did a final factory reset and deleted the cache also and all seems to be good.
When this crops up again I will try the cache delete w/o a factory reset and see how it goes.
Not getting much help here but I'll keep this thread upgraded.
It is again not working right. Lightroom is either not notifying or it's doing it 30 minutes late.
Play store downloads but then doesn't install for a period of time.
I'm beginning to think something is wrong with the phone.
This thing is driving me nuts. Following is what's going on, and have seen:
I've gone through 4 factory resets. All works find at first. Having decided that maybe there is an app interfering, I installed an app or two, tested, repeat...with delays between repeats. All seems fine.
But then late into the second day, w/o any installs, I goes haywire again. Symptoms are:
I use DGT GTD for my ToDo list. First thing I will notice is that when I add a new task, it will NOT show up in the widget list, and at the same time it stops notifications.
All apps stop sending notifications to Lightflow...or LIghtflow does not recognize the notifications. Not sure which is the case.
When add a new app on the Play Store, it downloads as quick as normal, but then it takes forever to install.
I installed AVAST, and checked for viruses. Came back clean.
I suspect it could be a phone problem. My Mate 9 works fine right now, with all the same apps. But, when a factory reset results in it working (at least during the short time a tech would evaluate), the phone can't be exchanged.
If anyone has any thoughts. I'm all ears. I'll keep posting, hopefully, ultimately, with a resolution. Maybe it'll help someone.
First of all here is the link to my profile so you can test it/see how it works.
So, the way I have it set up, it pretty much makes sense. If a notification comes in, and the notification reader is enabled (using AutoNotification Tile 3) then the task is run. The task first waits two seconds, for the notification sound, then checks to see if %Speaking is false. If it's false, it continues on to read the notification with WaveNet, otherwise it continues to wait. If %Speaking is false, it sets it true, then reads the notification (with a whole bunch of different events because I am checking for a lot of variables, namely %UserMusic, which is used by my other profiles to declare when I have an audio device connected, thus the reader reads through the Media Channel, and also it interprets different apps' notifications in different ways, but this is mostly irrelevant to my issue.) and once that's finished, it sets %Speaking back false. This way, if multiple notifications come in at the same time, the tasks don't talk over each other (this is what was happening before I implemented the variable checks.)
Except that's not what happens. Instead, for god knows what reason, 90% of the time, %Speaking never gets set back false, so Tasker gets stuck waiting forever and now my tasks stop working because the queue is filled up with notifications. I cannot for the life of me figure out what the heck is going on. And here's the kicker, it works sometimes. I've seen it work - I've sat there watching the variable switch from false and back to true in a split second and everything works fine. But for some reason that only happens a couple of times and then it stops again.
Can someone a little more savvy with Tasker help me out?
When you've seen it work compared to not work, is three a difference in the volume notifications? Maybe adding a brief wait before resetting %Speaking back to false to allow things down a bit. Add a brief cool down period (long press the profile name to select it and tap the gear at the top of the screen).
Things happening to fast sometimes cause these types of problems.
ktmom said:
When you've seen it work compared to not work, is three a difference in the volume notifications? Maybe adding a brief wait before resetting %Speaking back to false to allow things down a bit. Add a brief cool down period (long press the profile name to select it and tap the gear at the top of the screen).
Things happening to fast sometimes cause these types of problems.
Click to expand...
Click to collapse
Honestly, not really, once it runs out of notifications to read it sits dormant. I have woken up in the morning (having left it on overnight) and Tasker had a full queue, and none of the notifications were all that close together, and I've seen it get stuck when many come in at once. Even after just one notification, it sometimes fails to set that variable false. Even just running the task on its own can sometimes cause it to stay true afterward, and it works less often than it doesn't. When it does work it's great, but it doesn't work enough to rely on it.
The reason I don't want to add a cooldown is because then it might miss notifications. However, maybe I can try adding a wait action at the end after (or maybe before) the variable is set false. Might that help?
superluig164 said:
Honestly, not really, once it runs out of notifications to read it sits dormant. I have woken up in the morning (having left it on overnight) and Tasker had a full queue, and none of the notifications were all that close together, and I've seen it get stuck when many come in at once. Even after just one notification, it sometimes fails to set that variable false. Even just running the task on its own can sometimes cause it to stay true afterward, and it works less often than it doesn't. When it does work it's great, but it doesn't work enough to rely on it.
The reason I don't want to add a cooldown is because then it might miss notifications. However, maybe I can try adding a wait action at the end after (or maybe before) the variable is set false. Might that help?
Click to expand...
Click to collapse
I would try a wait in the task. The overnight thing might be due to power management issues.
Have you gone through all of the steps to make sure tasker (and associated plugins) are not being killed?
ktmom said:
I would try a wait in the task. The overnight thing might be due to power management issues.
Have you gone through all of the steps to make sure tasker (and associated plugins) are not being killed?
Click to expand...
Click to collapse
Yep. I have a Note 9 and I've added Tasker and AutoNotification as exceptions to the power management rules.
Hello,
I'm currently taking driving lessons and one of the most basic thing a driver should do is look in the rearview mirrors at least once every 5-7 seconds. That's the recommended time interval in my country. However, I keep forgetting to do this and I need a constant reminder, at least until I form a habit.
I want to use Tasker to set up an alert / notification to go out every 10 seconds on my Android smartphone. This will then be caught by my Amazfit Bip on my left wrist, which will vibrate when the notification is issued. This way I'll have a constant reminder during driving lessons to check the mirrors.
I tried to set up Tasker, but it only lets me create an event every two minutes. Is there any way to lower this threshold to 10 seconds? Or maybe another app which can achieve this?
Cheers.
zugurudumba said:
Hello,
I'm currently taking driving lessons and one of the most basic thing a driver should do is look in the rearview mirrors at least once every 5-7 seconds. That's the recommended time interval in my country. However, I keep forgetting to do this and I need a constant reminder, at least until I form a habit.
I want to use Tasker to set up an alert / notification to go out every 10 seconds on my Android smartphone. This will then be caught by my Amazfit Bip on my left wrist, which will vibrate when the notification is issued. This way I'll have a constant reminder during driving lessons to check the mirrors.
I tried to set up Tasker, but it only lets me create an event every two minutes. Is there any way to lower this threshold to 10 seconds? Or maybe another app which can achieve this?
Cheers.
Click to expand...
Click to collapse
Instead of using an a time context, create a loop with a 10 second wait in a task. Make sure you have a way to turn this off. Possibly set a variable and launch a notification at the start of the task. In the notification, use an action button to clear the variable. Loop only if the variable is set.
I am looking for a simple solution to turn on auto sync at a given time for a short moment like 5 mins.
I know there exist an app but i dislike have it running in the background the whole day.
Could there be a more efficient way to do the same with a magisk module ?
For it to work, you need to have something running all day in the background, otherwise it won't be able to know when it needs to toggle it on or off.
Anything running in the background like this will have next to no effect on batery.
@the_scotsman thanks for your answer.
Im not familiar with android but isnt there something like a cronjob which starts at a given time, does its job a single time and finish ? Then it could start at 22:00 enable auto sync and another job disables auto sync again 3 minutes later.
That would be a lot more efficient instead the app running in the background permanantly and what i suppose checking every second if the time is reached.
But if the consumption is really that small than i might have to live with it.
Do you have any suggestion maybe ? AutoSync app with certain interval or external power supply ? Or do there exist better options ?