Support TURZX 4.6" / 5.2" / 8" / 8.8" (V1.x) / 9.2"

[mathoudebine]

Supported:

• TURZX 9.2" (1920x462)
• TURZX 5.2" (1280x720)
• TURZX 8" (1280x800)
• TURZX 4.6" (960x320)
• TURZX 8.8" (1920x480)

[Nazgile94]

any news for this ? =)

[jurjevic]

Any update on this PR? I would really be happy to find the 8.8 support in the main release.

[drivin]

9.2" is working with the patch.

[JaxDagger]

9.2" is working with the patch.

Thank you for the heads up, how do i patch this? sorry if it sounds like a stupid question just very new to it all still

[mathoudebine]

Hi all, just so you know this PR is not merged yet because there is an issue with some themes: the frames sent to the display cannot exceed 1MB for now which means that the background of some 8.8" themes cannot be loaded

[patriq]

For 9.2" the product ID is 0x0092

Also thanks for the patch :)

[drivin]

9.2" is working with the patch.

Thank you for the heads up, how do i patch this? sorry if it sounds like a stupid question just very new to it all still

You can clone my fork (https://github.com/drivin/turing-smart-screen-python). That should work.

[owanachanaki]

Hi,
Thanks for all the hard work :)

Any updates on whether this project would work with Turing 5.2" display?

[drivin]

I have updated my pull request (PR 950).

I was not able to bypass the 1 MB limit, as this restriction also exists in the original program. Instead, the image is compressed before processing, which I have implemented accordingly.

Video files are now supported as well.

However, there is still an issue: JPEG-encoded images produce a visible bar with artifacts on the screen.

[smandon]

Hi,

They released a new 4.6" model, with a 960x320 resolution. Like other recent models, it doesn't use a serial port for communication. It uses the same app as the 8.8 and 9.2 devices, so I guess it will most likely use the same protocol.

I bought mine there: https://fr.aliexpress.com/item/1005010375743572.html

The vendor ID is the same (0x1CBE) and the product id is 0x0046.

Edit: I can confirm it uses the same protocols as the 8.8 V1.1 and 9.2 models, I made changes starting from @drivin fork and added support for the 4.6". I made a PR to @drivin's fork.