canadiancow wrote:I think that might result in issues with closing Waze. If Tasker could do it at all, it wouldn't be able to force Waze to do a "clean" exit. At best, it would kill the process, which could result in some issues.
Yes, it could - like in "a plane could crash onto your head when you leave the house".
I've been using this for weeks - and no "issues" appeared, other than Waze asking each time whether to send a crash report. But that closes on it's own.
It's not difficult to implement. A boolean setting, and one BroadcastReceiver listening for ACTION_DOCK_EVENT with CATEGORY_CAR_DOCK.
Using Tasker would have the advantage of also being able to automatically start Waze upon connecting to your car's bluetooth handsfree device. I guess there are more people that have one then there a people having a car dock.
Closing Waze the clean way could be done by Waze reacting to an broadcast intent. I already suggested that in an earlier thread.
BTW, while we're at it: Waze does not start cleanly when called from Tasker. The blue splash screen comes up and then vanishes - leaving Waze only in the notification bar.