CTCaer
commented
1 year ago That's the ram initial training.
So, I used to hide that with a backlight fade in/out before the L4T loader. Thing is that I can only do that for Erista (2017) models. On mariko (2019/lite/oled), I can't hide it.
So I took the decision to maintain consistency instead of UX, since UX could only be done for Erista models. (I removed the backlight fade out/in basically)
Technical: Now why that happens? During dram training, there are certain training hw functions that actually stall any access to RAM. When that specific training happens, the display hw logic memfetcher can't read the framebuffer's pixles at that point and just continues to try the next ones. These also last way less than 1ms, reason why you see glitches and not the whole screen going to hell. And it happens as many times as how many freqs the table has.
TL;DR: It's here to stay
Bladen123
Masamune3210
Hey CTCaer
Splashscreens do graphical glitches like a pc game without VSync , it splits the picture for a 0.5 second. Dont know if thats supposed to be so and dont know where to write u thats why i just used this Issues Tab to contact u about it. I noticed that when booting Kodi (libreelec) , Lakka , Linux like Ubuntu and Fedora. Even if i dont use Splashscreens its same with the stock Hekate IPL Bootlogo.
Its nothing dramatic , just a cosmetic thing that doesnt look appetite :) maybe u can take a short look at it someday when ur bored . Thank you
Check the Video u can see the problem i have 👍 at the end of video
https://user-images.githubusercontent.com/96496833/221041658-12f56046-2c9e-465c-a84c-74f1b7a7cbcd.mp4