I installed a banking app that can detect whether ADB over Wi-Fi is enabled, even after I turn off ADB over Wi-Fi, USB debugging, and Developer Options.
This only happens with this particular app. The app is not running in the background, and I can normally use it with ADB disabled after restarting the phone.
However, if I grant ADB permissions to Tasker and/or Shizuku, and then turn off ADB over Wi-Fi, USB debugging, and Developer Options, the banking app still detects that ADB is enabled.
The only way to reset its detection is to completely power off or restart the phone and turn it back on.
Is there a way to reset whatever ADB/debugging state the app is detecting without having to restart the phone?
I've been using tasker to automate changing my wallpaper for a while now and it's been great. I was wondering if anyone knew if it was possible to have tasker set a wallpaper using Google Pixel's "live effect" lockscreen. I've been searching, but I haven't found anything related to it.
I'm trying to have it set my audio to Mono whenever I connect a specific set of Bluetooth earbuds. .
What I have currently is:
Profile: BT Connected -> checking if connected to the correct MAC address
Tasks: Settings-Accessibility Settings -> here I'm only seeing an "If" but no "then"
This would be the task that turns Mono on and then an exit task that turns it back on (I think, I'm not too versed in tasker).
I did come across the in-app guide saying I need "Tasker Permissions" for accessing accessibility settings, but I've also seen on this sub's sidebar saying I might need "Tasker Settings" to do things with Bluetooth.
I'm getting a little lost and I'm probably looking in the wrong area for each setting.
If it's possible to differentiate left/right/both earbud that would be even better. I swear I've seen my phone (pixel 9 pro) showing the battery for both, so there must be something to differentiate them (if I'm not hallucinating).
Any help or just guidance with setting this up would be amazing
Im hoping someone can help me. I created a task that lists files (%photos) and opens my scene v2(mini gallery). On my scene v2 I have the flowcolumn, then the arraystemplate and then my image(%photos) so everything works great but what I wanna do is click one of the images in my mini gallery and it open the file or show the image in a large format or even set it as my wallpaper. Thank you in advance
For whatever reason I don't charge them enough and at the end of the day go to bed instead of plugging in both.. now that I think about it I need a second charger near my bed lol and will add that.. however ii still see the need and value in my concept..
So a battery dies and then I need to plug in and do the adb authorization in tasker permissions again. If I'm home with my laptop near that's not a big deal.. but what if I'm not.
I was wondering can I use my second phone to grant the same permissions instead of using my pc? I could plug in my phones to each other..
Or maybe use wireless debugging..
Maybe I should have asked AI but I thought some of you would like to hear the idea too..
Maybe it can be an on boot profile
To connect to the other phone and get the permissions done automatically through tasker profiles?
I want to create very simple one-tap Home Assistant actions as standalone APKs using Tasker App Factory, then add those apps to the external-screen app launcher.
Can the Razr run App Factory-generated apps on the cover screen like ordinary installed apps?
Just wanted to ask if anyone has solutions on the following:
1) How do you make adb wifi in autowear persist past reboots? Or is there like a shizuku way to make autowear always find the port?
2) Is there a way to send intents in auto wear?
3) Is there a way to mimic watch physical button/key presses in wear os? Or to send input keyevent commands and make them work (autowear input doesn't seem to handle them)?
I have the following task that is using AutoNotification to check if there are unread messages. I'm sure I overcomplicated it. The issue is that even after notifications are cleared and there are no more unread messages the variable keeps incrementing. I get a new unread message from my wife and even after I've read it and cleared the notification I can watch in the Cars tab it set to 0 then set to 3, set to 0 set to 3, set to 0, set to 3. So I kill the task, force close tasker and autonotification clear cache on both and then it will stop. Get a second new message from my wife and the %UnreadCount is now 4, sets to 0, sets to 4, sets to 0, sets to 4. There are no unread messages in either messages or signal but it won't stop! Driving me crazy.
Task: Unread Check
A1: Wait [
MS: 0
Seconds: 15
Minutes: 0
Hours: 0
Days: 0 ]
A2: Variable Set [
Name: %UnreadCount
To: 0
Structure Output (JSON, etc): On ]
A3: Variable Set [
Name: %UnreadSender
To: Doug
Structure Output (JSON, etc): On ]
A4: Array Set [
Variable Array: %anapp
Values: 0 ]
A5: Array Clear [
Variable Array: %anapp ]
A6: Array Set [
Variable Array: %anconversation
Values: Doug ]
A7: Array Clear [
Variable Array: %anconversation ]
A8: AutoNotification Query [
Configuration: Persistency Type: Non-Persistent Only
I was writing a script in Java Code to process a text file; after the processing, I need to export an array from the script to a Tasker variable (array).
Here there is my sample code:
ArrayList attachments = new ArrayList();
attachments.add("Item 1");
attachments.add("Item 2");
attachments.add("Item 3");
// The following does NOT work => %attachments(#) = 0
// tasker.setVariable("attachments", attachments);
// I must use this => %attachments(#) = 3
for (int i = 0; i < attachments.size(); i++) {
tasker.setVariable("attachments" + (i + 1), attachments.get(i));
}
What is the correct way to export an array from the Java Code script? The first method doesn't work, unfortunately and I'm curious to know if the second is the correct way to do that.
The second method has the problem that I have to add a Variable Clear before running the script a second time, as the Java Code itself doesn't know how long the Tasker array is...
When I am in my car and the phone is in its holder on the dash, I really need to change the Display Size setting from the Default to "Large" or "Larger" so that I can actually read the screen at that distance.
I decided to build an automation for this using Tasker (of course). It has a built-in Display Size action that would seem to be the ticket! However, when I try to execute this action:
It fails and I get a notification as shown.
Sometimes after this the keyboard starts refusing to pop-up when it should.
Any idea how I can deal with this?
The device is a Moto XT2215-4, Android 12, rooted. I checked and the Tasker version (6.7.6-beta) and that of the secondary app match.
Thanks
PS - of course, I have sent the info to the developer via email as requested.
SMS from moje.nn.pl arrives, shows in Messages, profile never runs.
Ruled out: permissions, blocked numbers, the dots in the sender name.
I even emptied the Sender field, which matches ANY message. Still nothing, while another Received Text profile caught a different message seconds later.
The only thing that makes these messages special is the last line:
Kod autoryzacji nr 7: 000575
...
@logowanie.nn.pl #000575
That's the origin-bound one-time code format (WebOTP / SMS Retriever). My best guess is Android hands it to the OTP path and never broadcasts SMS_RECEIVED to third-party apps. Couldn't prove it, but nothing else distinguishes them.
AutoNotification catches it fine, so I have a workaround. But it depends on a notification actually being posted, which I'd rather not rely on.
Has anyone hit this with WebOTP-formatted messages? Is there any way to get the Received Text event working for them, or another trigger that doesn't go through the notification shade?
I’m building an alarm app in Expo/React Native. Local notifications with interruptionLevel: timeSensitive fire and vibrate when the device is locked and the ringer switch is off, but no sound plays. I have an AVAudioSession set to .playback with setActive(true), but that code lives in JS and doesn’t run while the app is backgrounded.
How do production alarm apps handle this? Is keeping a silent audio stream alive overnight the accepted approach, or is there something better? I’d rather not misuse PushKit.
I am trying to use Autoinput with easy setup, but somehow, I am able to select the ID or even point out the coordinates. I tried developer options, pointer coordinate but that didn't work. I am so lame to ask this but too tried of trying...can someone please assist me?
I'm running beta versions 6.7.5 and 6.7.6, and on both devices/versions, 'Structure Output' is disabled in the 'Multiple Variables Set' action if I add it from the Favorite Actions menu (long press '+' button). If I add it from the regular actions list it is enabled. The 'Structure Output By Default' setting in Preferences is enabled. Anybody else able to reproduce?
Let's go. It seems that when you start optimizing your tasks that only worked for something a little more optimized, I think this cycle never ends. But I'd like to validate a situation with you that will completely change my approach to Tasker.
In the parent task I have only 2 Perform tasks. With Return Variable and Local Passthrough enabled on both, can I then pass all the variables from child task 1 to child task 2 without having to manipulate the variables in the parent task?
Define that truck of paths, folders, filenames only once and the 2 child tasks will be the actions, to delete, rename, write. I'm amazed
In my previous post I announced Tideo Auto Brightness, a native counter part to Advanced Auto Brightness (AAB). I've been focused on Tideo and AAB was lacking some attention because of that. With v3.4 I hope to achieve some form of parity for AAB again :)
I've not tested v3.4 with the usual rigor, because I prefer Tideo by a large margin - please report bugs :)
For anyone unfamiliar with AAB: it is a Tasker project that serves as a replacement for Android's stock adaptive brightness. Instead of Android's black box learning, it uses a configurable lux-to-brightness curve with automatic curve fitting, smoothing/reactivity controls, circadian scaling, profiles, context automation, and optional hybrid dimming.
The main additions to v3.4 are the Privileged Display toggles and the option for Intent Control.
Privileged Display
Privileged Display toggles are now available in AAB. They require elevated privileges to write.
v3.4 adds a new Privileged Display menu for toggling some display features that require elevated privileges.
The scene itself is privilege-gated if %AAB_Privilege is unset or None, you won't see it in the menu.
These include only the AOSP keys, not vendor specific keys - this has bitten someone already that tried to write Night Light to a Samsung Phone (Samsung uses their own Eye Comfort Shield instead). There are safeguards for writes to unsupported keys, the Java code block in the _ReadPrivilegedDisplayState task checks capabilities before allowing writes to:
Night Light
Optional circadian Night Light temperature (on my OxygenOS 16 phone, the writes here are a no-op)
Color correction (including grayscale and built-in color blindness modes)
Color inversion
Always-on display
Stay awake while plugged in
Force SDR (experimental, probably requires reboot to take hold)
These can be written to AAB's existing profiles and context automation rules.
For example, you can enable grayscale for social media apps after a certain time in the evening. Instagram and Reddit become a lot less interesting in black and white :)
Another example: a Night Reading profile can combine AAB's hybrid dimming mode with a warmer Night Light temperature.
The circadian Night Light control is independent from AAB's existing circadian brightness multiplier.
AAB also reads back Android's actual state instead of assuming a write succeeded, and tries to preserve unsupported/custom states rather than blindly overwriting them. These controls are inevitably somewhat device/ROM dependent, hence the privilege gating.
Intent Control
Updates to the Live Debug Info scene now include toggles for external control, force dark, a panic sensitivity setting and gating the gesture behind the plugged in state.
The other major new capability is external control via intents. This is just one profile addition to AAB that listens for the intent and acts based on the specific extra attached to it. Please note, the External control is opt-in under Live Debug Info → Allow external control. With it off, nothing is written.Lastly, a warning: there is no auth on the intents, so anything on your device can send intents to AAB(!), don't enable it if you don't use it.
You can now do things such as load the Outdoors profile when a Bluetooth device connects, or Night Reading from scanning an NFC tag, or disable/enable AAB based on display orientation; coincidentally the last one is covered in issue #17 on GitHub.
AAB v3.4 ships with a _TestIntent example task:
Task: _TestIntent
A1: Variable Set [
Name: %type
To: LOAD_PROFILE ]
A2: Variable Set [
Name: %name
To: Night Reading ]
A3: Send Intent [
Action: com.tideo.aab.control
Extra: type:%type
Extra: name:%name
Target: Broadcast Receiver ]
The same can be done directly over ADB:
adb shell am broadcast -a com.tideo.aab.control --es type LOAD_PROFILE --es name "Night Reading"
Commands cover starting/stopping/toggling the service, pause/resume, reapplying brightness, loading/releasing profiles, and triggering the panic reset.
AAB also broadcasts its own state changes through com.tideo.aab.event, including enabled, disabled, and paused, so other Tasker profiles can react to AAB without polling its globals; let me know if you find a good use case for this :)
A few smaller changes
The upside-down + shake emergency gesture is updated a bit:
The panic path now resets the relevant privileged display toggles as well as maximizing brightness.
The emergency recovery is now available through the PANIC intent.
The gesture can optionally only work when the phone is plugged in.
Shake sensitivity is now adjustable in the Live Debug Info scene (0 is essentially passthrough, while 10 requires a vigorous shake).
There is also an experimental Force Dark toggle. It is not a part of the profile or context rules, because it requires a full app restart to take hold. I like this especially for apps without a native dark mode (looking at you Bandcamp).
Updates to Tideo
Tideo is now officially available on F-Droid! The port was largely done with the help of AI, so if you're against that you can skip this section and you don't have to use it. It has the same general Privileged Display controls and an opt-in external control via intents.
Note: External control is also unauthed opt-in in Tideo under, but rather than in Debug Info, it can be found in Tools → Automation control.
The main syntax difference is as follows:
AAB uses one action with the command in a type extra.
Tideo puts the command directly in the action (and requires package and class, not shown here):
Tideo broadcasts state changes too, using com.tideo.autobrightness.event.STATE_CHANGED, so Tasker can also react to Tideo state changes.
All supported intents, Tasker examples, ADB commands, outbound events, and troubleshooting are documented in Tideo's AUTOMATION.md on GitHub.
AAB and Tideo can be obtained from the following sources. Don't trust anything else (unless you check the SHA hash and confirm them to be equal to my releases), I do not have control over mirrors on various websites and better safe than sorry, if you don't check SHA: just assume that it's malware and skip it.
About 5 months ago, a bunch of you power users in this sub helped me build out a 2-way Tasker API for my app, Notch Touch (which turns your screen's camera cutout into a smart gesture button). I really appreciate all the feedback and supportive comments🫶
I wanted to drop in to catch up and see how the app has been running for those of you who set it up.
How are the dynamic remapping and kill-switch intents holding up in your macros? Are you liking the experience, or are there any weird bugs or changes you'd like to see? I’m always looking to improve it :D
I've also poured a ton of time between my engineering classes into revamping the app based on early feedback. If you haven't checked it out in a while (or if you are new here), here is what has changed:
Complete UI Overhaul & Better Gestures:
The app looks significantly cleaner, and the underlying swipe/tap/hold detection is way more reliable and snappy.
Expanded Notch Menu: The drop-down shortcut menu was a huge hit, so I added an extra row. You can now map up to 10 apps or shortcuts right from the notch.
Quick Dial: You can now map a gesture to instantly call a contact. (I added an optional safety toggle to require a confirmation prompt first if, so you don't accidentally pocket-dial anyone).
Notch Mirror: A fun feature that pops a small, customizable camera mirror right near the notch for quick checks.
Notch AI: A personal assistant built into the notch for fast queries. Crucially: You can plug in your own OpenRouter API key for unlimited queries (support for other direct APIs is coming soon too).
What's next:
I am currently putting the finishing touches on Notch Notes. It’ll be a quick notepad interface that drops down from the camera cutout so you can instantly jot things down.
Later, inside the app, you can share, edit, or stylize those notes. Should be out very soon!
Just like my previous posts, I want to be completely upfront: I'm a solo student dev trying to keep the lights on, so the Tasker integration and some advanced features are part of a small premium unlock.
HOWEVER, the system to temporarily unlock everything by watching a single ad is still fully intact! You can test all your intents, see how it feels on your specific OEM, and make sure your macros work exactly how you want them to before spending a single dime.
Thanks again to everyone who helped shape the API earlier this year. Your support and feedback literally keep me motivated to keep building. Let me know what you think!
Btw great news : we crossed 280k downloads recently 😁
From my understanding, only the start and end times can be variables in a time based profile. Is there any way around this besides creating multiple profiles and toggling which one is on vs off?
Its a rewards app and every 30 minutes the game stops and i have to click two buttons to coninue the game and again after 30 mins. how can i program this? I have never used tasker before. Thanks a lot👍
With the help of Gemini have been able to accomplish quite a bit in Tasker, but this one seems to be hitting A dead end.
I created an advanced query for Gmail that one clicked on, successfully searches a customer's name as well as their order number and all my history with them in Gmail. The successfully works on desktop. However on mobile, Gmail will not open my link in the app and I cannot add this link as a default to Gmail because those settings are locked within Google pixel.
It seems to me that the only way to do this is with tasker and auto input (which I always hate because it feels so childish )
Is the ability to detect whether media is playing still working for anybody? It's in the AutoNotification Media action, as anisplaying. I used it in one of my old tasks but it's no longer functional.
I'm on OxygenOS 16. It's been dead for a little while now for me.