Pixel watch missing 2 simple but relevant features

Feature requests
1

Comparing to the native alarm, 2 important features are missing.
1- the alarm rings on the watch, not on the phone.
Being able to dismiss or snooze the alarm on the watch is great, but if it’s ringing on the phone it forces having the phone around anyway. The ring tones available on the watch are a bit different.
2- the crown button on the native alarm dismisses it.
Honestly, I think it’s a bit dangerous, but so is to snooze it while we are super sleepy and dismiss it by accident. I rather just press the crown if it snoozes. If it could be customized to be snooze or dismiss it would be perfect. But still, not using the crown is a missed opportunity.

There’s nothing much else to reach parity and these two things would be a huge quality of life improvement.

2

Hi @pplupo,
you can configure the alarm on the watch to start first, followed by the phone alarm with a delay (or silent) - Alarm settings - Sleep as Android.
Using the crown button has huge risk of accidents. If the native alarm cannot let you choose between snooze and dismiss, the 3rd party alarms app won’t probably have the tools to configure this as well.

3

Could you take a look at the crown thing?

It should, at very least, do nothing.

When we press the crown button while the alarm is ringing, the screen goes away, but the alarm keeps ringing. The solution is to open the apps list, find the alarm, click on it, so we can actually dismiss or snooze. All that while it’s ringing. If the intention was to snooze, by the time we get back to the screen we might as well just dismiss it. lol

4

" you can configure the alarm on the watch to start first, followed by the phone alarm with a delay (or silent) - Alarm settings - Sleep as Android."

I don’t see where. I can’t find this option in the app and not even in this page.

5

Hi, the link leads to this place in the documentation. What does it show to you? Is the section missing completely?

image
image958×388 23.9 KB

6

It says “vibrations” and “no sound.”

The vibrations work exactly the way I like. Slow vibrations first, watch only, then start the sound.
Unfortunately, the sound is on the phone, not on the watch. Which, again, makes us have to have the phone pretty close… :-/

7

HI, we do not use watch ringtones, the vibrations are usually enough to wake even the heavy sleepers. Does the vibration-based alarm not wake you up, even after the vibrations are continuous after a while?

8

I’ll have to test next weekend, as I don’t want to risk it during workdays. I usually leave the phone ringtone on, and that’s what wakes me up.

But please, if you can’t let us choose what to do with the crown or set it to snooze, at least make it do nothing. As it is, it’s really more like a bug: it hides the alarm, which keeps ringing in the background.

9

The crown is something like a home button on phones - it cannot be overwritten by apps to do tasks, or disable its functionality. This is not possible on Wear OS.
So pressing the crown opens the home screen and takes the app that was on the top (tracking screen or alarm screen) down and opens the main menu. There are no tools for us to change this at the moment.

10

Running the risk of sounding like a smartass (and I apologize if I do, I’m just trying to help), there’s also the possibility of just handling the fact that the app has gone to the background. If it happened while the alarm was ringing, you could snooze it:

    
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        
        ProcessLifecycleOwner.get().lifecycle.addObserver(AppLifecycleObserver())
    }
}

class AppLifecycleObserver : LifecycleObserver {
    
    @OnLifecycleEvent(Lifecycle.Event.ON_START)
    fun onAppForegrounded() {
        Log.d("AppState", "App in foreground")
        // App came to foreground
    }
    
    @OnLifecycleEvent(Lifecycle.Event.ON_STOP)
    fun onAppBackgrounded() {
        Log.d("AppState", "App in background")
        // App went to background - this includes crown button press
        handleAppGoingToBackground()
    }
    
    private fun handleAppGoingToBackground() {
        // Your logic here - save state, pause timers, etc.
        // This will be called when crown button sends app to background
    }
}```
or this if you use jetpack compose:

```@Composable
fun MyScreen() {
    val lifecycleOwner = LocalLifecycleOwner.current
    
    DisposableEffect(lifecycleOwner) {
        val observer = LifecycleEventObserver { _, event ->
            when (event) {
                Lifecycle.Event.ON_PAUSE -> {
                    // App going to background
                    handleAppPause()
                }
                Lifecycle.Event.ON_RESUME -> {
                    // App coming to foreground
                    handleAppResume()
                }
                else -> {}
            }
        }
        
        lifecycleOwner.lifecycle.addObserver(observer)
        
        onDispose {
            lifecycleOwner.lifecycle.removeObserver(observer)
        }
    }
    
    // Your UI content
}```
11

Hello, many thanks, this would not work IMHO… the problem is that the activity could go to background for various reasons… for instance display timeout… I think we do not want to snooze the alarm every time the screen times out…