AutoInput breaks the navigation buttons on the new Samsung One UI 7.0!

[ISILDUR]

Today's EUX update to Android 15 and One UI 7.0 has caused the bottom navigation buttons - like Recent Apps, Back, and Home - to become unusable. The only workaround is disabling Accessibility access for
AutoInput. Without doing so, you have to press the navigation buttons 3–15 times randomly before they respond. Please fix this urgently.

[João Dias]

Hi there, thanks for the report! Can you please try this version? https://drive.google.com/file/d/1_MCmNfnK4FpFB7HFOgkQxNKbtbmbb8Rs/view

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

On Mon, Apr 28, 2025 at 9:59 AM 'ISILDUR' via Tasker <tas...@googlegroups.com> wrote:

Today's EUX update to Android 15 and One UI 7.0 has caused the bottom navigation buttons - like Recent Apps, Back, and Home - to become unusable. The only workaround is disabling Accessibility access for
AutoInput. Without doing so, you have to press the navigation buttons 3–15 times randomly before they respond. Please fix this urgently.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/tasker/a7214cb2-25d6-41b1-b360-36eb65db0a21n%40googlegroups.com.

[ISILDUR]

Thank you for the quick response, João! I installed the version you suggested, and the issue disappeared! The navigation buttons are now working correctly in this version. I cannot yet confirm whether AutoInput itself has lost any functionality or if it is working properly - I will need more time to verify that. I will report back if I encounter any further issues.

[Dan Muller]

I will second that. I had the same problem on my S24 and this version fixed it. 

[Greg M]

@joao do you have a different version that may work on the s25? the s24 version broke my s25 even worse

[João Dias]

[ISILDUR]

Noticed problem:
Global Action Recent Apps not working anymore. Function dors nothing. Recent apps not shown.

[João Dias]

Can you try using the Show Recents action in Tasker itself?

[ISILDUR]

Show Recents action in Tasker itself gives this error:

11.25.01/MAS performGlobalAction: failed
11.25.01/E result: stop task (error)
11.25.01/E Error: 1
11.25.01/MacroEdit action finished exeID 1 action no 16 code 247 status: Err next 16

[João Dias]

Weird. both work for me... What Android version are you using?

[ISILDUR]

Weird indeed. Was working perfectly before upgrade to One UI 7.0 in Samsung S23 Ultra EUX region. Android version is 15.

[Ed Lawler]

I'm having the same problem on my Samsung S22 Ultra after recent upgrade to Android 15, OneUI 7.0.

Using the version of Autoinput from the Play Store, none of the buttons on the Navigation bar worked. My tasks using Autoinput v2 did work as long as the accessibility feature in autoinput was on. I tried the version from Google Drive that had accessibility turned off and my navigation buttons then worked, but any tasker tasks using autoinput v2 failed.

I have an alternate way to invoke the back, home, and recents actions by defining them in the  Settings - Accessibility - Interaction and dexterity - Assistant menu. This leaves the Navigation bar still unusable, but upon reinstalling Autoinput from the Play Store, my tasker profiles and tasks work again. Since my tasks are more important than the Navigation bar, I'm currently back to the Play Store version.

I'd really prefer not having to use the accessibility workaround, though.

Ed

[SportyRydr]

I haven't even gotten as far as testing navigation buttons with AutoInput, because the navigation buttons no longer work after the update on my S24+. Well, that's not entirely true, but they might as well not work. I have to tap multiple times on any of the nav buttons, and MAYBE, a tap will actually register. Because of their essential uselessness now, I've switched to navigation gestures.

Interestingly, in scrcpy v3.0, the right mouse button click still performs the BACK function just fine, even with nav gestures enabled.

Mark

[João Dias]

Did you try the latest version I posted above?

[ISILDUR]

Any updates on this issue? Is there anything I can do to help, maybe check something to help solve the recent apps problem?

[Ed Lawler]

I just installed the latest autoinput.apk from Google Drive and got the same result - Navigation buttons work, autoinput v2 broken. I emailed Joao the information from the error message. When I tried to open the Autoinput app, itself, I got the message that Autoinput keeps stopping.

As I said before, a working autoinput plugin means more to me than the Navigation bar buttons, and since I have a workaround, I have reverted to the Autoinput (Beta) version available in the Play Store.

Ed

[Ed Lawler]

SOLVED (at least for me)

After some correspondence with Joao, I just want to let others know that his APK version of Autoinput did solve my problems. The key, for me, was, after installing the APK, to find the option in Settings - Apps - Autoinput to allow restricted access. (the ... in the top right). After enabling that, both my tasks with autoinput v2 and the Android navigation buttons all work.

Thanks, Joao.

Ed

[João Dias]

👍

[Harry]

I've used the update APK with success. Later while working in Tasker the buttons became inactive again. I  pressed the Home button until it activated (10 or 15 press) and opened the AutoInput app. I clicked the Accessibility (where it says "Enabled   AutoInput accessibilty service is enabled!" and the buttons were useable again. Didn't get a chance to test if just opening AutoInput by itself would solve the problem. But there is still something going on with the navigation buttons.

[Alan Levine]

Does this version work on the S25+?  Someone else said that it fouled it up even more, and I don't want to install it unless it works with the S25+

[Alan Levine]

Well, what about the rest of us?  You went silent on this. My membership request to this group has been pending for days, so I can't even start a thread.

[João Dias]

Well, all I can say is that you have to try it yourself 😅 I can't possibly test apps on existing devices. There's just no way to do that...

[Greg]

Fwiw. My Verizon Samsung s25 Ultra is still facing regular issues (it has become marginally better).

If there is anything I can send to help. Please let me know. 

Thank you 

[Alan Levine]

I paid for the app.  I did try it myself. I also tried the updated version you provided others in the thread, and followed your suggestions.  Like others, when Accessibility access is granted, the phone's navigation buttons do not work and you become stuck in the no longer functioning app screen.  This is obviously a problem of the app.  I guess your flippant answer means you won't fix this or do not know how to fix this, so I guess I paid you for nothing.  We're paying customers and deserve better than obnoxious response.

[Alan Levine]

Thanks, Greg, but we deserve more than marginally better.  Seems that more than a few of us are experiencing this same issue and all we are getting from the developer is being ignored or flippant answers.  Not even an acknowledgment that this is a known issue he needs to fix.

[João Dias]

I'm so sorry, I didn't mean to be obnoxious. I'm trying to get it to work, but it's hard to do.  I've been updating the app multiple times lately to try and fix all the issues, and the latest version has been confirmed to fix the navigation issues for other users.

Are you absolutely sure you used the latest version I provided? You can get it here. https://drive.google.com/open?id=1_MCmNfnK4FpFB7HFOgkQxNKbtbmbb8Rs&usp=drive_fs

[João Dias]

Can you please clarify what you mean by "flippant answers"? Also, can you please clarify where I didn't acknowledge the issue? Thanks in advance.

[Alan Levine]

No, if you read the thread, the update has not fixed the navigation issues for anyone who is using the S25.  S24 maybe, but not S25.  Again, the problem can't be fixed if you don't even recognize it.

[Alan Levine]

Flippant: adjective

1. not showing a serious or respectful attitude.

   "a flippant remark"

   
   

   You have to try it yourself with a laughing emoji is a flippant remark.  

   
   

   Is the link you just provided the same one you provided elsewhere in this thread?  If it isn't please explain how I was supposed to know it was available and how I was supposed to know it was available.

[João Dias]

The emoji means "nervous laugh" which I wanted to mean that I feel bad for not being able to test the app on all existing devices, but unfortunately that's just the way it has to be. I didn't mean for it to be flippant, and if it came across that way I sincerely apologize.

About the link, yes, it's the same, but I always update the app on that same link, so I was thinking that maybe I already applied a fix that would work for you after you downloaded the app from it before, so maybe if you update it again and it will start to work properly.

Hope this makes sense.

[Alan Levine]

Let's try and do this the easy way: when was the last time you updated the app?  On May 12th I updated with the link you provided on this thread in April.  May 12th was the date I started asking questions in this thread and reporting that it didn't work.  If you updated after May 12th, I will update again, if not, I won't waste my time.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/pUsqk1MnfzY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFeCQiA%3DwvqTwR6wdiC7BUAVS7FNf-P_GPaNKoVaBWAGXw%40mail.gmail.com.

[João Dias]

The last update was on May 14th.

[Alan Levine]

Thank you, I will try it, but again I ask you how were we supposed to know this?

Please grant my pending join request so I can start a dedicated thread for future issues if there is not already an appropriate thread.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/pUsqk1MnfzY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFdwY00i3RWs0%2BWg3s8b1hTa8KWBd-6cAkkVRWqriUsUGQ%40mail.gmail.com.

[João Dias]

There are a lot of threads that I have to keep track of. I apologize that I didn't ask you to try a new version again.

I already granted your join request. Hope this helps.

[Alan Levine]

It does not appear that my join request was granted (see screenshots

.)  As it appears that the only way to find out if there has been a fix for the problem is a response from you in this group, please grant my join request.

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/pUsqk1MnfzY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFc3Q7fo7EE5FmsaMtPiNENef-P8%3DFW2ggGCvXu32QzgYQ%40mail.gmail.com.

[João Dias]

I don't see your request but I sent you an invite. Maybe that helps?

[Greg M]

Joao - thank you for all you do, I appreciate all the work and efforts put in. I am still seeing issues (to get back on subject) and can provide feedback or logs as needed, if needed. -Greg

[Simon Ayling]

Alan

Bearing in mind that English is not the developer's first language, once you've been a user for long enough, you'll find that he is one of the most helpful and diligent developers on the scene - particularly as he does this alone, not as part of some large corporation.

Respectfully, chill a bit.

[João Dias]

Thanks Greg. What specific issues are you seeing now? Is it still the same "navigation buttons not working" issue?

Thanks Simon! 😉

[alan.h.levine]

I updated yesterday with the link to the new version provided, but it still breaks the navigation buttons.

[joaomgcd]

Thanks. Does the issue go away immediately if you turn off AutoInput's accessibility service?

[Alan Levine]

Yes.  What happens is I use the help feature to build a task.  When the task is built and finished, I try it out and the navigation keys will no longer work so I am stuck in the Tasker task screen.  The only way to get out of it is to access settings and turn off the accessibility feature.  As soon as it is turned off, the navigation buttons again work.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/tasker/0e6e23ad-a1da-4760-b8b0-2cd754414db8n%40googlegroups.com.

[João Dias]

And if you turn it back on again, do they still work? Or will they go back to not working right away?

[Alan Levine]

I'm not quite sure what you are asking.  Previously, after I turned it off and could use the navigation keys, I left it at that.  But, to try to answer your question, I just went into my settings and turned it on for AutoNotification Toast Intercept (the only AutoNotification installed app indicated in the accessibility settings) and tried the task.  Now, the task does not execute -- the green triangle appears, but nothing happens, and the green circle never replaces the triangle.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFdP4AdvhH_pnxpybsAAn92wPAm7hYUAcjVvcOsBsU4wiA%40mail.gmail.com.

[João Dias]

Wait, are we not talking about AutoInput here?

[Alan Levine]

Yes, my mistake.  Sorry, it is early here. Let me try again.

On May 23, 2025, at 8:30 AM, João Dias <joao...@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFcc9LxEHSYmoO2ecTkABPLORWLNqTFnjk71qvN8thMeLg%40mail.gmail.com.

[Alan Levine]

Ok, ran the task first time and navigation buttons not working. Went into settings and turned accessibility off for AutoInput, and the navigation buttons immediately begin to work.  Turned accessibility back on, ran the task again, and the navigation buttons again do not work.  Again, my apologies.

On May 23, 2025, at 8:30 AM, João Dias <joao...@gmail.com> wrote:



[ISILDUR]

Hi, just to let you know - suddenly recent apps started working again!

[João Dias]

Oh, cool! 😁

[João Dias]

Do the buttons work before you run the task again but after you turn the accessibility service on?

[Alan Levine]

Not exactly sure what you mean, but the buttons work until I run the task, stop working after I run the task, and begin working again after I turn accessibility off.  If I then turn accessibility back on, the buttons work until I run the task again and then stop working once I run the task.  Running the task breaks/disables the buttons, turning off accessibility restores the function of the buttons.

On Wed, May 28, 2025 at 9:58 AM João Dias <joao...@gmail.com> wrote:

Do the buttons work before you run the task again but after you turn the accessibility service on?

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFfq6cACMvYroT-dxm75ocvzhYtG%3DLKsjgNCLWVHSSQQew%40mail.gmail.com.

[João Dias]

Yes, that's what I meant, thanks.

Can you please export your task's description (not xml) so I can take a look? Long-click the task in Tasker->export description Thanks in advance

[Alan Levine]

Task: Forward GV Text
  
    A1: AutoInput Actions v2 [
         Configuration: Actions To Perform: openApp(com.google.android.apps.googlevoice)
       
         click(point,484\,344)
       
         click(point,262\,1892)
       
         longClick(point,263\,1891)
       
         click(point,894\,166)
       
         openApp(com.google.android.apps.messaging)
       
         click(point,937\,2071)
       
         openApp(com.google.android.apps.googlevoice)
       
         click(point,974\,1891)
       
         click(point,909\,1502)
       
         click(point,79\,1498)
       
         click(point,703\,1495)
       
         click(point,185\,1500)
       
         click(point,594\,1502)
       
         click(point,689\,1493)
       
         click(point,167\,1505)
       
         click(point,430\,443)
       
         click(point,548\,1243)
       
         click(point,1012\,1237)
         Not In AutoInput: true
         Not In Tasker: true
         Separator: ,
         Check Millis: 1000
         Timeout (Seconds): 60
         Structure Output (JSON, etc): On ]
  
    

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFe6vVbthhf1zG-jxfwjOiiwc0nd9wVWBTL6SgrB%3DDeLew%40mail.gmail.com.

[João Dias]

Thanks. Can you try reducing that action to just openApp(com.google.android.apps.googlevoice) and see if it still blocks the keys?

[Alan Levine]

I wasn't sure how to edit it, so I made a new task that just opens googlevoice as you asked.  I can run that without it disabling the navigation keys.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFdBcMjvdwG7oDd21Q8D%2Ba-zkCar61JDPsZ_mBnJOYEfHw%40mail.gmail.com.

[João Dias]

Thanks. Can you try adding just 1 click after that and see if it still works?

[Alan Levine]

I added one click action and the navigation buttons still work

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFe8Py995-bsJCZxWmNTcHvJ8XYPiM%2B1v3jLqMW%2BgcEj1g%40mail.gmail.com.

[João Dias]

Thanks. Can you continue adding until they stop working like in the other example? That way I can better figure out what could be happening...

[Alan Levine]

I've been remaking the task each time with the helper because I don't know how to edit it otherwise, so this is a substantial ask.  Is there an easy way to add actions by editing it instead?

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFdNT%3DLE8t8pm4ikybKk3j%2Bxd-GmzQp_%2BhFNEo7f07N5RQ%40mail.gmail.com.

[João Dias]

When using the helper you can select to add to the existing actions instead of replacing them. Did you see that?

[Alan Levine]

I'm getting inconsistent results. Sometimes after two actions - one to open the app, and one to click -- it will work the first time w/o disabling the navigation buttons, but then I will run it again and it will disable them. The after resetting accessibility, the task won't run at all.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFf61J%2BTujuFfQrDq_2TrJOHuPrvVLL1EA3bxvGt63Wd6Q%40mail.gmail.com.

[João Dias]

Is it's not too much to ask could you create the minimum task possible that always makes the button stop working for you? I want to try and recreate the exact same conditions that I know will break it for you. Thanks in advance

[Alan Levine]

Like I said, it is inconsistent. This does it sometimes, but not others.  I think it kills the navigation buttons when the task can't complete for some reason, but i don't know why this completes sometimes, and sometimes not.

    Task: Ai3

   
    A1: AutoInput Actions v2 [
         Configuration: Actions To Perform: openApp(com.google.android.apps.googlevoice)
        

         click(point,122\,179)
        
         click(point,203\,799)
        
         click(point,83\,171)

         Not In AutoInput: true
         Not In Tasker: true
         Separator: ,
         Check Millis: 1000
         Timeout (Seconds): 60
         Structure Output (JSON, etc): On ]
   
   

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFfmPo_JyEgdv9SDE1vPufx1UJCh80ZcrER_q8URSdifag%40mail.gmail.com.

[Alan Levine]

Sorry, it is early and I didn't register that you said always.  I really have been unable to figure out what the minimum is that always makes the buttons stop working.  I really do think now that they stop working when the task is unable to complete for some reason -- task gets stuck while executing and buttons stop working.  This probably has to do with my configuring the task with the helper.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFfmPo_JyEgdv9SDE1vPufx1UJCh80ZcrER_q8URSdifag%40mail.gmail.com.

[João Dias]

Hhm, ok, can you do another test: in the AutoInput action just add a wait of 10 seconds and run it. Do the buttons become unresponsive during those 10 seconds?

[Alan Levine]

Again, inconsistent results.  But, when it does freeze the buttons it is on a click>find>absolute action, which initially works while setting it up, but sometimes yes, sometimes no when testing it. When it doesn't work (the point is not clicked), the buttons freeze.  I've also tried to build a task with the helper that just opens the voice app and then waits 10 seconds -- the buttons do not freeze during these 10 seconds.

On Jun 2, 2025, at 5:22 AM, João Dias <joao...@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFfHJJ79w%2Bd8D6i1%2BbF0FoMk_sY%2BNit79amJZQBArkFzww%40mail.gmail.com.

[Alan Levine]

Again, inconsistent results.  But, when it does freeze the buttons it is on a click>find>absolute action, which initially works while setting it up, but sometimes yes, sometimes no when testing it. When it doesn't work (the point is not clicked), the buttons freeze.  I've also tried to build a task with the helper that just opens the voice app and then waits 10 seconds, but when building this act and performing each action during the build, the wait 10 seconds never seems to complete as the helper never asks if I want to add another action.

On Jun 2, 2025, at 5:22 AM, João Dias <joao...@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFfHJJ79w%2Bd8D6i1%2BbF0FoMk_sY%2BNit79amJZQBArkFzww%40mail.gmail.com.

[ISILDUR]

Hi Joao,

I found the reason why the recent apps action stops working. It’s caused by switching the graphics driver on Samsung Galaxy devices to Vulkan instead of the default one.

Recently, with the introduction of Android 15, Vulkan drivers have become quite popular due to the significant improvements they bring to system performance. I’ve been using this method myself, and after several tests, I can confirm that switching to Vulkan causes Tasker to produce the issue mentioned above.

Interestingly, the Vulkan driver change isn’t permanent — it has to be reapplied after every reboot. Thanks to this behavior, I was able to identify that it’s specifically the Vulkan switch that triggers the problem with Tasker and the recent apps action.

Please investigate this matter. Here’s the link: GAMA

https://github.com/popovicialinc/gama

On Wednesday, 7 May 2025 at 11:43:10 UTC+1 joaomgcd wrote:

Weird. both work for me... What Android version are you using?

[Ed Lawler]

Switching drivers may be one reason, but it is not the only reason. I still periodically have the problem and I have never touched a driver  or any other stock Android service. Other than Samsung add-ons such as Good Lock, Android 15 is not being modified, nor have I rooted it.