When in the run log go to Menu / External Viewer then you can copy paste it here.
I can, but it will show that the task runs on time. The only thing mildly of interest is the start and stop of the task service, several times, AFTER all of the steps have been run.
In the log, the profile goes active shortly after I get in my car, at 17:11:59. The enter task completes less than a minute later, at 17:12:46. It was at least 17:15 before the actions do anything, based on what I actually see happening on my phone. The profile becomes inactive when I leave the car at about 17:30.
Again, I am pretty sure this is not a Tasker problem, since Tasker thinks everything ran correctly.
20160112 17.11.59 P Active ID102 BT Car Mode On
20160112 17.11.59 E Start ID0:0.0 TaskService
20160112 17.11.59 T Running ID95 Turn On Car Mode
20160112 17.11.59 A OK ID95.1 Turn On Car Mode.Var Set, %Carmode=On
20160112 17.11.59 A OK ID95.2 Turn On Car Mode.Bluetooth
20160112 17.11.59 T ExitOK ID95 Turn On Car Mode
20160112 17.11.59 P Active ID62 Car Docked
20160112 17.11.59 P Active ID94 CarModeOn
20160112 17.11.59 E Stop ID0:0.0 TaskService
20160112 17.11.59 E Start ID0:0.0 TaskService
20160112 17.11.59 T Running ID12 Car Docked Enter
20160112 17.11.59 T Running ID30:2 Car Mode On
20160112 17.11.59 A OK ID12.1 Car Docked Enter.Var Set, %CARDOCKED=1
20160112 17.11.59 A OK ID12.2 Car Docked Enter.Bluetooth
20160112 17.12.00 A OK ID12.3 Car Docked Enter.Auto Brightness
20160112 17.12.00 A OK ID12.4 Car Docked Enter.WiFi Net
20160112 17.12.00 A OK ID12.5 Car Docked Enter.WiFi
20160112 17.12.00 A OK ID12.6 Car Docked Enter.Launch App
20160112 17.12.00 A OK ID12.7 Car Docked Enter.If
20160112 17.12.00 A OK ID12.11 Car Docked Enter.Media Volume
20160112 17.12.00 A OK ID12.12 Car Docked Enter.Notification Volume
20160112 17.12.00 A OK ID12.13 Car Docked Enter.Ringer Volume
20160112 17.12.00 A OK ID12.14 Car Docked Enter.In-Call Volume
20160112 17.12.00 A IfFail ID30:2.1 Car Mode On.Car Mode
20160112 17.12.00 T ExitOK ID30:2 Car Mode On
20160112 17.12.15 A OK ID12.15 Car Docked Enter.Wait
20160112 17.12.15 A OK ID12.16 Car Docked Enter.Bluetooth Auto Connect
20160112 17.12.31 A OK ID12.17 Car Docked Enter.Wait
20160112 17.12.31 A OK ID12.18 Car Docked Enter.Bluetooth Auto Connect
20160112 17.12.46 A OK ID12.19 Car Docked Enter.Wait
20160112 17.12.46 A OK ID12.20 Car Docked Enter.Bluetooth Auto Connect
20160112 17.12.46 A OK ID12.21 Car Docked Enter.BT Voice Volume
20160112 17.12.46 T ExitOK ID12 Car Docked Enter
20160112 17.12.47 E Stop ID0:0.0 TaskService
20160112 17.15.48 E Start ID0:0.0 TaskService
20160112 17.15.48 E Stop ID0:0.0 TaskService
20160112 17.16.39 E Start ID0:0.0 TaskService
20160112 17.16.39 E Stop ID0:0.0 TaskService
20160112 17.17.08 E Start ID0:0.0 TaskService
20160112 17.17.08 E Stop ID0:0.0 TaskService
20160112 17.17.12 P Instant ID105 Focus Waze
20160112 17.17.12 E Start ID0:0.0 TaskService
20160112 17.17.12 T Running ID106 Focus Waze Enter
20160112 17.17.42 A OK ID106.1 Focus Waze Enter.Wait
20160112 17.17.42 A OK ID106.2 Focus Waze Enter.Launch App
20160112 17.17.42 T ExitOK ID106 Focus Waze Enter
20160112 17.17.42 E Stop ID0:0.0 TaskService
20160112 17.18.00 E Start ID0:0.0 TaskService
20160112 17.18.00 E Stop ID0:0.0 TaskService
20160112 17.20.41 P Inactive ID102 BT Car Mode On
20160112 17.30.52 P Inactive ID62 Car Docked
20160112 17.30.52 E Start ID0:0.0 TaskService
20160112 17.30.52 T Running ID-6142 System
20160112 17.30.52 T Running ID15:2 Car Docked Exit
20160112 17.30.52 A OK ID-6142.1 Anon.In-Call Volume
20160112 17.30.52 A OK ID-6142.2 Anon.WiFi
20160112 17.30.53 A OK ID-6142.3 Anon.Ringer Volume
20160112 17.30.53 A OK ID-6142.4 Anon.BT Voice Volume
20160112 17.30.53 A OK ID-6142.5 Anon.Notification Volume
20160112 17.30.53 A OK ID-6142.6 Anon.Media Volume
20160112 17.30.53 T ExitOK ID-6142 System
20160112 17.30.53 A OK ID15:2.1 Car Docked Exit.Display Brightness
20160112 17.30.53 A OK ID15:2.2 Car Docked Exit.Auto Brightness
20160112 17.30.53 A OK ID15:2.3 Car Docked Exit.Var Clear, %CARDOCKED=%CARDOCKED
20160112 17.30.53 A OK ID15:2.4 Car Docked Exit.Bluetooth Auto Connect
20160112 17.30.53 A IfFail ID15:2.5 Car Docked Exit.Bluetooth
20160112 17.30.53 P Inactive ID94 CarModeOn
20160112 17.30.53 A OK ID15:2.6 Car Docked Exit.Var Clear, %Carmode=%Carmode
20160112 17.30.53 A OK ID15:2.7 Car Docked Exit.Car Mode
20160112 17.30.53 T ExitOK ID15:2 Car Docked Exit
20160112 17.30.53 T Running ID92:3 Car Mode Off
20160112 17.30.53 A OK ID92:3.1 Car Mode Off.Car Mode
20160112 17.30.53 T ExitOK ID92:3 Car Mode Off
Scott
Can you provide a copy of the run log?
When in the run log go to Menu / External Viewer then you can copy paste it here.
--
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.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.
Anyhow, I can't offer an answer, other than to say have you tried changing the order of the actions or temporarily disabling some of them to determine if there's one in particular that maybe causing the delay?
Yes, I most certainly have made changes. Disabled some actions, removed others completely.
While not totally solved, two things happened that have made an improvement. First, I restarted the phone. This seems to have helped reduce the delay, but it still takes longer than I think it should. Now it's 2 or 3 minutes, not 5 or 10. The very next day I received the January patch update, so my phone would have restarted then if I hadn't already done so. Of course it did again. So the bottom line is that the task performs better, but it's not as instant feeling as it used to be. I still blame Android. I was just hoping someone might have discovered a setting or something that might be the culprit. The delay is annoying, but it's not gonna kill me.
Scott
TimeStamp | Count | Delay |
19:27:57 | 120 | |
19:28:11 | 121 | 00:00:14 |
19:28:13 | 122 | 00:00:02 |
19:28:15 | 123 | 00:00:02 |
19:28:36 | 124 | 00:00:21 |
19:28:56 | 125 | 00:00:20 |
19:29:08 | 126 | 00:00:12 |
19:29:11 | 127 | 00:00:03 |
19:29:13 | 128 | 00:00:02 |
19:29:15 | 129 | 00:00:02 |
19:29:17 | 130 | 00:00:02 |
I've always had battery saver disabled and battery optimizations disabled for Tasker and all of the plug-ins I use (as well as some apps).
I'm going to delay the wifi/off until the end of my task and see if that helps.
I thought I would post an update to this old thread. On Monday of this week, I received the October 5 2016 Security Patch Update for my Nexus 6. It's still on Android 6.01. But what a difference. Tasker is running tasks almost too fast, now. The task I wrote about here is working correctly once again. I have no idea what Google fixed with this patch update, but they certainly did fix something. I guessed this was a Google problem from the beginning, but I had no way to prove it. I don't have Android 7, yet, but I know it's coming soon. I hope Google doesn't screw it up again when I get that version.
Thanks to CoolRaoul pointing me to this post from another. This seems to be the exact same problem as I have (Android 5.0, latest Tasker), at least now I confirm it's not my phone or any app I installed that conflicts. And it seems the delay is somehow related to wifi and/or bluetooth on/off, as this usually happens when I'm switching location based on cell tower/wifi, and then for now reason (now there is) there is a delay of seconds to minutes.Does anyone figure out a workaround? I'll also try pushing the wifi/BT on/off later in the tasks, and calling a separate tasks and see if that helps. From Phil's posts it seemed it's not speeding it up.
In all case it seem that switching networks (from mobile data to wifi and back or when activating VPN too ) have a huge impact on Tasker performance.
Coincidentally, I just noticed today that activating the VPN causes a Tasker monitor restart on the S7, possibly other network events do too.