Sometimes no notifications for new received SMS messages

[jimbobcraig]

Checklist

• [X] I can reproduce the bug with the latest version given here.
• [X] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• [X] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• [X] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• [X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [X] This issue contains only one bug.
• [X] I have read and understood the contribution guidelines.

Affected app version

1.0.1

Affected Android/Custom ROM version

Android 12

Affected device model

Nokia G22

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Receive an SMS from and external number (contact or non)

Expected behavior

Receive a notification when a new message arrives.

Actual behavior

Sometimes there is a notification, sometimes there is not. I can open the app manually and then the message list will show one conversation in bold (although in the list view the new message is not previewed) When I open the conversation then the new message appears at the bottom.

There seems to be no corelation between do-not-disturb / silent / vibrate global settings.

It appears random at the moment and has been an issue since installing. This wasn't a problem when the app was "simple mobile tools" AND before the Android 12 update but I can't pinpoint exactly when it started to happen. It's intermittant. Doesn't seem to differentiate between contacts or non-contacts. There are no per-contact custom notifications set. I have tried a "reset to defaults" of all phone notifications, but the behaviour persists.

Screenshots/Screen recordings

No response

Additional information

No response

[ulfi]

Same at my Gigaset GX6 and Android 13. I reinstalled 1.0.1(NeoStore shows installed by F-droid and IzzyOnDroid) I enabled all rights as well marked it as not stopped if it runs in background.

[WebworkrNet]

Device: Samsung Galaxy A13 5G (SM-A136B/DSN) Operating System: Android 14, One UI-Version 6.1 Fossify Messages: Version 1.0.1 Installed by F-Droid

[Jawzper]

Same problem on my device.

Device: Pixel 7 OS: Android 13 Fossify Message: Version 1.0.1 Installed by: Play store

I have gone through my settings carefully to confirm the app should not be getting suspended somehow. Background data is enabled, pausing app if unused is disabled, data access and battery usage are unrestricted, and it's set as the default messaging app. And yet I've apparently been missing messages since yesterday, only to receive them all at once when I opened the app today.

This app is unusable and dead to me until this is fixed - a messaging app that doesn't reliably receive messages is nothing but a source of stress. Some SMS messages are IMPORTANT. This has really ruined my day...

[jackthebean]

I have had this problem for months (both with Simple version and this Fossify version).
Using Android 10, Honor View 20, Fossify Message 1.0.1 and installed from F-Droid.

and again problems are intermittent. Mostly notification appears in proper place, sometimes just a dot on the app icon and sometimes nothing at all and don't see message until I open app for something else.

[rafael-alcantara]

Same here. Notifications are enabled but they don't always are received.

• Android 9
• Messages 1.1.5 installed fron f-droid

[WebworkrNet]

Motorola moto g34 5G XT2363-3

Android 14

[WebworkrNet]

Would support for “UnifiedPush” (or similar) help to keep the “Messages” app in the foreground? Android "likes to park” apps in the background from time to time. Even if you make the corresponding system settings in Android for the respective app, this cannot be completely prevented.

“DAVx⁵”, “SMS-Gate” and “Signal” have their own built-in notifications to keep the app itself active and/or enable notifications. However, I don't know what technology is behind this. At least Signal is based on “WebSocket” and probably even manages without Google's “Firebase Cloud Messaging (FCM)” and is therefore also available on non-Google devices.

I imagine this could also be useful for the phone and calendar app.

Compare:

• https://unifiedpush.org/ (English)

• https://www.kuketz-blog.de/empfehlungsecke/#unifiedpush (German).

• https://f-droid.org/packages/at.bitfire.davdroid/ (English)

• https://f-droid.org/en/packages/com.github.axet.smsgate/index.html (English)

[naveensingh]

SMS/MMS delivery is handled by the system. There's no need for push messages.

The app's role is to write these messages to the database and notify the user (the glitchy part). This was reported multiple times in SMT but I was never able to reproduce it.