Skip to content

SMS messages fail to be delivered in “Do Not Disturb” mode #824

Description

@asluihtweoirpuqpwe

Checklist

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

Affected app version

1.8.1

Affected Android/Custom ROM version

Android 15

Affected device model

Motorola moto g15 power

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Have Fossify Messages set as the SMS app. Enable “Do Not Disturb” mode and disable all exceptions; optionally, forcibly terminate the messaging app. Lock the screen and leave the phone unattended for about 30 minutes. Then have the phone receive an SMS message.

Expected behavior

All messages received by the phone eventually appear in the inbox, regardless of whether “Do Not Disturb” is active. In “Do Not Disturb” mode, notifications may be silenced, delayed or suppressed entirely, but received messages are still stored.

Actual behavior

The SMS message fails to appear anywhere. Messages are apparently received by the phone, as evidenced by adb logcat traffic, but they are not routed to the app. The app does not manage to notify about the message or even store it in the inbox; the message is essentially dropped on the floor as soon as it is received and no record of it appears.

Screenshots/Screen recordings

No response

Additional information

Discovered by having the phone permanently in “Do Not Disturb” mode. Messages do arrive if the app has recently been opened (which triggers silent notifications). Creating a “People” exception to “Do Not Disturb” mode covering “Messages” from “Everyone” appears to work around the problem. Adding an “Apps” exception covering the messaging app itself does not. The app otherwise has all power and data traffic limiting exceptions enabled.

Google’s messaging app (com.google.android.apps.messaging) does not seem to be affected. Device is not rooted, though it has been considerably de-bloated, including disabling Google Play Services (these need to be re-enabled to use Google’s app).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is not workingneeds triageIssue is not yet ready for PR authors to take up

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions