Hiring Tasker Pro to debug clipboard issue, description bellow

• Tasker-Random-Stuff

  22 13 0.0 Shell

You are running a loop every five seconds. There might be issues with intent limits, sending too many will likely result in delays from android os, and if autoinput in not processing stuff quickly enough. There might also be issues with android os killing autoinput or it crashing for some reason resulting it in not receiving intents, or tasker getting killed and task stopping, since you are saying keyboard method stops working too. You should start relevant tasks in Monitor Start event so that when tasker process restarts, your task starts running again. If you are willing, you could possibly find the real issue with logcat dump, since I am not sure how cache itself would cause the problem, unless internal storage space is running out and android is wiping cache directories of apps to make space, resulting in autoinput getting in an inconsistent state When you detect that its not responding anymore, you can run Save logcat, dmesg and last_kmesg task to get a dump and then see log entries near the time it stopped. Can also run adb logcat -d > logcat.txt from pc or su -c "logcat -d /sdcard/logcat.txt" with root to take a dump. If you don't know when it stops, you can continuously log logcat output with adb logcat > logcat.txt and stop at earliest time with ctrl+c and then see any entries related to tasker or autoinput processes or cache. You may also want to investigate when tasker and autoinput processes and their services are running when they stops responding, I think dumpsys activity should do it. There are other commands for getting process and intent info.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project