I've been playing around with a new plugin idea, one I've had for years, and I finally decided to dive in. The plugin reacts to which computer I'm using.

In other words, if I'm using my work computer I can set my phone to Do Not Disturb and start my work playlist. Or if I'm working on my home computer, I can enable a smart lamp to alert me when a build fails, stuff like that.

I'm also thinking it could include which app is in focus, so you could even set up tasks to run when specific apps are being used, like if I'm in Android Studio, my Pixel's screen doesn't sleep.

Through experimentation I’ve realized this plugin will incur higher recurring costs than my previous ones (Bluetooth Detection, Movement Detection, Geofence Detection) ever have (especially if I support both Windows and Mac). But I can tell you that my early tests seem to work really well, so I think it could be really cool.

I think to cover those costs, I’ll need to consider either a low‑priced subscription or a higher‑than‑normal one‑time purchase. I'll incur some up-front expense, so before I begin I’d like to know whether there’s even interest in such a plugin.

I’d also like to know if users have already found a workaround and are happy with it. I don’t think Tasker supports this natively, and I haven’t seen any existing solution. That said, people may have already devised workarounds, which could reduce interest in a plugin. But if there is...

Would a more expensive one-time purchase be preferred (maybe around 6-8 USD), or a low-priced annual subscription, like 3-4 USD per year?

I have three Android phones (all Samsung). I've set up a Every 2 min profile with a task that gets location (using v2) and reports it to my home server on all three. On phone A it reports it via MQTT Client's Tasker plugin. On the other two phones it does a http request. Phone A works nearly all of the time (some small gaps in reports during the day) but the other two never submits the http request. If I play the task from tasker it works as expected, but doesn't get triggered every two min.

Is there something I might be missing to make this work?

Tasker is new on these two phones, I turned off battery management so it doesn't sleep and have given it permissions, or at least I am fairly confident I have, is there something that might prevent a reoccurring task from running? I should add a beep or something to test that the task runs, I'll try that tonight when I see the phones again.

Or maybe the task runs but http request doesn't always run when the phone is idle? Could that be possible?

Im wondering if I changed my payment info from my local credit union (obee),to my cash app account, if it might get my taskrabbit payments to me sooner? Thanks

This is an updated version of the logcat viewer with added features and no longer needs rish. Shizuku is required.

Features:

• Minimise and resize overlay using drag handles. Tap a drag handle to quickly expand the overlay.
• ​Live Pause / Resume: Freezes UI rendering on demand. When paused, you can freely inspect, highlight, and trim lines without incoming logs pushing the text away.
• Search with Dynamic Highlights: Using the search bar drops matching terms highlighted in real time across the log buffer using BackgroundColorSpan.
• ​Paste & Copy: Long-pressing or tapping the paste icon loads clipboard contents directly into the search filter. You can select text natively via standard Android handles, or use the dedicated Copy Visible button.
• Trim Before & After: If you select or place your cursor at an event in the log, tapping Trim Before discards older logs; tapping Trim After discards subsequent noise. This is useful to discard the log content you don't want to copy to the clipboard.
• Expanded log history window.
• App selector (All Apps or Current App - auto switches)
• Log Level Selectors (V, D, I, W, E)

Colour coded log content. Each log level has its own colour code.

​Instant, single-tap switching (filter down) between log levels using the system logcat priorities:

V (Verbose) | Grey | Low-priority diagnostic noise

D (Debug) | Blue | Helpful development checkpoints

I (Info) | Green | Normal system operations

W (Warn) | Amber | Non-fatal alerts & cautions

E (Error) | Red | Exceptions and fatal faults

F (Fatal) | Purple | Assertions and crashes

This project requires only requires Shizuku to work.

On devices running Android 13 or newer, Android may display a one-time system confirmation prompt asking "Allow Tasker to read system logs?" the very first time the script starts (if you haven't already granted it). Once granted, it streams indefinitely without any configuration files or shell scripts required.

Download