I'm starting empwake with Bitt's preinit.d and it seems to be starting fine.

First (only) bug (or "feature" that causes hang ) Pressing a button to bring up Hijack's "Clock" causes a hang if your interface is active.

I still have to see if this next one is something I've missed...

It doesn't seem to read from the config settings for me right now. So the active state isn't set and neither is the time (reads all 0's). If I manually set the alarm it will go off (a few seconds late) but will jump to some random tune while also choosing to play the entire player (tested by presetting to a single song or a small list before the alarm goes off and leave it in pause)

Also, the time displayed is always "Timezone-offset" hours from actual time. I'm using the Hijack time offset adjustment in the config to get Hijack to show the correct time. I guess you'll need such an offset option if you're not going to use Hijack's.

For now I've removed Hijack's time offset and have changed over to using GMT with the player. So my player clock always matches up with the time the kernel gets. It would be nice if you could read the current time details from wherever the player stores its settings, each time your menu pops up.

One suggestion... In your time setting, would you make it so that it wraps around the time? So going backwards from 00 will get me to 59. That'll make setting a lot faster.

[edit] Some other weirdness... On first entering your menu, it will sometimes skip over the "Time" item when I rotate the knob (and I'm rotating it very carefully by a single click). This instance it also took a long time for your interface to pop up. The screen stayed blank for some 2 seconds after clicking empwake in Hijack's menu.

Bruno