Diagnosing the R36S Plus Display Issue: A Deep Dive
Over the past few weeks, I undertook a deep technical investigation into the R36S Plus retro gaming handheld to understand and resolve a persistent display issue. What began as an attempt to make a new image work turned into a hardware diagnosis journey. Here's a comprehensive documentation of everything that was tried, tested, and discovered.
On first boot with various firmware images, the R36S Plus would run flawlessly for a few minutes before crashing or displaying vertical lines, flickering, or freezing. Later attempts to reboot it often resulted in an unstable or completely unresponsive screen.
Software or Firmware Error: Since the device initially worked fine, it was suspected that something in the OS or drivers was modifying the system state after first boot.
Resolution Mismatch: Boot files referred to a resolution of 1280x720, while the display was known to be 720x720.
Bad DTB/KERNEL Config: DTB files might have had incorrect display or GPIO configuration.
Power or VRAM Limitation: A theory emerged around insufficient memory or power supply to the display after boot.
The boot.ini file had a video parameter: video=HDMI-A-1:1280x720@60.
This was odd since the screen was 720x720 (HL-MP40HD-A-V1).
Despite the mismatch, the system still booted and displayed correctly for a short time.
Examined the provided image files:
KERNEL
rk3326-gameconsole-r36s.dtb
No immediate visible errors, but screen problems persisted.
Attempted to replace only the display section (panel and timing) from other working devices (R46S, R36S Max).
DTB swaps and screen timing edits had no effect.
Tried unofficial ArkOS and PalmOS builds made specifically for R36S Plus.
Same problem: worked perfectly for 2–3 minutes, then failed.
Considered and attempted CPU downclocking.
Explored whether changing VRAM allocations in JELOS settings would help.
Nothing resolved the display instability.
Shook, tilted, and tapped the device — no visible impact.
Tried different SD cards — same issue on all.
Swapped displays between devices:
Took the R36S Plus display and installed it into a perfectly working R46S → immediate flickering and uneven brightness on the R46S.
The HL-MP40HD-A-V1 display was faulty.
Despite all the correct drivers and kernel settings, the display itself had a hardware issue. It would heat up or degrade after a few minutes of usage, resulting in visual glitches. This was conclusively proven when the same screen failed in another previously working device.
Display hardware can fail in non-obvious ways. Initial boot working fine is not enough to rule out hardware issues.
Always isolate variables. Testing the screen in another known-good unit confirmed the real culprit.
Community ROMs are not always the problem. Many of them worked perfectly on other hardware.
Avoid tunnel vision. Software and kernel debugging was thorough, but it was hardware all along.
When debugging a new handheld:
Start by testing core hardware (display, power, buttons).
If the problem only appears after warm-up, consider thermal/hardware aging.
Keep a spare SD card with a known working image for quick diagnosis.
Document screen part numbers and test compatibility across devices.
Display Used: HL-MP40HD-A-V1
Tested Devices: R36S, R36S Plus, R46S, R36S Max
Images Used: Official and unofficial (ArkOS, PalmOS, JELOS)
After all the work, I chose to retire the R36S Plus for now. The R36S — even with a dim corner — is stable and functional. If I revisit this device in the future, it will be with a new display.
Hopefully, this helps someone who runs into similar display issues and doesn’t know where to begin. Sometimes, the most elusive bugs are simply a piece of bad hardware pretending to work.