Accelerometer sensor not detected  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
appas
Posts: 36
Joined: Mon Oct 09, 2023 4:40 pm

Accelerometer sensor not detected

#1 Post by appas »

I would not say that "move to Ubuntu/Mint" is a "solution". If it works in different distros, how can we make it work in MX?

As you might've guessed, I am also having a problem with these features. I installed the iio-sensor-proxy package, but

Code: Select all

sudo iio-sensor-proxy --no-udev
gives no output, which supposedly means no sensors were detected.

How do I get the accelerometer sensor detected? And how do I go from there to auto-rotate on MX?

User avatar
Eadwine Rose
Administrator
Posts: 14476
Joined: Wed Jul 12, 2006 2:10 am

Re: Touchscreen function is not working when screen is inverted in convertible mode.

#2 Post by Eadwine Rose »

@appas Please start a new topic next time, do not tack on to old posts, thanks.

Also, with all help requests, please share your full Quick System Info, found in the menu under Favorites. Press the Copy for forum button, then click paste in a reply. If need be, you can do this with the LiveUSB, thanks.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
appas
Posts: 36
Joined: Mon Oct 09, 2023 4:40 pm

Re: Accelerometer sensor not detected

#3 Post by appas »

Ah, I personally prefer continuing old threads because starting new ones on the same topic leads to fragmentation of the forums, but I can appreciate that there are many opinions on "necro" posting. I see that the topic was split, so I will re-iterate on the problem: with the Lenovo X1 Yoga (I have the 2nd generation model), which is a 2-in-1 laptop/tablet convertible, on the stock Windows 10 operating system, turning the display around will take me into tablet mode. In this mode, the machine behaves like a tablet, in that turning it physically around will rotate the display. Well, in MX, this doesn't happen, and if I rotate the screen manually, the touchscreen coordinates are not correct: I will now try to describe the behavior: consider the screen's sides as they are in the laptop orientation as x (horizontal) and y (vertical). When I rotate the screen, and the machine in my hand, they should get re-mapped, so that what was the x axis now becomes the y axis, and vice versa. As it is, if I move my finger along the short edge of the screen (that is vertical in laptop orientation), the cursor moves along the long edge (that is horizontal in the laptop orientation).

The author of the previous thread "solved" this by changing to Mint/Ubuntu, so it must be solvable in MX, which I'd like to stay with.

Please help me solve these two problems, which, again, are: autorotation, and touchscreen funcitionality when rotated.

QSI:

Code: Select all

System:
  Kernel: 6.1.0-23-amd64 [6.1.99-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-23-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto May 19  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Convertible System: LENOVO product: 20JES45V01 v: ThinkPad X1 Yoga 2nd
    serial: <superuser required> Chassis: type: 31 serial: <superuser required>
  Mobo: LENOVO model: 20JES45V01 v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO
    v: N1NET64W (1.51 ) date: 03/27/2024
Battery:
  ID-1: BAT0 charge: 46.7 Wh (100.0%) condition: 46.7/56.0 Wh (83.3%) volts: 16.9 min: 15.3
    model: SMP 01AV441 type: Li-poly serial: <filter> status: full cycles: 320
CPU:
  Info: model: Intel Core i7-7600U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check
    gen: core 7 level: v3 note: check built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 9 microcode: 0xF4
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 800 min/max: 400/3900 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 23199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel arch: Gen-9.5
    process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
  Device-2: IMC Networks SunplusIT Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4
    chip-ID: 13d3:5682 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: LG Display 0x04aa built: 2016 res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2
    size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
  API: ALSA v: k6.1.0-23-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IF-ID-1: wwan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3
    chip-ID: 8087:0a2b class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 4 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 100 hci-v: 4.2 rev: 100
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 1.88 TiB used: 366.99 GiB (19.1%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: SanDisk model: SD64G size: 58.24 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-2: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT2000P3PSSD8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P9CR40D temp: 36.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 1.35 TiB size: 1.33 TiB (98.35%) used: 53.04 GiB (3.9%) fs: ext4
    dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 1.95 GiB (48.8%) priority: -2 file: /swap/swap
  ID-2: swap-2 type: file size: 24 GiB used: 0 KiB (0.0%) priority: -3 file: /swapfile
Sensors:
  System Temperatures: cpu: 56.0 C pch: 52.5 C mobo: N/A
  Fan Speeds (RPM): fan-1: 0
Repos:
  Packages: pm: dpkg pkgs: 2724 libs: 1522 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 347 Uptime: 5d 9h 56m wakeups: 6 Memory: 15.37 GiB used: 13.15 GiB (85.6%)
  Init: SysVinit v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0
  alt: 12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

User avatar
appas
Posts: 36
Joined: Mon Oct 09, 2023 4:40 pm

Re: Accelerometer sensor not detected

#4 Post by appas »

I found this tool that seems to be made for this purpose: https://github.com/sarmbruster/thinkpad ... a_rotation

However, it is quite old so I think it's made for the 1st gen Yoga, and does not work with my machine. As it's unmaintained, I am posting the output here instead of in its issue tracker, in the hopes that it will help us get this issue resolved:

Code: Select all

2024-08-27 00:09:31,463 - root - INFO - detected wacom devices: ['Wacom Pen and multitouch sensor Finger touch', 'Wacom Pen and multitouch sensor Pen stylus', 'Wacom Pen and multitouch sensor Pen eraser']
2024-08-27 00:09:31,470 - root - INFO - found stylus Wacom Pen and multitouch sensor Pen stylus
2024-08-27 00:09:31,470 - root - INFO - found finger touch Wacom Pen and multitouch sensor Finger touch
2024-08-27 00:09:31,470 - root - INFO - found touchpad and trackpoints ['TPPS/2 IBM TrackPoint', 'SynPS/2 Synaptics TouchPad']
2024-08-27 00:09:31,475 - root - INFO - connected to acpi socket <module 'socket' from '/usr/lib/python3.11/socket.py'>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 173, in activate_name_owner
    return self.get_name_owner(bus_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 348, in get_name_owner
    return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 634, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.hadess.SensorProxy': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/appas/Downloads/thinkpad_x1_yoga_rotation/./thinkpad_x1_yoga_rotation.py", line 154, in <module>
    main(options)
  File "/home/appas/Downloads/thinkpad_x1_yoga_rotation/./thinkpad_x1_yoga_rotation.py", line 140, in main
    proxy = bus.get_object('net.hadess.SensorProxy', '/net/hadess/SensorProxy')
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 237, in get_object
    return self.ProxyObjectClass(self, bus_name, object_path,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 250, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 178, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 273, in start_service_by_name
    return (True, self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 634, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name net.hadess.SensorProxy was not provided by any .service files
2024-08-27 00:09:31,639 - root - INFO - running ['xinput', 'enable', 'TPPS/2 IBM TrackPoint'] with exit code 0
2024-08-27 00:09:31,655 - root - INFO - running ['xinput', 'enable', 'SynPS/2 Synaptics TouchPad'] with exit code 0
2024-08-27 00:09:31,663 - root - INFO - running ['xsetwacom', '--set', 'Wacom Pen and multitouch sensor Finger touch', 'rotate', 'none'] with exit code 0
2024-08-27 00:09:31,670 - root - INFO - running ['xsetwacom', '--set', 'Wacom Pen and multitouch sensor Pen stylus', 'rotate', 'none'] with exit code 0
2024-08-27 00:09:31,677 - root - INFO - running ['xsetwacom', '--set', 'Wacom Pen and multitouch sensor Pen eraser', 'rotate', 'none'] with exit code 0
I am willing to write some code for this, but I think the "SensorProxy was not provided by any .service files" is related to the same problem of not having the acceleromer sensor available, in the first place.

There are some modules loaded that look like they could be related:

Code: Select all

lsmod |grep acc
hid_sensor_accel_3d    20480  0
hid_sensor_trigger     20480  14 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_rotation
hid_sensor_iio_common    24576  7 hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_rotation
industrialio          114688  9 industrialio_triggered_buffer,hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_incl_3d,kfifo_buf,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_rotation
hid_sensor_hub         28672  9 hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_rotation,hid_sensor_custom

User avatar
j2mcgreg
Global Moderator
Posts: 6627
Joined: Tue Oct 23, 2007 12:04 pm

X*M

#5 Post by j2mcgreg »

@appas wrote:
so it must be solvable in MX
I'll add "eventually" to that statement. The problem is that Debian is a very conservative distro that puts stability above all else while the Ubuntu family lean more towards the cutting edge. "Eventually"can be a really long time, so if you need that accelerometer working today or tomorrow, you should make the distro switch too.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
appas
Posts: 36
Joined: Mon Oct 09, 2023 4:40 pm

Re: X*M

#6 Post by appas »

j2mcgreg wrote: Mon Aug 26, 2024 5:16 pm @appas wrote:
so it must be solvable in MX
I'll add "eventually" to that statement. The problem is that Debian is a very conservative distro that puts stability above all else while the Ubuntu family lean more towards the cutting edge. "Eventually"can be a really long time, so if you need that accelerometer working today or tomorrow, you should make the distro switch too.
Ok, but before I do that, let's try to fix this in MX.

So, the Gitlab page for iio-sensor-proxy says to run udevadm info --export-db to debug. This gives output with, among other things, these entries:

Code: Select all

P: /devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0002/HID->
M: HID-SENSOR-200073.12.auto
U: platform
T: mfd_device
V: hid_sensor_accel_3d
E: DEVPATH=/devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0>
E: SUBSYSTEM=platform
E: DEVTYPE=mfd_device
E: DRIVER=hid_sensor_accel_3d
E: MODALIAS=platform:HID-SENSOR-200073
E: USEC_INITIALIZED=6909928
E: ID_PATH=pci-0000:00:13.0-platform-HID-SENSOR-200073.12.auto
E: ID_PATH_TAG=pci-0000_00_13_0-platform-HID-SENSOR-200073_12_auto

P: /devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0002/HID->
M: iio:device0
R: 0
U: iio
T: iio_device
D: c 239:0
N: iio:device0
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0>
E: SUBSYSTEM=iio
E: DEVNAME=/dev/iio:device0
E: DEVTYPE=iio_device
E: MAJOR=239
E: MINOR=0
E: USEC_INITIALIZED=7276816
E: IIO_SENSOR_PROXY_TYPE=iio-poll-accel iio-buffer-accel
E: SYSTEMD_WANTS=iio-sensor-proxy.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

P: /devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0002/HID->
M: HID-SENSOR-200073.13.auto
U: platform
T: mfd_device
V: hid_sensor_accel_3d
E: DEVPATH=/devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0>
E: SUBSYSTEM=platform
E: DEVTYPE=mfd_device
E: DRIVER=hid_sensor_accel_3d
E: MODALIAS=platform:HID-SENSOR-200073
E: USEC_INITIALIZED=6910631
E: ID_PATH=pci-0000:00:13.0-platform-HID-SENSOR-200073.13.auto
E: ID_PATH_TAG=pci-0000_00_13_0-platform-HID-SENSOR-200073_13_auto

P: /devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0002/HID->
M: iio:device2
R: 2
U: iio
T: iio_device
D: c 239:2
N: iio:device2
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001F:8087:0AC2.0>
E: SUBSYSTEM=iio
E: DEVNAME=/dev/iio:device2
E: DEVTYPE=iio_device
E: MAJOR=239
E: MINOR=2
E: USEC_INITIALIZED=7291416
E: IIO_SENSOR_PROXY_TYPE=iio-poll-accel iio-buffer-accel
E: SYSTEMD_WANTS=iio-sensor-proxy.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
Then, it advices to run gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy, which gives the same error as that Python script:

Code: Select all

gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy
Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.hadess.SensorProxy was not provided by any .service files
In iio-sensor-proxy's Gitlab, I found "It requires [...] systemd". So, I will now reboot with systemd.

User avatar
appas
Posts: 36
Joined: Mon Oct 09, 2023 4:40 pm

Re: Accelerometer sensor not detected  [Solved]

#7 Post by appas »

That did it!

So, for anyone else facing this issue: install the thinkpad_x1_yoga_rotation script (probably a good idea to have it in autorun) - note that it requires the python3-docopt package in addition to the listed requirements!

Post Reply

Return to “MX Help”