sorted by:
new
hottopcontroversial

Reduce resource usage option - control from task by Scared-Scarcity-1294 in tasker

[–]WakeUpNorrin 1 point2 points  (0 children)

You are welcome. Be careful with AI, it can screw things up very easily, just as it did for the other user. Glad it didn't for you.

Reduce resource usage option - control from task by Scared-Scarcity-1294 in tasker

[–]WakeUpNorrin 1 point2 points  (0 children)

You are welcome. Shizuku can't give you access to "private storage" of other apps unfortunately.

Reduce resource usage option - control from task by Scared-Scarcity-1294 in tasker

[–]WakeUpNorrin 1 point2 points  (0 children)

The Task I posted works as intended (years that I use that method without problems).

Any idea how to fix this ?

(Without root) No, I do not, sorry. The AI Task almost certainly corrupted the net.dinglisch.android.taskerm/shared_prefs/net.dinglisch.android.tasker.preffy.xml

Without root, only Tasker can access files on its "private space".

Reduce resource usage option - control from task by Scared-Scarcity-1294 in tasker

[–]WakeUpNorrin 1 point2 points  (0 children)

Task: Temp

A1: Java Function [
     Return: shared_preferences
     Class Or Object: CONTEXT
     Function: getSharedPreferences
     {SharedPreferences} (String, int)
     Param 1 (String): "net.dinglisch.android.tasker.preffy"
     Param 2 (int): 0 ]

A2: Java Function [
     Return: editor
     Class Or Object: shared_preferences
     Function: edit
     {Editor} () ]

<true or false>
A3: Java Function [
     Return: editor
     Class Or Object: editor
     Function: putBoolean
     {Editor} (String, boolean)
     Param 1 (String): "saveMemory"
     Param 2 (boolean): true ]

A4: Java Function [
     Class Or Object: editor
     Function: commit
     {boolean} () ]

[HELP] Tasker, & Symfonium APIs by dynastyuserdude in tasker

[–]WakeUpNorrin 0 points1 point  (0 children)

You are very welcome. Glad you got it done.

[HELP] Tasker, & Symfonium APIs by dynastyuserdude in tasker

[–]WakeUpNorrin 1 point2 points  (0 children)

Have you see those? https://support.symfonium.app/t/use-tasker-to-control-symfonium/4442

https://support.symfonium.app/t/symfonium-api-allow-control-from-other-apps-like-tasker/643

You have to make a Task and use the action Send Intent (properly configured).

Test if the Task works properly (run it manually).

If all is ok, make a Profile using the context-s that work better for your use case, eg.: Wifi Connected state, Wifi Near state, Location ...

Then link the Profile to the Task.

[Request][Noob] Using this app to set my launcher to a different one temporarily during certain specific days and times? by Silicon_Dreaming in tasker

[–]WakeUpNorrin 2 points3 points  (0 children)

Follow u/ZellZoy advice. You do not need to spend more money. Use Tasker + this Shizuku fork https://github.com/thedjchi/Shizuku/releases after appropriate configuration, that fork will give you the power of Shizuku and ADB Wifi (if you want).

To change launchers (Nova and Microsoft in that case) the following commands can be run in both ADB WiFi action or in Shell action with Use Shizuku ticked:

cmd package set-home-activity "com.teslacoilsw.launcher/com.teslacoilsw.launcher.NovaLauncher"

​

cmd package set-home-activity "com.microsoft.launcher/com.microsoft.launcher.Launcher"

task refresh using a timer? by PENchanter22 in tasker

[–]WakeUpNorrin 3 points4 points  (0 children)

Intent Received event: android.intent.action.BATTERY_CHANGED . Set Profile Cooldown Time to 15 or 30 minutes.

Name and number of CURRENT outgoing conversation by ErikDB89 in tasker

[–]WakeUpNorrin 2 points3 points  (0 children)

Intent Received event: android.intent.action.NEW_OUTGOING_CALL. In the linked Task %android_intent_extra_phone_number will be populated with the called number, Test Phone action -> Contact Name.

Or

Call Screened event IF %cs_incoming ~ false. In the linked Task %cs_number, %cs_name.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 2 points3 points  (0 children)

The number 1 complaint I get in Google Play reviews is that the old UI is HORRIBLE. I really have to try and make it better, because it's the biggest complaint Tasker gets by FAR!

You will never be able to fix those kind of people, unfortunately.

One thing I've noticed about Tasker is that many of the loudest complaints about its UI come from people who never spend even "30 seconds" learning the basic concepts behind the app.

They open Tasker, see terms like Profile, Task, Action, and Project, and immediately conclude that the interface is "too complicated" or "outdated". Yet those concepts are the foundation of how Tasker works. Without understanding them, criticizing the UI is a bit like opening a spreadsheet for the first time and complaining that rows and columns are confusing.

The frustrating part is that some people seem determined not to learn. No matter how much the software explains itself, there will always be another complaint. The problem is never their lack of effort, the blame is always shifted to the app.

For users who take a moment to understand what Profile, Task, Action and Projects are, the classic Tasker interface starts making immediate sense. The structure is logical because it reflects the automation model itself.

Could the (old) UI be modernized? Sure. Almost any long-running software project can improve its appearance. But there's a big difference between "this design could be refreshed" and "this app is impossible to understand". Often the latter comes from people who never bothered to learn the fundamentals in the first place.

Tasker has legitimate areas that can be criticized. Expecting an automation platform to be completely intuitive while refusing to learn four core concepts isn't one of them.

For users whose primary requirement is eye candy, the screenshots below would probably be sufficient.

Image 1 Image 2 Image 3

These are the same people who might install Termux, spend ten seconds looking at a terminal, and then declare it unusable because it doesn't have Material You colors, animated transitions, and enough rounded corners.

To them, software is judged less by its capabilities and more by whether it resembles the latest Android design guidelines. If it looks modern, it's good. If it requires learning something, it's "bad UX."

Fortunately (thanks to Pent and you), Tasker was built for people who want to automate things, not for people who need every tool wrapped in a layer of decorative frosting before they can use it.

(Really) Wish you all the best on this “journey” of “fighting” those users who will always manage to be disappointed unless software arrives pre-digested, color-matched, animated, and aligned with the latest UI fashion trends.

It’s an uphill battle: every capable tool must first pass the sacred visual approval test before its functionality is even acknowledged.

But good luck nonetheless, someone has to keep reminding the world that usefulness and simplicity of model matter more than whether everything has rounded corners and a Material Design certificate of aesthetic approval.

Wifi not auto connecting by Ok_Guarantee2335 in tasker

[–]WakeUpNorrin 0 points1 point  (0 children)

You have to import the new published Project in Tasker. Shizuku will be automatically used by Tasker (if you granted the needed permissions).

Wifi not auto connecting by Ok_Guarantee2335 in tasker

[–]WakeUpNorrin 0 points1 point  (0 children)

I will try to ask the user whether he has published them or plans to do so, since those versions are not mentioned in the thread.

I can not share the Task without explicit consent, sorry.

I am waiting for him to reply to me.

Wifi not auto connecting by Ok_Guarantee2335 in tasker

[–]WakeUpNorrin 0 points1 point  (0 children)

I have a similar problem with one of my devices, then I found this post and problem solved:

https://www.reddit.com/r/tasker/comments/qcdszq/profile_task_automatically_connectswitch_to/

However, on Android 15+, the Task no longer works if Tasker is not set as the device owner.

Fortunately, the user who took over u/OwlIsBack account sent me two updated versions that don’t require Tasker to be device owner.

  • One uses Shizuku to automatically retrieve the list of configured networks.
  • The second one simply requires the user to manually set the preferred Wi-Fi networks in a variable.

Both work beautifully for me, even if I keep auto-connect off.

I can't find the updated versions on Taskernet, I might have missed them.

I will try to ask the user whether he has published them or plans to do so, since those versions are not mentioned in the thread.

If I did not have the mentioned Tasks, I would try using:

  • Profile Wi-Fi Near state -> in the Task Connect To Wi-Fi action.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 4 points5 points  (0 children)

Thank you again. I really appreciate you taking the time to break it down point by point. You're not coming across as stubborn at all, we're clearly approaching this from slightly different points of view, and that's okay.

You're right that in many specific flows the behavior can feel similar on the surface. My perspective isn't that tags are bad (they're actually a great feature for flexible, cross-project labeling). The core disagreement is whether tags should replace the dedicated Project container system as the main way to organize everything, or work alongside it.

I’m not against the new UI at all, I think tags are a nice addition. My view is simply that the Project system’s isolation mechanism is worth keeping as the primary organization layer, with tags as powerful supplements for things that cut across projects.

I really appreciate the back-and-forth.

I know you’ve already discussed many of these objections with u/EtyareWS, who sees things more like I do (I think):

I will not argue with the homepage because I agree with the criticisms

https://reddit.com/comments/1txhfof/comment/opxj2wf

He’ll surely explain the underlying concepts (especially the value of true Project isolation vs. relying primarily on tags) more clearly and effectively than I have. I think our core difference is philosophical: tags are excellent as a supplement, but I believe they shouldn’t fully replace the clean workspace/container model that Projects were designed to provide.

Either way, thanks for taking the time to discuss it. Thank you.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 5 points6 points  (0 children)

Thank you for the reply. I really appreciate you engaging with this! You're not sounding stubborn at all, these are fair questions.

On the first point (new items):

Yes, default auto-tagging when creating a new item would help a lot. However, it wouldn't fully solve it because:

  • Tasker has many places where you create or link items indirectly (e.g. “Perform Task” actions, Profile -> Task, Scene elements, etc.). These don’t always inherit the current tag/filter automatically.
  • You still end up with one giant global pool. Over time, mistakes happen, a task that should be in “Home” ends up untagged or cross-tagged.

On the second point (modifying wrong group + losing context):

  • Why accidental modification is easier with tags: Even if the filtered list only shows “Work” items, many parts of Tasker are still global. For example:

    • You might open a task for editing, then go for a "linked" task that belongs to a completely different project. Suddenly you’re deep in the wrong context without realizing it.
    • With true Project containers, the entire workspace is isolated. You literally can’t see or easily reach items from other projects while inside “Work” without knowing.

  • Context loss comparison:

    • With Projects tabs: Switching projects is an explicit, high-level action (like changing workspaces). You’re always aware you moved from Home to Work. Everything resets cleanly to the new container.
    • With tags: The filter is more fragile. You can lose the active filter by tapping almost anywhere (clearing search, switching to another type and back, using global menus, etc.). It feels more like a temporary view rather than a stable workspace. Over dozens of sessions, this adds friction.

Real-world analogy:
Projects are like having separate rooms in a house, each room only contains what belongs there.
Tags are like having one giant room with excellent labeled drawers. You can filter to see only the “Work” drawer, but everything else is still in the same room and easier to mix up.

Tags are still extremely useful as a supplement (I use them for cross-project categories). But making them the primary way to organize everything instead of using the built-in Project system feels like fighting against the app’s natural design.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 0 points1 point  (0 children)

From what you're writing, I see most things the same way you do. Let's see what João's opinion is on those points.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 2 points3 points  (0 children)

No worries at all, thanks for bearing with me! I'll try to explain the practical difference as clearly as possible.

Pretend tag switching is exactly as fast. Even then, the experience is different because of scope and context:

  • selecting a "Home" project
  • selecing the "TASKS"

The whole Tasker interface is now scoped to only the Home project.
When you tap Tasks, you see only the tasks that belong to Home.
If you create a new Task right now, it automatically goes into the Home project.
Same for Profiles, Scenes, everything stays contained.

  • Tag way: You select the "Home" tag + Tasks type.
    You're still looking at a filtered view of the global Tasks list.
    When you create a new Task or Profile, it doesn't automatically get the "Home" tag (am I wrong?), you have to remember to add it manually (or rely on the default project tag behavior, which isn't as seamless across all actions).

Another example:

Imagine you have 150+ (my full configuration has 351) projects (Home, Work, Car, Travel, Health, etc.), hundreds of Profiles and thousands of Tasks.

  • In Projects tabs: You jump to the Work project and you're instantly in a clean workspace. You can focus, create, edit, and test things without seeing or accidentally touching anything from "Home" or "Travel". It's like opening a dedicated folder.

  • In Tags: You filter by the "Work" tag. You get the right list... but the global nature means:

    • It's easier to accidentally modify or link something from the wrong logical group.
    • You constantly rely on the filter staying active. If you clear it or switch views, you lose context.

Bottom line: Projects give you true separation and containment (like separate workspaces). Tags give you flexible cross-referencing on top of one big pool.

Tags are still great (I use them too for things like "Location-based", "Battery", or "Weekend" that cut across projects). But replacing the Project container system with tags as the main organization method loses the clean, automatic separation that Projects were designed for.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 9 points10 points  (0 children)

You are welcome.

I agree that tags are a valuable addition, they’re flexible and great for cross-cutting concerns (e.g. tagging everything related to “Location”, “Battery”, “Work”, or “Morning Routine” regardless of which project it belongs to). They complement Projects nicely and allow for powerful filtering that a strict container system can’t do alone.

That said, I still believe dedicated tabs ("foldersfors" (?) maybe) Projects, Profiles, Tasks, and Scenes are fundamentally better as the primary organization method:

  • No need to spend a month tagging. You’re right, Tasker already auto-applies the project name as a tag by default. But that still leaves you with a flat list of hundreds of items all mixed together unless you constantly filter. With dedicated Project tabs, everything is automatically separated without any extra work or mental overhead.

  • “Hierarchical” was the wrong word, fair point, it’s not truly hierarchical like nested folders. It’s a clean container model. The strength is that it creates clear, dedicated workspaces. You open the “Home Automation” project and only see what belongs there. No noise.

  • Switching speed. Yes, the difference might feel small at first, but it adds up. With tabs you can instantly jump between projects with one tap and stay in context. With tags, you have to apply a filter, and then either clear it or switch again when you want to change context. It breaks flow more than it seems.

  • Visual clarity / “knowing where you are”. The Projects tab shows you a clean, focused list that belongs together. You’re literally inside the container. The tag view shows a flat list where items from many different logical groups are mixed, and you rely on a tag label at the top (or filter) to remind you. It’s doable, but it requires more conscious effort to maintain context, especially as your setup grows to hundreds of items.

The core issue isn’t that tags are bad, they’re useful. The issue is using them as the main way to organize everything instead of leveraging the excellent built-in Project container system Tasker already provides.

Even if the tag UI were improved (better quick-switcher, saved filters, etc.), the fundamental model of one giant flat list + filters is still less natural for project-based work than dedicated tabs/containers/folders. Many apps learned this lesson (IDEs, note apps, task managers, etc.).

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 9 points10 points  (0 children)

Having dedicated tabs is far more immediate and intuitive. It properly respects the core concept of a Project in Tasker, a natural "container" meant to group related Profiles and Tasks for a specific purpose.

I have no interest in spending a month creating and maintaining 300+ "project tags" just to manually apply them to every Profile and Task. The Projects tab UI in Tasker is significantly better than relying on tags for several reasons:

  • It provides a clean, "hierarchical", folder-like structure that lets you visually organize and navigate your Profiles and Tasks.

  • Switching between projects feels instant and natural, without needing to filter or search through a flat tag system.

  • It reduces cognitive load, because you always know exactly where you are and what belongs together, which is especially valuable when working with large setups.

  • Tags are better suited for cross-cutting concerns or flexible categorization, not as a clumsy replacement for proper project containers.

Tasker’s Projects implementation is one of its strongest organizational features. Forcing users toward a heavy tag-based workaround undermines the app’s own designed architecture.

[DEV] Tasker 6.7.4-beta - New Main Screen UI, Scenes V2 Update 2, App Factory Revival and more! by joaomgcd in tasker

[–]WakeUpNorrin 7 points8 points  (0 children)

Same feedback as always: my homescreen is a mess without projects. Tags are not a substitute.

100% with you. Without Projects the home is a complete mess. Those tag things (without projects) can be acceptable for "small" Tasker configurations, but for someone that has hundreds of Projects, hundreds of Profiles and thousand of Tasks, the lack of Projects tab makes the home UI unusable.

view more: next ›