Refund Policy
From the day you start receiving the product , 30-day no-questions-asked refund policy on all products.
Description
Free Shipping
Payment & Security
Your payment information is processed securely. We do not store credit card details nor have access to your credit card information.
FAQ：
1. Are there any tutorials and software installation guides available?
Yes, please refer to this curriculum link: 35-ips-screen.rtfd.io
2. Why does my 3.5-inch screen stay black or white after powering on?
Make sure the correct driver is installed.
For detailed instructions, please refer to the detailed Online Tutorials here: 35-ips-screen.rtfd.io
If you are using Raspberry Pi OS on Raspberry Pi 3B/3B+ or Zero 2W boards, you must install Bullseye instead of Bookworm to ensure compatibility.
Ensure the screen is firmly connected and properly aligned with the GPIO pins.
3. Can the 3.5" IPS touchscreen and the HDMI monitor be used simultaneously?
The 3.5-inch touchscreen cannot be used simultaneously with an HDMI monitor.
After installing the driver for the 3.5" IPS display, if both the 3.5" IPS screen and an HDMI monitor are connected, the system will default to HDMI output.
To display on the 3.5” IPS touchscreen, disconnect (unplug) the HDMI monitor.
4. Can I use it without installing drivers?
No. This screen uses an SPI interface and requires a dedicated driver to work properly.
5. Can this screen work on Ubuntu, Kali or RetroPie?
Yes, but it requires installing specific drivers. RetroPie is supported on Raspberry Pi 4, 3, and Zero 2W, but not on Raspberry Pi 5.
6. Can it operate under extreme temperatures?
The operating temperature range is -20°C to 60°C. Do not exceed this range to avoid damage or shortened lifespan.
7. Why can't I log in after installing the 3.5-inch display driver?
This issue may occur if the driver is installed on a system that has already been configured rather than on a fresh OS installation. After installing the driver, the system might boot into an unexpected login screen, and previous login credentials may no longer work — even though the same credentials still function via SSH.To prevent this, we recommend installing the driver on a freshly imaged system (factory defaults) before making any other configurations. Systems that have been modified or customized beforehand are more likely to experience this issue.We are aware of this bug and are currently investigating its root cause while working on improvements.
Important: Do not update the system kernel. The display depends on a kernel-level driver, and updating the kernel may cause driver conflicts that render the touchscreen non-functional.