Strange Scrolling on Ender 3 V2 with SYNWIT (VIEWE) screen unit

[mriscoc]

Strange Scrolling on Ender 3 V2 with SYNWIT (VIEWE) screen unit

[mriscoc]

The icons are not fixable for your screen firmware version. You can select a darker background color in the Advanced Settings menu.

[mriscoc]

Please post a capture of your info page. From your screenshot, something is bad with your version because the icons are not with transparent background. Maybe the screen is loaded with an incompatible icon set.

[andrewandneil]

Is this what you were asking for?

[mriscoc]

Did you flash your screen before? If yes, you need to re-flash with a compatible icon set from here: https://github.com/mriscoc/Ender3V2S1/wiki/How-to-update-the-display

If not, and you have a stock screen unit and your printer is a new purchase, then maybe we have here a new screen unit not checked before, if you can, please post a capture of the board inside of your screen.

[andrewandneil]

You know, I think you’re right. Doesn’t fit either the DACAI nor the DWIN screen type. Just got it a few days ago. Everything is stock apart from fans and a CRTouch install.

[mriscoc]

Please take a closeup picture from the main chip of the board of the screen unit, as clear as possible, and also from the labels, I will do research. It is similar to the DACAI screen.

[andrewandneil]

Hope these help. Took them zoomed in as much as I could. Please notify if you require more. Thank you for all this.

[mriscoc]

I'm preparing a version for your test, could you try it?
Experimental-Ender3V2-BLTouch-20220413.zip

[andrewandneil]

So I just got a chance to try it out. This has fixed the strange scrolling issue, however, scrolling seems ‘laggy’. But much more useable than before. However, I don’t know if you tried to, but it has not fixed the black boxes around the icons. Please see video attached. Thank you again
https://user-images.githubusercontent.com/20885631/163368531-d5d8d2a4-555c-42c3-b9ac-0db2c043a54b.MOV

[mriscoc]

Hi, do you have the problem reported here? #323

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.