#How to completely disable background services

1 messages · Page 1 of 1 (latest)

void walrus
#

According to this announcement: https://wooting.io/post/wootility-update-introducing-the-background-service -we should be able to completely disable the background services on the keyboard. Please advice how to disable service, without having to download and install irrevelant client software and relinquishunrelated control on my desktop.

brave tendon
#

you dont install the background service to begin with and thats it

#

its an optional separate software so wootility doesnt need to be installed but can keep being used as web as well

slow matrix
#

What Liq is asking I think is if it's possible to block any communication that doesn't specifically come from Wootility. Through any SDK or otherwise?

void walrus
#

The idea of my keyboard just eagerly awaiting some software to connect to it makes me sad

brave tendon
#

it doesnt

#

and we have no option to disable SDK communications. would probbaly break some of wootility as well as it also uses parts of the SDK

void walrus
# brave tendon it doesnt

hm, maybe the solution could be documented better or it could just be a question about UX. Cause this makes me think otherwise:
(cant post pic, hit by slowmode)

brave tendon
#

should only be 5seconds

void walrus
brave tendon
#

im a bit confused how it can be more clear its not even installed beyond this

void walrus
#

but honestly its mostly boils down to me being confused about the perspective of the service. I saw it as a new thing running on the keyboard -and not being aware of wooting keyboards already having some form of api endpoint active already

brave tendon
#

not an api endpoint

#

but USB commands

#

if these didnt exist you wouldnt be able to configure the device

void walrus
#

Im aware you need to send some form of command to flip devices into dfu mode etc. if wooting does something similiar

#

so you're saying that the Background Service, if installed, would be communicating with the keyboard via regular usb commands as well?

brave tendon
#

yes

#

as we dont have custom drivers it has to be usb commands

void walrus
#

interesting and informative, thank you

#

there's no blog post or any technical paper describing this in anyway? just to please my curoisity

brave tendon
#

our SDKs are opensource

#

you can take a look at how it works

#
GitHub

Native support for Analog Keyboards #WootDev. Contribute to WootingKb/wooting-analog-sdk development by creating an account on GitHub.

GitHub

Customize colors on Wooting Keyboard #WootDev. Contribute to WootingKb/wooting-rgb-sdk development by creating an account on GitHub.