Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2020/05/project-left-right-speaker-test-v10.html
#project #LeftRightSpeakerTest
DESCRIPTION
This small and simple project allows you to check if your earphones/headphones are working well, by sending an acoustic signal to each side independently.
This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet, or when the dev considers it is needed even not imported from TaskerNet.
Notes:
- Thanks to Vecteezy for the pics used on this project.
- The project doesn't measure the earphones/headphones wear (damage) in any way. It just plays an acoustic signal (voice or beep) that needs to be interpreted by the listener (user).
- More pics (Extra Resources) are also available to fully customize it.
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
This small and simple project allows you to check if your earphones/headphones are working well, by sending an acoustic signal to each side independently.
This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet, or when the dev considers it is needed even not imported from TaskerNet.
Notes:
- Thanks to Vecteezy for the pics used on this project.
- The project doesn't measure the earphones/headphones wear (damage) in any way. It just plays an acoustic signal (voice or beep) that needs to be interpreted by the listener (user).
- More pics (Extra Resources) are also available to fully customize it.
CREDITS
@SmartPhoneLover
VERSION
v1.0
#warning #TaskerDev
[DEV] Tasker 5.9.3.beta.6 - Tasker veterans rejoice!
A new beta is here! Two major pet peeves of mine while using Tasker have been fixed in this version :) Read below!
Sign up for the beta here.
If you don't want to wait for the Google Play update, get it right away here.
You can also get the updated app factory here.
Local Variable Passthrough
Demo here: https://youtu.be/MZIcX5Oe5CM
When you use the Perform Task action in Tasker you can usually only send 2 variables to the child task so that the child task can work dynamically based on these. Otherwise you could use some not so pretty workarounds to send more values...
Sometimes sending 2 values to the child task simply isn't enough. Wouldn't it be great to send an unlimited number of values? 😁
Well now you can, with Local Variable Passthrough!
If you enable this option all of the variables in the parent task will be available in the child task! That simple! No complicated variable splits, no JSON to keep everything, just nice and simple variables!
Likewise the Return action has the same option now! This means that you can send all the variables from the child task back to the parent task as well!
This means that Tasker now effectively supports tasks with unlimited parameters and return values!
Phew! 🤗
Easy If-Else-End-If Blocks
Demo here: https://youtu.be/iXCjg4JDyfY
When you add an If action in Tasker isn't it a drag to always have to add Else and End If actions as well? The End If action at least will be needed 99% of the time, right?
In this new version Tasker will ask you what other relevant actions you want to insert whenever you insert an action that has relevant related actions :)
- If you insert an If action, it'll ask you if you want to insert just the If, If and End If or If, Else and End If actions!
- If you insert a For action it'll ask you if you also want to add an End For action!
I could very easily add more of these related actions now, so let me know if there are any others that make sense.
Full Changelog
- When adding "If" or "For" actions, give user the option to automatically add other appropriate actions (else, end if, end for)
- Automatically focus in the variable field in the "If" action so that you can select a variable right away without first clicking on the field
- Added "Local Variable Passthrough" options to the "Perform Task" and "Return" actions. If enabled will make all variables available in the other task
- Made checking your current settings in "Custom Setting" action and states not rely on ADB Wifi but works as well as before
- Made notification show text like "No active Profiles (x of y enabled)" when no profiles are active
- Made "Kill App" action use ADB Wifi if available and warn users that ADB Wifi can be used
- Fixed issue with "Keyboard" action sometimes getting stuck on the Tasker keyboard
- Made map that shows in "Get Location v2" action when you pick your initial location to show a hybrid map
- Fixed bug with "File Attribute Changed" variables
- Fixed showing maximum possible screen brightness when setting up the "Display Brightness" action on some devices
- Fixed setting animation in "Show Scene" action config
- Fixed bug in Javascript actions where some variable names couldn't be used
- When inputting app factory certificate password make input field hide characters
Added "File Path To Content URI" action in "Tasker Function" action
Source: Go!
[DEV] Tasker 5.9.3.beta.6 - Tasker veterans rejoice!
A new beta is here! Two major pet peeves of mine while using Tasker have been fixed in this version :) Read below!
Sign up for the beta here.
If you don't want to wait for the Google Play update, get it right away here.
You can also get the updated app factory here.
Local Variable Passthrough
Demo here: https://youtu.be/MZIcX5Oe5CM
When you use the Perform Task action in Tasker you can usually only send 2 variables to the child task so that the child task can work dynamically based on these. Otherwise you could use some not so pretty workarounds to send more values...
Sometimes sending 2 values to the child task simply isn't enough. Wouldn't it be great to send an unlimited number of values? 😁
Well now you can, with Local Variable Passthrough!
If you enable this option all of the variables in the parent task will be available in the child task! That simple! No complicated variable splits, no JSON to keep everything, just nice and simple variables!
Likewise the Return action has the same option now! This means that you can send all the variables from the child task back to the parent task as well!
This means that Tasker now effectively supports tasks with unlimited parameters and return values!
Phew! 🤗
Easy If-Else-End-If Blocks
Demo here: https://youtu.be/iXCjg4JDyfY
When you add an If action in Tasker isn't it a drag to always have to add Else and End If actions as well? The End If action at least will be needed 99% of the time, right?
In this new version Tasker will ask you what other relevant actions you want to insert whenever you insert an action that has relevant related actions :)
- If you insert an If action, it'll ask you if you want to insert just the If, If and End If or If, Else and End If actions!
- If you insert a For action it'll ask you if you also want to add an End For action!
I could very easily add more of these related actions now, so let me know if there are any others that make sense.
Full Changelog
- When adding "If" or "For" actions, give user the option to automatically add other appropriate actions (else, end if, end for)
- Automatically focus in the variable field in the "If" action so that you can select a variable right away without first clicking on the field
- Added "Local Variable Passthrough" options to the "Perform Task" and "Return" actions. If enabled will make all variables available in the other task
- Made checking your current settings in "Custom Setting" action and states not rely on ADB Wifi but works as well as before
- Made notification show text like "No active Profiles (x of y enabled)" when no profiles are active
- Made "Kill App" action use ADB Wifi if available and warn users that ADB Wifi can be used
- Fixed issue with "Keyboard" action sometimes getting stuck on the Tasker keyboard
- Made map that shows in "Get Location v2" action when you pick your initial location to show a hybrid map
- Fixed bug with "File Attribute Changed" variables
- Fixed showing maximum possible screen brightness when setting up the "Display Brightness" action on some devices
- Fixed setting animation in "Show Scene" action config
- Fixed bug in Javascript actions where some variable names couldn't be used
- When inputting app factory certificate password make input field hide characters
Added "File Path To Content URI" action in "Tasker Function" action
Source: Go!
#warning #TaskerDev
[DEV] New "Local Network" condition in Join allows you to react to devices being on the same network!
Check out the new Join beta that was just released! All of the details on that here:
https://www.reddit.com/r/JoinApp/comments/go076m/dev_join_23beta3_full_local_network_pushes/
In the new beta you get 2 new Tasker conditions: Local Network State and Local Network Event.
These allow you to create profiles in Tasker based on which devices are on the same local network as you!
For example, if you turn on your PC and is Chrome is loaded, you can react to that by activating a Work profile in Tasker.
Also new in this beta is the ability to set a bunch of new Notification parameters in the Join Send Push action in Tasker like for example:
- Notification Category
- Notification ID
- Notification Group
- Dismiss on Touch
and more!
Let me know how the new stuff works for you if you can! :)
Source: Go!
[DEV] New "Local Network" condition in Join allows you to react to devices being on the same network!
Check out the new Join beta that was just released! All of the details on that here:
https://www.reddit.com/r/JoinApp/comments/go076m/dev_join_23beta3_full_local_network_pushes/
In the new beta you get 2 new Tasker conditions: Local Network State and Local Network Event.
These allow you to create profiles in Tasker based on which devices are on the same local network as you!
For example, if you turn on your PC and is Chrome is loaded, you can react to that by activating a Work profile in Tasker.
Also new in this beta is the ability to set a bunch of new Notification parameters in the Join Send Push action in Tasker like for example:
- Notification Category
- Notification ID
- Notification Group
- Dismiss on Touch
and more!
Let me know how the new stuff works for you if you can! :)
Source: Go!
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2020/05/project-caffeine-qs-tile-bring-caffeine.html
#project #CaffeineQSTile
DESCRIPTION
This project was based on the LineageOS Caffeine Quick Settings tile, which helps to keep the screen on for a longer time than the one set from Android settings, temporally.
These are the available versions:
• Tasker QS Tile: It uses one of the 3 QS Tiles included into Tasker (1st in that case), and generates a statusbar notification to show timer.
• AutoNotification QS Tile (1): It uses one of the 40 QS Tiles available in AutoNotification (1st in that case), and generates a statusbar notification to show timer.
• AutoNotification QS Tile (2): Same as version (1), except that no notification is shown. The tile is dynamically updated showing the timer.
This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet, or when the dev considers it is needed even not imported from TaskerNet.
Notes:
- Thanks to @AndersonMarcio and @sinisterstrike for helping.
- Long press event (cancel timeout) is only available in AutoNotification QS Tile (1/2) versions.
- To use QS Tiles from Tasker or AutoNotification, you will need to enable them from the appropriate settings of each app first. Then, add the one that would be linked to the project to the Android QS panel.
- There's no reason to do so, but if decided, specifying values below current device's screen timeout will make the display to be turned off sooner, if not touched within that time.
- By default, the timer is updated every 100ms, but you can change it if you are concerned about possible battery drain. (Use 'Update Delay' action from 'Timer' task)
- The screen timeout set by this project may be overruled by the Stay On action when the device is plugged into a power source. (reference)
- If you go to Android settings (or Display settings) while the project is running, Android may overwrite the screen timeout. (reference)
CREDITS
@SmartPhoneLover
@AndersonMarcio
@sinisterstrike
VERSION
v1.0
DESCRIPTION
This project was based on the LineageOS Caffeine Quick Settings tile, which helps to keep the screen on for a longer time than the one set from Android settings, temporally.
These are the available versions:
• Tasker QS Tile: It uses one of the 3 QS Tiles included into Tasker (1st in that case), and generates a statusbar notification to show timer.
• AutoNotification QS Tile (1): It uses one of the 40 QS Tiles available in AutoNotification (1st in that case), and generates a statusbar notification to show timer.
• AutoNotification QS Tile (2): Same as version (1), except that no notification is shown. The tile is dynamically updated showing the timer.
This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet, or when the dev considers it is needed even not imported from TaskerNet.
Notes:
- Thanks to @AndersonMarcio and @sinisterstrike for helping.
- Long press event (cancel timeout) is only available in AutoNotification QS Tile (1/2) versions.
- To use QS Tiles from Tasker or AutoNotification, you will need to enable them from the appropriate settings of each app first. Then, add the one that would be linked to the project to the Android QS panel.
- There's no reason to do so, but if decided, specifying values below current device's screen timeout will make the display to be turned off sooner, if not touched within that time.
- By default, the timer is updated every 100ms, but you can change it if you are concerned about possible battery drain. (Use 'Update Delay' action from 'Timer' task)
- The screen timeout set by this project may be overruled by the Stay On action when the device is plugged into a power source. (reference)
- If you go to Android settings (or Display settings) while the project is running, Android may overwrite the screen timeout. (reference)
CREDITS
@SmartPhoneLover
@AndersonMarcio
@sinisterstrike
VERSION
v1.0