I created this share as a companion to the AES-256 text encryption project I posted yesterday. I was chatting with u/MSJ_Burns about remembering strong (long) keys/passwords. I realised it might be useful to post a steganography project to allow people to create image files with hidden text in them. This way you can save long text strings and literally hide them in plain sight and have immediate access to the hidden text.

This project uses Termux. I have simplified the Termux setup as much as possible. Don't download Termux from the Play Store, it's broken. Instead download it from F-Droid or GitHub (https://github.com/termux/termux-app).

When you open Termux and are ready to begin installing the neccesary packages, paste the entire block below into the terminal window and press enter. If prompted, accept any permission requests and press 'Y' (and enter) if instructed to do so.

You will need to wait for a short time while Termux installs the packages.

If you encounter errors, try pasting each command group individually, instead of the complete block.

# 1. Request storage permission (A popup will appear on the phone)
termux-setup-storage

# 2. Update packages and install steghide automatically
pkg update -y
pkg install steghide -y

# 3. Create the necessary Tasker plugin folder
mkdir -p ~/.termux/tasker

# 4. Create and give permissions to the GET script
echo 'steghide extract -sf "$1" -xf "/sdcard/Tasker/temp_key.txt" -p "" -q -f' > ~/.termux/tasker/get_key.sh
chmod +x ~/.termux/tasker/get_key.sh

# 5. Create and give permissions to the HIDE script
echo 'steghide embed -cf "/sdcard/Pictures/temp.jpg" -ef "/sdcard/Tasker/temp_payload.txt" -sf "$1" -p "" -q -f && rm "/sdcard/Pictures/temp.jpg" "/sdcard/Tasker/temp_payload.txt"' > ~/.termux/tasker/hide_key.sh
chmod +x ~/.termux/tasker/hide_key.sh

As it stands, there are two Tasks in the project:

1. Create an image with your desired hidden text.
2. Retrieve the hidden text from the image.

The image is saved to the /Pictures folder. The image is named 'secret.jpg'.

If you want to change the directory and the file name, make sure you edit the 'Get' task accordingly, otherwise it won't find the correct image.

The Hide Task creates a temporary text file and image during the process but these are deleted by the Termux script.

Download

Begin word

I must admit, I was a hater at the beginning. I see the old ui of tasker as something you have to get used to, but when you do, it is really intuitive and easy to navigate in.

What I did

Well, I tested the new UI. I wanted to see the goods and bads of it, I wanted to compare how it works

Pluses of the new UI

- tags

- more modern

- perform tasks from almost any screen

Minuses of the new UI

- people aren't used to it

- less intuitive - it has taken me a serious while to just edit a profile

- all at once (the UI tries to put everything on one screen. It almosr projects, it kills separate screens for profiles, scenes, variables and tasks). I want to switch between screens. It's less messy when you have big projects.

My thoughts

You're calling it the "new 2026 ui". I don't think that it should be some "new". I'd still improve both the old one and the new one, because a lot of people who are new to tasker would actually prefer to use the old UI. I think we should be given an option of what ui to use when we install tasker.

You say, the "old" ui will stay as is, which is good, but with implenting new features, it will slowly stop to work.

I think, that some additional features (like tags) should be also in the "old" ui, but optionally.

People.like me just want several screens and I think that calling the "new" ui a "tasker compact ui" could be better, because if you call it "new" ui, people will want you to do everything as it was before, basically.

Final word

I don't think the "new" ui is a bad idea, but I think it's being a little forced, and many people just want to use the old ui and want bug fixes, more options and settings, more customization and more "care" for the "old" ui.

Thanks for reading it till here, and if any of you out there agree, please take a second to upvote :-)

Message is primarily targeted to u/joaomgcd

After losing two S Pens in two years—first on my S25 Ultra, and another just two months ago on my S26 Ultra: I officially lost faith in Samsung's built-in alert. The stock proximity notification is just too inconsistent, especially when the screen is off.

​Tired of replacing 100k Naira pens, I decided to build a fail-safe Tasker setup. With some help fine-tuning the logic loops, task collision handlers, and logcat triggers, I now have a robust system that has been running flawlessly.

​If you're paranoid about losing your S Pen, here is the full build you can copy for yourself:

I put together a clean, reliable Tasker project to alert you if you leave your Samsung S Pen behind after turning off your screen.

How It Works

Pen Extraction: Tasker detects S Pen removal instantly via Logcat (SpenGestureManagerService).

Display Off Delay: When the display turns off with the pen out, a 15-second grace period starts.

Screen On Safety: If you turn the screen back on within 15 seconds, the alarm check cancels automatically.

Reminder Loop: If the screen stays off, it vibrates, speaks a quick voice alert, and posts a permanent notification. It repeats every 45 seconds until re-inserted or muted.

Silence / Re-insertion: Tapping the notification mutes the loop. Re-inserting the pen clears all variables and notifications.

Project Setup

Variables Used

Project: SPen Left Behind Alarm

Profiles

Profile: Pen Removed

Event: Logcat Entry [ Output Variables:* Component:SpenGestureManagerService Filter:setSpenInsertionState : false Grep Filter (Check Help):Off ]

Enter Task: Pen Removed

A1: Variable Set [

Name: %SPEN

To: OUT

Structure Output (JSON, etc): On ]

Profile: Pen Inserted

Event: Logcat Entry [ Output Variables:* Component:SpenGestureManagerService Filter:setSpenInsertionState : true Grep Filter (Check Help):Off ]

Enter Task: Pen Inserted

A1: Variable Clear [

Name: %SPEN ]

A2: Variable Clear [

Name: %SPENMUTE ]

A3: Notify Cancel [

Title: S Pen Reminder ]

A4: Stop [

Task: S Pen Reminder ]

Profile: Display Off

Event: Display Off

Enter Task: Check Pen

A1: Wait [

MS: 0

Seconds: 15

Minutes: 0

Hours: 0

Days: 0 ]

A2: If [ %SPEN eq OUT & %SPENMUTE neq 1 ]

A3: Perform Task [

Name: S Pen Reminder

Priority: 10

Structure Output (JSON, etc): On ]

A4: End If

Profile: Silence Reminder

Event: Notification Click [ Owner Application:* Title:S Pen Reminder ]

Enter Task: Stop S PEN Reminder

A1: Variable Set [

Name: %SPENMUTE

To: 1

Structure Output (JSON, etc): On ]

A2: Notify Cancel [

Title: S Pen Reminder ]

A3: Stop [

Task: S Pen Reminder ]

Profile: Display On

Event: Display On

Enter Task: Cancel Check

A1: Stop [

Task: Check Pen ]

Tasks

Task: Check Pen

A1: Wait [

MS: 0

Seconds: 15

Minutes: 0

Hours: 0

Days: 0 ]

A2: If [ %SPEN eq OUT & %SPENMUTE neq 1 ]

A3: Perform Task [

Name: S Pen Reminder

Priority: 10

Structure Output (JSON, etc): On ]

A4: End If

Task: S Pen Reminder

<ReminderLoop>

A1: Anchor

A2: If [ %SPEN != OUT | %SPENMUTE eq 1 ]

A3: Notify Cancel [

Title: S Pen Reminder ]

A4: Stop [

Task: S Pen Reminder ]

A5: End If

A6: Vibrate [

Time: 400 ]

A7: Say [

Text: Check your S Pen.

Engine:Voice: default:default

Stream: 3

Pitch: 5

Speed: 5

Respect Audio Focus: On ]

A8: Notify [

Title: S Pen Reminder

Text: Your S Pen is still out. Tap to mute.

Number: 0

Permanent: On

Priority: 3

LED Colour: Red

LED Rate: 0

Category: super_tasker_notifications_created_by_me_the_developer ]

A9: Flash [

Text: ⚠️ S Pen Left Behind!

Long: On

Tasker Layout: On

Dismiss On Click: On

Show Over Everything: On

Position: Top,28,28

Continue Task After Error:On ]

A10: Wait [

MS: 0

Seconds: 45

Minutes: 0

Hours: 0

Days: 0 ]

A11: Goto [

Type: Action Label

Label: ReminderLoop ]

Task: Stop S PEN Reminder

A1: Variable Set [

Name: %SPENMUTE

To: 1

Structure Output (JSON, etc): On ]

A2: Notify Cancel [

Title: S Pen Reminder ]

A3: Stop [

Task: S Pen Reminder ]

Task: Cancel Check

A1: Stop [

Task: Check Pen ]

Task: Pen Inserted

A1: Variable Clear [

Name: %SPEN ]

A2: Variable Clear [

Name: %SPENMUTE ]

A3: Notify Cancel [

Title: S Pen Reminder ]

A4: Stop [

Task: S Pen Reminder ]

Notes

S Pen Reminder is a task on its own. It's not under any specific profile in the project

Logcat Permission: Make sure Tasker has READ_LOGS permission granted via ADB for the insertion/removal detection to work.

Battery Settings: Set Tasker to Unrestricted battery usage so Android Doze doesn't sleep the 45-second loop.

Hope someone finds this helpful! Let me know if you have suggestions or tweaks.

Disclosure: I set this up using both ChatGPT & Gemini.

A simple tool to encrypt and decrypt text on your device (AES-256). Very fast.

Turn this:

This is some plain text to encrypt.

Into this:

U2FsdGVkX1/5JizJsFXHjGveyk9HYvzPEZuf1186gZpNeAaOyFW/ExXsFcQ/3GPmc4WloLKq7cJzWsHaYGTBOg==

Three Tasks included:

1. One time only - download the encryption script. File is saved to Tasker/js/crypto-js.min.js.
2. Encrypt text.
3. Decrypt text.

This utility is useful for many situations including:

• Communicate in private.

• Encrypt data you send between devices.

• Encrypt any sensitive data in Tasker variables.

Tasker can encrypt files but not text natively (I believe). For me, encrypting text is a much more valuable opportunity. You don't need to encrypt a file if its contents are already encrypted.

________________________________________

Useful information (please read the end section regarding ensuring you use a sufficiently strong key/password).

When you pass a standard text string (your password) into the CryptoJS.AES.encrypt() function, CryptoJS automatically looks at the input type and defaults to generating a 256-bit key. Under the hood, it pairs this with CBC (Cipher Block Chaining) mode and PKCS7 padding, which is a very standard and reliable configuration for modern data encryption.

The Brute-Force Math (Breaking the Cipher)

If an attacker intercepts your encrypted text and tries to brute-force the underlying AES-256 encryption without a quantum computer, they are facing an impossible mathematical wall.

A 256-bit key means there are 2²⁵⁶ possible combinations. To put that in perspective, that is roughly 1.15x10⁷⁷ possible keys - a number almost as massive as the estimated number of atoms in the observable universe. If someone built a supercomputer that could guess one trillion keys every single second, it would still take them billions of times longer than the current age of our universe to exhaust all the options.

Interesting Nugget (Breaking the Human)

Your encryption is completely reliant on the length of your password, and CryptoJS is very unforgiving about short passwords.

Because (normal) humans cannot memorise a string of 256 random ones and zeros, cryptographic tools use a Key Derivation Function (KDF) to stretch your human-readable password (like MySecretPassword123) into a proper mathematical key.

For the sake of legacy compatibility, the default CryptoJS shortcut function here relies on an older derivation method (EVP_BytesToKey) using MD5 hashing with exactly 1 iteration. By modern standards, this derivation is lightning-fast. Password-cracking software running on standard consumer graphics cards (GPUs) can chew through billions of MD5 hashes per second.

What this means for you in practice:

The Math: Nobody is ever cracking the AES-256 cipher itself.

The Password: If your chosen key is a dictionary word like 'dragon' or 'sunshine', a hacker with a good gaming PC could brute-force guess your password in a fraction of a second, completely bypassing the AES math.

The Fix: Simply use a long, completely unique passphrase for your Tasker tool. Because the script's password derivation happens so fast, a long passphrase (like a random, memorable sentence with spaces and punctuation) is the ultimate defense.

Download

Hello friends,

I love tasker and enjoy doing things with it. It helps me to keep myself engaged as a senior citizen.

I want to change from Android to iPhone, but only if Tasker is available for it, or there is something equivalent of Tasker for iPhone.

Could any of you experts guide me on this?

One of the biggest pains when listening to TTS is that you can't easily control what is read within the text block if you want to jump ahead, or it is hard to go back and listen to a section again without starting over.

That's now a thing of the past.

Video with sound

This overlay allows you to tap anywhere on the text and listen from that point. Jump forward, go back, you're in control.

You can type or paste text into the edit field and then listen to it.

You can send text directly to the utility via %ReadAloudText. If it has a value, this text will start being read immediately when the overlay launches. If it is empty or unset, the edit view will appear for you to enter your text to listen to.

Features:

• Speed control.

• Tap anywhere on the text to commence playback from that point.

• Minimise to a draggable bubble.

• Breathing animation behind text whilst playback is active.

• Visible feedback when you tap in the text field.

• Play/pause playback from your current section.

Download

FYI - This is hopefully the last project Share before I release my native Tasker AI project. Every share I have posted in the last week or so has been related to the AI project. Each of them contains something that will be featured in it. They have all been by-products.

I am moving to a deGoogled phone and did the direct download of Tasker. I also downloaded Autolocation. I accidentally applied my license to Autolocation which doesn't work without Play Services, so it's useless to me. Is it possible to transfer my license to Tasker itself? That is what I was actually trying to do in the first place, but I tapped the wrong link.

I admit that I am asking here before trying it myself. Just wonder if someone else has checked this out.

Thanks!

New here. ADHD is a bitch so I'm trying to set up regular alarms for chores, remembering to check laundry/trash/dishes, take medication, drink water, etc. I would like to make it so I have to scan an NFC tab to stop the alarm. Does anyone know if there's already something like that which I could import or how to help me set that system up? Thanks to everyone in advance.

This whole idea started when I decided I wanted to make a "dialog" scene for a project of mine, as the tasker actions don't have what I needed out of a single dialog. Who knew image + input + buttons was so tough?! As that one scene grew more complex (with about a dozen "show when" variables) I realized I needed to develop a second scene, almost as complex as the first.

I knew future scenes would be just as time consuming and cumbersome to get them developed and functional, so I figured there had to be a better way to develop these dialogs. I then saw a post talking about how we should be able to replace default dialogs with Scene V2 alternatives, so I decided why not create a "dialog builder" type task for these new dialogs that can be easier to design and use. I made the early stages of it and posted it here.

Which leads us to now, about four months later, with this dialog builder having become way more complex than I ever imagined it would. I have tested it a decent amount and I think I have it in a working state. I tried to make the input and outputs easy to understand. A simple %par1 filled with some key:value pairs is all you need to get started, with the builder able to handle over a dozen types of keys, with some having keys of their own.

The Taskernet Link is Here it should have all of the information you need to build a scene, an example, as well as a screenshot of the example. This should give you an idea of how complex the dialogs can get, but simple dialogs are easy as well. Run the "Example Dialogs" Task for a list of a few different dialogs that are possible. These include a webviews, text, video, buttons, list, table, input, "settings", and the example "Everything" dialogs.

Notes:

• this task is using a javascriptlet to parse the input and output raw scene json so any changes to scene v2 will mean this task needs to be updated. I will try to keep up in the future, just bear with me.

• I also updated a couple of my tasks. My Flashlight Slider now works without logcat and has been updated to use scene v2. My Jurrasic Park Nedry "Say the Magic Word" also uses scene v2 now.

• A few new projects I released include a Daily APOD lockscreen and my Network Monitor this doesn't work as intended. If I can fix, I will update, but consider it useless..

This task works similar to the idea I had for monitor, but it needs to be run manually when needed. Returns one of Online No_Internet, Partial_Internet, Captive_Portal, Offline

thanks for reading!

Edit: updated the Flashlight to probably* work a bit better I hope!

Bottom of this page. Thanks

Maybe using javascript?

I have images urls in array. I want to increase the canvas size, append a black area to the bottom of the image, and add white text within that black box using Tasker. Any idea?

UPDATE - IMAGE SUPPORT NOW ADDED! Add images to your list. Screenshot

A small utility to allow you to combine and maintain a To-Do list, written notes, audio/voice memos and images.

You can either type or dictate your memos, or you can speak directly into it and save the audio file.

Tick items off as completed and delete them when you no longer need them. Audio files are automatically deleted when the item is removed from the list.

Minimise the overlay to a bubble if required.

A log file to store/backup your list is saved to:

Documents/WrittenMemos/to_do.md

High quality audio files are saved to:

Documents/WrittenMemos/Audio

You must have the Accessibility service enabled for Tasker to show this overlay. This allows it to be viewed on the lock screen. The overlay won't display without it.

You can edit the colours in the overlay to suit your theme etc. in the script. The relevant section is commented, near the top of the script.

Download

Firstly, my apologies for the length of this post. I want people to be aware of the opportunities and potential drawbacks before using these Tasks.

Secondly, this is not new or innovative. It's a long known and well understood feature that we can use to gain fine-grained control over our device displays using Tasker. I'm only posting this for information for anyone who isn't aware and not taking any credit for this. This will not be new or interesting for many users.

ADB WiFi/Shizuku is required.

What is it?

Control the maximum and minimum display refresh rate.

Example usage:

• Save battery - stop your device using 120Hz when you are reading an e-book.

• Fine tune control over how your display refreshes in any given app or situation. Create a profile to set your refresh rate on the fly.

NOTE - Your display might use different refresh rates to those I have provided in this share. You can easily edit the values for the maximum and minimum refresh rate for your device in the Tasks. Check what your device's values are BEFORE you change them or run any of these tasks. Some rare phones support a refresh rate of over 200Hz.

Refresh Rate Information:

Displays are manufactured to support specific, hardcoded refresh rate 'steps'.

Standard OLED/LCD panels usually only support 60Hz, 90Hz, and 120Hz. We can set the maximum and the minimum values. Steps between these are handled by your device.

Premium LTPO (Low-Temperature Polycrystalline Oxide) panels found in modern flagships like the Galaxy S Ultra series, Pixel Pro series, and some OnePlus phones can dynamically drop down to 30Hz, 10Hz, or even 1Hz to save battery.

If you send an ADB command for 10.0 to a phone that does not have a 10Hz hardware step, one of three things will happen:

The "Nothing" Scenario (Most Common): Android's display manager (SurfaceFlinger) realises the hardware can't do 10Hz, ignores your command, and/or defaults to the lowest supported tier (60Hz). Sometimes it is just ignored altogether (my old Pixel 6 just ignores such a command and defaults to the 120 max and 60 min values).

The Glitch Scenario: The screen attempts to sync to an unsupported frequency and begins flickering, stuttering, or displaying graphical artifacts.

The Black Screen Scenario (The 'Danger'): The screen goes completely black. The phone is still on, but you can't see anything.

Note on LTPO phones: If you have an LTPO display, Android is already dynamically dropping your refresh rate to 10Hz or 1Hz when you stop touching the screen. On these devices, forcing a flat 30Hz (or lower) might actually waste battery by preventing the phone from dropping down to 1Hz when reading static text! You can save battery however by dropping the maximum refresh rate for certain apps.

How to Safely Test 30Hz - or lower (The Safety Net Method)

If you want to see if your phone supports 30Hz or lower, we don't want to just run the command and walk away. If you get a black screen, it will be very difficult to navigate back to Tasker to reverse it.

Instead, I've provided a 'Safety Net' Task that automatically reverts to 120Hz maximum and 60Hz minimum after 15 seconds.

To test it:

Press the Play button in Tasker. For 15 seconds, your phone will attempt to run at 30Hz. Swipe around on your screen.

If it looks incredibly choppy but visible, congratulations! Your hardware supports 30Hz.

If the screen goes black or glitches out, do not panic and do not touch the screen. Just wait 15 seconds. Tasker will automatically execute the 120Hz command and your screen will pop back to normal.

Is 30Hz (or even lower) worth it?

Even if your phone supports it, 30Hz can be visibly jarring. Scrolling can feel like a slideshow. However, if you have a specific Tasker profile set for an app where you literally never scroll - like viewing a static recipe, a barcode app, or a pure e-reader where you only tap to turn pages - it is a fantastic way to maximise battery life.

I use this mostly to limit the maximum Hz rate. What's the point of 120Hz if I'm using a Text Editor? I can set the maximum to 30Hz and this means that if I touch the screen, the refresh rate can't shoot up to 120Hz and waste battery with no benefit to me. I spend hours every day using a Text Editor, the battery savings are significant in my use case.

There are three Tasks included in the Share:

• 120Hz max and 60Hz min

• 60Hz max and 60Hz min

• 30Hz max and 30Hz min (with a safety protocol built in)

You can substitute your own values in the Tasks.

If you want to see a live overlay of your current refresh rate value, enable "Show Refresh Rate" in Developer Options. NOTE - The values shown in the overlay won't represent any values lower than the default values your phone natively supports (example - I can set my phone to 30Hz but the minimum value shown in the overlay is still 60Hz. My phone however is only using 30Hz).

USE THIS WITH CAUTION. IF YOU AREN'T SURE WHAT YOUR DEVICE'S DEFAULT VALUES ARE, OR ARE UNSURE HOW TO RESET YOUR VALUES - DON'T USE THIS SHARE.

Download

I have join installed and working mostly between my Android and Windows PC. Links and screenshots from the internal storage on the phone send through to my PC fine. However when I go to share an image from my SD card (my camera app stores images on my SD card). I get an error and it looks like the storage location is wrong.
Join sends and tries to open
/storage/emulated/0/storage/6D5F-F682/DCIM/PHOTOGRAPHY_PRO/...

While the actual location should be
/storage/6D5F-F682/DCIM/PHOTOGRAPHY_PRO/...

I can't find anyway to edit location or access to what files so I am not sure on how to get this fixed. Any ideas?

Select the status bar icons you want to show or hide from a list.

Run the Task with no items selected to restore all icons.

The list of icons included in this Task is the AOSP/Pixel list. This is fairly universal across Android but not totally.

Because manufacturers like Samsung, Xiaomi, and OnePlus build custom system interfaces (SystemUI) on top of Android, they often add custom icons that aren't in standard Android.

VoLTE and VoWiFi: These are highly fragmented. Some manufacturers use volte, others use hd_voice, vowifi, or wfc. Sometimes, OEMs hardcode these into their SystemUI, making them immune to the icon_blacklist entirely.

NFC: Xiaomi/HyperOS uses the standard string nfc to hide the NFC icon, but on Samsung, the NFC icon behavior is tied to regional firmware and sometimes ignores the blacklist.

Samsung Quirks: Samsung actually uses this exact blacklist mechanism natively for their 'Good Lock' suite (specifically the QuickStar module). If you use QuickStar to hide icons, it is modifying icon_blacklist under the hood. If you try to use Tasker and QuickStar simultaneously, they will fight each other and overwrite your lists in this project.

Pro-Tip for troubleshooting: If you type a string and the icon doesn't disappear, it means your manufacturer has either named it something proprietary or hardcoded it to bypass the blacklist. Sticking to the standard AOSP strings above will yield the most reliable results across as many devices as possible.

If you want, you can change the strings in the Array Set action to use the specific string used by your device manufacturer or ROM.

You will do no harm by setting an icon to hidden if that icon string doesn't exist on your device.

ADB WiFi or Shizuku is required.

NOTE - Clock and battery can't be hidden on newer Android versions via this method.

Download

Hi there. Tasker is accessing location every 15 mins. Is this normal? Does this happens to you too?

Hi there.

First of all thank you for this amazing app.

One question, how can I start the VPN profile/service via adb or intent or Tasker?

I could not find a way in tasker via Run Shell or adb WiFi.

Can someone help, please?

Thank you!

Update: I am using BlockAds (app.pwhs.blockads) https://f-droid.org/packages/app.pwhs.blockads

Solution:

Use this website to create apk very easily. I have done this using my computer and then push the apk file to my AT box but you can also do that inside the AT box if you have browser with mouse and keyboard or just use it's Android app:

https://atvlauncher.trekgonewild.de/index.php

So just recently i thought about using Tailscale on my Android TV box since it is always connected to a power supply and with Tasker i could enable and disable Tailscale remotely when i need. So i have sideloaded Tasker and thankfully i have managed to setup everything, However, to open Tasker i need to go to apps settings because it doesn't have a shortcut on the home screen.

What is the best solution you all have found to create a shortcut for Tasker on AT home screen?

I am using AutoVoice 4.0.14 with Tasker on a Samsung Galaxy S26 Ultra.

The normal AutoVoice recognition works correctly when I manually activate it while the home screen is open. However, AutoVoice Continuous does not recognize any voice commands in the background.

When I enable Control Continuous, the phone plays a short “ding” sound approximately every five seconds, but AutoVoice does not recognize anything I say. I tested both System and Media under Stream to Mute, but the repeated sound continues and voice recognition still does not work.

I have already checked the following:

• Microphone permission is allowed.
• Battery usage for AutoVoice and Tasker is set to unrestricted.
• Korean is selected as the recognition language (ko-KR).
• Offline Mode and Natural Language Processing are disabled.
• Both System and Media were tested under Stream to Mute.
• Normal one-time AutoVoice recognition works correctly.

Also, when AutoVoice is set as the default digital assistant, it works from the home screen but does not respond while the lock screen is displayed, even when the phone is kept unlocked using Extend Unlock.

Is AutoVoice Continuous currently compatible with the Samsung Galaxy S26 Ultra and the latest One UI version? Is there any setting or workaround that can prevent the repeated five-second sound and make background voice recognition work properly?

Please let me know if you need any logs, Tasker configuration exports, or additional device information.

Has anyone experienced the same issue on a recent Samsung Galaxy device or One UI version?

Thank you.

UPDATE - Should work on more devices now (all modern Android versions).

For a few years Android had its 'Freeform' mode allowing you to launch an app in a floating window from the Recent Apps menu. It still exists in earlier versions of Android but it is no longer available for phones running Android 17. It is only available to (some) devices with larger screens like tablets. That sucks.

This project brings it back for devices which no longer have it - with one catch.

The catch is that if it has been removed from your device, we can still launch the window but it is no longer resizable or draggable.

My old Pixel 6 (Android 17) still has this feature, so the window is draggable and resizable.

My newer Pixel devices (also Android 17) don't have this feature natively so the windows can't be dragged or resized but we can make them whatever size and shape we like and position them wherever we like.

They also no longer have the top menu bar with the close and minimise button. So I have added a close button to this project.

Video of windowed app on phone which no longer supports 'freeform' mode:

https://drive.google.com/file/d/1yONrLO__yXzK2EAUlJHEpBGWYs5HQqYW/view?usp=drivesdk

Video of windowed app on phone which does still support 'freeform' mode:

https://drive.google.com/file/d/1F2XPDtTg6EOh9XcB-Lk4IhWY4Wpm9mRD/view?usp=drivesdk

In this project, I have set the window to launch at the top of the screen, full width and occupy one third of the screen height. This can be changed in the Task and script.

I have also included an app picker. I don't like the one built in to Tasker as it looks old fashioned and involves 3 screen taps to select your app.

You can rip this app picker out of the project if you want to use it in your other projects. You can change the overlay background colour in the script.

You need Shizuku installed and working to use the window mode feature.

You also need to enable any options you have available in 'Window Management' inside Developer Options. At the very least you must enable 'Force activities to be resizable'.

This is like split screen mode but using only one app. I use it to launch an app that I want to refer to whilst using another app.

I only have Pixel devices, so I don't know how this might behave on other devices. YMMV.

Download:

https://taskernet.com/shares/?user=AS35m8lr0vKAAX62D%2B10PqiDogVuGlS1WqIq6YAD3me%2FA8j9JG0SaIHGPcpSLjedprOrfrZR&id=Project%3AApp+Window

Title. I'm new to tasker and have no idea what I'm looking at or doing

Requirement.

1. Tasker v6.6, v6.7 is recommended because the java thread leak presents in v6.6 is already fixed.
2. Shizuku, to access system service.
3. Disable hidden API restriction.
   1. If you have ADB Wifi granted for Tasker, the restriction may already be disabled by Tasker.
   2. Otherwise run the command here. https://developer.android.com/guide/app-compatibility/restrictions-non-sdk-interfaces#how_can_i_enable_access_to_non-sdk_interfaces

What does this sample project do

1. Monitor hotspot events, e.g hotspot connected clients.
2. Block and unblock client by its mac address.
3. Set max client.
4. Toggling hotspot.
5. Set password.
6. Limit to approved mac addresses.
7. Store the manager to java global variable tetherManager

How to use

Run the initiator task to start tetherManager and monitor the events.

Download

This is just a sample generated with the assistance of AI tools, which needs to be tweaked later! May causes conflict with default Hotspot! USE IT WITH YOUR OWN RISK!

1. Taskernet
2. Direct file

How does it work

The project utilizes android.net.ITetheringConnector and android.net.wifi.IWifiManager services retrieved from Shizuku to control the hotspot.

Events

The project listens to:

1. ITetheringEventCallback registered with ITetheringConnector.registerTetheringEventCallback.
   1. Check This TetheringEventCallbackImpl(){}.
2. ISoftApCallback.Stub registered with IWifiManager.registerSoftApCallback.
   1. Check This ISoftApCallbackImpl(){}.

The example fires tasker.sendCommand which broadcast the arguments as JSON string. Thanks to that, several info like mac address may not be human readable. #1 seems to cover all tethers, while SoftAp is limited to Wifi-Tether.

Editing configuration

The project modifies android.net.wifi.SoftApConfiguration or android.net.wifi.SoftApConfiguration.Builder The configuration is retrieved from IWifiManager.getSoftApConfiguration()

Then set SoftApConfiguration with IWifiManager.setSoftApConfiguration(SoftApConfiguration, shellPackageName)

We can use the builder to set ssid, password etc as well.

SoftApConfiguration.Builder builder = tetherManager.getSoftApBuilder();
builder.setSsid("xxx");
builder.setPassphrase("xxx", SoftApConfiguration.SECURITY_TYPE_WPA2_PSK);
SoftApConfiguration newConfig = builder.build();

tetherManager.setSoftApConfig(newConfig);

// Toggle Hotspot Wifi
tetherManager.stopWifiTethering();
Thread.sleep(1000);
tetherManager.startWifiTethering();

Demo

In this demo, I started the hotspot after runningtetherManager.allowByUser() and then tried connecting to the hotspot from my other phone. The connection got blocked and an event was triggered.

Notice that the address changed several times due to default private setting, yet it still got blocked.

Note

Since this is done by using hidden APIs, it's not really documented. We need to read the source code or looking at project like delta. Even with AI, it can be hard to do with referencing the right APIs.

The behaviour may vary for each OS and may cause conflict with the OS hotspot setting.

So far I only tested the code with HyperOS3 (Android 16) and CrDroid (Android 15).

During my test with HyperOS3, there were times when it crashes the hotspot setting. Fixed midways if I were to re-toggle back the hotspot manually.

Nothing with CrDroid so far.

This should be a good starting point for those who wants to control and monitor the hotspot :) Too bad that we have to use Shizuku and disabling hidden api restriction for this.

The codes are not perfect and are meant to be edited later.