Calls ringing through bedtime mode

[AmeliaMN]

I've been experiencing an issue that I believe is a bug. I have bedtime mode set up to turn on and off automatically. I have the mode configured to allow interruptions from my starred contacts. I do not have the "allow repeat callers" checked. I use the stock Graphene phone/contacts app to star contacts.

I regularly get a call at 5 am (during my bedtime mode hours) from a contact that is not starred. When this call comes in, both my phone itself and my bluetooth-linked smart watch (Withings brand) go off.

I'm happy to provide any type of logs or additional system details that might be helpful!

[inthewaves]

Android apparently waits at most 3 seconds to look up a contact for an incoming call, and if it takes too long, it just automatically marks the call as from a starred contact which would satisfy your bedtime mode: https://github.com/GrapheneOS/platform_frameworks_base/blob/2026060600/services/core/java/com/android/server/notification/NotificationManagerService.java#L549-L557

When this fallback behavior happens, there should be system log entries for it: https://github.com/GrapheneOS/platform_frameworks_base/blob/2026060600/services/core/java/com/android/server/notification/ValidateNotificationPeople.java#L211-L219

try {
    if (!s.tryAcquire(timeoutMs, TimeUnit.MILLISECONDS)) {
        Slog.w(TAG, "Timeout while waiting for affinity: " + key + ". "
                + "Returning timeoutAffinity=" + timeoutAffinity);
        return timeoutAffinity;
    }
} catch (InterruptedException e) {
    Slog.w(TAG, "InterruptedException while waiting for affinity: " + key + ". "
            + "Returning affinity=" + affinity, e);
    return affinity;
}

The system log can be accessed in OS Settings > System > View logs (only visible from owner user of device). There is a search function; try to see if you have any entries for the string, while waiting for affinity. If it's been too long since it happened, the system log might not show it, since it's not infinite afaik

Note that this specific code seems to have existed since 2014 due to GrapheneOS/platform_frameworks_base@12aeda8