~stacyharper

Cyber Space, sometime in France

https://willowbarraco.fr

Willow Barraco, a french trans lesbian lover.

I write code, freelance and hireable.

If you like what I an doing, please consider supporting it

https://liberapay.com/StacyHarper https://donate.missbanal.net

Trackers

~stacyharper/fossbill

Last active 1 year, 6 months ago

~stacyharper/wee-matter

Last active 2 years ago

~stacyharper/bonsai

Last active 2 years ago

#615 Responsiveness / latency optimization of sxmo menus 5 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

Not at all. This one is only used by the retro-compatible script.

#615 Responsiveness / latency optimization of sxmo menus 5 days ago

on ~mil/sxmo-tickets

Thank you for the reply ~stacyharper. Are you referring to the SXMO variable "$SXMO_THRESHOLD" here?

#615 Responsiveness / latency optimization of sxmo menus 5 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

#TODO: button events

There is probably some overhead the multi press timeout in bonsai / sxmo_multikey.sh, how much? See also #574.

#sxmo_appmenu.sh / sxmo_hook_contextmenu.sh

On the bonsai side, there isn't much extra latency. Except for the tiny unix socket initialization on client and server sides.

But we effectively feels a lot of latency, because the tree is designed this way. To emulate the behaviors we want, we have to wait a bit of time after most of the key events. Meaning single click start a timer after which, when no new events are received, we dispatch our scripts.

We could reduce the timeout duration (that I've increased a bit at some point). That could make the feeling better, but would also increase the difficulty to trigger the two-clicks.

#614 Calls not working on Pixel 3a XL 8 days ago

on ~mil/sxmo-tickets

Do I have to unsubscribe from each ticket separately? I also don't want to receive messages about new tickets.

On 2/2/25 10:02, ~stacyharper wrote:

ah, nvm. This is a todo :D Similarly, you can unsubscribe if you are not authenticated with:

Similarly, sending an email to ~username/tracker-name/ticket-id/subscribe@todo.sr.ht or ~username/tracker-name/ticket-id/unsubscribe@todo.sr.ht will (un)subscribe the sender to the ticket.

#614 Calls not working on Pixel 3a XL 8 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

To respond to the OP:

The audio mode mode is based on a pulseaudio/pipewire profile, on the input device. You should be able to check those profiles with pavucontrol, or other gui/tui based programs.

The program that does this is callaudiod. On your device probably this one:

https://gitlab.com/mobian1/callaudiod

You should be able to debug this futher by inspecting the script sxmo_modemaudio.sh.

sxmo_modemaudio.sh setup_audio
sxmo_modemaudio.sh reset_audio

Too much things can go wrong. If you manage to debug, and fix the issue, please send a patch.

#614 Calls not working on Pixel 3a XL 8 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

ah, nvm. This is a todo :D Similarly, you can unsubscribe if you are not authenticated with:

Similarly, sending an email to ~username/tracker-name/ticket-id/subscribe@todo.sr.ht or ~username/tracker-name/ticket-id/unsubscribe@todo.sr.ht will (un)subscribe the sender to the ticket.

#614 Calls not working on Pixel 3a XL 8 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

On Sun Feb 2, 2025 at 8:49 AM CET, ~Elias Ståhlberg wrote:

Sorry for the offtopic, but how can I unsubscribe from this mailing list and leave the list? There are no instructions on the website.

No problem, you can unsubscribe using either the web-ui, if you are authenticated. Or you can mail a dedicated adress:

https://man.sr.ht/lists.sr.ht/#email-controls

#613 sxmo_bg on x11 running in a loop burning cpu 11 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

There is default values that are safe to use imho

#613 sxmo_bg on x11 running in a loop burning cpu 11 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

#613 sxmo_bg on x11 running in a loop burning cpu 11 days ago

Comment by ~stacyharper on ~mil/sxmo-tickets

After some tries, it seems superd already handle StartLimitBurst and StartLimitIntervalSec correctly. With, or without success exit code. So the missing SXMO_WM should not result with a burnt CPU from superd (before the patch).

Then, Restart=on-failure on Type=simple should do what we expect. If the script exits correctly, superd will not restart it.