diff --git a/FAQ.md b/FAQ.md
index b346fbd9f2..22d85a22de 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -896,6 +896,9 @@ In the settings you can select a schedule for message synchronization (this is a
 Some providers don't follow the IMAP standard and don't keep connections open long enough, forcing FairEmail to reconnect often.
 You can workaround this by lowering the keep-alive interval in the advanced account settings to for example 9 minutes.
 
+Some providers send every two minutes something like *Still there* causing network traffic and FairEmail to wake up and thus extra battery usage.
+You can long press *Operations* in the main navigation menu to check if your provider is doing this.
+
 If you got the message *This provider does not support push messages* while configuring an account,
 consider switching to a modern provider which supports push messages (IMAP IDLE) to reduce battery usage.
 
diff --git a/app/src/main/java/eu/faircode/email/ServiceSynchronize.java b/app/src/main/java/eu/faircode/email/ServiceSynchronize.java
index 610935b1d8..3f8583a1bf 100644
--- a/app/src/main/java/eu/faircode/email/ServiceSynchronize.java
+++ b/app/src/main/java/eu/faircode/email/ServiceSynchronize.java
@@ -592,7 +592,7 @@ public class ServiceSynchronize extends LifecycleService {
                         @Override
                         public void notification(StoreEvent e) {
                             if (e.getMessageType() == StoreEvent.NOTICE)
-                                Log.i(account.name + " notice: " + e.getMessage());
+                                EntityLog.log(ServiceSynchronize.this, account.name + " notice: " + e.getMessage());
                             else
                                 try {
                                     wlFolder.acquire();