LineageOS delays notification, despite io.heckel.ntfy.MESSAGE_RECEIVED intent being sent about ntfy HOT 3 OPEN

Ok, I'm trying to understand what is going on from the logs.

First of all, looking through the from-app captured log, i see a Sending message intent broadcast: line, but no corresponding Broadcast received: line (?!?).

Are those logs collated somewhere else? Where can I find those?

That said, from the Displaying notification Notification(...) log entry, it seems that NotificationService.display is getting called, but is it completing? And moreover, is the subsequent call to NotificationManager.notify (from within displayInternal) getting the wakelock handed off to it (or held for it? I don't know the convention here).

In short: I think that that UserActionManager is being tasked to handle two kinds of work: tasks that should be handled once the phone wakes up (like sending network responses) and also things that need to be handled immediately (like sending notification to the user, passing off unifiedpush messages to other phone apps).

Shouldn't those two kinds of tasks be handled separately? Both seem to be enqueued at the same time there?

from ntfy.

To address your first point (no corresponding broadcast received), I wouldn't expect ntfy to receive its own intent. I'm pretty sure (without digging into the code right now) that the message intent broadcast line corresponds to the setting in the Android app settings called "Broadcast Messages."

If you disable "Broadcast Messages", I would expect that line in the logs to go away. I believe the Broadcast Messages setting is only there for automation apps, like Tasker and MacroDroid, to react to received notifications. I'm pretty sure UnifiedPush continues to work (e.g., broadcast message intents to UP apps) in the background, even if that setting is disabled

from ntfy.

Doesn't BroadcastReceiver in BroadcastService.kt receive the SEND_MESSAGE intent? The comment there at least suggests it does. But thank you for pointing out another thing it should be doing, and also explaining why it shouldn't be showing up! Anyway, it doesn't really matter.

I am able to confirm that holding the wakelock for another few seconds causes the phone to respond to incoming messages nearly instantaneously. I've put this into a WIP patch.

@wunter8 I'd really appreciate your insight in that PR when you have time.

from ntfy.