comma four OLED red black-level tint temporary (til next boot) cleared by RM67162 sleep/wake lifecycle
- Dominant language
- Python
- Stars
- 63.7k
- Forks
- 11.4k
- Avg merge
- 17h 53m
- Merged PRs (30d)
- 171
Description
### Describe the bug
On my comma four with the Bantian/DWO RM67162 OLED, nominally black areas show a strong red glow. Gamma and RGB adjustments do not fix it, but a complete `DISPOFF`/`SLPIN` followed by the stock init and `SLPOUT`/`DISPON` greatly reduces the glow until the next reboot. This suggests an incomplete panel sleep/power sequence during the bootloader-to-kernel continuous-splash handoff.
Test environment
- Device: comma four
- Codename: `mici`
- Panel: DWO/Bantian DO0200FAT06, RM67162
- Display ID: `00 80 00`
- AGNOS: `18.4`
- openpilot: `0.11.1`
- Kernel: `4.9.103 #1 SMP PREEMPT Mon May 11 05:09:32 UTC 2026 aarch64`
- Final DSI error count: `0x00`
- Final kernel taint: `0`
### Provide a route where the issue occurs
N/A — the issue is reproducible offroad immediately after a warm reboot. Dongle ID: b790ecad7726a655
### openpilot version
0.11.1
### Additional info
[comma-four-bantian-oled-developer-report.zip](https://github.com/user-attachments/files/31498956/comma-four-bantian-oled-developer-report.zip)
Contributor guide
Research direction
No source file, test, or entry point is identified; start by examining the attached developer report and tracing the comma four/mici RM67162 bootloader-to-kernel continuous-splash handoff. Done means reproducing the warm-reboot red tint and confirming that the relevant sleep/wake lifecycle removes it through the next boot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100