#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

#profile #ListenForVolumeChangesDynamically
DESCRIPTION
With this profile you can listen for volume changes on every channel, retrieving: current audio channel, last value changed and also the previous (old) value before it got changed. And with a single profile.

As the profile is right now, it only shows the above mentioned data, so its usefulness will be reduced to that. But it may be useful to you in a future project or profile where you need to identify the audio source or the previous level when it has changed.

Notes:
- I don't know why the intent is sent more than once when changes are detected (not documented, or I couldn't find the reason), so a delay of 20ms (optional) is included at the top of the actions within the linked task.
- The intent is categorized as @hide (not officially documented) and has three extras "officialy" reported: EXTRA_VOLUME_STREAM_TYPE, EXTRA_VOLUME_STREAM_VALUE and EXTRA_PREV_STREAM_VOLUME. But it is sent with an additional extra for me: EXTRA_VOLUME_STREAM_TYPE_ALIAS. So, you can the use my Intent Broadcast Monitor project to check what extras are sent for you actually, if needed.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#tutorial #HideVoiceDialogAndLongPressedMenuAutoVoice

#task #RerouteAudio
DESCRIPTION
I have managed to reroute audio from one channel to another on Android, and using only Tasker. Therefore, it will no longer be necessary to use the well-known SoundAbout app, at least with the most common audio channel: Multimedia.

These are the available routings:
• Headphones > Speaker (and viceversa)
• Headphones > Bluetooth (and viceversa)
• Speaker > Bluetooth (and viceversa)

Notes:
- The values and the way how the task manages the audio routing were based on my current device and ROM. So, it could work or not for your device.

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Headphones > BT & BT > Headphones
- Other: Changed task name.
- Other: Other minor changes.

VERSION
v1.1

#task #TogglePixelStyle
DESCRIPTION
This task will allow you to switch between all your available Android themes (Styles) if using a Google Pixel device, Pixel Experience custom ROM, or any other custom ROM based on Pixel devices.

Notes:
- This task was based on a request from a Reddit user. (reference)
- The 'android.permission.WRITE_SECURE_SETTINGS' permission will have to be granted to tasker for non-rooted devices (guide), and 'android.permission.WRITE_SETTINGS' too.
- All of the properties from every action were based on my current device and ROM, so I would suggest you to find and use yours instead. Just to avoid possible problems.
- Styles are managed by the Google Wallpaper app, but its settings could exists or not on the Secure Settings table (or maybe other), as custom ROM devs can make some redirection for the app to not allow it to save/load content from Settings tables. If it's your situation, try looking at '/data/data/.../shared_prefs/*' (root required) to try changing app's values by this way.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#task #CheckKeyguardStatus
DESCRIPTION
Here you have a little task that will help you to get more information than the 'KEYG' built-in variable, about the device lock status.

Quick information:
• Device Locked: The device is locked and asks for authentication in order to use it.
• Device Secure: The device is protected (service), regardless of if the protection mechanism is not currently required to use the device.
• Keyguard Locked: The device is locked and doesn't ask for authentication in order to use it.
• Keyguard Secure: The Lockscreen is enabled (service), regardless of if the device is locked or not.

The Device/Keyguard Locked represents the current state of the device, and Device/Keyguard Secure represents the general configuration of the device.

CREDITS
@SmartPhoneLover

VERSION
v1.0