Log notices

pull/157/head
M66B 6 years ago
parent 32515e01df
commit 484ee8eeab

@ -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. 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. 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, 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. consider switching to a modern provider which supports push messages (IMAP IDLE) to reduce battery usage.

@ -592,7 +592,7 @@ public class ServiceSynchronize extends LifecycleService {
@Override @Override
public void notification(StoreEvent e) { public void notification(StoreEvent e) {
if (e.getMessageType() == StoreEvent.NOTICE) if (e.getMessageType() == StoreEvent.NOTICE)
Log.i(account.name + " notice: " + e.getMessage()); EntityLog.log(ServiceSynchronize.this, account.name + " notice: " + e.getMessage());
else else
try { try {
wlFolder.acquire(); wlFolder.acquire();

Loading…
Cancel
Save