Sadly, seems like it made no difference. Here’s the output from last night, using the OnePlus Watch 2 and Sleep as Android:
So, I decided to have a look at both the stock OnePlus Clock app, the 3rd party one, that @bmoyles mentioned, and the Google Clock one and they all worked, with one common feature: they all displayed their screen by default!
For as long as I remember, the SaA app has not displayed the screen on WearOS (I always have to tap the Clock icon at the bottom of the watch for it to open), but if it did, it would solve the issue for this watch.
And seeing as this is the behavior of at least 3 different other apps, I wonder if this shouldn’t be the case (at least optionally) for SaA? It could break expectations of former users, potentially flashing them in the middle of the night, but if there were an opt-out option, maybe it could be ok? On the other hand, it is the default for several other Wear OS alarm apps, so maybe this is a convention?
@petr-urbandroid : could we persuade you to implement a screen on option (or default behavior) for Wear OS? I tried making the case that this is not just a workaround for one specific watch, but instead something several other apps follow, and as such could be desirable for users.
Hello @ravemir … I have prepared a blind workaround… for this… in addition to the CPU lock we are also taking a screenlock… would you be willing to give it try and sideload the APK:
https://sleep.urbandroid.org/wp-content/uploads/release/SleepWear-5.24.apk
It worked: the screen kept on, and so the alarm kept vibrating! There’s a chance that if I put my hand on the watch I end up muting them again, but at least it will start vibrating by default.
Thank you for the willingness to try it out! Is this something you will consider adding in a future stable, or would you like to investigate further?
Ok, after having a missed alarm the very next day, I decided to test an hypothesis and it checked out: tilting the watch during the alarm shuts the screen off.
At the time of the first missed alarm, I had that setting on, but have since tested with it off and flicking the wrist made the screen turn off still.
The third party app manages to work even then. The only visible change is that it displays the snooze+dismiss screen during the alarm.
@ravemir here is a another APK 5.25 https://sleep.urbandroid.org/wp-content/uploads/release/SleepWear-5.25.apk
Would you be willing to give it a try?
I cannot properly test this on my TWP5 as 1) it is Wear OS 4 (Android 10) and there are more and more restrictions to start screens from background in every new version of Android - in fact I did not expect I would be even able to start the screen if you look at Restrictions on starting activities from the background | Android Developers … 2) TWP5 has a LCD display layer so even when a screen is started it is not visible until the screen is pressed…
Please let me know…
Tested it out, and the screen does pop-up successfully (at least when out of DnD, or this watch’s Sleep Mode). Tilting the watch back still causes it to be dismissed, sadly 
Even the 3rd and 1st party apps do this!
Can this be a watch bug, when even the 1st party app is misbehaving? If it isn’t, not sure how Wear OS got to this point: triggering an alarm app causes it to be so easily dismissed to the point you can’t trust it.
EDIT: Was on my way to post on their forums, when I realized that I had actually tested on the Google Clock app. The actual stock app behaves exactly as expected! (how convenient!). Will still reach out to them.
EDIT 2: @petr-urbandroid my my OnePlus is also running WearOS 4, but it shows Android 13 as its version (you can check the screenshots below).
@ravemir many thanks for further tests…
What I’m doing in the latest version is: getWindow().addFlags(WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON);
This should at least on phone keep the screen on when the app is in foreground… but it may be ignored on Wear OS…
Also I’m taking a screen bright wake lock, but this is documented to get released when screen is turned off…
I guess I;m doing maximum I can on my end :(… I do not have more ideas…
You are right Wear OS 4 is Android 13 and Wear OS 5 is Android 14, my bad…
I think this isn’t a Wear OS problem as other devices will keep vibrating even with screen off…
Thanks for all the effort. I will reach out to OnePlus through their support channels to get some sort of confirmation on whether this is intended behavior or a bug, and will let you know if they do reply.
I would not rule out the former, seeing as they have really good battery numbers, which might be supported by this type of behavior.
I’m still providing details to the OnePlus support team (it may take a while, as they might want me to factory reset the watch, of all things…) but I have a new development that could be relevant: I was able to get Google’s Clock app to keep vibrating with the screen off by changing the “Alarm volume” Setting to be non-zero.
This might still mean there’s a bug at play on the 1+ Watch 2, since I doubt it was their intention to also silence alarm “vibrations” when setting watch volume. Is this the current behavior on the TWP5 watch as well? (I’ll be somewhat embarrassed if I missed this)