[Bug]: SteelSeries Arctis Nova 5X reports 3% battery instead of 97%

Abierto
#628 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, linux

Línea de trabajo

The code in question is the Linux kernel driver drivers/hid-steelseries-arctis.c, not this placeholder repository. Start at steelseries_arctis_nova_parse_status(), where the battery percentage is read from data[2], and compare it with the captured 0xb0 response (byte 3 is 0x61, or 97). Done means the Nova 5X reads the correct byte without changing decoding for other models, verified against that capture.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Kernel

7.3.1-1-cachyos

Desktop environment / window manager

KDE Plasma, Wayland.

CPU

AMD Ryzen 7 7800X3D 8-Core Processor.

GPU / driver
  • NVIDIA GeForce RTX 4080 SUPER, using the nvidia driver, version 615.78.08.
  • AMD Radeon 610M integrated graphics, using the in-kernel amdgpu driver from 7.3.1-1-cachyos.
Description

KDE shows a critical-battery notification when a charged SteelSeries Arctis Nova 5X is turned on. HeadsetControl reports 97% battery, but the kernel power-supply device and UPower report 3%.

The affected device has USB vendor ID 1038 and product ID 2253. Its active HID driver is hid-steelseries-arctis.

Steps to reproduce
  1. Connect the Nova 5X USB transmitter and turn on the charged headset.
  2. Query its status with headsetcontrol -d 0x1038:0x2253 -m -o json.
  3. Compare the battery percentage with upower --dump and the headset's power-supply properties under /sys/class/power_supply/.
  4. Observe the critical-battery notification in KDE.

In the affected session, a ChatMix helper also runs the HeadsetControl query every 0.5 seconds. Reproduction with that helper stopped has not been tested.

Expected behavior

The kernel and UPower should report the headset's battery percentage correctly. KDE should not warn that a nearly full battery is critically low.

Actual behavior

HeadsetControl reports 97%, while the kernel reports 3%. UPower marks the battery as critical, and KDE displays a low-battery warning. UPower history also contains repeated jumps between near-full and critically low readings.

Logs / error messages

Relevant excerpts only. Full system logs are not attached to avoid disclosing unrelated personal information.

HeadsetControl 4.1.0 reports:

"battery": {
  "status": "BATTERY_AVAILABLE",
  "level": 97
}

The kernel power-supply properties report:

POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=3
POWER_SUPPLY_CAPACITY_LEVEL=Critical
POWER_SUPPLY_MODEL_NAME=Arctis Nova 5X
POWER_SUPPLY_MANUFACTURER=SteelSeries

UPower reports:

model: Arctis Nova 5X
warning-level: critical
percentage: 3%

A read-only capture from the transmitter's HID interface 3 received a 64-byte status response. Its first eight bytes were:

b0 03 03 61 03 64 64 00
Additional context

The evidence points to a model-specific offset error in the 0xb0 status decoder:

  • steelseries_arctis_nova_parse_status() reads data[2] as the battery percentage. That byte is 0x03 in the captured response, which explains the kernel's 3% reading.
  • HeadsetControl's Nova 5X implementation reads data[3]. That byte is 0x61, or 97 in decimal, matching its reported percentage.
  • The kernel assigns the Nova 5X to the shared Nova decoder. A correction should account for the Nova 5X report layout without changing other models' decoding incorrectly.

The same shared decoder still reads data[2] in Linux 7.4-rc1 and in the upstream development source checked on 2026-11-03. The running kernel's upstream version, 7.3.1, is the latest stable release listed on kernel.org on that date. A full system update was not performed as part of this investigation, and a different kernel was not boot-tested.

References:

Lenguaje dominante
Sin datos de lenguaje
Estrellas
29
Forks
2
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CachyOS/distribution

Todos los issues de CachyOS/distribution

Issues similares

Más issues de Operating Systems

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.