Doing "systemctl stop bluetooth.service" and after that "systemctl disable bluetooth.service"
gives the following output:
sudo systemctl disable bluetooth.service Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install disable bluetooth insserv: warning: current start runlevel(s) (empty) of scriptbluetooth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script bluetooth' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of scriptbluetooth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script bluetooth' overrides LSB defaults (0 1 6). ~ ❯❯❯
UPDATE
Starting and stopping udevd with:
sudo systemctl start systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket
Seems to solve this CPU hogging but I don't know what's causing it ...... I suspect waking up from suspend scripts.
Update the update
Connecting the charger is what causes this.
Unplugging makes all activity go away including the bluetooth activation.
This looks like a wrong setting in cpu-freq (it also resembles a bug I encountered in kernel 4.0.19-05) ... it could be because I used E2x to manipulate power-settings can anybody see if they have the same issues?
