Strange, it consumes some cpu even on my idle phone (~3%, but it may be misleading, I’m not sure how fast cpu is running at this state).
To dbus-monitor, it is simple. As root, just execute:
dbus-monitor --system
There is some activity from logind (path /org/freedesktop/login1
belong to logind)
signal time=1636672660.372447 sender=:1.6 -> destination=(null destination) serial=81804 path=/org/freedesktop/login1/session/c1; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.freedesktop.login1.Session"
array [
dict entry(
string "Active"
variant boolean true
)
]
array [
]
signal time=1636672660.377794 sender=:1.6 -> destination=(null destination) serial=81805 path=/org/freedesktop/login1/seat/seat0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.freedesktop.login1.Seat"
array [
dict entry(
string "ActiveSession"
variant struct {
string "c1"
object path "/org/freedesktop/login1/session/c1"
}
)
]
array [
]
But I am not sure what exactly these properties mean. My guess is that it is signaling if session is active and it is caused by short cpu sleeps…? Not sure without reading documentation / source code.
But I believe that this activity is not caused by another application, they are signals triggered by logind.