Device: BraX3, iodéOS 7.8-20260930-brax3 (also present on 7.6-20260623-brax3), kernel 5.15, MT6835
Symptom: The phone occasionally freezes completely for a while, then recovers. Looking into it over adb, the touchscreen controller (Omnivision TCM, SPI3, IRQ 157) is firing interrupts continuously whenever the screen is on, even with no finger anywhere near the screen. The kernel thread serving that IRQ plus the SPI thread together use roughly half a CPU core all the time, and load average sits at 12-18 on an idle phone.
Measurements (screen on, nothing touching the screen):
$ adb shell "grep '^ *157:' /proc/interrupts; sleep 5; grep '^ *157:' /proc/interrupts"
157: 4733178 0 0 0 0 0 0 0 mtk-eint 1 Level omnivision_tcm
157: 4753763 0 0 0 0 0 0 0 mtk-eint 1 Level omnivision_tcm
= 20,585 interrupts in 5 s (~4,100/s). Earlier samples went as high as 36,000 in 5 s. 4.7 million interrupts 22 minutes after a fresh boot.
$ adb shell "timeout 5 getevent -t /dev/input/event2 | grep -c ."
0
= zero input events from the touch device in the same period. The controller asserts the attention line nonstop, but the driver finds no touch data to report.
$ adb shell top -b -n 2 -d 3 -s 3 -o %CPU,TIME+,ARGS | grep -E 'omnivision|spi3'
18.3 5:05.79 [irq/157-omnivision_tcm]
10.3 2:44.50 [spi3]
What I have ruled out:
- USB / charging: same rate plugged and unplugged (tested over a 2-minute unplug).
- OS build: identical on 7.6 and 7.8.
- Settings: high touch polling rate, high touch sensitivity, glove mode, touch hovering all off; wake gestures on or off makes no difference.
- Uptime: present within 3 minutes of a fresh boot, so not something that builds up.
- Screen off: interrupts stop completely while the screen is off and resume instantly at screen-on, so the driver’s suspend path works; the problem is in active mode.
Touch itself still works normally. The interrupt is level-triggered, so this looks like the controller signalling data that the driver never acknowledges, i.e. a firmware/driver protocol mismatch, or a hardware fault holding the line low.
Question for other BraX3 owners: could you run this with the screen on and nothing touching it, and post the two numbers?
adb shell "grep '^ *157:' /proc/interrupts; sleep 5; grep '^ *157:' /proc/interrupts"
On a healthy device the first column should grow by a few hundred at most in 5 seconds. If yours grows by tens of thousands like mine, this is a driver issue in the brax3 kernel and affects everyone’s battery and responsiveness. If yours stays low, my unit has a hardware fault.
Question for Brax / iodé: can you check the omnivision_tcm driver’s interrupt handling in active mode? The driver’s sysfs node (/sys/bus/spi/devices/spi3.0/omnivision_tcm.0/) exposes info and irq_en, but they are root-only so I cannot read the controller’s firmware mode myself. If you want a dmesg from the touch driver I can provide one if you tell me how to get it without root.