FP6: Do Not Disturb automatically turns itself off

I’m using a FP6 with the Android 15 based /e/OS 3.3 (official), since Christmas, and I’ve noticed a weird behaviour with Do-Not-Disturb on the device:

I’ve set the Moments switch to enable Do-Not-Disturb when set, and have no schedules set for enabling Do-Not-Disturb. I usually set Do-Not-Disturb via the Moments switch and leave it there 95% of the time, except in rare cases like when I expect a phone call from an unknown number.

What’s strange is that, for some reason, Do-Not-Disturb keeps automatically turning off around once per day even though the Moments switch is still set, but at seemingly irregular times. The behaviour is usually that I unlock my phone, I’m surprised that I hear the unlock sound (because Do-Not-Disturb was off), and then I see a small toast at the bottom of the screen with “Do-Not-Disturb disabled”.

When googling for issues like this I find cases across multiple different Android ROMs on many different devices, but there people often talk about Bedtime mode, Mode schedules, and Mode syncing with smart watches.

  • /e/OS does not have Bedtime mode in the settings, at least I can’t find it
  • The default Do-Not-Disturb Mode doesn’t even have the possibility for me to add a schedule in the Mode menu (if I add a custom mode, I can add a schedule)
  • The quick settings duration for Do-Not-Disturb is “until you turn off”
  • I don’t own a smart watch, and the setting for syncing modes is also not in the settings.
  • No app besides “Shell” (which I can’t remove) is allowed Mode access
  • Additionally, no triggers for device Profile transitions are set up (I’m only using the default profile)

Does anyone else experience this issue or an issue like it, or know whether there is a workaround for it?

It strikes me that this Do not Disturb Mode is as a “demonstration” from this screenshot it is clearly intended as less than Do not Disturb.

I guess you can create “new” Modes with filters more close to what you need.

The filters work completely fine! I’ve set it up exactly how I like it. The only issue is just that it turns itself off at unpredictable moments, which sounds like a bug to me (which I should report to the bug tracker).

I also can’t use a custom mode, because I can’t tie the “Moments” switch to custom modes, only Do-Not-Disturb.

I can confirm this happens for me as well.

I use the “Moments” slider on /e/OS to control the do-not-disturb feature.

After a while with the slider in the same position, the mode changes for no apparent reason.

This makes the slider quite useless, as the do-not-disturb mode could deactivate itself in the middle of the might for example.

Is there any bug report for that on the /e/OS gitlab so far ?

EDIT: yes, there is: "Do Not Disturb" mode deactivates on its own when Fairphone "Moments" Switch is set to "Do Not Disturb" (#9132) · Issues · e / Backlog · GitLab

1 Like

Yes, that bug report is by me.

I also finally found a reliable workaround: You need to set the “Moments” switch to something else than Do-not-Disturb, and activate Do-not-Disturb via the normal quick menu, and then it will stay on.

This is sad, because it would be really convenient to use the switch for Do-not-Disturb.

Right now I’m using it for the Flashlight, which is ok, and with /e/OS 3.4 it looks like they’ll import the “Moments” feature from the Stock Fairphone 6 Android ROM.

1 Like

@yrlf thanks for posting the workaround, I’ve seen this bug as well and didn’t know what triggered it turning off again.

This topic was automatically closed after 180 days. New replies are no longer allowed.