Database Develop

[GUIDE][Difficulty: Intermediate] Entering Night Mode depending on alarm clock state

On the portal news on 2016-03-11 (thanks to @MishaalRahman for this).
This profile requires AlarmPad (either free or Pro version) and will activate your own Night Mode by setting an alarm.
You have to go to work the next morning, are sleeping, dreaming of the ones/things you love and then – BEEEEEEP BEEEEEEP BEEEEEEP – getting woken up by some more or less (most likely less) funny message by one of your friends. Awesome, right? No way… But this comes to an end right now.
Use Alarm Pad in combination with Tasker to set up a Night Mode, where you won’t get disturbed by any loud notification anymore. Activating an alarm will automatically set your phone into silence mode during a specific time, only the alarm is allowed to wake you up. When you dismiss the alarm, the Night Mode will turn itself off automatically. Cool, eh?
So, what do we need? First of all, you have to install AlarmPad (which is a great and customizable alarm clock app with native Tasker integration). Download it by following the above inserted Play Store link and continue with Tasker. Let’s start.
1. First, set up a profile called “Alarm set”. This will set a variable %ALARM to true if the alarm has been set. We need this variable to determine whether an alarm is currently set or not.
Use Event -> Plugin -> AlarmPad and select the Edit button. Choose “Alarm set” and confirm it by clicking the check mark on top right (OPTIONAL: you can choose a specific alarm for this by selecting “Restrict alarm” and then choosing the desired alarm).​Create a new task and name it (for example) “Set Alarm VAR”. Create a new variable %ALARM and set it to true.​Add Audio->Alarm Volume and set it to your desired value (maximum, if you tend to sleep very deep).​Now you are done. You can optionally add a toast notification to verify that the task has been executed, for example Alert -> Flash -> Text “Alarm set”.
2. Create a new profile called “Alarm disabled”. This will set %ALARM to false if the alarm gets disabled manually.
Use Event -> Plugin -> AlarmPad and select the Edit button. Choose “Alarm disabled” and confirm it by clicking the check mark on top right.​Create a new task and name it (for example) “Reset Alarm VAR”. Set variable %ALARM to false.​Add Audio->Alarm Volume and set it to your desired default alarm value when being outside of your house.​Now you are done with it. You can optionally add a toast notification to verify that the task has been executed, for example Alert -> Flash -> Text “Alarm disabled”.
3. Create a new profile called “Alarm playing”. This will set %ALARM to false if the alarm is fired and manually disabled.
Use Event -> Plugin -> AlarmPad and select the Edit button. Choose “Alarm triggered” and confirm it by clicking the check mark on top right.​Create a new task and name it (for example) “Reset Alarm VAR”. Set variable %ALARM to false.​Add Audio->Alarm Volume and set it to your desired default alarm value when being outside of your house.​Now you are done with it.
4. Create a new profile “Night Mode”. This will set your device into silent mode during a specific time interval when an alarm is set.
Use State -> Variables -> Variable Value and enter %Alarm ~ true. Return to your profile and select a new task which you call “Night Mode on”.​Add Task -> Wait -> 1 minute. Return to the task menu.​Add Task -> If and select “%ALARM ~ true”. Return to the task menu.​Add Display -> Display Brightness and set it to 0. Return to the task menu.​Add Audio -> Notification Volume and set it to 0. Repeat the same for Media Volume and Ringer Volume. Add Audio -> Alarm Volume and set it to your desired value. This will ensure that no other profile which might be triggered between setting the alarm and starting the Night Mode task has reset your alarm volume.​At last, add Task -> End If.​That’s it.
5. OPTIONAL: Return to the profile screen and add a trigger event to the profile Night Mode: Time.
Here you can define when the Night Mode will start and when it will end, for example, you set your alarm at 8 p.m., but go to bed at 10 p.m. and don’t want to miss messages until 10 p.m. because of reasons. Then select 10 p.m. as start time and whatever end time you want, for example 10 a.m. (don’t worry, if the alarm is triggered before 10 a.m., the Night Mode will automatically being deactivated and you can receive audio notifications again).
6. Create a new exit task for the profile “Night Mode” and call it “Night Mode off”. This will reset your device from silent mode after the alarm is triggered or manually disabled.
Add Task -> Wait -> 1 minute. Return to the task menu.​Add Plugin ->AlarmPad and select AlarmPad perform Action” and select “Disable” (OPTIONAL: select the alarm that is to be disabled). Confirm and return to the task menu.​Add Display -> Display Brightness and set it to your default brightness. Return to the task menu.​Add Audio -> Notification Volume and set it to your default volume value. Repeat the same for Media Volume and Ringer Volume.​That’s it.
Now we have set up Tasker to toggle your own Night Mode automatically depending on your alarm’s status.
That’s all, folks. Have a nice dreaming :good:

I' not sure if i understand it very well. How can we set the audio volumes (notifications, ringer and media) in silence mode only at one specifit hore (21:00 pe). When i disable the alarm the volumes are set to the default configuration that we have on the phone? And how do they turn off (silent mode) again?

joguirian said:
I' not sure if i understand it very well. How can we set the audio volumes (notifications, ringer and media) in silence mode only at one specifit hore (21:00 pe). When i disable the alarm the volumes are set to the default configuration that we have on the phone? And how do they turn off (silent mode) again?
Click to expand...
Click to collapse
Setting an alarm will trigger the Night Mode profile (and its related task Night Mode on, which sets all notification/media/ringer volumes to 0). If you have set up a time-trigger (for example between 10 p.m. and 10 a.m.) the task will only being executed within this time frame. For example, if you set your alarm at 8 p.m. and have the given time frame from 10 p.m. to 10 a.m., the Night Mode will only being executed if %ALARM is true and it is past 10 p.m. and before 10 a.m. of the following day.
Disabling the alarm will trigger the exit task (Night Mode off) of the Night Mode profile, thus all volumes are set back to their (pre-defined in exit task Night Mode off)volume level.
If you want to silence your phone at 9 p.m., just use a time trigger for the profile and set 9 p.m. as start and whatever you like as end time.

orville87 said:
Setting an alarm will trigger the Night Mode profile (and its related task Night Mode on, which sets all notification/media/ringer volumes to 0). If you have set up a time-trigger (for example between 10 p.m. and 10 a.m.) the task will only being executed within this time frame. For example, if you set your alarm at 8 p.m. and have the given time frame from 10 p.m. to 10 a.m., the Night Mode will only being executed if %ALARM is true and it is past 10 p.m. and before 10 a.m. of the following day.
Disabling the alarm will trigger the exit task (Night Mode off) of the Night Mode profile, thus all volumes are set back to their (pre-defined in exit task Night Mode off)volume level.
If you want to silence your phone at 9 p.m., just use a time trigger for the profile and set 9 p.m. as start and whatever you like as end time.
Click to expand...
Click to collapse
ok, understood
Thanks

[PROJECT] Automactically Switch between 12hr/24hr on WatchMaker (Android Wear)

Hello all XDA users! I created a project that automatically switches the clock format on your WM watchface whenever you switch between the formats on your phone via system settings.
===Prerequisites===
First and foremost, you need to install the Tasker (I used this on full version but it may work on the trial version) and have Allow External Access enabled, you can do this by doing the following:
Press the 3 dot menu
Click Preferences
Swipe over to Misc and find Allow External Access, then tap it to enable it
Done!
Then you need AutoTools by joaomgcd, you can download it here
Have USB Debugging enabled for ADB configuration for AutoTools
To Enable this, do the following:
Go to Settings
Go to About Device
Find your build number and click it several times until the phone says that you have enabled developer mode
Go into Developer Settings
Click on the tab that sets USB Debugging to enable it
Done!
Have ADB Drivers/Fastbook installed, here are two places that you can download these from but you don't have to download from these: Skipsoft, XDA
Have Installed WatchMaker Premium or Free Version
===About this Project===
What this project does is check if you have booted up your device and if so, it records the current time format your clock is set to. Then it checks if you have changed the format of your clock via broadcast intent, then it compares the previously recorded setting and the new setting, if they do not match, the task sends the new setting to WatchMaker and it changes the format on the watch to the new setting.
===Building the Project===
The first and foremost you MUST do is ensure that you have downloaded and got everything from the prerequisites. Once you have everything, follow the instructions for enabling access to system settings for AutoTools (you HAVE to do this in order for the profile to function correctly, as it needs to read the configuration for the 24hr format switch in the system settings, the profile will ONLY be looking at this setting). Once you have done these, you can move on to making the actual profiles
For the first profile, it will record the current clock format soon after the device boots up
So we must create an Event profile that will trigger soon after the phone finishes booting on, leave Invert unchecked
Now here's what you need for the actions:
Plugins -> AutoTools -> Secure Settings. Then click custom settings and do the following:
Setting Type: System
Name: time_12_24
Input Type: String
Leave Value Blank
Read Setting: Enabled
Variables -> Variable Set. Set %TIME_FORMAT to %time_12_24 (its the variable that AutoTools passes for the custom setting). This records the value we got from AutoTools and stores it in a global variable for us to use later on
OPTIONAL: Alert -> Notify Vibrate. For Title: put 'Logged Format Time' without quotes, and for text, added 'Log Format: %TIME_FORMAT' without quotes. This will notify that you have logged the format and will tell what the format is.
OPTIONAL: Task -> Wait. Set it for 10 seconds. This will make Tasker wait 10 seconds to move on to the next action
OPTIONAL: Alert -> Notify Cancel. For Title: put 'Logged Format Time' without quotes, and have Warn Not Exist checked. This will dismiss that notification we just sent 10 seconds ago
For the second profile, it will do the actual process of sending the variables to the WatchMaker App
We're going to create a Intent Received profile that will check if the specified broadcast intent has been received. For action, put 'android.intent.action.TIME_SET' without quotes. This will check if the TIME_SET intent has been received
Now here's what you need for the actions:
Task -> If. Set the condition to %TIME_FORMAT is SET. This will check if the global variable we defined in the first profile has something in it (this is for in case that you didn't boot up your device to store the value to the global variable so Tasker does not return an error since there is no value in the variable)
Plugin -> AutoTools -> Secure Settings. Like the same as like time, we're going to be finding that system variable, time_12_24. Just do the exact same steps as listed for the last time we defined this action
Task -> If. This time, set the condition to %time_12_24 does not match (!~) to %TIME_FORMAT. This will make Tasker check if the system format variable we just grabbed in the previous action DOES NOT match the previously recorded variable from our first profile. This is necessary to check because if you have automatic update clock enabled in system settings, that TIME_SET intent gets called whenever the phone updates to the network time, and because of this, we do not want Tasker constantly nagging us that the format has been update, despite that the format is the same as before.
Plugin -> WatchMaker -> WM Send Variable. Set the variable to send to %time_12_24, which is the new format that we switched to and just checked for.
OPTIONAL: Alert -> Notify Vibrate. For Title: put 'Time Format Changed' without quotes, and for text, added 'Updated Format to %time_12_24' without quotes. This will notify that you have logged the format and will tell what the format is.
OPTIONAL: Task -> Wait. Set it for 10 seconds. This will make Tasker wait 10 seconds to move on to the next action
OPTIONAL: Alert -> Notify Cancel. For Title: put 'Time Format Changed' without quotes, and have Warn Not Exist checked. This will dismiss that notification we just sent 10 seconds ago
Task -> End If. Close that If stated that we have created so far
Variables -> Variable Set. Set %TIME_FORMAT to %time_12_24. This will override the previously recorded value and place the new one in its place in the variable, %TIME_FORMAT
Task -> Stop. Leave everything else blank. This will make Tasker end the task from here
Task -> Else. Leave everything else blank. This basically says that if that system format variable DOES have something in it. This is necessary to check because
OPTIONAL: Alert -> Notify Vibrate. For Title: put 'Logged Format Time' without quotes, and for text, added 'Log Format: %time_12_24' without quotes. This will notify that you have logged the format and will tell what the format is.
OPTIONAL: Task -> Wait. Set it for 10 seconds. This will make Tasker wait 10 seconds to move on to the next action
OPTIONAL: Alert -> Notify Cancel. For Title: put 'Logged Format Time' without quotes, and have Warn Not Exist checked. This will dismiss that notification we just sent 10 seconds ago
Variables -> Variable Set. Set %TIME_FORMAT to %time_12_24. This records the value we got from AutoTools and stores it in a global variable for us to use later on.
Task -> End If. Close up the main IF statement that surrounds everything.
One final thing! Make sure that your watchface in WM has this method or something similar (WITH the quotes): '{ttime_12_24}' == '24' and '{dh23z}:{dmz}' or '{dh}:{dmz} {da}'. This sets the clock format to 24hr if the tasker value is 24, and switches to 12hr if the value is 12.
Note: You DO NOT have to have items such as he notification and clock method text to display exactly as I have, as I have designed these for my convenience.
===Download===
The download files are attached below, you can import this by doing the following:
Long-press the little icon that looks like a house at the bottom of the main menu
Press Import
Locate the downloaded file
Tasker should do the rest and import the entire project and the profiles
===Final Notes===
If you have any questions or issues, please feel free to post them here! ^^

[Noob question] Setting up 'Car Mode'

Hey folks,
I'm totally new to Tasker and after having spent hours reading tutorials and browsing forums, I hope to get some help here.
I'm not able to set up any task at all admittedly.
I'm trying to set up a 'Car Mode', i.e. when my device connects to my Bluetooth Car Adapter, it's supposed to trigger a couple of tasks, such as
- Setting Display Timeout to maximum (30 minutes)
- enable 'Double-tap to wake up'
- Read messages aloud (SMS, WhatsApp, Telegram, ...)
I've set up a profile with BT connected and the name of my adapter and tried to trigger one of the given tasks, but I can't even get the tasks running.
When, for example, setting up a new task ("Display Timeout: Max") and adding an action 'Settings --> Display Settings', I get the possibility to add the %DTOUT variable and set the value to 30, but it's always an If variable.
How can I set up this (actually fairly simple imo) task: If BT device connected, then set display timeout to 30 minutes.
Sorry for this most likely stupid question.
Thanks a ton in advance!
Edit: I figured out how to make my device read messages aloud (Thanks to Notification Listener) and set the display timeout to 30 resp. 1 minute (It wasn't the Settings section but the display section).
Still no clue how to toggle Double-Tap to Wake ...

Making a Tasker profile overrule another

I have a profile that when the screen turns on it enables location to battery saving mode for 1 minute the turns off completely. I then have a 2nd profile that turns location to high accuracy when I open Google maps. The problem is my first profile overrides the maps profile and disables location after 1 minute even if maps is open and location changes to high accuracy.
So how can I make my 2nd profile override the first? I feel like it can't be too difficult to do but I can't figure it out.

farquea said:
I have a profile that when the screen turns on it enables location to battery saving mode for 1 minute the turns off completely. I then have a 2nd profile that turns location to high accuracy when I open Google maps. The problem is my first profile overrides the maps profile and disables location after 1 minute even if maps is open and location changes to high accuracy.
So how can I make my 2nd profile override the first? I feel like it can't be too difficult to do but I can't figure it out.
Click to expand...
Click to collapse
Hello my friend.. You need something like in the first profile long press in the name and add second condition to trigger profile... Add Google maps and in selection of app press the invert button... I thing this setup does your work.. Try and tell me!!
Sent from my SM-G900F using XDA Labs

I thought that would work but it didnt Here's my profile.
When Display is On, Location = Battery Saving, Wait 1 Min, Location = Off
If i use the invert, it just turns off the Display On profile but i think the 1 minute timeout is already triggered as its still turning off location 1 minute after even with Maps open even though in Tasker the Display profile doesnt show as active.
I need something to say Wait 1 min unless Maps is open but then what happens when Maps closes, the 1 minute begins? Doing that may not be easy. Is there no way to add weight or priorities to tasks to say the maps profile.
! REALLY horrible way i suppose i could do it is in my maps profile say wait 61 seconds and then set location mode to GPS, so that it reenables if the Display profile has disabled, i just could end up with a small gap of time where location is off.

Here's what you do.
Add an action to both location profiles that (and every profile or task that turns on loc services) sets a timer
set variable LOCATIONtimer=%TIMES+60
Then create a profile with a time context and set the time to activate as %LOCATIONtimer
The task will disable location services.
Now set your maps profile to clear the %LOCATIONtimer variable
(this will prevent the disabling of loc… since the variable has no time, it can't fire)
Then when your battery saving profile activates it will set the timer for 60 secs… but when you activate maps… it will clear the variable, so it won't adjust your loc srvices
Btw… it's a huge battery impact when you do the "app" context as it checks for open apps every two secs.
It's much better to get rid of all app context profils and launch those apps via a tasker shortcut that
1 launches the app
2 then sets a variable eg. isopenMAPS=true
Then set a. If variable value context of isopenMAPS=true then every time that variable is true, you'll know the app was opened, so you can then clear that variable to show you've closed three app

Alarm clock with tasker

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.