Hey guys,
before you rip your phones apart to cut some wires...
What do you think about "cutting wires" in software?
Have a look here:
https://gitlab.com/mobian1/devices/sunxi...phone.dtsi
Especially this entry gives the needed information:
So if you are familiar with kernel compilation you could disable this entry by comment out the vibrator part in the DTS and generate a new dtb file.
There should also be some system service handling this, but i'm still searching...
EDIT:
O.k. dbus.service is starting /usr/libexec/feedbackd which handles the vibrator afterwards.
So you could start tweaking the theme for pinephone at: /usr/share/feedbackd/themes.
But maybe this isn't nasty enough
The daemon feedbackd has a rules definition in /lib/udev/rules.d/90-feedbackd.rules
In this file there's a definition for the vibrator:
Maybe it's enough to uncomment this line with "#".
Just a thought... i did not try that.
AFAIK this stuff is all handled by the kernel event system, look here as a reference (pinephone console output, the last entry):
Maybe this helps in any way.
Cheers,
scholbert
before you rip your phones apart to cut some wires...
What do you think about "cutting wires" in software?
Have a look here:
https://gitlab.com/mobian1/devices/sunxi...phone.dtsi
Especially this entry gives the needed information:
Code:
vibrator {
compatible = "gpio-vibrator";
enable-gpios = <&pio 3 2 GPIO_ACTIVE_HIGH>; /* PD2 */
vcc-supply = <®_dcdc1>;
};
So if you are familiar with kernel compilation you could disable this entry by comment out the vibrator part in the DTS and generate a new dtb file.
There should also be some system service handling this, but i'm still searching...

EDIT:
O.k. dbus.service is starting /usr/libexec/feedbackd which handles the vibrator afterwards.
So you could start tweaking the theme for pinephone at: /usr/share/feedbackd/themes.
But maybe this isn't nasty enough

The daemon feedbackd has a rules definition in /lib/udev/rules.d/90-feedbackd.rules
In this file there's a definition for the vibrator:
Code:
SUBSYSTEM=="input", KERNEL=="event*", ENV{ID_INPUT}=="1", ENV{ID_PATH}=="platform-vibrator", TAG+="uaccess", ENV{FEEDBACKD_TYPE}="vibra"
Maybe it's enough to uncomment this line with "#".
Just a thought... i did not try that.
AFAIK this stuff is all handled by the kernel event system, look here as a reference (pinephone console output, the last entry):
Code:
mobian@mobian:/dev/input/by-path$ ls -l
total 0
lrwxrwxrwx 1 root root 9 16. Mär 11:31 platform-1c21800.lradc-event -> ../event1
lrwxrwxrwx 1 root root 9 16. Mär 11:31 platform-1c2ac00.i2c-event -> ../event2
lrwxrwxrwx 1 root root 9 16. Mär 11:31 platform-1f03400.rsb-platform-axp221-pek-event -> ../event4
lrwxrwxrwx 1 root root 9 16. Mär 11:31 platform-gpio-keys-event -> ../event0
lrwxrwxrwx 1 root root 9 16. Mär 11:31 platform-sound-event -> ../event3
lrwxrwxrwx 1 root root 9 16. Mär 11:31 platform-vibrator-event -> ../event5
Maybe this helps in any way.
Cheers,
scholbert