diff --git a/FAQ.md b/FAQ.md index 8cae1430f6..13492135b4 100644 --- a/FAQ.md +++ b/FAQ.md @@ -3961,6 +3961,9 @@ Some companion apps ignore [local only](https://developer.android.com/training/w causing the summary notification (*nnn new messages*) to be bridged. Unfortunately, it is not possible to workaround this problem. +Some smartwatches do not display notifications with non-[ASCII](https://en.wikipedia.org/wiki/ASCII) characters, +in which can you can enable the option *ASCII text only* in the display settings tab page. + Ongoing notifications shouldn't be bridged, but some companion apps bridge all notifications. This results in the "monitoring" status bar notification to be bridged. The workaround is to disable this notification, see [this FAQ](#faq2). diff --git a/index.html b/index.html index 5cb67742f9..9b5d15c17b 100644 --- a/index.html +++ b/index.html @@ -109,7 +109,7 @@
Block toolbar (version 1.1967+)
When enabled in the three-dots overflow menu of the message editor, a toolbar to perform operations (align text, insert list, indent text, insert blockquote) on a block of text (consecutive non-empty lines) will be shown.
(126) Can message previews be sent to my wearable?
+(126) Can message previews be sent to my smartwatch?
FairEmail fetches a message in two steps:
Directly after the first step new messages will be notified. However, only until after the second step the message text will be available. FairEmail updates existing notifications with a preview of the message text, but unfortunately wearable notifications cannot be updated.
-Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option Only send notifications with a message preview to wearables and if this does not work, you can try to enable the notification option Show notifications with a preview text only. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
-If you want to have the full message text sent to your wearable, you can enable the notification option Preview all text. Note that some wearables are known to crash with this option enabled.
-If you use a Samsung wearable with the Galaxy Wearable (Samsung Gear) app, you might need to enable notifications for FairEmail when the setting Notifications, Apps installed in the future is turned off in this app.
+Directly after the first step new messages will be notified. However, only until after the second step the message text will be available. FairEmail updates existing notifications with a preview of the message text, but unfortunately smartwatch notifications cannot be updated.
+Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a smartwatch.
+If you think this is good enough, you can enable the notification option Only send notifications with a message preview to smartwatches and if this does not work, you can try to enable the notification option Show notifications with a preview text only. Note that this applies to smartwatches not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
+If you want to have the full message text sent to your smartwatch, you can enable the notification option Preview all text. Note that some smartwatches are known to crash with this option enabled.
+If you use a Samsung smartwatch with the Galaxy smartwatch (Samsung Gear) app, you might need to enable notifications for FairEmail when the setting Notifications, Apps installed in the future is turned off in this app.
Some companion apps ignore local only notifications, causing the summary notification (nnn new messages) to be bridged. Unfortunately, it is not possible to workaround this problem.
+Some smartwatches do not display notifications with non-ASCII characters, in which can you can enable the option ASCII text only in the display settings tab page.
Ongoing notifications shouldn’t be bridged, but some companion apps bridge all notifications. This results in the “monitoring” status bar notification to be bridged. The workaround is to disable this notification, see this FAQ.
(127) How can I fix ‘Syntactically invalid HELO argument(s)’?