#project #IntentsBroadcastMonitor
DESCRIPTION
Intents and its broadcasts are very useful to allow apps communicate each other, also system broadcasts can be used to trigger almost everything in Android.

But, when we want to take a look at the information sent within an intent (extras) to react somehow and carry out something, the official documentation, especially in the case of Android system intents, there are times that we cannot find clear references to all the extras. This is because device manufacturers, when customizing their base systems (ROMs), they rebuild part of the original Android code, adding/removing information sent and received from some of the system intents.

Therefore, this project, originally based on the Internal Broadcasts Monitor app, will help you to capture sent intents (by system or other apps) and absolutely all its extras that your device/app is capable of generating in each intent (if they contain any). And all in real time.

Main features:
• Receive intents and all its extras in real time.
• Colored information (date, time, intents count, intents names...)
• Hide/Show the scene to allow keep receiving intent information in the background. (*)
• Stop/Start control buttons to stop receiving broadcasts, or register them again.
• Export results to TXT file. (*)
• Receive intents from Android system as well as third-party apps (if installed). (**)

Notes:
- Thanks to @joaomgcd and @sdfsung (Reddit) for helping on building the project. (reference)
- (*) All these options are accessible from the generated notification (buttons), once the project is launched.
- To know what are the intents that the project is capable of monitoring, here you have a complete list: Android System and Third-Party Apps. They will be updated as new intents are included in future versions, if possible.
- Use Show Intents List task to view all the included intents in off-line mode. (Colored ones are the last included)
- (**) Two versions of the project are available to download. The first one (Android System Intents = A) will listen to all the intents coming from the Android system, only; the second one (Third-Party Apps Intents = B) will listen to all the intents coming from 3rd party apps, only. (Do not use both at the same time)
- All the profiles are configured with a Cooldown Time of 1 sec to avoid receiving aggressive (redundant) broadcasts. If you need to listen to an intent without restrictions, set the Cooldown Time to 00:00:00:00 for the corresponding profile.
- If Tasker alerts you about queued tasks number have been exceeded, try increasing the Maximum Tasks Queued value from its Preferences.

CREDITS
@SmartPhoneLover
@joaomgcd
@sdfsung

VERSION
v1.0

#project #BackgroundMusicPlaybackResumeforTwitter
DESCRIPTION
As many users may know, Twitter does not resume music playback if it was previously active after closing/exiting from a video within the app. It just stops it (possibly by sending an 'stop()' call from 'AudioManager' using 'AudioFocus').

So, this project is an experimental attempt to try resuming the background music playback, if any, after exiting from a video within the app.

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:
- It was based on a user request from Reddit. (link 1/link 2)
- As the project uses the Logcat Entry profile to detect video playback (activity), the android.permission.READ_LOGS permission will have to be granted to Tasker. (instructions)
- If you haven't previously done it, you will have to disable automatic video playback: Profile > Settings and Privacy > Data Usage (General) > Video Autoplay (Video) = 'Never'.
- I have used the 'resume' Poweramp intent from here. But you can use your own intents, or the 'Media Control' action if you want.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#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

#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!