Just a +1 for this feature request, it would make it a lot easier to keep threads together.

For what it's worth, I have a Oneplus 6 now and don't have this issue; data works fine for me.

"~proycon" outgoing@sr.ht wrote:

On Mon Jul 3, 2023 at 3:41 PM CEST, ~magdesign wrote:

we could add a variable in deviceprofile, telling how many characters are hidden by the notch. e.g. NOTCH="9" would add 9 characters between battery and wifi symbol like this: sxmobar -a notch 35 ooooooooo

That sounds like the easiest solution to me too. I do worry if sufficient space remains for all our icons then.

I'm pretty much sure we can configure a blank space in Sway. This avoid the problem, without being satisfying. Only the composer could handle this.

On Mon Jul 3, 2023 at 3:41 PM CEST, ~magdesign wrote:

we could add a variable in deviceprofile, telling how many characters are hidden by the notch. e.g. NOTCH="9" would add 9 characters between battery and wifi symbol like this: sxmobar -a notch 35 ooooooooo

That sounds like the easiest solution to me too. I do worry if sufficient space remains for all our icons then.

Perhaps we should ask Miles to alter the description of the old sxmo-svkbd repo indicating it's long obsolete?

On 23-01-19 01:50, ~phartman wrote:

btw can you add my luc.edu e-mail address to sxmo-devel so I can flag things as closed/etc. via e-mail. I think I'm entered with my gmail.com account. Catch me on #sxmo for details.

I think we need Miles (~mla) to do that. Poking him on IRC may be quickest?

This is high on my wishlist as well, the issue back on github was https://github.com/eXeC64/imv/issues/38, in which the main developer already expressed some ideas on implementing this. Would love to hear if anyone is working on it (otherwise I might have a try myself).

I opened an issue for this at Alpine Linux to discuss how we can best resolve this permission conflict between feedbackd and sxmo-utils: https://gitlab.alpinelinux.org/alpine/aports/-/issues/14466

December 15, 2022 5:55 AM, "~proycon" outgoing@sr.ht wrote:

On the Pinephone A64, megapixels 1.6.0 pulls in feedbackd as a dependency. With feedbackd installed there are continuous messages in tinydm.log about permission denied:

/usr/bin/sxmo_led.sh: line 69: can't create /sys/class/leds/red:indicator/brightness: Permission

Ah, good catch! This is new. Sxmo sets up udev rules to set the proper permissions for these. The key is that the user should be in the 'video' group. But it seems feedbackd changes the group of these leds to 'feedbackd'. So we have a conflict here we should settle.

(Adding your user manually to the feedbackd group should bypass the issue).

I confirm that adding the user to the feedbackd group does fix the led issue.

Thanks proycon.

Mark

On the Pinephone A64, megapixels 1.6.0 pulls in feedbackd as a dependency. With feedbackd installed there are continuous messages in tinydm.log about permission denied:

/usr/bin/sxmo_led.sh: line 69: can't create /sys/class/leds/red:indicator/brightness: Permission

Ah, good catch! This is new. Sxmo sets up udev rules to set the proper permissions for these. The key is that the user should be in the 'video' group. But it seems feedbackd changes the group of these leds to 'feedbackd'. So we have a conflict here we should settle.

(Adding your user manually to the feedbackd group should bypass the issue).