SMS notifications in Secondary Users show at top of screen, and phone vibrates, but phone will not make a notification sound.

[jay46jay]

I use a secondary user as my daily phone user and while SMS message notifications come in visually at top of the screen and vibrate, there is no new message notification sound.

While in the main admin user there is a notification sound for new SMS messages.

I did a factory reset, and setup a new user, and still same issue without having done any phone or app setups yet. There is no setting turned off that varies from admin user and no setting when changed or flipped off and back on could get the SMS new message notification sound to work.

I also went on grapheneos webchat and found others with same exact issue.

I am using a carrier unlocked Pixel 5.

[tsaoi]

Similar issue here on carrier unlocked Pixel 4a (not 5G). Factory reset last night, reinstalled latest RQ2A.210305.006.2021.06.06.00 on 4a and did nothing else. Initially struggled to get any notifications on Admin (yes all notifications volume turned up, yes messaging app was opened to initialize etc), but then suddenly it started alerting after testing sending/receiving some text messages leaving the Messaging App open and now it seems to work even on lock screen from sleep. Will continue to monitor.

Second User on the other hand is still silent, even after replicating the same steps as Admin user from fresh install.
On previous build, I could at least get Notification Screen and Vibrate on Second User, now nothing at all.

Awesome OS and looking forward to this fix! Keep up the great work @thestinger !

[tsaoi]

Ok, so it's now vibrating & alerting on sleeping screen as second User, aligned with @jay46jay issue.
All I did was access the App info under Settings, modified Messaging App and checked: Allow interruptions and Override Do Not Disturb. Will watch this for further updates thanks.

[thestinger]

It sounds like you have Do Not DIsturb enabled which would explain why you weren't getting the notifications with vibrations.

[thestinger]

The original issue appears to be that the Messaging app doesn't have working sound in secondary users. I don't think you've identified any additional problem but rather you must have Do Not Disturb enabled. If you don't want that enabled, you should really disable it rather than working around it case-by-case.

[tsaoi]

but rather you must have Do Not Disturb enabled

Thanks for your response however DND was definitely not enabled on either profile (never touched the setting from fresh install), neither was any Battery Saver as I have seen can cause issues on this forum previously with notifications.

Yes, let's leave the original issue as it stands - and I can confirm no working sound in secondary users. Thank you.

[dr-frasier-crane]

I have the same issue. My initial install of GrapheneOS was this week with the most recent image on the Pixel 4a (non-5G). I use a secondary profile for daily use. Do Not Disturb is not enabled. Incoming SMS create a banner and then a notification icon at the top as well as vibrating, but it does not play a notification sound. I tried both using Messaging's option to use the default notification sound as well as manually setting it and neither triggered a sound from an incoming SMS.

[zvl12]

if anyone find a way to have the sms sound in secondary profile, please post !
vibrate works, sound not

[tsaoi]

if anyone find a way to have the sms sound in secondary profile, please post !
vibrate works, sound not

#459
Thanks @zvl12 for raising this back in February - shouldn't have been closed but is open here now with more detail for attention.

[dr-frasier-crane]

I'm bumping this as the last comment was over 2 months ago. Has anyone found a fix for this? It would greatly improve my QOL to hear incoming SMS message notifications.

[thestinger]

Please test on the latest June release.

[dr-frasier-crane]

@thestinger I have the June update, rebooted, entered the secondary profile, made sure sound was on and turned up, and received an SMS message. The device vibrated but did not make a notification sound. The issue was not fixed on my device (Pixel 4a 4G-version)

[zvl12]

same here problem still exists here as well 4a 5g ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

…

On Sunday, June 13th, 2021 at 19:58, Dr. Frasier Crane ***@***.***> wrote: ***@***.***(https://github.com/thestinger) I made have the June update, rebooted, entered the secondary profile, made sure sound was on and turned up, and received an SMS message. The device vibrated but did not make a notification sound. The issue was not fixed on my device (Pixel 4a 4G-version) — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#483 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AS3SNJRGEJUEQTO4ZCKF73LTSVH25ANCNFSM4Y47QCYA).

[tsaoi]

Messages through native App are vibrating but still do not sound alerts on new June release.

[dr-frasier-crane]

Here's some supplemental information in case it helps with diagnosing/fixing the issue:

If a conversation in the SMS app is open and that contact sends a message, the notification bar at the top appears, the phone vibrates, and the message still appears unread when you back out into the list of conversations. Reopening the conversation will remove the notification from the top and mark it as read (un-bolded) in the conversation list.

This behavior is different from the main profile. A new message from a contact in which the conversation is already open in the SMS app does not create a notification at the top, does not vibrate or play the notification tone, and is automatically marked as read.

[dr-frasier-crane]

Does this issue affect everyone or just a few people?

[zvl12]

Does affect ALL phones i ever had with graphene (in secondary profile only)

…

-------- Original Message --------

On Jul 10, 2021, 19:52, Dr. Frasier Crane wrote: Does this issue affect everyone or just a few people? — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#483 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AS3SNJT6VUO6AET5AIWA5I3TXDTLVANCNFSM4Y47QCYA).

[damienrg]

The issue appears to be in the AOSP Messaging App. If this is the case it will never work in GrapheneOS unless someone fixes it upstream.