I am experiencing some really strange issues lately with tasks related to Autosync (I am struggling with some other issues related to repeating time context though, see THIS thread)
However, I am creating some really basic tasks with three actions.
A1: Autosync ON
A2: Wait 2 min
A3: Autosync OFF
When I test these actions with the ``PLAY´´ button in the Task, the actions wont play. Nothing happens. When I try to activate the Task with a Profile (connected to wifi), nothing happens either.
If I reboot my phone, the Task starts running and Autosync goes on when the Wifi connects. But if I shuts off Wifi and try running the task with the ``PLAY´´ button or through disconnecting/connecting my Wifi, nothing happens again.
The really strange thing is though that my OTHER ``Autosync work´´-task works every time I test it through ``PLAY´´ button or inactivated/activates it´s profile, the only different between these Tasks are longer wait-interval. I tried to clone this Task since its working and the other one does not, but the cloned Task will not work either. Isn't this VERY strange?
I try to make new Tasks from scratch with Autosync On -Wait - Off, but same issue they wont even start when tested with ``PLAY´´. The only thing I can think of now is some bug with Tasker related to Autosync (and also repeating time context, as mentions in my other thread..)
Is it only me having these problems?
No problem here repeatedly running those 3 basic actions in a Task.
There must be something wrong on your end. Maybe you should clear Tasker data and reinstall Tasker from scratch and see if these 3 simple actions can run without any problem.
Thanks
thanks for this post keep it up <3 :good:
It seems that my problems with repeating time context and Autosync tasks that wont run are solved. Thanks @GrippingSphere for the help!
I did following;
Clear cache/data in Tasker. Uninstall Tasker. Reboot phone. Install Tasker again. Restore old Tasker backup (before my Autosync/repeating time context problems started). Manually restored these profiles/tasks from scratch.
I have logged the repeating time context Autosync today, every task have been performed without misses or delays. So re-installation seems to done it, hope it stays like that ^^
Hopefully this will help others in the future if having similar problems.
Related
I started using Tasker which has been fantastic. I also setup the juicedefender replacement profiles that enable/disable data and auto-sync as needed to conserve battery.
I notice that when auto-sync is disabled and then re-enabled that my phone will immediately begin syncing. Would it be better to keep auto-sync enabled at all times and toggle the data connection only instead of both? The phone shouldn't be able to sync without data and this way it shouldn't immediately begin to sync each time the screen comes on.
I suppose it could be setup this way so that you don't miss any data during a data:ON window. Would love to hear from someone with more knowledge on this.
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".
So, over the last few weeks I've found that my P20 Pro vibrates for no (known reason), every now and again. Usually multiple times per day.
I've tried turning it off and back on, killing the apps, checking for updates, turning notifications off on most apps.
Has anyone had a similar problem and /or has any way of diagnosing or fixing it?
I have experienced the same thing, so you're not totally alone if that helps. I haven't found the cause yet either. I suspect it might be WiFi+ vibrating when the source switches back and forth so it'll happen in stints for me.
i have the same thing and i think i might found the reason, i have some muted WhatsApp chat groups and it seems like that every now and then when i get messages in these groups my phone vibrates although i muted them . There is no notification but a short vibration.
Another thing that bothers me more is when receiving an whats app message my phone vibrates once short and after that the way i set it up in the settings...
I begin to get it after an update. hope to see a solution soon.
No
I believe I've found the cause and solution to the Huawei mate 20 pro random vibrations.
I installed a notification logger from the play store and found that it was logging notifications of repetitive image downloads completing that lined up with every buzz.
If you go into settings, apps and choose to see system apps in the menu, you can force close the download and download manager apps. If you then clear the data and cache from each, you should find the phantom notifications stop.
I haven't had one in days now, and it was all the time.
I hope this is of help.
This happens to me a lot. Its mainly due to voice recognition thinking I'm am speaking to the phone. It happens randomly when watching TV, at work on even in the train. There's no specific key work that triggers it,. It happens at random. This is my issue with the random vibration but your could be a different reason although
Ereckson said:
This happens to me a lot. Its mainly due to voice recognition thinking I'm am speaking to the phone. It happens randomly when watching TV, at work on even in the train. There's no specific key work that triggers it,. It happens at random. This is my issue with the random vibration but your could be a different reason although
Click to expand...
Click to collapse
Mine was definitely the download manager continuously redownloading Google photos images. Force stop, clear data, clear cache of the download and download manager system apps and mine has been fine now for a week. Try it!
Had the same issue months ago. Cleaning cache and data of stock download manager app solved it for me.
Mine started doing same yesterday ?
I have the mate 20 pro, and it's just started randomly vibrating with no notification
So my phone is now starting to randomly vibrate like bursts of short vibrations that last a while, but there's no notifications or anything? I don't know how to find the "download manager" to check if it's that. I'm not sure which apps to force stop. It's really annoying though.
Do you use Textra? Happened to my wife's s8 and she just uninstalled then reinstalled Textra to make the problem go away.
I have cleared the download manager and everything else several times, but it only works for few days even hours and starts again. I'm not sure if it activities itself again after I download something, but nevertheless, this just shouldn't happen. How can I disable download manager permanently (or preferably just the vibrations, as I assume DM is there for a reason)
Had the same issue. No problem from textra, for me it was google drive. I uninstalled it, cleared cahe and data and I am now using OneDrive. I haven't experienced any random vibrations since then.
Mate 20 X had similar issue after EMUI 9.1 upgrade and turned out to be contacts sync system app constantly trying to sync contacts. Force stop and cleared data and all good now.
I have the same issue on regular mate 20 since the last software update to EMUI 9.1.0. All the suggested solutions here did not resolve the issue. If someone has more suggestions please share
I fixed it. It's a system application called "Contacts Sync" disabling it solved the issue for me.
Settings > apps > show system processes > search for Contacts Sync > disable and force close it
humax1 said:
I fixed it. It's a system application called "Contacts Sync" disabling it solved the issue for me.
Settings > apps > show system processes > search for Contacts Sync > disable and force close it
Click to expand...
Click to collapse
This didnt work for me, but i found another solution. I stopped almost all apps from autostart. except email and messangers. that immediately solved the issue and the phone boots much faster as well, nice sideeffect
You need to go into battery usage and then click on the individual app, then app launch.
I hope that helps
shingers5 said:
Mate 20 X had similar issue after EMUI 9.1 upgrade and turned out to be contacts sync system app constantly trying to sync contacts. Force stop and cleared data and all good now.
Click to expand...
Click to collapse
I just noticed this on my mate 20x on 9.1 on vibrate mode. Did your solution permanently resolve this issue or do you have to do it multiple times or after restarts?
Pacman1969 said:
I just noticed this on my mate 20x on 9.1 on vibrate mode. Did your solution permanently resolve this issue or do you have to do it multiple times or after restarts?
Click to expand...
Click to collapse
Yes it did. I force close it and disabled it from app settings. Never came back
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.
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 ?