I noticed that if I use Macrodroid's built in "Display Notification" action with "Overwrite Existing Notification" checked, the notification will visibly refresh when updated (disappear and quickly reappear).
If I use AutoNotification to do the same thing, and set an notification ID number for...
I don't know of any way to set an arbitrary timeout on OOS12 or OOS13, but if you want to stay awake for a certain amount of time, you can automate pressing an unknown button to keep your phone awake. I haven't noticed any side effects from this.
If your on android 12 or older, you can detect Android auto via logcat messages.
If your on Android 13 or newer, log cat is now blocked, and I had to switch to detecting the android auto notification.
As of Android 13, the above tools, even when systemized, stopped working.
I did however discover that the VPN hotspot app is somehow able to toggle BT tethering off and on with only root without being systemized, on my OnePlus 8 Pro.
Unfortunately, VPN hotspot has no automation functionality...
I think I'm doing something similar to you in my car.
I handle screen dimming by setting an unlimited screen timeout and then I alternate brightness between Auto and 0%.
To detect screen presses anywhere like you want to do, I'm pretty sure you need to use the TouchTask plugin. I don't think...
FYI: I did some logcat exploring last night, and found on my Android 12 phone both CAR.SERVICE and CAR.SERVICE.LITE have good "CONNECTED" and "DISCONNECTED" events you can use as triggers for detecting android auto starting and stopping.
I don't know how hard it would be to implement, but this is a code snippet from the Android Auto documentation:
https://developer.android.com/training/cars/apps#car-connection
Pretty sure this is how Tasker updates %UIMODE
I've been doing a lot of Android Auto macro testing with Headunit...
I had this failure happen again, while I was set to QHD+. Same symptoms. But this time it started after I rebooted while I had Full Sensor Rotation on. I had to clear Macrodroid's cache and restore from a backup to recover. Going to stop using Full Sensor rotation for a while to make sure...
Confirmed: On my OnePlus 8 Pro, QHD+ is required for "Full Sensor" - "Force Screen Rotation".
It works really good though, once I figured out the resolution thing.
I think I have the problem narrowed down. If my phone is set to FHD+ (2376 x 1080) resolutions (either manually set, or auto select to save power), Macrodroid's Force Screen Rotation and screen orientation based triggers eventually breaks. As long as I leave my phone set to QHD+ (3168 x 1440)...
Using "Force Screen Rotation" set to "Full Sensor" seems to reliably break Macrodroid on my OnePlus 8 Pro on Oxygen OS 12 C33.
If I try using this action, Landscape / Portrait mode detection seems to break, and Macrodroid eventually stops opening. Rebooting doesn't help.
If I try to open...