authenticator-rs VS waked

In a similar position as OP and recognize most of what they're saying.

> Modem: Frequent disconnects, not receiving calls

Something I believe to be observing is that the phone can stay consistently connected for days if stationary but as soon as I take it out for a drive or longer walk I immediately start getting the disconnects, which I so far have only been able to resolve by a full reboot (there are some pointers that I was not aware of tho, especially the state of baseband firmware; thanks!

> Bluetooth Audio

At this point I'm realizing OP may have a masochistic leaning. But props for pushing :)

Regarding TOTP apps: https://github.com/grumlimited/authenticator-rs is very close to being a nice experience. It mostly needs what seems to be a couple of simple UI tweaks.

That's an "interesting" solution, since exactly what waked does is already done by kernel internally if you use timerfd, without the need for any special daemon. Any app that wants to be woken up at certain time can just register a timer for that time with the kernel.

I wonder if waked writing directly to RTC doesn't break the kernel alarm functionality used by timerfd, but hopefully not https://gitlab.com/seath1/waked/-/blob/master/src/main.cpp#L...

But why not, it's FOSS. :)