Hacker News Reader

Comment by ryukafalz | Hacker News Reader

> Gomuks: Ever wanted to get Matrix protocol notifications on your Pinephone, without the sluggishness of an Electron UI? Now you can!

AFAIK: not without draining the battery you can't. You have to either disable the deep sleep mode ("CRUST") while the screen is blanked or leave the screen on, otherwise any Matrix client including gomuks won't run at all once you turn the screen off. (So no notifications for incoming messages.)

Maybe this isn't a problem if you're a very occasional Matrix user, and the battery drain even with everything running isn't too bad, but if you've been using it as long as I have and are in a lot of active rooms it's just not workable.

View on HN

There‘s a script for waking the PinePhone up regularly to mitigate this: https://codeberg.org/Silmathoron/pinephone-autowake

How can one make the PinePhone detect incoming calls on a regular basis using this method? It looks like the code sleeps for minutes at a time, which is ideal for fetching notifications for IM apps etc. but not for detecting incoming calls (which usually last about 30 seconds iirc before timing out/going to voicemail).

I would assume that suspending and waking, say, every 10 seconds could allow for detecting incoming calls but not be as energy efficient (or in the worst case, more detrimental than just keeping the phone on)?

imo I'd implement this by not suspending (except for some kind of 'battery saver' mode) and just keeping the screen at 0% brightness (which I assume is one of the primary consumers of energy from the battery cell)...

The modem is a wakeup device. IIRC there's a separate GPIO line with interrupts specifically for this.

That's handy, thanks for letting me know! I assume that applications that are resumed from suspension can then continue checking for incoming phone calls and alert the user when necessary, much like how (from my 'experiments' with the PinePhone) pressing the power button to wake the phone will still allow applications to capture the keypress event.

That's not necessarily true. Instead of just suspending you can make "suspend" a runlevel which includes a service that periodically wakes the phone up so apps can manage connections to servers that might push data to them. I wrote my own stuff that does that and I think many distros include something similar now.

Reply on news.ycombinator.com