Hi all,
I've been using GrapheneOS for about a year now and with one of the recent updates, I'm not sure which, I've been having trouble with the default SMS app. The issues started with not having vibration on SMS receive when in silent mode (speaker with a cross through it) formerly, it would still vibrate. Then in more recent updates, I also lost all my custom sounds for different contacts in SMS. The sound selections are there and they still play if I check them in the settings, but when a message is received from them, I get the default notification sound. I have confirmed that my vibration motor is still functioning.
These issues have caused me to miss some important messages because: 1. I have my phone on silent at work, but still need to receive messages and 2. the default notification sound is intentionally set to something rather short and unobtrusive but some of my SMS contacts (spouse) have more obvious sounds. I can't find anything in the settings that has changed and it doesn't seem to affect other apps.
Any ideas or is this a bug?

    Statik I experience the same issue. In my case, I used GrapheneOS for almost 3 years with only owner profile and nothing else. I just upgraded my phone to Pixel 8a and enabled multiple users, and not using the owner profile for anything other than updates, etc. Not only it is the SMS app notification sound, but also customized ringtones are not respected by the OS. Even the default ringtone is not played if a customized ringtone is set for a caller. Instead, a weird beep sound is played, which I am not even sure if it is among the choices. I have never had this problem before, and I am suspecting that using the multi-user profile may be the root cause somehow. I reported this today as an issue (#4779) on GitHub.

      I don't think I have multiple users enabled. There is only one user right now. I don't see an option to enable multiple users anywhere to see if it's turned on or off. 'Enable user switch' is off.

      just wanted to say that i am also experienceing the same custom sounds ignoring by operating system since recent os update

      Corellation is not a causation, just because two not randomly picked events happen at the same time they don't have be related. If I were you, I would go over my global device settings and app references in great detail to rule out user input.

        DeletedUser127 That's why I posted here before filing a bug report. I can't find any settings that seem to affect this but I thought I'd ask.

        New data point: sounds work as expected when the phone is unlocked but not when the phone is in the locked state. In the locked state, I get the default sound and no vibration.

          It's likely caused by the recent overhaul and is being looked into now.

          I am also experiencing this same issue. I don't believe multiple users has anything to do with it as I had been using that feature for several weeks at least before this issue started.

          There are times when the custom notification sounds have managed to still show up. Once was while I was still in the conversation thread and a new message came in and the second was after a force stop. After the first notification post force stop however, everything reverted back to the default sound.

          The cause of the issue is known and it will be resolved in a future release.

          13 days later

          Is there an ETA on the resolution to this issue?

          6 days later

          GrapheneOS Messaging version 6 has a complete overhaul of the notification implementation including support for notification channels, chat bubbles, quick replies, etc. It fixes the per-conversation configuration not being respected anymore for the notifications outside the app caused by the initial update of the target API level to 35 (Android 15). It's currently available in the Alpha and Beta channels of our App Store so you can switch Messaging to Beta or Alpha there via the menu to obtain the update fixing this and greatly improving the notifications beyond how they worked before.

            GrapheneOS Are there plans to improve the UI for dealing with multiple SIMs? in the messaging app? I too often find myself doxing my private number to work contacts and vice versa. This also applies to calling but in a somewhat lesser extent.

              6 days later

              The latest update to the Messaging app (Friday 28 Feb 2025?) seems to have fixed the issue on my device.

                Statik Thanks for reporting back!