You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It mentions some software called Guition which seems to be different from the stuff I have already seen. Maybe this is another variant of a newer screen type?
Hello @braewoods you're right it seems there is a new smart screen model on the market, thanks for telling me!
Damn, this will not help with my smart screen addiction 😆
I will definitely buy some and try to integrate it to this project!
This line in the ad is a lie, or this smart screen use a different technology than the others 3.5" that are unable to display gifs due to their very low refresh rate.
Hi again! I finally received the product and investigated a bit using HHD Serial Port Monitor to get the data transiting between the display and the computer.
I have bad news unfortunately.
Based on what I've seen, it seems like the display is based on an ESP32. When a theme is selected from the Windows software, a new complete ESP32 firmware is compiled by the Windows software and flashed to the display. I can see it on the Serial Port Monitor interface.
Then, when program is running, only sensors data are sent to the display periodically as you can see on this screen capture:
Frames in red are sent periodically by the software to the display, and contains a set of predefined sensor values separed by $N. Here I created a theme with only 1 sensor (CPU usage) and it is the data you can see (22,61) in the frame. The display acknowledge every frame from the computer.
So it seems you were right: even though the display does not use the HID protocol to communicate with the computer but a virtual serial port, it is working as the Fuldho 3.5" IPS Screen you're working on.
I don't think it can be integrated to this project.
Hi again! I finally received the product and investigated a bit using HHD Serial Port Monitor to get the data transiting between the display and the computer. I have bad news unfortunately.
Based on what I've seen, it seems like the display is based on an ESP32. When a theme is selected from the Windows software, a new complete ESP32 firmware is compiled by the Windows software and flashed to the display. I can see it on the Serial Port Monitor interface.
It seems like everything including the toolchain, obfuscated (maybe?) source code is in the main executable by finding patterns like GCC using a hex editor, also will try using binwalk to see if there is anything inetresting in there. So to add support, reverse engineering of the executable is needed to extract the source code and the build flags.
Hi @mathoudebine and everyone interested in this screen! 👋
Like many others, I purchased this exact Guition 3.5" IPS USB-C Secondary Screen, but the proprietary software bundled by the seller was no longer functioning properly. To bring this hardware back to life and make it genuinely useful, I refactored the ESP32-C3 firmware and transmission logic with the assistance of AI, and I can confirm it now works flawlessly with turing-smart-screen-python!
I created a dedicated repository containing the pre-compiled firmware binaries, factory restore backups, and full setup guides:
👉 Guition-Turing-Smart-Screen (GitHub)
Protocol Compatibility: By flashing the 80MHz SPI DMA custom firmware at offset 0x10000, the screen responds 1:1 to the standard REVISION: A (Turing Rev A / Command 197 DISPLAY_BITMAP) protocol.
Factory Firmware Backup: A clean 4MB raw factory flash dump is also provided at 0x0, so anyone can safely restore it at any time.
Hi @mathoudebine and everyone interested in this screen! 👋
Like many others, I purchased this exact Guition 3.5" IPS USB-C Secondary Screen, but the proprietary software bundled by the seller was no longer functioning properly. To bring this hardware back to life and make it genuinely useful, I refactored the ESP32-C3 firmware and transmission logic with the assistance of AI, and I can confirm it now works flawlessly with turing-smart-screen-python!
I created a dedicated repository containing the pre-compiled firmware binaries, factory restore backups, and full setup guides:
👉 Guition-Turing-Smart-Screen (GitHub)
Protocol Compatibility: By flashing the 80MHz SPI DMA custom firmware at offset 0x10000, the screen responds 1:1 to the standard REVISION: A (Turing Rev A / Command 197 DISPLAY_BITMAP) protocol.
Factory Firmware Backup: A clean 4MB raw factory flash dump is also provided at 0x0, so anyone can safely restore it at any time.
No source code for both ends and with it being apparently closed source (only .exe binaries and pre-compiled firmware binaries for the ESP32-C3 display) based off upstream sounds like a GPL violation to me, will sources be published (atleast for the upstream frontend software fork) to comply with the GPL?
Hi @mathoudebine and everyone interested in this screen! 👋
Like many others, I purchased this exact Guition 3.5" IPS USB-C Secondary Screen, but the proprietary software bundled by the seller was no longer functioning properly. To bring this hardware back to life and make it genuinely useful, I refactored the ESP32-C3 firmware and transmission logic with the assistance of AI, and I can confirm it now works flawlessly with turing-smart-screen-python!
I created a dedicated repository containing the pre-compiled firmware binaries, factory restore backups, and full setup guides:
👉 Guition-Turing-Smart-Screen (GitHub)
Protocol Compatibility: By flashing the 80MHz SPI DMA custom firmware at offset 0x10000, the screen responds 1:1 to the standard REVISION: A (Turing Rev A / Command 197 DISPLAY_BITMAP) protocol.
Factory Firmware Backup: A clean 4MB raw factory flash dump is also provided at 0x0, so anyone can safely restore it at any time.
⚙️ Recommended config.yaml Settings
display:
REVISION: A
DISPLAY_REVERSE: true
RESET_ON_STARTUP: false
No source code for both ends and with it being apparently closed source (only .exe binaries and pre-compiled firmware binaries for the ESP32-C3 display) based off upstream sounds like a GPL violation to me, will sources be published (atleast for the upstream frontend software fork) to comply with the GPL?
The change is complete. I also separated and re-uploaded the entire source code and the ESP-related parts.
Activity
mathoudebine commentedon Dec 22, 2023
Hello @braewoods you're right it seems there is a new smart screen model on the market, thanks for telling me!
Damn, this will not help with my smart screen addiction 😆
I will definitely buy some and try to integrate it to this project!
This line in the ad is a lie, or this smart screen use a different technology than the others 3.5" that are unable to display gifs due to their very low refresh rate.
mathoudebine commentedon Feb 19, 2024
Hi again! I finally received the product and investigated a bit using HHD Serial Port Monitor to get the data transiting between the display and the computer.
I have bad news unfortunately.
Based on what I've seen, it seems like the display is based on an ESP32. When a theme is selected from the Windows software, a new complete ESP32 firmware is compiled by the Windows software and flashed to the display. I can see it on the Serial Port Monitor interface.
Then, when program is running, only sensors data are sent to the display periodically as you can see on this screen capture:

Frames in red are sent periodically by the software to the display, and contains a set of predefined sensor values separed by
$N. Here I created a theme with only 1 sensor (CPU usage) and it is the data you can see (22,61) in the frame. The display acknowledge every frame from the computer.So it seems you were right: even though the display does not use the HID protocol to communicate with the computer but a virtual serial port, it is working as the Fuldho 3.5" IPS Screen you're working on.
I don't think it can be integrated to this project.
[-]New 3.5" screen variant?[/-][+]GUITION 3.5" screen support[/+]matu6968 commentedon Jun 29, 2024
It seems like everything including the toolchain, obfuscated (maybe?) source code is in the main executable by finding patterns like GCC using a hex editor, also will try using binwalk to see if there is anything inetresting in there. So to add support, reverse engineering of the executable is needed to extract the source code and the build flags.
q20021410 commentedon Sep 14, 2026
Hi @mathoudebine and everyone interested in this screen! 👋
Like many others, I purchased this exact Guition 3.5" IPS USB-C Secondary Screen, but the proprietary software bundled by the seller was no longer functioning properly. To bring this hardware back to life and make it genuinely useful, I refactored the ESP32-C3 firmware and transmission logic with the assistance of AI, and I can confirm it now works flawlessly with
turing-smart-screen-python!I created a dedicated repository containing the pre-compiled firmware binaries, factory restore backups, and full setup guides:
👉 Guition-Turing-Smart-Screen (GitHub)
📷 Hardware Showcase (Verified Working)
🔍 Technical Details & How It Works
0x10000, the screen responds 1:1 to the standardREVISION: A(Turing Rev A / Command 197DISPLAY_BITMAP) protocol.0x0, so anyone can safely restore it at any time.⚙️ Recommended
config.yamlSettingsmatu6968 commentedon Sep 14, 2026
No source code for both ends and with it being apparently closed source (only .exe binaries and pre-compiled firmware binaries for the ESP32-C3 display) based off upstream sounds like a GPL violation to me, will sources be published (atleast for the upstream frontend software fork) to comply with the GPL?
q20021410 commentedon Sep 14, 2026
The change is complete. I also separated and re-uploaded the entire source code and the ESP-related parts.