Galaxy watch 3: Unable to reply to notifications (whatsapp, messenger, ...) + no Messages app

[Beckero]

Hi,

I am having troubles responding to notifications on my new Galaxy watch 3. (Connected with Bluetooth)

I am using a Nokia 9 Android phone. As far as I know notifications/responses/messages should work with this?

First; there is no 'Messages' app on my watch. Which I thought it should be there. But, when I go to contacts, select a contact, I have the option to send a message. There everything works; I can type, say something, use an emoji, .... When I click send, the message is being send and delivered. So far so good (except I don't understand why I don't have a Messages app, and also can't find the Samsung messages app in the store when I search with my phone).

Notifications from WhatsApp and Messenger are also coming through (so I think everything about notifications is set correctly in the Gear app), but I can't reply. In attached screenshots you can see that I am able to select something (for example the 'What?', but when I click that 'send' button, nothing happens.

Also,  when clicking on the 'microphone, 'emoji' or 'type text' buttons (see other screenshot) nothing happens. It doesn't

go to the next screen. I have no idea what could be the issue here.

I have found some posts with (possibly) similar issues but haven't found a real solution or a clear explanation on how/why it does not work and if it should work (and how )

Thanks!

Joeri

[PYPPO]

Tôi cũng gặp vấn đề tương tự với ss sw act2 và nokia 8.1. Trung tâm SS bảo tôi mang đến TTBH nhưng chắc khỏi cần vì có vẻ như đây là vấn đề chung 😞 bùn

[yozzerhughes]

I am having the same issue on a Nokia 8.3. I contacted Samsung before I bough the watch and the Nokia and they assured me this would work. I used the reply function a lot and then it stopped working. Like most things Samsung, unless you buy the latest or the own a complete Samsung device they don't want to know. I will, most likely in vain and at wasting my own time, log a support call to see if we can get this in their radar.... It's just one of the reasons I moved away from Samsung and I was a loyal buyer since the galaxy 1.... 

[Paul Freund]

I have the same Problem with a Nokia 9 PureView. I checked the system logs and found at least one error that might be related:

07-07 10:01:39.956  9004 17937 I GM/SapServiceManager: Gear Request - Notification clear request received
07-07 10:01:39.956  9004 17937 W System.err: android.content.pm.PackageManager$NameNotFoundException: com.samsung.accessory.permission.TRANSPORTING_NOTIFICATION_ITEM
07-07 10:01:39.956  9004 17937 W System.err:    at android.app.ApplicationPackageManager.getPermissionInfo(ApplicationPackageManager.java:327)
07-07 10:01:39.956  9004 17937 W System.err:    at com.samsung.android.hostmanager.broadcast.BroadcastHelper.sendBroadcast(BroadcastHelper.java:41)
07-07 10:01:39.956  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.utils.SAMiniMsgUtils.cancelNotification(SAMiniMsgUtils.java:683)
07-07 10:01:39.956  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.sync.SASapServiceManager.notificationClearRequest(SASapServiceManager.java:1107)
07-07 10:01:39.956  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.sync.SASapServiceManager.processsingIncommingWork(SASapServiceManager.java:1037)
07-07 10:01:39.956  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.sync.SASapServiceManager.doProcessingIncomingwork(SASapServiceManager.java:906)
07-07 10:01:39.957  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.sync.SASapServiceManager.doProcessPendingWork(SASapServiceManager.java:648)
07-07 10:01:39.957  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.sync.SASapServiceManager.onDataAvailableonChannel(SASapServiceManager.java:1503)
07-07 10:01:39.957  9004 17937 W System.err:    at com.samsung.accessory.saproviders.samessage.sync.SAMessageProviderImpl.onDataAvailableonChannel(SAMessageProviderImpl.java:369)
07-07 10:01:39.957  9004 17937 W System.err:    at android.os.Handler.dispatchMessage(Handler.java:107)
07-07 10:01:39.957  9004 17937 W System.err:    at android.os.Looper.loop(Looper.java:214)
07-07 10:01:39.957  9004 17937 W System.err:    at android.os.HandlerThread.run(HandlerThread.java:67)
07-07 10:01:39.957  9004 17937 I GM/SapServiceManager: notificationClearRequest, notificationId = 888
07-07 10:01:39.957  9004 17937 I GM/SapServiceManager: finish pending work call stop service

07-07 10:01:39.957  1523  1591 W BroadcastQueue: Permission Denial: broadcasting Intent { act=com.samsung.accessory.goproviders.sanotificationservice.ACTION_CLEAR_NOTIFICATION_FROM_GEAR flg=0x10 (has extras) } from com.samsung.android.gearrplugin (pid=9004, uid=10385) requires com.samsung.accessory.permission.TRANSPORTING_NOTIFICATION_ITEM due to registered receiver BroadcastFilter{c32017f 10385/u0 ReceiverList{a58d29e 9004 com.samsung.android.gearrplugin/10385/u0 remote:307c8d9}}

So for me this looks like a bug Samsung can fix.

[Ruxflux]

Hey folks,

are there any updates on this? Even after the last watch update I still have this issue (Nokia 6, Android 10).

[yozzerhughes]

I think we have had several updates and this is not fixed. This sounds like a permissions thing which would be fixable but I suspect that Samsumg (as always in my opinion with so many other products that Ive purchased over the years) will leave this now and focus on their 'new' watch range...

They have moved from Tizen as an OS now with the new range, but you can expect more issues with that an operability with non-Samsung devices.

If the pixel watch had a bezek I would be straight in there... 

Very dissappointed with Smasung as a company in their watch department....