I suppose i can’t claim true 100% hardware support without having it work and it doesn’t seem much trouble so i think i’ll add it as an edev and the user can decide what to do with it.
This might be silly to ask, but could it be piped into a script for alternate functionality? For example, in e/OS, the default setting is to disable access to Microphone and Camera… I am aware there’s not hardware switch for them, but if a there’s a script later down the line to facilitate that, it’d be neat to run it with said switch too.
I suppose i can’t claim true 100% hardware support without having it work and it doesn’t seem much trouble so i think i’ll add it as an edev and the user can decide what to do with it.
Nice! It might be a good idea to set it by default to turn on Do Not Disturb mode, to keep the functionality similar to the original OS.
I looked into this and it’s already in, its in /dev/input/event2 emitting
SW_MUTE_DEVICEevents.This might be silly to ask, but could it be piped into a script for alternate functionality? For example, in e/OS, the default setting is to disable access to Microphone and Camera… I am aware there’s not hardware switch for them, but if a there’s a script later down the line to facilitate that, it’d be neat to run it with said switch too.
Yes, since its just a reguler edev you can do trigger any script you want with it.