My first patch is in this release, it was for battery level reporting of a wireless keyboard.
The main AI assistance was in determining why my mouse's battery level was easy to see, but not my keyboard's battery level. Having assistance identifying the information pipeline (kernel -> UPower -> xfce4-power-manager) and then identifying which step was broken was vital for me starting the project. The patch itself was trivial, so no coding assistance was needed.
IMHO this is where AI truly shines; being able to understand a system and its components and analyze them is institutional knowledge that requires a long time for an individual to obtain. AI can do this in a much shorter period and allow contributors otherwise unfamiliar with a codebase to make a meaningful contribution.
The keyboard is a Logitech G915 TKL. The problem is that when the keyboard was connected via the Logitech Lightspeed adapter the battery levels did not appear in xfce4-power-manager (the taskbar widget). When connected via bluetooth the battery level was visible. The root cause was that the lightspeed usb connector (device id 0xc545), one of many from Logitech, was not associated with the kernel driver needed and defaulted to hid-generic. Keyboard functionality worked, but not the battery level reporting. So my kernel patch was a simple mapping telling the kernel to use the proper, already existing recvr_type_gaming_hidpp_ls_1_3, driver for this previously unknown device id.
So what was actually broken? Just yesterday I set up my wireless keyboard on Ubuntu LTS 26.04 using bluetoothctl and BlueZ seemed to report the battery fine but I didn’t check upower.
The kernel didn't know to use the proper driver for my usb wireless dongle. Adding a few lines of code telling the kernel this usb device id requires this driver was the only change needed.
The main AI assistance was in determining why my mouse's battery level was easy to see, but not my keyboard's battery level. Having assistance identifying the information pipeline (kernel -> UPower -> xfce4-power-manager) and then identifying which step was broken was vital for me starting the project. The patch itself was trivial, so no coding assistance was needed.