I'm trying to follow this how-to: Dynamic Home Button Behavior (GrogBase), but I am having problems sending and receiving an intent. Can anybody tell me how to format the intent to be sent by a task, to be received by tasker?
1. Just create a task with a "send intent" action and fill in the first field (action): TEST_ACTION
2. Now Create a profile (Event, Intent received) and again, fill in the first field (action): TEST_ACTION
Then add a popup or vibration or something as a task to see whether it will work.
Now go back to the task from 1. and run it.
This should work.
(Credit goes to @ascsa who explained it to me here)
Related
In this days, i desperately tried to find a way in how to save a text that I wrote in my application made by Tasker. Everytime I opened my application and wrote something in EditText box and close the app.... It disappeares! So with some help (I don't know how to tag him: RuggedHunter, @RuggedHunter thank you so much) he helped me how to make it:
In the task that launches your scene, before the Show Scene action:
1) Variable Set: %Text to: Enter Text Here (if %Text is't set)
2) Show Scene
In your Text Edit element:
1) Text field: %Text
In the task that destroys your scene, before your Destroy Scene action:
1) Variable Set: %Text to: %new_val
When you close the scene, that new text is saved as a global variable.
The next time you open your app, the text edit field should display the text you previously entered.
Good morning XDA:
I have a Galaxy S8 and trying to create a tasker profile that will let me create a blank sms when I press the Bixby Button. This would be similar to blackberry m shortcut. Here is what I have so far:
Profile: bixbye to tasker
Tasks:
1. Launch App
App Messages
2. AutoInput Action
Configuration Type: Text Value: Compose Action: Click
3. Wait
5 MS
4. AutoInput Action
Configuration Type: Text Value: Compose Action: Click
-------------------------------------------------------------------------------------------------
Profile will run fine the first time after that it stops at step 2. Thanks in advance I cannot figure what I am doing wrong.
--- fixed problem----
Created APK please
Please close thread and delete
Sent from my SM-G950U using XDA-Developers Legacy app
Is this possible to do through Tasker? If so, how do you code it?
I want my cameras to record but I don't want to get notifications except for after sunset and just after sunrise everyday. So like 6pm to 8am.
Otherwise I want it to record but not notify me.
I posted this on reddit/r/tasker but no one has responded yet.
The time profile is easy. The trigger context is the window of time you want to block notifications.
The task would do the heavy lifting of actually blocking the unwanted notification. You probably could handle that using Notifications Off (Root), assuming of course that you're rooted. Else, AutoNotification can do that for you. Both are tasker integrated.
Get Started With AutoNotification
Use Tasker and AutoNotification to block notifications from certain apps (AutoApps forum)
ktmom said:
The time profile is easy. The trigger context is the window of time you want to block notifications.
The task would do the heavy lifting of actually blocking the unwanted notification. You probably could handle that using Notifications Off (Root), assuming of course that you're rooted. Else, AutoNotification can do that for you. Both are tasker integrated.
Get Started With AutoNotification
Use Tasker and AutoNotification to block notifications from certain apps (AutoApps forum)
Click to expand...
Click to collapse
Unfortunately neither of those are working. I have a pixel that is rooted and an s8+ that is not. So I tried both and I'm still getting notifications. Any ideas?
DudeThatsErin said:
Unfortunately neither of those are working. I have a pixel that is rooted and an s8+ that is not. So I tried both and I'm still getting notifications. Any ideas?
Click to expand...
Click to collapse
I didn't specifically state, but should have, that when using the AutoNotification method, an additional profile trigger needs to be an AutoNotification intercept event.
You could post a export (description) of the profile you've built.
ktmom said:
I didn't specifically state, but should have, that when using the AutoNotification method, an additional profile trigger needs to be an AutoNotification intercept event.
You could post a export (description) of the profile you've built.
Click to expand...
Click to collapse
Stuff (4)
A1: AutoNotification Block [ Configuration:Apps: com.netgear.android
Toggle: Enable Timeout (Seconds):60 ]
I pressed on export and that's what it gave me.
I also took screenshots. Here you go: https://imgur.com/gallery/bAhRY
Lmk if there is anything else you need.
Your profile is currently triggered by the arlo app. So anytime that app opens, your "stuff" task runs. Not what you were shooting for ?
On the left side of that screen, on top of the part that shows an icon and "arlo", do a long press. That will allow you to add a context.
Choose: state -> plugin -> AutoNotification -> Intercept.
Then leave "Event Behaviour" checked.
Tap on "Action type" and select created.
Tapp on "Apps" and check the box next to the Arlo app.
At the top of the screen tap the check mark to accept the configuration. Then on the next screen, the left arrow at the top left to lock in the context.
You will now have two contexts for that one profile.
Long press the original one for the arlo app and select delete.
Again, long press on the context that is remaining (AutoNotification Intercept) and tap add.
Now tap "time" and configure for the window you want this profile to be active.
Hi,
might seem a silly question but it's very annoying while driving that I receive Samsung calendar notifications. While they appear full screen, Waze and music sounds are silenced.
I have to manually dismiss them before all sounds are 'restored'.
I just want to drive without interruptions of the calendar app, anyone know how this can be done? I'm also using Android Auto but don't see any setting that can accomplish this.
thank you
I'm using Tasker and AutoNotifcation for this. I block some notifications and enable the AOD while connected to my cars Bluetooth.
- install both apps
- in Tasker add a task and search for "AutoNotification Block".
- Tap the pen of Configuration and select the apps you want to block the notification for. You can also add the package name manually
- Under "Toggle" set it to "Block"
- go back and set the timeout to none (slide the slider to the most right)
- go back to the task
- go back to the task list
- add a new task, do the same as above but instead of "Block" set the Toggle to "Unblock".
Now you have the needed tasks and you can set the profiles for them.
- In Tasker go to the profile tap and add a new profile, name it whatever you want.
- Tap on "Status" and filter for "Bluetooth connected" (Note: Bluetooth must be enabled while creating the profiles!).
- Name is optional, tap on the magnifying glass for "Address" and select your cars Bluetooth address.
- go back and Tasker will popup a window where you need to assign a task. Assign the "block" task.
- now do the same again but Mark the "Reverse" check mark in the Bluetooth address menu and after this select the "unblock" task.
So, Tasker will tell AutoNotification to block the specific notifications while connected to the Bluetooth device and unblock it if disconnected.
I hope it works for you. I don't know the English menu entries for Tasker since my app is in German, sorry if there's something different.
thanks, great tip : I already bought Tasker a while ago, I'll set it up like that
Hello everyone i have a huawei mate 20 non root with android 9 and i would like to cancel an alarm with tasker but impossible.
I can activate an alarm at a given time but in the opposite direction impossible. do you have an idea thanks again
cordially
There are several ways to do this. What have you tried that isn't working? Even better, post the profile or task that isn't doing what you want. If you post just the task to snooze/dismiss an alarm, what triggers the task to run?
Before exporting, if you have sensitive information such as logins, api keys or anything else, you might consider setting those values to a variable and use the variable in your tasks so they won't export with the task.
To export a task description for posting, press on the name to highlight the profile. Go to the 3-dot menu and select export -> Description to Clipboard.
Now you'll be able to paste it. Be aware, it easier to use something like pastebin.com / hastebin.com and link to a post here. If you paste in a post here, the forum software will convert semicolons with characters directly after, into emoticons making it very hard to read.
Hello everyone here is what I can do and what does not work.
* What works
Calendar Entry Profile -> Work
Then task -> Set ALARM AM 05 H 45
* What does not work is the reverse task if not working then disable alarm clock
Thanks
Flechg said:
Hello everyone here is what I can do and what does not work.
* What works
Calendar Entry Profile -> Work
Then task -> Set ALARM AM 05 H 45
* What does not work is the reverse task if not working then disable alarm clock
Thanks
Click to expand...
Click to collapse
Posting the profile and task (as described above) is always more illuminating. However, the inverse of that would just be not setting an alarm. If there's no calendar entry the alarm is not set. I'm still missing the problem. Is there a residual alarm that goes off without having been set through tasker?
Edit -
I've been pondering and the only thing I can come up with is that you set an alarm and then the next day you set an alarm... then end up with a clock app full of alarms. If that's the problem, and the goal is to have the alarm only go off on work days, then approaching this problem the other way might be better.
Set the alarm to go of every day at the right time in the clock app, then create a profile that checks if today it's a work day, then set a variable.
In a second profile, use the variable (not a work day) as a context plus an AutoNotification intercept, for the alarm notification. You'll be canceling the alarm on days you don't need it.
On newer Android, there is a pre-notification that shows up some period before the alarm is set to fire (an hour maybe?). That notification has a dismiss button. If you intercept that notification, then the entry task can click on the dismiss button again using an AutoNotification action.
I think the category id is "Upcoming Alarms". This field can be examined by grabbing it in the AutoNotification profile context configured to "get all fields". Then flash %ancategoryid.
There are also clock app intents that can dismiss alarms. I don't use that because it doesn't work on my device. The intent looks like the following:
Code:
Send Intent [
Action:android.intent.action.DISMISS_ALARM
Cat:Default
Mime Type:
Data:
Extra:android.intent.extra.alarm.SEARCH_MODE:android.all
Extra:
Extra:
Package:
Class:
Target:Activity
This intent should only cancel the current occurrence of a repeating alarm.
If this works for you, then you can explore the android developer documentation - alarm clock and discover a variety of intents.
For the sake of completeness, in case this thread is found by others in the future, there is an action system -> cancel alarm.
This can be used to cancel/snooze/disable an alarm. However, it's reliability is dependant on the device/OS and at least in my case doesn't work any better than the intent. Some devices will always get a pop-up menu to confirm which alarm to take action on.
Hello and thank you for your answers
i tried intent as well as other things like cancel alarm but with my huawei it does not work okay is this android 9
I give up thanks again for your help
:crying:
The autoNotification method should work. If you haven't gone through and made sure that all of Huawei's power saving "features" are disabled so the apps can wake up and do their job without being killed by the system.
Read these
https://dontkillmyapp.com/huawei
https://tasker.joaoapps.com/userguide/en/faqs/faq-problem.html#00
If you really want help, then post what isn't working. Instructions to do so were given in post 2.