[Wear OS Software and Hacking General] Tech Critic:
cyrilp is the developer ;) He's trying to identify the source of the bug so he can fix it for us.

You never mentioned the phone you are using with your Huawei watch and which version of Android it is running.

I'm also using a Huawei watch with SWN, and my phone is a Nexus 6P. I can tell you from a good amount of trial error that most issues stem from the phone and not the watch, so factory resetting the watch when you run into issues is probably a waste of time and effort. I think these issues are the result of the phone app failing to notice new notifications and play the corresponding sound.

I never got confirmation from cyrilp on this, but I'm pretty sure each sound is initiated when the SWN phone app notices a new notification. The actual notifications on the watch and their corresponding sounds are not linked at all on the watch itself. For each notification there are two things going on:

1. Android Wear Service on phone sends notification to watch.

Your phone (the Android system) receives a notification from an app, and the Android Wear app, which has been granted notification access, notices and pushes that notification over to the watch.

2. SWN service *on phone* tells the watch to make a sound.

SWN also requires that you grant it notification access to function. I am pretty sure that without root, an Android wear companion app installed on the watch itself cannot access notifications for other apps on the watch itself. I don't think the permission exists for the developer to use. So, instead, like the Android Wear phone app, SWN monitors notifications on the phone, and when a notification comes in, it tells the SWN companion app installed on the watch to make the designated noise.

The two commands being sent to the watch are completely separate, so the fact that notifications are showing up on the watch does not necessarily mean that the watch is also receiving a command from SWN to make a sound. The companion app on the watch can be working perfectly, but if it didn't receive a command from SWN on the phone, it has no idea that there's a new notification and it doesn't make a sound. The sound files themselves might also be stored on the phone and sent over for each sound, that's largely irrelevant here, but I'd be interested to know.

The app has an option in settings called "reset notification access" which takes you to the page with the toggles and instructs you to flip it on and off to reset.

I have had success with the following procedure, although I suspect one of the two setting toggles is unnecessary and I just haven't narrowed it down.

1. Reset notification access

2. Go to settings cog in top right of SWN home page and toggle "sound" on and off.

3. Reboot phone and watch

This generally seems to work, although it doesn't always take effect instantly upon reboot. I'll have to pay closer attention next time, but it's usually not an immediate aha thing where it starts working. It might just be that the phone and watch app take a little while to make contact on the background.

I think it's a possibility that doze is creating problems. Android wear asks you to disable battery optimization while SWN does not. However, if doze were at fault, I would think opening the SWN app in the foreground would fix the issue? Perhaps doze kicking in changes something that can only be reversed with the settings toggles and reboot?

I haven't yet tried shutting off battery optimization for SWN, but having just thought of the above maybe I'll give it a try.

The app used to have a notification logging feature on the side menu settings page which allowed you to confirm that notifications are working. I don't know why cyrilp for rid of it. I think simply logging the only most recent notification might be a good way to go. That way people don't have to turn it on and off or clear the list, but they can verify SWN sees the notifications.