I downloaded Tasker with the intent of doing one single action - turning my equalizer on whenever I plug in my earphones, as the topic title might suggest.
Is this possible? The app I use has an option to put a shortcut on my home screen that turns it on without actually opening the app. Is there a way that I can set Tasker to perform this same fucntion?
(Additionally: is there a way to set it to ignore the function if the equalizer is already on? And is it possible to set it to turn the equalizer off in the same way (there's a home screen shortcut provided for that too) when I unplug my earphones?)
You can do that, but you need to have "autoShortcut"
Sorry, I can't link to it, but search for it on google play
Or actually, you don't need it, you can do it by running scripts that emulate screen touches, but option one is the easiest by far
(EDIT: You need root to emulate screen touches)
You can launch shortcuts within Tasker by selecting "All" in the launch application task (to show all applications installed) then simply long-press on the app you installed and it will bring up relevant activities that you can directly launch.
I saw the theme switcher for layer on one of the tasker day feature and really like the idea. Can we do this with CMTE?
Sent from my Nexus 6P using Tapatalk
I have a custom task that switches themes with the help of AutoInput (plugin) for input on screen and Secure Settings (plugin) to turn AutoInput on/off so that AutoInput's accessibility service isn't running when it shouldn't be. It works for CM TE, but not COS Themer. COS is more complicated to implement than CM and I just never got around to implementing it.
However, am not attaching my task here because it needs your screen to be unlocked to use it. In my case, I have another custom task that unlocks my phone. I cannot and will not share that task.
Let me know if you have a task to unlock your screen or if you use a simple lock screen that you can manage unlock using AutoInput, and I'll share my CMTE theme switcher here. How to go about unlocking your screen is up to you to figure out, and getting that working is essential to making my task work.
Alternatively, you could set up a context using the event for display unlocked, that sets a global variable to anything you want such as "yes", and another context using event display off, that clears the global variable. You could then add the global variable as a "wait until" at the top of my task for changing themes, so that the task proceeds only when your phone is unlocked.
Hi, i am sorry if i am posting into wrong forum
but i have issue with tasker i have couple program in there very simple ones based on location and simple switch for example to silent and back to sound when i am and exit certain location and so on. and after i think last update the profiles does not activate any more. i havent done anything in tasker did not added the profiles are on and the location services are on. i have version 4.8u1m. do you know what could have happened? thanks
In your settings in accessibility do you have tasker turned on. Also in tasker itself go to preferences monitor and make sure use new cell Api is checked .
Maybe you switched off tasker? Long press the Tasker icon in the app in the upper left corner. If it's not colored it's switched off
Follow_and_Feel said:
Maybe you switched off tasker? Long press the Tasker icon in the app in the upper left corner. If it's not colored it's switched off
Click to expand...
Click to collapse
That was it for me! Thanks!!
I want to trigger a specific routine i created in Yonomi. Their triggers aren't versatile enough so i always have to do it manually. Yonomi can create shortcuts on homescreen but when launching the app (shortcut) trough tasker, the routines i made aren't there (i can only choose launch activity). I can use autoinput to do it, but that doesn't work when screen is off. Somethoing that works with screen off is my goal since i want to trigger it by webhook. I did use the assistant voice command task already but it seems overkill to me.
Any idea?
Phone is Pixel 3a running Android 10, Tasker is up-to-date.
I have a profile called PwrConnect that runs a task called Clock. The task simply launches my alarm clock app on the phone. The profile is primarily triggered when any power is connected to the phone but it has a secondary condition that specifies the time must be between 10:30pm and 6:00am.
When I plug my charger into the phone the profile is not triggered. If I remove the secondary condition (the time constraint) then the profile triggers when I plug in. But here's where it gets kind of strange. If I include the secondary condition (the time constraint) and I have the Tasker app open when I plug the charger in then the profile fires and runs the task which launches the clock app. Alternatively, I have also tried putting the time constraint in the task (%time > 2230) but that does not work either.
What am I doing wrong??? Or, is this a bug? Anyone else see anything like this?
Do you have "reliable alarms" enabled?
Have you tried a simple profile to just test the time context?
ktmom said:
Do you have "reliable alarms" enabled?
Have you tried a simple profile to just test the time context?
Click to expand...
Click to collapse
I'm not sure what "reliable alarms" is. Is that a setting in Tasker or Android?
Anyway, I have done some more testing. I added another step to the Clock task to simply flash a message when the task runs and I have found that the task (and therefore the profile) is indeed being executed as it should be - that is: when power is connected and the time is between 10:30pm and 6:00am. I can tell this because the message flashes on the screen when I connect power. BUT... the clock app only launches if I have the Tasker app open when I connect power. If the Tasker app is not open then I see the message flash but the clock app does not launch.
Reliable alarms is a tasker setting in preferences on the monitor tab. It helps tasker accurately execute time related activities.
What device and ROM are you on?
The following profile works fine for me with Tasker not in the foreground:
Code:
Time: From 11:44AM Till 3:44PM
State: Power [
Source:Any
]
Enter: Open App
A1: Launch App [
App:Clock
Data:
Exclude From Recent Apps: Off
Always Start New Copy: Off
]
ktmom said:
Reliable alarms is a tasker setting in preferences on the monitor tab. It helps tasker accurately execute time related activities.
What device and ROM are you on?
Click to expand...
Click to collapse
Device: Pixel 3a, ROM: stock Android 10 (not rooted)
I am fairly certain that the problem lies with the clock app that I am using. When I change the task so that it launches the stock, built-in clock app then everything works as it should. The clock app that I am trying to use (Kaloer Clock) is no longer in the PlayStore so has not been updated in a while. So, I suspect that there is something about it that Android 10 does not like. The app still functions fine and I can manually start it or Tasker will start it IF Tasker is running in the foreground. In fact this app has a setting that should start it automatically when power is plugged in but that stopped working about the time that I upgraded to Android 10, which is why I was trying to automate it with Tasker. I hate to give up on this app though because it is the only clock app I have found that allows me to tap anywhere on the screen to snooze the alarm (or long-press to cancel it). Everything else I have tried makes you tap an on-screen button which is difficult without my glasses.
Using AutoNotification (or any tasker notification listener plugin), a scene and intents, you can make the Google Clock have a full screen snooze/dismiss "button".
I slapped together an example that I put on Taskernet. It's full screen, a tap snoozes and long press dismisses.
To run it as is, you will need AutoNotification installed. The "ktm" after the profile/task/scene names can be removed. I do this to help prevent name collisions with anything already existing during import.
ktmom said:
Using AutoNotification (or any tasker notification listener plugin), a scene and intents, you can make the Google Clock have a full screen snooze/dismiss "button".
I slapped together an example that I put on Taskernet. It's full screen, a tap snoozes and long press dismisses.
To run it as is, you will need AutoNotification installed. The "ktm" after the profile/task/scene names can be removed. I do this to help prevent name collisions with anything already existing during import.
Click to expand...
Click to collapse
Ktmom,
I installed AutoNotification and imported your project. I am assuming that I need to delete either step 2 or 3 in the Stop Alarm ktm task. But, the scene does not appear unless I have Tasker running in the foreground when the alarm fires. Just wondered if you have test this in Android 10? Seems as though all my problems started after I upgraded.
dremelts said:
Ktmom,
I installed AutoNotification and imported your project. I am assuming that I need to delete either step 2 or 3 in the Stop Alarm ktm task. But, the scene does not appear unless I have Tasker running in the foreground when the alarm fires. Just wondered if you have test this in Android 10? Seems as though all my problems started after I upgraded.
Click to expand...
Click to collapse
The action that you're not using can be deleted or left paused.
And no, sorry, I'm always slow to update to major releases. But, there's something to try.
Edit the scene that your using, without changing anything else, tap the 3-dot menu. Select "properties" and change the "property type" to "activity". Save out of the scene.
Now edit the task -> show scene action that you are using and change "display as" to "activity".
Save out of the task, and Tasker, then test again.