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.
Related
I had been waiting with bated breath for the Marshmallow update to arrive, mainly because of the expected addition of the "Until next alarm" setting to the "Do not disturb" feature, but woe to me, no such luck! "Do not disturb" doesn't seem to have changed at all from Lollipop, and there is no "Until next alarm" option to be seen anywhere. What's going on, T-Mobile and Samsung? I have a really hard time using my alarm clock without this feature. Every once in a while, I forget to disable "Do not disturb" after I get up and then walk around half a day incommunicado, wondering why no one calls me. This is ridiculous! Doesn't T-Mobile realize how freakin' important this feature is to people?
Does anyone know anything about this issue?
No reason to walk around with it in at day. You can set up your days and times.
rile1564 said:
No reason to walk around with it in at day. You can set up your days and times.
Click to expand...
Click to collapse
Thanks, I am aware of this option and have already started using it, but it is terribly inefficient, as it requires me to go through about 20 clicks EVERY SINGLE night just to set up the alarm and the Do Not Disturb mode for the next day. And it is impossible for me to set it up in advance for every day of the week, as the time I go to bed and get up is never the same day to day. With the Until Next Alarm option, it takes only two clicks to activate Do Not Disturb.
Best Regards...
I set mine up once, checked the box "Turn on as scheduled"and never had to touch it again. Once 10pm, on the days I set up, hits the Do Not Disturb automatically turns on. Then at 7am it automatically goes off.
ogrfnkl said:
Thanks, I am aware of this option and have already started using it, but it is terribly inefficient, as it requires me to go through about 20 clicks EVERY SINGLE night just to set up the alarm and the Do Not Disturb mode for the next day. And it is impossible for me to set it up in advance for every day of the week, as the time I go to bed and get up is never the same day to day. With the Until Next Alarm option, it takes only two clicks to activate Do Not Disturb.
Best Regards...
Click to expand...
Click to collapse
I never touch my Do Not Disturb. I use AlarmDroid for my alarm clock. It makes me do maths to turn it off in the morning. Annoying, but effective.
rile1564 said:
I set mine up once, checked the box "Turn on as scheduled"and never had to touch it again. Once 10pm, on the days I set up, hits the Do Not Disturb automatically turns on. Then at 7am it automatically goes off.
Click to expand...
Click to collapse
That works great for people who always go to bed and get up at the same time. I don't...
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".
Hello all,
I want to have a profile that checks for "multiple time interval" conditions, can anyone help me achieve this?
I want to have a BT Near check, that will turn on my BT, when I'm next to a certain BT device, but I know that daily, there are only certain time intervals, where I might (or might not) be next to it... So I only want it to be "active" or check it, within those time intervals...
For example:
From 6AM to 8AM or from 7PM to 9PM...
But it has to check on both those intervals daily.
How can I get a profile that checks for BT Near, only when within both of these time intervals?
I know I could have two profiles... One that would have BT Near From 6 to 8 AM, and another with BT Near From 7 to 9 PM, but I would rather have it all on one only profile...
If anyone can help, I would appreciate it. Thanks!
Tecno83 said:
Hello all,
I want to have a profile that checks for "multiple time interval" conditions, can anyone help me achieve this?
I want to have a BT Near check, that will turn on my BT, when I'm next to a certain BT device, but I know that daily, there are only certain time intervals, where I might (or might not) be next to it... So I only want it to be "active" or check it, within those time intervals...
For example:
From 6AM to 8AM or from 7PM to 9PM...
But it has to check on both those intervals daily.
How can I get a profile that checks for BT Near, only when within both of these time intervals?
I know I could have two profiles... One that would have BT Near From 6 to 8 AM, and another with BT Near From 7 to 9 PM, but I would rather have it all on one only profile...
If anyone can help, I would appreciate it. Thanks!
Click to expand...
Click to collapse
You could try using the %CATITLE to trigger the profile, but you will need to add these to your google calendar and specify the time rang in those. Also make sure you name them the same for both time range.
If you don't want the notification to appear in android when the event has triggered, you can just disable notifications in the events that you specified.
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 ?