ACR does not work if phone is in Do Not Disturb mode

Issue #2301 resolved
Adam Klobukowski created an issue

ACR does not work if phone is in Do Not Disturb mode.

Samsung Galaxy S7 Edge (SM-G935F) with Android 8.0.0.

Comments (9)

  1. Adam Klobukowski reporter

    I do not have any disabled notification. I'm not 100% sure if it is DND mode issue to be honest, but recently I'm implementing my own webhook so I have a sort of call log on my server, and thats how I noticed there is something wrong.

    I have automatic DND mode on 22:00-6:00. While I see ACR notification outside this hours (and it works), I was not present when I noticed the problem (it was my DND time). I have none so called ram/battery 'optimizers' installed.

    On DND mode, there is a section with 'App rules' (my probably not correct translation to english) section. I can't do anything there (it is empty, there is no way to add/modify anything), and I think apps should/could add DND related rules there. Maybe it is worth checking.

  2. copluk repo owner

    It is not possible for apps to add such rule. I am using DND mode on similar times. What happens when you make or receive test call during those times? Does ACR notification blink?

  3. Adam Klobukowski reporter

    There was no ACR notification.

    I've checked my phones ACR notification settings, and everything is 'on' (notification on, app icon badges on, main on, high priority on, low priority on, cloud upload on).

  4. Adam Klobukowski reporter

    I investigated #607 before starting this issue, and while my UI looks very different, I found out that ACR is on the list of apps that have no limits on battery usage, and are not throttled power-wise.

  5. copluk repo owner

    No notification means ACR is closed. ACR cannot close itself, therefore something on your phone must be closing it. Perhaps you have selected DND to close/hide all notifications?

  6. Adam Klobukowski reporter

    That might be it. I'll expeirment with notification settings a bit and I'll let You know.

  7. Log in to comment