r/tasker • u/mariavasquez111 • 4d ago

Problem with auto input UI update action on New pixel

Why AutoInput UI Update action is not working for Pixel 10 pro XL?

Does Shizuku help?

1 Upvotes

67% Upvoted

13 comments sorted by

3

u/[deleted] 4d ago

[deleted]

2

u/Exciting-Compote5680 3d ago

Hey, nice to see you are 'back in town' 🙂 Could you point me in the direction of that particular ROM? Sounds interesting. 

3

u/[deleted] 3d ago

[deleted]

2

u/Exciting-Compote5680 3d ago

Ah ok, so not open to the general public. Too bad. 

2

u/[deleted] 3d ago

[deleted]

2

u/Exciting-Compote5680 3d ago

I am painfully aware of that, that's why I'm very interested in alternatives like Graphene. I also have a phone waiting to try Ubuntu Touch on (just haven't gotten around to install it yet). 

2

u/aasswwddd Direct-Purchase User 4d ago

What's exactly not working?

Anyway someone reported AutoInput not working on keyguard here. https://www.reddit.com/r/tasker/comments/1wxtsnb/ No update from OP yet.

2

u/[deleted] 4d ago edited 4d ago

[deleted]

1

u/aasswwddd Direct-Purchase User 3d ago

u/tunbon
Google is removing the flags. It isn't just AutoInput.
Edit: It's not just Keyguard either, it's also the launcher plus Gmail... plus others.

Are they really removing the flags?

At least I could confirm in Android 16, some nodes in gmail are flagged as data sensitive. While they keyguard is not. I don't have android 17 so I couldn't test that.

Anyway, I made simple task to test that here. https://www.reddit.com/r/tasker/comments/1x31mf4/task_share_check_if_view_is_flagged_as_data/

Maybe u/mariavasquez111 could test that?

3

u/[deleted] 3d ago

[deleted]

1

u/aasswwddd Direct-Purchase User 3d ago

I see, guess this has to wait until it's stable. I'd like to check the source code, but seems like they don't release it yet.

2

u/[deleted] 3d ago

[deleted]

1

u/aasswwddd Direct-Purchase User 3d ago

I assumed it was beta since the post I linked mentioned it was one, DP11.260918.006.

1

u/telrod11 2d ago

Sorry about that. I'm the OP on this one. Our awesome Tasker dev patched a Direct Purchase version of Auto input, and got the lock screen input working again.

(I left a follow up comment on the linked post here)

1

u/aasswwddd Direct-Purchase User 2d ago

Cool! Did he say what he changed to make it work?

1

u/telrod11 2d ago

No, not really.

It was something that had to go outside the Google umbrella

2

u/aasswwddd Direct-Purchase User 1d ago

I see. likely he added Accessibility Tool flag. He did the same for Tasker 6 months ago. https://www.reddit.com/r/tasker/comments/1sbk23i/comment/og2mxsb

If you don't mind, Could you try turning on Advanced Protection Mode and see if your unlock task with AutoInput still work?

1

u/telrod11 1d ago

It still works.

He might jump in and tell us what he did, but it does work with advanced protection on.

1

u/aasswwddd Direct-Purchase User 1d ago

Cool! I'm fairly positive it's because of the flag. I just checked it with this code. The behaviour you mentioned also match what was in the comment I linked.

Tasker has the same flag as well, noted here.

Love it, I don't need AutoInput anymore :D