I hope this will work: https://lists.sr.ht/~mil/sxmo-devel/patches/25546
Yeah, because for some reason the full stop at the end of sentence, became the part of the url. Please copy/paste the url and remove the dot at the end. I have no idea how to amend a comment, so cannot fix that. Sorry.
I've reworked my original idea and submitted a patch https://lists.sr.ht/~mil/sxmo-devel/patches/25546. In there I extracted the LED usage from scripts (sxmo_screenlock.sh, sxmo_rtcwake.sh, sxmo_postwake.sh and sxmo_notificationmonitor.sh) into one script (sxmo_leds.sh) and introduced a config file to control them. It is a very basic solution. In the config file that was included in the patch, I added the original LED settings. On my device, I have tested both the original and my custom settings and both worked well. What do you think?
I was trying to set up wvkbd to use only the "full" and "specific" layers, but somehow managed to break the system. Tinydm stopped and couldn't be started again. I needed to restore a backup to the phone but I only had a backup of sxmo rather than wxmo. So, I'll play with this keyboard setup later, because first trying to work on what I mentioned in #375. :)
I think the key point here is the ability to configure according to our needs. If I could configure the LED as I needed, I wouldn't want to start this topic. As currently the LED usage is encapsulated in a few scripts, I think, it would be a good start to separate them into one script. which then could be driven by a config file. Then, a maintenance option (if needed) could be developed to manipulate that config file. On my device, I'll try to do this.
Thanks for explaining a little bit about the keyboard. Now, I understand the purpose of Cmp key and in this case, I definitely don't want to lose it. :) You said fairly easy to make my own layout. Just like with the LED setting, I think this is the best option for me. Especially that I don't use the majority of the current layouts. (e.g. I don't need the emoji, Cyrillic and all the rest "keyboard screens" except the first two.) Could you please suggest a good site where that layout creation is described? Or I should do my own research? :) The svkbd screens were a better fit for my usage. The other thing I spotted is how the 'Sym' key is functioning. It takes me to the "second keyboard screen" where if I press the 'Abc' key I expected to get back to the "first keyboard screen" (similarly to svkbd) but instead, it takes me to the "emoji keyboard screen". (I call them "keyboard screens" because I don't know the proper term. :))
Is there a reason why the keyboard layouts are different on sxmo and swmo?
It would be nice if that Alternate Greater (shown as AGr) key is displayed on the first keyboard screen. In place of the Cmp key. (I am not sure what is that for.) This way the AGr would be visible immediately on the screen where the letters and numbers are both there. (It would be useful for using Midnight Commander (mc)).
I agree with @stacyharper.
Yeah, I see your points/reasons. As a developer, I absolutely agree: I would like to know whether the device is on and in crust or just screen off. As a user, I don't care. When the screen is off (even in crust) I expect all the basic functions (receiving SMS/calls) do work and the device won't switch off silently. :) I've found keeping the LED on especially during the night is disturbing. However, I agree that this is down to each individuals' taste. :)