Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/project-intents-collection-v10.html
#project #IntentsCollection
DESCRIPTION
A set of most used intents on Android.
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
A set of most used intents on Android.
CREDITS
@SmartPhoneLover
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/project-intents-collection-v11.html
#project #IntentsCollection
DESCRIPTION
A set of most used intents on Android.
CREDITS
@SmartPhoneLover
CHANGELOG
- New: 107 new intent profiles added
VERSION
v1.0
DESCRIPTION
A set of most used intents on Android.
CREDITS
@SmartPhoneLover
CHANGELOG
- New: 107 new intent profiles added
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/08/task-miui-music-player-intents-v10.html
#task #MIUIMusicPlayerIntents
DESCRIPTION
Intents for the MIUI Music Player app, included in all Xiaomi devices.
Notes:
- The app have to be already running (service) when using these intents.
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
Intents for the MIUI Music Player app, included in all Xiaomi devices.
Notes:
- The app have to be already running (service) when using these intents.
CREDITS
@SmartPhoneLover
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/project-morse-code-translator-v10.html
#project #MorseCodeTranslator
DESCRIPTION
What the current project does?
It was originally designed to only translate plain text (letters and numbers) into morse code. But during these days I managed to add some new features, and also rework all the tasks, and this is what I got: translate text or numbers (+ signs) into morse, and vice versa; encrypt/decrypt both translations (or raw inputs) using Cipher with AES protection (128/192/256bits); merge all the previous existing tasks into a single one (MC - Translator); added some new parameters to control it from a second task (MC - Start); permanent notification with the current status of the task, and a few more things.
How does it work?
First, we need to take a look at the 4 main tasks: 'MT - Start', 'MT - Stop', 'MT - Translator' and 'MT - Key Generator'.
- Start: Here we will have to set every of the available paramaters to pass to the task who really does the job. Them are: Message, where we will write the string (text, numbers, signs); Translation, this will tell Tasker what we want to translate from and to (alpha-morse or morse-alpha), and the available commands are: 'A-M' and 'M-A', respectively; Encryption, with it we can encrypt and decrypt strings, and the args are: '0', 1-KEY', '2-KEY', where (0) means disabled, (1)-KEY is to encrypt, and (2)-KEY decrypts the passed string from 'Message', and where 'KEY' appears we will need to write our own AES key; Interpretation, does the job of playing the translated string into Sound (beeps), Vibration (pattern) and Flashlight (pattern), and to control it: 'S' = sound, 'V' = vibrator, 'L' = flashlight (take into account that morse to alpha will only use Voice to play what we sent to it); Clipboard, it will allow us to automatically copy contents of main task to clipboard, for example useful when we use encrypt feature, because as Morse doesn't recognize capital letters, I had to modify the output string to allow Tasker to understand it and also decrypt it correctly.
- Stop: It just manages all the actions to does just one thing: stop the main task immediately, after pressing on the notification (Processing..., Playing...). So, you can decide, if the message is too long and want to stop Tasker from doing the hard work, just press the notification. Also works while playing the translated string. (you DO NOT HAVE to toggle the associated profile manually, but Tasker will)
- Translator: So here we are with the main task that does the job. I think will better not to explain how it works. Take a look and understand what it does ;) But what I can tell is: A4-A11 stores all the characters and associated morse code for translation, so may have to edit them to fit your requirements.
- Key Generator: This is a stand-alone task to generate our own random keys, to use with Cipher actions. You can decide how long and secure will be the password by choosing from 16, 24 or 32 hardcoded characters (128/192/256bits). But take into account that, first: using encryption will increase the final string lenght to be translated, so if morse is choosed, it will take more time to process if the raw input is too big; and, second: because morse code does not support capital letters, I had to modify the task to tell Tasker where the capital letters are, by adding a sequence of numbers next to the encrypted code, so it can make it insecure, and also will requiere more time to process. (USE ENCRYPTION AT YOUR OWN RISK)
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
What the current project does?
It was originally designed to only translate plain text (letters and numbers) into morse code. But during these days I managed to add some new features, and also rework all the tasks, and this is what I got: translate text or numbers (+ signs) into morse, and vice versa; encrypt/decrypt both translations (or raw inputs) using Cipher with AES protection (128/192/256bits); merge all the previous existing tasks into a single one (MC - Translator); added some new parameters to control it from a second task (MC - Start); permanent notification with the current status of the task, and a few more things.
How does it work?
First, we need to take a look at the 4 main tasks: 'MT - Start', 'MT - Stop', 'MT - Translator' and 'MT - Key Generator'.
- Start: Here we will have to set every of the available paramaters to pass to the task who really does the job. Them are: Message, where we will write the string (text, numbers, signs); Translation, this will tell Tasker what we want to translate from and to (alpha-morse or morse-alpha), and the available commands are: 'A-M' and 'M-A', respectively; Encryption, with it we can encrypt and decrypt strings, and the args are: '0', 1-KEY', '2-KEY', where (0) means disabled, (1)-KEY is to encrypt, and (2)-KEY decrypts the passed string from 'Message', and where 'KEY' appears we will need to write our own AES key; Interpretation, does the job of playing the translated string into Sound (beeps), Vibration (pattern) and Flashlight (pattern), and to control it: 'S' = sound, 'V' = vibrator, 'L' = flashlight (take into account that morse to alpha will only use Voice to play what we sent to it); Clipboard, it will allow us to automatically copy contents of main task to clipboard, for example useful when we use encrypt feature, because as Morse doesn't recognize capital letters, I had to modify the output string to allow Tasker to understand it and also decrypt it correctly.
- Stop: It just manages all the actions to does just one thing: stop the main task immediately, after pressing on the notification (Processing..., Playing...). So, you can decide, if the message is too long and want to stop Tasker from doing the hard work, just press the notification. Also works while playing the translated string. (you DO NOT HAVE to toggle the associated profile manually, but Tasker will)
- Translator: So here we are with the main task that does the job. I think will better not to explain how it works. Take a look and understand what it does ;) But what I can tell is: A4-A11 stores all the characters and associated morse code for translation, so may have to edit them to fit your requirements.
- Key Generator: This is a stand-alone task to generate our own random keys, to use with Cipher actions. You can decide how long and secure will be the password by choosing from 16, 24 or 32 hardcoded characters (128/192/256bits). But take into account that, first: using encryption will increase the final string lenght to be translated, so if morse is choosed, it will take more time to process if the raw input is too big; and, second: because morse code does not support capital letters, I had to modify the task to tell Tasker where the capital letters are, by adding a sequence of numbers next to the encrypted code, so it can make it insecure, and also will requiere more time to process. (USE ENCRYPTION AT YOUR OWN RISK)
CREDITS
@SmartPhoneLover
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/project-music-control-control-your.html
#project #MusicControl
DESCRIPTION
Control your music app (any) using your hand, thanks to the proximity sensor.
CREDITS
@SmartPhoneLover
CHANGELOG
- fix: %time var values ( multiple conflicts) [thanks @MeloProfessional]
VERSION
v1.2
DESCRIPTION
Control your music app (any) using your hand, thanks to the proximity sensor.
CREDITS
@SmartPhoneLover
CHANGELOG
- fix: %time var values ( multiple conflicts) [thanks @MeloProfessional]
VERSION
v1.2
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/task-omnia-music-player-v10.html
#task #OmniaMusicPlayerIntents
DESCRIPTION
Intents for the Omnia Music Player app.
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
Intents for the Omnia Music Player app.
CREDITS
@SmartPhoneLover
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/task-podcast-addict-intents-v10.html
#task #PodcastAddictIntents
DESCRIPTION
Intents for the Podcast Addict app.
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
Intents for the Podcast Addict app.
CREDITS
@SmartPhoneLover
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/07/task-podcast-addict-intents-v11.html
#task #PodcastAddictIntents
DESCRIPTION
Intents for the Podcast Addict app.
Notes:
- To make 'Force Playback Speed' work, you have to enable the playback button (toggle) manually first, from within the app.
- Disable Variable Playback Speed works as expected, except it doesn't get updated (button) within the app. In other words, Tasker can manage to disable current custom speed, but if you go inside the app you will see the toggle enabled.
CREDITS
@SmartPhoneLover
CHANGELOG
- Fix: Added appropiate class and package name for matching fields, as new v4.x.x version of the app requires.
- Fix: com.bambuna.podcastaddict.service.player.customspeed intent was not correctly identified.
- Fix: com.bambuna.podcastaddict.service.download.toggle intent was not working.
- Other: Small changes.
VERSION
v1.1
DESCRIPTION
Intents for the Podcast Addict app.
Notes:
- To make 'Force Playback Speed' work, you have to enable the playback button (toggle) manually first, from within the app.
- Disable Variable Playback Speed works as expected, except it doesn't get updated (button) within the app. In other words, Tasker can manage to disable current custom speed, but if you go inside the app you will see the toggle enabled.
CREDITS
@SmartPhoneLover
CHANGELOG
- Fix: Added appropiate class and package name for matching fields, as new v4.x.x version of the app requires.
- Fix: com.bambuna.podcastaddict.service.player.customspeed intent was not correctly identified.
- Fix: com.bambuna.podcastaddict.service.download.toggle intent was not working.
- Other: Small changes.
VERSION
v1.1
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2019/05/task-poweramp-intents-v11.html
#task #PowerampIntents
DESCRIPTION
Intents for the Poweramp app.
CREDITS
@SmartPhoneLover
CHANGELOG
- Fix: pause intent not working.
VERSION
v1.1
DESCRIPTION
Intents for the Poweramp app.
CREDITS
@SmartPhoneLover
CHANGELOG
- Fix: pause intent not working.
VERSION
v1.1