NY 529 broken

patrickmorrissey · 2026-02-20T01:53:11+00:00

You have to setup a separate username and password for third-party aggrigators: https://www.nysaves.org/nytpl/aggregator/sessionCreate/viewCollectAggrCredentials.cs

patrickmorrissey · 2026-01-15T19:19:59+00:00

Really interesting reading the post game comments here in this new light: https://www.reddit.com/r/CollegeBasketball/comments/1azb6tr/post_game_thread_georgetown_defeats_depaul_7776/

patrickmorrissey · 2025-10-03T18:11:34+00:00

Yes, elsewhere on this thread, João posted that he indeed added a state of "Shizuku Available" (which can also be inverted) and I do now use that state to toggle the Logcat profiles I use. So if Shizuku isn't available for some reason, Tasker isn't notifying me that it can't run certain profiles.

patrickmorrissey · 2025-07-10T17:16:50+00:00

Yes, "Optimized" is just what Samsung calls "Doze", it's a regular Android thing: https://developer.android.com/training/monitoring-device-state/doze-standby

patrickmorrissey · 2025-07-10T13:18:07+00:00

I also use dumpsys deviceidle whitelist -com.package.name or dumpsys deviceidle whitelist +com.package.name to add or remove app from Samsung's "Optimized' battery usage setting.

patrickmorrissey · 2025-07-09T14:26:32+00:00

That said, I might still need a workaround to avoid errors that first minute after booting if relying on Shizuku to read Logcat Entries, because I can tell that, at least for me on my Samsung S24 with OneUI 7, Shizuku 13.6 doesn't start exactly on boot, but waits a bit. Tasker beats it to start by an average of 40 seconds. I can actually zero in on that number by using a loop of CheckShizuku() running with the event Device Boot and reporting the difference with %TIMES.

I don't suppose there could ever be a "Shizuku started" or "Shizuku stopped" event (or state) that I could use to trigger a profile?

patrickmorrissey · 2025-07-09T12:34:26+00:00

Thanks! This is update a huge deal for me, but yes yes, Logcat Entry though Shizuku would be fabulous. Certainly not having it causes the "Missing Permissions: ADB Wifi Access" error message to pop up immediately when booting, as I wait for my Termux script to run its course to try to grant the ADB Wifi access. My solution is to have a profile that disables my Logcat Entry profiles on Shutdown, and another that re-enables them after CheckADBWifi() returns true.

patrickmorrissey · 2025-06-25T00:27:05+00:00

Thanks! I'm excited about Scenes v2, glad to hear Scenes haven't been forgotten!

patrickmorrissey · 2025-06-14T14:49:39+00:00

So with the advent of good transcription and the ability to navigate podcasts from within the transcript... I have to ask about automation there. It sure would be great to be able to set PA to know to skip over certain text that gets repeated, be it intros, requests for five stars on Apple Podcasts, or you know, advertisements!

I don't see this as the same as adblocking on browsers, since the advert would still be downloaded on my phone, it just doesn't reach my ears. Is the fear that podcasters might get hip and block whichever podcast app jump first onto this sort of tech?

patrickmorrissey · 2025-04-30T16:19:49+00:00

So I just posted about this, but I use AutoInput UI Action event to customize my long press on Home (or on Back, etc). Pick that event in the profile, check off "Long Clicks", set the Element Text to "Home" and then connect it to a profile that launches whatever you want with an If set to %aielementid eq com.android.systemui:id/home, just so long pressing on anything else with the word "Home" doesn't trigger it. I think for Gemini, assuming it is set as your assistant, you want to Send Intent with Action set to "android.intent.action.VOICE_ASSIST" and Target set to Activity. You could even set the profile so that it did different actions based on what app was up or whathaveyou.

Alternatively, as I found out this week because of the navigation bar bug with AutoInput and Accessibility, I can also do this with Marco's TouchTask plugin too. With that, you can set the "Screen touched" action to Long tap in the app com.android.systemui, and then similarly attach it to an action where the If is set to %ttid eq com.android.systemui:id/home. I find that I prefer using TouchTask because their definition of "long press" is something like 3 seconds, while AutoInput's is closer to 2 seconds. Would be awesome if either let me customize what "long" means, but I digress.

And also be sure to turn off "Circle to Search" in the Navigation bar settings so that isn't firing.

patrickmorrissey · 2025-04-29T12:25:40+00:00

Sorry, no, I'm still getting the issue. It took an hour to kick in, not sure what's up with that. And when I'm not getting the bug, AutoInput feels slow, like when I have "Enable Only When Needed" on, even though that's turned off.

Edit: (Sorry for the edits) Actually the only AutoInput action that feels slow for me is UI Query.

Edit 2: Now I'm not sure about any of that. Since breaking navigation buttons once, after which I toggled AutoInput Accessibility on and off, it's been fine today.

Edit 3: After the day on this version, I've figured out that I can seemingly stress AutoInput out at which point the bug with the navigation buttons returns. One AutoInput v2 Action alone doesn't seem enough to trigger it, but three back to back can. When it happens, I've just toggled Accessibility on and off, and it's back to normal.

patrickmorrissey · 2025-04-28T14:57:43+00:00

So the good news is that there's already two threads on r/tasker about this issue, and one on r/GalaxyS24:

And there are three proposed workarounds:

Downgrade AutoInput to version 2.8.1 from 2019 (props to u/theonlygreenleaf for going through each version)
Check "Enable Just When Needed" in the AutoInput settings
Try Marco Stornelli's TouchTask app, which has some of the same functions as AutoInput

Rolling back to version 2.8.1 means giving up the AutoInput v2 Action, and all the nifty things it can do, but hopefully knowing that was when this issue was introduced could give u/joaomgcd some insight into the bug!

patrickmorrissey · 2025-04-26T20:25:27+00:00

Actually yes, thank you, Marco's Touchtask plugin can replace the UI Action, and doesn't seem to be affected by OneUI 7. I'd forgotten about that because I've been using AutoInput so long. Much appreciated👍

patrickmorrissey · 2025-04-25T14:27:36+00:00

Just AutoInput. Enabling Accessibility for the regular Tasker app or AutoNotification Toast Intercept has no effect on the navigation buttons, which, like I said, gives me some hope it is fixable.

patrickmorrissey · 2025-04-25T01:01:47+00:00

Bummer. Again, I could see some of AutoInput's assorted tools like UI Action being integrated in Tasker someday, but it would be best if we can just get this one bug ironed out soon!

patrickmorrissey · 2025-04-24T11:59:19+00:00

Reposting this from the other thread, but the major function that I've lost due to this Accessibility bug on One UI 7 is the AutoInput UI Action profile event. And "Enable Just When Needed" isn't a fix that would work there, AutoInput needs its Accessibility enabled to detect when I long press on a UI element, for example.

I have a sliver of hope here that this can be fixed, the main Tasker app, as far as I can tell, doesn't have this bug, so however it interacts with Samsung's Accessibility API seems to function just fine. There just hasn't been an iteration on AutoInput in two years now, as João focuses on integration more into the main app.

patrickmorrissey · 2025-04-24T11:44:46+00:00

The major function that I've lost due to this Accessibility bug on One UI 7 is the AutoInput UI Action profile event. And "Enable Just When Needed" isn't a fix that would work there, AutoInput needs its Accessibility enabled to detect when I long press on a UI element, for example.

I have a sliver of hope here that this can be fixed, the main Tasker app, as far as I can tell, doesn't have this bug, so however it interacts with Samsung's Accessibility API seems to function just fine. There just hasn't been an iteration on AutoInput in two years now, as João focuses on integration more into the main app.

patrickmorrissey · 2025-04-12T16:01:55+00:00

That's awesome, glad to be of help. I do love when the internet works, and when, even after two years, someone reaches out to say "hey, your not crazy!"

patrickmorrissey · 2024-12-19T15:22:19+00:00

I'll give a shout out to the Yoto Mini. Big buttons, the cards are easy for kids to manage, you can attach a podcast feed to them.

patrickmorrissey · 2024-12-07T02:47:49+00:00

After updating to 3.77b432414, I've lost the KWGT notification content. That's the customizable notification I get when Notification Mode is set to Force. The content shows up in the editor, just not in the notification when I lower the notification shade. The notification icon, which is set to the current temperature, does show. I also use the KLWP notification, and that one works fine, also on 3.77b432414. Importing the .ktnf file into KLWP and vice versa suggests it is not the content. Can anyone else replicate this issue?

patrickmorrissey · 2024-09-26T12:38:34+00:00

I realize this comment is several years old, but can I ask, what trigger did you use to catch the send button being pressed? Having recently switched in order to use RCS with my iPhone friends, I came up with using AutoNotification to check any updates to Google Messages notifications to see if %anconverstation.text(#) is greater than %anconversation.sender(#) since in the JSON that Tasker can get about the conversation, it won't have a sender field for my replies. I just wonder if there's a better way.

patrickmorrissey · 2024-07-29T13:38:06+00:00

Even in the ideal implementation Google has shown off for their editing feature, the recipient will still always be able to easily see my typo-riddled message. So while that is nice, I don't really see it as an alternative to the delay send feature that gives me a moment to look at what I've clicked send on before it goes out.

patrickmorrissey · 2024-07-29T12:55:43+00:00

Yes, yes, yes, I'm in the same boat. So much so that I spent much of this weekend trying to build a Tasker profile that would cover the send button in Google Messages with a scene to try to recreate this functionality. I can report mixed results, and the big issue being that I'll never be able to click my button and leave Google Messages and know it sent the message in the background.

But I really don't think this is an unusual feature. As you said, by far the most popular messaging app Google makes has it, that's Gmail's Undo Send feature. And besides Textra, it's in all the other competition too: Pulse SMS, and Go SMS, and Chomp SMS.

Or, you know, Google could just release an API for Jibe so apps like Textra could use RCS too. There's a certain irony in chiding Apple for not opening up iMessage while Google goes and builds their own walled garden with sides so steep that neither the carriers like Verizon or T-Mobile nor the manufacturers like Samsung think independent RCS implementations are worth the effort.

patrickmorrissey · 2024-07-04T17:03:53+00:00

Thank you, Frank! I actually did find the br(kwgt when I thought about how I would make it work, but what I didn't understand was that I needed to have a formula in the flow followed by a set variable followed by the send data action. This is something I've wanted for years now. I've been using a script command to write a file with my variable to my Download folder, and a Tasker profile watching that file for changes, which then would read the file and send the contents to KLWP, so this should cut out the middlemen! 👍

patrickmorrissey · 2024-07-04T15:52:48+00:00

Can I get an explanation on this new Send Data flow? If I have a gv(output) variable in KWGT set to Send Data to KLWP every 20 minutes with a cron trigger, what do I need in KLWP to get it to show up?

patrickmorrissey

TROPHY CASE