Macrodroid not firing even though phone gets woken up for other tasks?

lloydthedroid

New member
I'm having a good time with Macrodroid on my stock Pixel 5 (Android 13) after setting it up to act like Llama, changing phone settings based on the current cell tower.

However, the app does not seem to trigger as efficiently as Llama did in some situations.

When the phone is idle and I enter a new area, then the phone rings due to a call or sounds a notification from calendar or another app - with Llama, the phone's sound would start up at the volume set for my previous area, then within a half second Llama would kick in, notice the cell tower change and then set the volume for the current location. So I'd hear the notification's volume change midway, and would know Llama was working as desired. But with Macrodroid, the app doesn't wake up with these events. It won't notice the new area until I unlock the phone to use it for something.

I have Macrodroid set to look for cell towers every 2 minutes. But if the phone is idle it does not detect any changes until I unlock the phone. I have Macrodroid exempted from battery optimization. I briefly tried using "alarm mode" for the cell tower polling, but I have the time of the next alarm displayed in another app and that became useless so I didn't use that feature.

I have Macrodroid showing a clearable notification at all times, displaying when the last area change was. I recall with previous Android versions that was supposed to help Android prioritize the app, but it doesn't seem to make much difference now.

I don't really need Macrodroid to wake up every 2 minutes, but it would be really good if it woke up whenever the phone was doing something else like taking a call or playing another notification. Are there any more settings to try out?
 

lloydthedroid

New member
The site says the Google Pixel phones are mostly well-behaved. The only thing they mention is exempting the app from battery optimization, which I did immediately after installing the app.

I should mention that Macrodroid missing an area change doesn't always happen - sometimes it picks them up when expected.
 

MacroDroidDev

Administrator
Staff member
Unfortunately things have moved on a lot from the time llama was popular and phones are massively more restrictive in terms of background updates (I assume it's at least partly responsible for llama being abandoned). If you don't set the alarm option then there is no guarantee that the phone will wake up when requested (and they all pretty much wake up when they feel like rather than when asked for).

It is certainly true that pixel devices are about as good as it gets, but they still have the same limitation as above.
 
Top