i have to confess that sometimes i talked to my phone to set up a tea timer (because the UI hoops to get there is unnecessarily complicated). which is the only use case i ever had of talking to my android phone. but that's also broken now :D also quite dystopian that they're sending my pleas for a tea timer to gemini cloud. longing for a linux phone, and some simple short command CLI for common tasks. oh, now the tea timer went off. so it worked and didn't work at the same time. nice.

@mntmn diiing (says the linux phone)

actually lots of things are not there yet tho. the clock does not set up rtc wake yet so if the phone goes to sleep the timer won't ring (i'll work on that myself). and the sound volume control is not differentiated by category (media/call/notification) so if you lower the volume the alarm is super quiet too. but none of this is rocket science and we'll fix it!

@valpackett im curious about the technical details, my guess is this would use an internal RTC's alarm IRQ as wakeup source? as i'm designing my own hardware (tablet) i want to try another approach which would be relying on full suspend of the SoC, and bundle all background notification APIs, and a low speed mobile connection for something like UnifiedPush. it would then wake up the SoC on demand and offer an API to grab the latest events. what do you think? do you know of similar prior art?

@mntmn yes, you just tell the rtc (via a CLOCK_*_ALARM timerfd and linux just does it, but we'll have to make a dbus api because that's protected by linux capabilities which are a nightmare) and it pings the wake irq when it's time.

wrt mobile connection, the qcom IPA driver already sets its irq as a wake irq, so incoming data from modem should wake the system. well I haven't confirmed that it does for real but I am seeing odd wakeups with no irq reason lol. but we're missing filters support.

@mntmn i made a recent post about push, definitely will need to work on it soon. tl;dr i don't think the coalescing into a single source is a big deal, and it doesn't fit into the p2p-all-the-things vision of the future.

so yea if i confirm that ipa wakeup already works we'll be able to have a "wakeups only when push arrives because the only open connections are push ones lol" thing, until someone figures out ipa filters to make it better

@valpackett on my platform the modem is pluggable (though still qualcomm (quectel)), currently USB, which normally presents itself as a set of virtual serial ports for AT commands and a USB ethernet device. do you happen to know if packet filtering for wowwan is a thing there/supported by drivers? perhaps as WOL ont he virtual ethernet? hm.
@mntmn oh oof usb is quite a different situation, no ipa there