#project #CheckDeviceOrientation
DESCRIPTION
This project will allow you to check the values in degrees of the orientation of the device in real-time.

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:
- A task for the same purpose is available here.
- If what you want is to know the orientation of the screen (not device), go here.
- To learn more about device orientation and how it works, go here.

CREDITS
@SmartPhoneLover

VERSION
1.0

#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

#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

#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

CHANGELOG
- Fix: (B/C): Long click event not working in some cases.
- Fix: (B/C): Tile was deactivated but timer continued to run on long click event.
- Fix: Not possible to set more than 59'59" (3599 seconds) from 'Setup' task.
- Other: Display timeout and tile are now restored and deactivated, respectively, when the device is rebooted for whatever reason.
- Other: Added some labels.
- Other: Small changes.

VERSION
v1.1

#project #FilenameChooserforEasyVoiceRecorder
DESCRIPTION
With this project you will be able to specify a custom name for audio files, just before starting the recording in Easy Voice Recorder app.

Available versions:
• Version (A): Audio files will be renamed as: DATE_TIME_FileName_DATE_TIME (if specifying extra info) or FileName_[#] (if no extra info).
• Version (B): Audio files will be renamed as: [DATE] [TIME] FileName [DATE] [TIME] (if specifying extra info) or FileName (#) (if no extra info).

Notes:
- This project was based on a request from a Reddit user. (reference)
- To delete Quick Presets, long press them.
- There's no need to configure any specific filename within EVR app. The project will work with any.
- When using this project, DO NOT use pause function. Otherwise, the file will be saved and renamed prematurely.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#project #SystemLocaleQSTile
DESCRIPTION
I have built this project for my personal usage, so I can switch system Locale (Android language) easily between my original language (Spanish) and the one used for all my projects (English), and others in some cases. Now, hope it helps to some of you in some way...

These are the available versions:
• Tasker QS Tile: It uses one of the 3 QS Tiles included into Tasker (1st in that case), and it changes locale and tile (name) based on predefined locale names (tasks).
• AutoNotification QS Tile: It uses one of the 40 QS Tiles available in AutoNotification (1st in that case), and it changes locale and tile (name) based on predefined locale names (actions).

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:
- To use this project SecureTask plugin is required.
- To allow the plugin to change locale in the background, CHANGE_CONFIGURATION permission needs to be granted to it. To do that, run this cmd: pm grant com.balda.securetask android.permission.CHANGE_CONFIGURATION.
- 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.
- To customize the project with your own langs use the 'Get Current Locale' task to get locale name.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#project #DeviceFloatingVolume
DESCRIPTION
It shows a floating bubble, in this case of identical appearance to that of my device, with useful information about the audio channel currently in use (changes on its status).

It works on the following audio channels:
• Alarm
• Call (in-call)
• DTMF
• Multimedia
• Notification
• Ringer (incoming call)
• System

These are the available volume panel models:
- Xiaomi Android 9 based (n° 1)
- Pixel Experience Android 10 based (n° 2)

Feel free to edit it as per your needs 😉

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:
- The default scene position for each audio channel (profile's tasks) is set to 0,0 (x,y), so you will need to adjust it according to your needs (yellow label).

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Added new volume panel model, based on my current ROM.
- Fix: UI update was slow.
- Other: Changed default position of scene to (0,0). (You will need to adjust it for your device)
- Other: Other minor changes.

VERSION
v1.2

#project #DeviceFloatingVolume
DESCRIPTION
It shows a floating bubble, in this case of identical appearance to that of my device, with useful information about the audio channel currently in use (changes on its status).

It works on the following audio channels:
• Alarm
• Call (in-call)
• DTMF
• Multimedia
• Notification
• Ringer (incoming call)
• System

These are the available volume panel models:
- Xiaomi Android 9 based (n° 1)
- Pixel Experience Android 10 based (n° 2)

Feel free to edit it as per your needs 😉

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:
- The default scene position for each audio channel (profile's tasks) is set to 0,0 (x,y), so you will need to adjust it according to your needs (yellow label).

CREDITS
@SmartPhoneLover

CHANGELOG
- Fix: Default scene position was not 0,0 (x,y).
- Fix: Volume panel model (2) was not adjusted to be shown in landscape mode.

VERSION
v1.3

#project #HeadsetButtonHelper
DESCRIPTION
This project will help you to keep your device in your pocket while on the street, gym, or wherever you are, by using the button of your headset (or BT headset) to perform whatever action you would like.

These are the available versions:
• Demo Version: If what you want is to import a clean version of the project to fully custimize it from 0, use this one. It doesn't include any specific action (opposite of mine), but just a set of 3 groups of actions as a generic implementation.
• Personal Version: If you would like to import a fully functional project, use this one. It includes all those actions that I currently use on my device, like: get current date and time, call a contact, check battery level, start/stop playing music, and maybe more, depending on my needs and tastes.

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 @plepleus and @Ratchet_Guy (Reddit) for the calendar base task (reference), @abhishekabhi789 and @gerardo246 for helping on building the project.
- To use this project you will need the AutoInput plugin, a TTS Engine (+ voice package) of your choise (IVONA TTS, if interested), and grant the 'android.permission.SET_MEDIA_KEY_LISTENER' permission to Tasker, if requested (guide). (These requirements are the basic ones for both projects versions)
- If the 'Personal Version' contains any error, I won't update the project just due to that. I will only release a new public version (including my current 'Personal Version') if the bug(s) affects the 'Demo Version' in terms of base functionatily. Sorry.
- It is highly recommended to disable media button listeners for music apps, or any other app you could have for this kind. Otherwise, the project may interfere with those apps, if not configured on it.
- To abort the current action, press the button (single tap) while the TTS engine is speaking. It will cause the entire task to be stopped and return to the previous state: 'Waiting for button pressed events...'.

CREDITS
@SmartPhoneLover
@abhishekabhi789
@gerardo246
@plepleus
@Ratchet_Guy

VERSION
v1.0

#project #CPUStats
DESCRIPTION
This project will give you the possibility to see the usage (%) of your CPU in real time, depending on the workload on each state.

Main features:
• Real-time usage
• Total CPU usage
• Per-core CPU usage
• Statusbar (text) or Overlay display.

The project is in an experimental state, so expect failures, or errors in the final calculations.

As I don't have a x86 device, the project will work but will propably not report correct values for CPU usage (regardless of the formula applied, containing errors or not), as the internal Kernel clock is measured in a different clock rate.

Notes:
- To use statusbar info style, AutoNotification will be required.
- Tasker is not the best way to monitor the CPU usage, as it runs on the main thread. So, use it at your own risk.
- Before setting up the project ('Setup' task) to allow it to show per-core usage, check if your device has a multi-core CPU. Otherwise, the project will fail to start.

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Ability to get multicore usage for compatible devices. (scene and notification)
- Other: Unchecked root usage for Shell Code action that gets the CPU info from '/proc/stat' file, as it was not necessary. (The project works on non-rooted devices)
- Other: Changed scene type to 'Overlay', so it won't affect elements behind it.
- Other: Other small changes.

VERSION
v1.1

#project #vip #TerminalLog
DESCRIPTION
This project aims to emulate the basic operation of apps like: Terminal or Termux, at least in the majority of commands and taking into account Tasker's own limitations, showing a command log report of its execution on the screen (stdout and stderr).

Notes:
- Avoid running cmds like 'logcat' (without params) or any cmd that runs indefinitely, because the project will probably get stuck. The Shell Code action is not adjusted to accept extra commands once it has been executed, by now.
- Some errors could be shown as normal STDOUT outputs, as they are not registered as 'Errors' actually. This is not a Tasker issue.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#project #vip #TerminalLog
DESCRIPTION
This project aims to emulate the basic operation of apps like: Terminal or Termux, at least in the majority of commands and taking into account Tasker's own limitations, showing a command log report of its execution on the screen (stdout and stderr).

Notes:
- Avoid running cmds like 'logcat' (without params) or any cmd that runs indefinitely, because the project will probably get stuck. The Shell Code action is not adjusted to accept extra commands once it has been executed, by now.
- Some errors could be shown as normal STDOUT outputs, as they are not registered as 'Errors' actually. This is not a Tasker issue.

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Added '$' and '#' symbols for commands executed as user or root-user, respectively.

VERSION
v1.1

#project #BitcoinMiningProfitabilityCalculator
DESCRIPTION
This project will help you to calculate the earnings of your mining hardware, providing you the total earnings (approximate) based on: power consumption (*), electricity cost (**), per-device income and the time it will be mining.

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 flaticon for the pics.
- This project won't provide you the current hashrates and/or possible earnings for your devices based on an on-line database. It just makes calculations based on pre-defined entered user data. But at least, you won't need internet access to make a quick calculation for approximate values. So, to get current and software based values for your devices, check appropriate web platforms.
- The project was based on bitcoin cryptocurreny type, that's why 'Bitcoin' appears on its name. But it can be used with absolutely any other type of currency, if needed.
- (*) To get the power consumption (watts) of your device/mining rig, you can check on-line references, specialized web services (OuterVision PSC, as an example), forums, or use a digital power meter (HiDANCE, as an example).
- (**) To get the electricity cost check your own bills, since they usually have it well detailed on the reverse. You can also get the taxes, if applicable.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#project #Energy3DOverlay
DESCRIPTION
This project was based on the Battery Meter Overlay app. So, it will act the same way, showing the current battery status at the top of the statusbar.

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:
- An extra profile (Apps) is included, but disabled by default. It will allow the scene to be hidden/shown based on specific apps when they are opened/closed. Configure and toggle it manually according to your needs.
- There's another project for the same purpose, but displaying the battery level as a horizontal line across the statusbar. (Energy Bar)
- If you want different colors than the ones included by default, contact me through this post or by Telegram, WhatsApp or Discord (also Reddit thread or AutoApps forum) to request it.

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Added new 'Rainbow' multicolor resources.
- New: Chooser dialog for 'Initial Setup' task to select the decided theme to apply on first setup.
- Fix: Wrong scale for battery indicator.
- Other: Added 'Initial Setup' task.
- Other: Make the overlay to be shown on first project import, without the need of restarting. (Make sure to run Initial Setup task after importing)
- Other: Deleted PSD resources. (Contact me by PM if you want custom colors)
- Other: Small changes (also to resources).

VERSION
1.4

#project #TaskerClockScreensaver
DESCRIPTION
Now you can have your own screensaver, the original Android style (clock app). But without having to depend on that app.

Notes:
- As the project calculates the position of the clock randomly on each pass taking into account the size of the main scene (Clock), you must resize it (including the 'Top Layer' element), according to the available dimensions on your device.
- If you prefer to continue using the original Android screensaver, you can use this task. (requires root)
- If you don't have virtual buttons (navbar) on screen, you can disable all optional actions from the 'Toggle Status' task.
- Single tap on the screen to close it.
- The project doesn't keep the screen on for a given time, it just shows the clock on the screen. The user will have to add the corresponding actions/task to keep it on the decided time.
- As an exmaple of a possible trigger, go here.

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Battery level.
- New: Next alarm (if set).
- Fix: Position of elements not readjusted when the device was rotated. (Position fix only happened at time change)
- Other: Increased animation delay (+1500ms) for a smoother experience.
- Other: Moved some settings to 'Setup' task.
- Other: Changed the way how elements are positioned, based on fixed offsets now. (*)
- Other: Added some labels.
- Other: Minor changes.

* Not really the best solution, but will make things easier for maintaining. It doesn't affect dynamic elements positioning, but manual offsets will have to be configured in 'Update Time' task manually, based on the position of each element (except for 'Text (clock)') from the scene.

VERSION
v1.2

#project #BatteryMonitor
DESCRIPTION
Here you have a project to be aware of the status of the battery while charging, providing useful information in real-time and helping to protect the battery and the device itself against critical temperatures and warning you when charged at a specific level.

These are the main features:
• Real time information (notification and floating scene)
• Battery level and temperature protection (charging limits).
• Enable/disable charging in the background (charging limits). (root only)
• Solid and colored battery icon, according to the current level (%).

This is the info you will know in real time:
• Connection type (AC, USB, Wireless)
• Estimated total charging time
• Input current (mA)
• Max input from charger (mA, V, W)
• Temperature (ºC/°F)
• Voltage (V)
• Watts (W)

An 'Initial Setup' task is included, which needs to be executed on first import, regardless of whether it is imported from TaskerNet or XML.

Although the project obtains the values from the system itself, these will never reflect the accuracy of those returned by specific power meters.

Notes:
- Thanks to @AndersonMarcio, @cruzer_blaze2, @GeovanDamascenofor, @gerardo246, @MeloProfessional and @Valdorg for helping on building and testing/debugging the project.
- Here you will find the task from which the color animation feature was based on. (Credits: @MeloProfessional)
- Single click the notification to show 'Desktop View' mode.
- During the first seconds or perhaps minutes, some of the values may not appear. That's because Tasker must wait for the intent to collect all the corresponding data. If some of them remain unset for a long time, that means that your device doesn't support retrieving such information, or the project is not yet adapted for your device.
- The capacity (%) and temperature (ºC/ºF) can be used as charging limiters to protect the battery and the device itself. When a certain value (configured from 'Setup' task) is detected during charging, the device will automatically cut off the power even if the charger remains plugged in, if rooted; and, a notification (voice) will begin to warn of this situation, if not rooted.
- By default, the 'BM - Timer' profile (trigger: temperature) will check every 10 min if charging can be resumed without user interaction. Configure it according to your needs.
- The file(s) that allows cutting off the power and resuming charging in the background, if supported, must be configured for your device. Look for the actions labeled as yellow (Enable/Disable Charging) on 'BM - Collect Battery Data' task and the task linked to the 'BM - Timer' profile.
- If Tasker fails to write to the 'Enable/Disable Charging' file, try using 'chmod +rw' or a permission that works for you.
- To find the right file(s) for toggling charging in the background, if available for your device, you can try 'ACCA' app, or 'Tasker Charging Switch' project (Credits: @MeloProfessional).
- If you don't know the battery design capacity of your device you can get it using this profile.
- If you see the 'time_error' message for charging time, that means that your SDK is not the minimum required and there was an error getting mAh of your battery. So, you will need to configure the capacity from 'Setup' task, manually.
- A debug task (Debug Task) is included in case the user has problems with erroneous values or not shown. Follow the instructions inside it to know how to use it.

CREDITS
@SmartPhoneLover
@AndersonMarcio
@cruzer_blaze2
@GeovanDamascenofor
@gerardo246
@MeloProfessional
@Valdorg

- BY TYPE -
#vip (vip content)
#project (projects)
#profile (profiles)
#task (tasks)
#scene (scenes)
#tutorial (tutorials, guides...)
#warning (channel messages and other news)

#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

CHANGELOG
- Fix: 'Export' button was not saving the file to the specified location set within 'Setup' task.
- Fix: Small error that showed the error triangle from one of the project's scenes. (didn't affect the main functionality)

* I decided to stop supporting this project because of the complexity in terms of the huge number of intents that actually exists for Android, and not only for the system itself, but each device in the world. So, if you want to continue this work, you are fully free to use it as a base, re-edit it as well, or creating an Android app including its intents.

VERSION
v1.1