the fact that the display works perfectly with devices other than the pis strongly suggests to me that it's a software issue, which is either fixable by tweaking driver settings, messing around with compositors or via a driver update. the hardware to me clearly isn't at fault here.
In the past, I've had screen tearing caused by cheap HDMI cables. Have you tried using an actual HDMI cable instead of that little adapter? I think it's worth a try, since it was fine with your PC when you used an actual HDMI cable and because that little screen actually does look really good. Nice video!!
This definitely seems to be case here. I've had a couple super cheap 6 inch HDMI cables through various products and they all either didn't work entirely or had horrible connection issues.
yeah i dont get the troubleshooting he did with this. if it worked fine on pc its either the pc or the cable. so i would blame the pi or the cable in this scenario
I agree. The display isn't at fault here as demonstrated by hooking it up a PC, This is a good demonstration of how sucky the Raspberry Pi is at playing video in a webbrowser (Vsync is like "Am I a joke to you?"). I guess if he used omxplayer he wouldn't have any screen tearing (because it actually uses the GPU). Maybe broadcom needs to release proper drivers for their videocore GPU that enables VDPAU and VAAPI support. Couple that with a custom chromium build that has VDPAU and VAAPI support and then video in chromium would be a better experience instead of this teary mess. I have used a similar chromium build from the arch user repository (I used Manjaro) on a 2012 low power PC with an AMD APU, It worked fine until windows update nuked my dualboot setup and had to reinstall everything. The PC is running only Windows 10 Home right now.
I've already seen someone else suggest this, but I think this may have something to do with those adapters. The only thing that changes when the screen is not hooked up to the pi is the host device and the cable attaching it, so I would assume it's the cable. The only other thing I could think of is the possibility that whatever compositor RPD has may not have vsync enabled/working. I know that(for me at least) xfce's compositor is always broken on any of my Linux installs, and usually requires installing the compton compositor to fix tearing. That said, it wouldn't really explain why it still tears in retro pie, so I'm leaning more on it being a connector issue. I wish you luck and hope I was helpful in some way.
This is most likely due to the way the screen refreshes. This is a more common issue on cell phone displays, where Portrait mode works fine but Landscape mode has the same issue that you're having, and it's due to the way that the screen refreshes its pixels. I'd be willing to bet money that they use a panel originally designed for a cell phone (hence the portrait-mode by default), and it's the reason you're having the issue. I'd try running the display in portrait and running your tests again. If everything looks normal in portrait mode, it was originally a cell phone display and designed for portrait viewing.
Worse comes to worst you could build an NDS wedge-like handheld and run it vertically. One could also use it as a secondary display on a PC during NDS emulation. I'm curious if the tearing is present on PC.
@@SimmanGodz Right, and his PC also has enough horsepower to drive a full 60FPS so there's no perceived tearing, however the Pi doesn't have that same level of power, and anything UNDER the refresh rate of the screen can show tearing. When you combine that with wrong direction refreshing, you get the type of tearing he has.
@@paparansen what? He's pretty clued up mate and if you watch the beginning of video the screen is in portrait mode and he says he can fix it, so I assume he used display_rotate.
6H means its as hard as glass or harder, Glass is typically 5.5H Also if I decide to do this, I don’t like the whole not having a case thing. Do they make cases for these?
Where do you think the screen came from? They didn't manufacture the units specifically for the Pi, they just stuck an HDMI controller board on the back of a standard phone screen unit.
I have this and I love it. I saw the "tearing" when I ran it on pi zero but on pi 4 8 gig ram I haven't seen it at all. I am not using it for games or video though... I don't think it's an issue with the screen just a limitation of the pi. Recommending avoiding is a bit much. This is the best ever screen for rpi. Thé color is so beautiful and I love that I can see it in full sunlight
I'm thinking one of 3 things are happening here, 1- it has to do with the "works out of the box", it might need a firmware update or something like that. 2- the orientation change, in which case if you get no tearing in the original orientation, it might be solved with a firmware update for landscape, 3- the adapter might not be the greatest, try using a quality HDMi cable. other than that I'm out of ideas.
No. Videocore GPU is rotating the framebuffer by copying one buffer diagonally to another one which actually gets out of to an LCD. That's why it needs more memory allocated to the GPU, for this to work. Apparently a hack to get around some use cases and portrait monitors. I've used display_rotate=1 once when I rotated my LCD and got the same screen tearing. Maybe double buffering would get around it, but it'd have to be implemented in hardware. Synchronized to VSYNC. You can do memory copies on offscreen buffers, but the Videocore GPU evidently doesn't double buffer this video buffer transposition en.wikipedia.org/wiki/Transpose
I've had similar issues when using my GPD Win 2 on some Linux distros. The problem is not the screen itself, but rather the display drivers (is that what you call it?). I'm 100% certain that if you flip the resolution back to portrait mode and test the screen tearing again it would completely disappear. I'm theorizing that this may be caused due to the developers not intending people to flip their resolution like that all too often, so they probably haven't focused on that feature too much. Though, I'm pretty sure knowing Linux that this issue would get fixed eventually. TLDR: The screen isn't the problem! It's just the display drivers that flipping the resolution that's causing all of this.
I really hope ETA revisits the screen and explains what he did to get it working. Sounds like a really awesome screen, and the flaw seems like it has a solution (according to WaveShare).
Raspberry pi 5 has the best compatibility and resolutions/refresh I’ve seen in pi’s so far. Seriously crazy. Running a 13” AMOLED on a pi5 with recalbox and tons of N64, PSX, PS2, PSP, SNES, etc games.
It's probably been suggested already but I recommend using different power supplies for your display and raspberry pi. There could be some noise injected into the micro USB port on the raspberry pi. I figure it's worth a try considering you don't have to buy anything it takes like 5 seconds to plug it into a new power adapter. if this ends up fixing your issue than you might be able to get away with using a powered USB hub since most isolate their power and data lines.
I'll go with the video drivers causing the choppiness & screen tearing issues while using my Pi4 and this happens despite using an official power supply and a mini HDMI cable.
This is really the kind of content I come here for. You win some you lose some. Hopefully the company comes up with a solution for you and you can let us know.
Please make a follow up on this with some TS done in the video. I feel like this should be something that can be resolved with some more TS. If the 4 can push 4K there's no logical reason it can't push this, probably a config/driver issue or maybe a faulty HDMI bridge since it clearly works from PC. I think I may buy one of these next week just to test this theory out myself if we don't hear back from you. This seems like it's an easy enough fix though if we can run through some tests
The Raspberry Pis as of late have strange VSync issues just in general, it just doesn't show up as badly on lower end displays. jamesh, one of the engineers on the Raspberry forums even said as much. Just personally, I think it's a cooling issue, the core is thermally throttling under any real load.
Jess Ragan $130 for a display that will last for 2-3 years also. I'm not a big fan of OLEDs because of burn-in problem and fullscreen flicker which makes your eyes bleed.
@@shadowflash705 OLEDs can easily last much longer than that lol, I'm still playing my early release edition Vita with an OLED screen and that thing is like 8 years old with no burn in. These are much newer more advanced OLEDs so you should easily get that much out of these, these are literally phone screens and those do static images like crazy. Sounds more like you problems than screen problems
Ameoled is great especially if shatterproof but dims over time especially with high brightness and white background objects.. and prone to screen burn or pixel lines
maybe this is someghing that they can fix with a firmware upgrade of the screen controller .... o the way to hook the Pi .... what do you think ? At the end is an 1080p AMOLED maybe used often into the smarphone market .... and of course no one is facing problems like the ones shown.
That is actually the raspberry pie's fault, not the display. I mean seriously, problems only occour when used with the raspy It cannot be more obvios But yet here we are, with everyone thinking the display is bsd somehow Trust me and lower the res Then your problems will be gone
@@icebread9335 Peace, mate, I didn't want to hurt anyone's feelings. Accordig to the video I understood that this behaviour culd be blamed on the display. Frankly speaking I don't care wich is the side to fix, when the systems works properly at 1080p. Is it on the Pi ? Good to know, let's hope that they can provide a solution soon.
Apart from the issue that you're experiencing its a very cool screen. I didn't even think companies were doing stuff like this. I can think of some awesome applications for this.
Id say its unfair to blame it on the screen, as you said it works fine in windows... That means the Pi isnt pumping out the frames correctly.. Thats a software fault in the Pi not the screen.
Little late watching this, but had you recommended this, I most likely would have bought one. Thanks for your honest assesment. Love my Odroid Advance Go, by the way. It looks great in yellow with the paint you recommended.
Its not a display problem, but a Pi one, I have the same problem different screen. There are even cases of this on TVs, with no fix, stay away from a Pi.
*Scren tearing only occours when your device falls out of sync with the display* this happens when your device cant keep up, or is faster than the current refresh rate. In this case you arw using a way to weak pc-the raspberry pie. You can work arround this with using a lower Resolutionen Or stronger Hardware... I only know theese two
Frankly, there's no need to get a whole new display. You can get adapters to make old Pi 3 screens (ones that plug into the GPIO for power and touch interface, at least) work with a Pi4 on eBay for very cheap. I was experimenting with a Pi 4 handheld a while back(abandoned it for the Odroid Go Advance) and it was rather easy once I had the adapter - the drivers would not auto-install, but plugging it into a TV and following the instructions to install them via terminal it worked fine. I STRONGLY recommend you get such an adapter and test with the displays you already have.
Try changing the refresh rate and resolutions of this display. Different resolutions with refresh rates might produce different results with raspberry pi.
Damn and that screen was looking really good too. Maybe not for that price, but for the size and quality. Hopefully the screen tearing can be solved with a screen-firmware or raspberry pi update.
Thanks for the warning. According to the comments, it might be a configuration issue causing the tearing. A follow-up response video would be worth my time watching. I've just subscribed, and am hoping we're both still here to care this much about frivolities in the near future.
@ETAPRIME Perhaps separating the Pi from the screen (interference due to proximity?) and swapping their adapters (the Full-HDMI to uHDMI and the USB connector) for quality cables (plugging the USB-to-uUSB into one of the 2.0 ports) you've tested with on the pi with other devices. My only other idea is to make sure your drivers are up to date and that Vsync is enabled.
Like many people have recommended, make sure you try a good HDMI to HDMI cable from the pi4 to screen before writing it off. Those home made adapters they come with can be total crap sometimes.
There are on mac custom resolution program that you can try the screen in many resolutions and sync mods. I also think that Rasp pi drive that screen at 24 Hz instead of 60Hz is something there in mapping Hz in the video.
Could you try to make a handheld with this screen and maybe a small compute stick Windows based machine? That would be different and amazing to see. Almost like the Alienware handheld? That would be sexy AF to see
If this works fine with a PC and not the Pi, the problem is either a bad cable or Pi's video drivers. There are timings specified in Waveshare Wiki, have you tried those ?
I'm still using my Coolpad legacy setup with a Lynx 9 controller, and couldn't be happier as far as portable retro emulation. I wouldn't have looked twice at the Coolpad, but ETAs review convinced me. Thanks!
I know I'm very late to the party but try running it again with a hdmi cable instead of the included adapters. I've been doing a bit of self research into pcb adapters and realistically speaking the included HDMI adapter is not large enough or designed well enough to be able to carry the signal.
Hey @ETA Prime, can you please try this: Switch the screen back to vertical mode then seeing if you can run MAME games (vertically) at normal speed. I found in the past that when you flip the screen into vertical mode, it causes Retropie games to slow down. If the makers intended on the screen to only display vertically, then this screen would be a great option for a Coleco tabletop arcade build i'm doing.
Open the NViidia Control Panel on a windows system, go i to the builtin Custom Resolution Utility, and copy the values in that to get your display settings. That should solve any configuration issues.
@@blaziken1564 Display resolution and timing works the same on linux or windows, ARM or x86. the tearing is either caused by horrid timing or a bad cable, so being able to copy timing values from a system where they work and mirror them to a system where what it's using doesn't work, would cross off one of the two possibilities. If the tearing is still bad then something to replace the daughterboard-style cable that came with the kit is in order.
The tearing is more noticeable might due to its an 1080 x 1920 resolution, not a 1920 x 1080 resolution. The refresh direction is sideways might make the tearing more noticeable.
Hi, ETA Prime, I got the TV HAT and I'm using it on a RPi 4. Got some recommendations what display I should choose? The official one is too expensive plus a protective case costs extra so it's a even bigger turn off.. Would prefer a display with touch so that I can easily use my RPi 4 as a mobile mini TV.
Future video suggestion. Peloton old monitor/tablet. See if u can get anything running on them. They are selling on eBay for 50-100$. People got android 4.1
6H hardness just means tempered glass, it basically means (like JerryRigEverything always says when using Moh's hardness test) scratches at level 6 with some deeper grooves at a level 7.
Whatever is causing tearing is software related. Something is not v-syncing. Most probably the rotate of xrandr. Check there. (I'd say, blaming this to the screen is a little too much, the screen has nothing to do with it, it's a diplay driver issue)
Not having variable refresh or the ability to run the screen at slower speeds than its refresh is not the issue. The issue with this device is with the touchscreen the image processor cant actually handle the task of keeping things synced properly and not have screen tearing. This is a real issue its why a flawless screen with touch tends to be expensive. the image processor needs to be 3 times as powerful being more like a coprocessor than a simple chip for putting the image on the screen from the digital signal being sent to it. This is why gsynk freesynk and variable refresh tech is still something that billions in r&d is spent on it.
@@Kumimono if you just disconnect the touch screen part it just wont work thats how this screen gets its power via usb so no because its not engineered to be optional on this screen witch also means disabling it in software wont work. This is why i dont like always on display because the touch is always on scanning for touch using power and running on the cpu/soc on my galaxy S9 for saving power on long trips. Most touchscreens are made in such a way to be thin and not take up much space so the screen and touch layers are just too much a part of each other and share the one processing chip and as far as i know that cant be changed because its also one of the things they do to eliminate internal latency to combat screen tearing to have one chip for the screen and touch. All this means is you just cant go too cheep or buy just a screen and hope there even made in the resolution youre looking for with the screen panel technology you want.
#Nice to see an honest review. Honestly I've had several - and even if it did work - when looking at the command line on a screen that size - one is asking for eyestrain... if they were a tenner yes but 19" monitors are dirt cheap..
Sounds more like a Raspbian/DesktopEnvironment issue to me. Did you test the same configuration on other HDMI displays (e.g. a tv)? VSync in linux isn't always that easy to do depending on the used software.
Yeah I wanted to re-emphasize for people that this is *not* a display issue. It is a 100% rPI issue. So while the "takeaway" might be correct, it should be amended to more like "For use as a horizontal display"...because the panel is natively vertical, likely made for a phone.
Rotation to 90 or 270 through the pi directly causes performance issues. If the screen is better without rotation you can grab the dev branch of EmulationStation and have it rotate on start.
Knowing Waveshare they'll prolly release a patch for that soon(ish) if it isn't a hardware / cable problem. I take you have looked at their wiki and the "3.2 Working with Raspberry Pi" section for this display? They seem to set /list some specific timings in there.
It hardly matters when the guys selling it are selling it specifically to Raspberry Pi users. If you sell it as compatible, you can't blame the incompatibility on the other party.
@@nialltracey2599 It IS compatible, though. I'm just saying the screen does in fact work with the Pi even with the screen tear. And if it does not have tearing with other devices, then maybe the Pi is the culprit. maybe a fixable issue through a gpu update or something.
@@ramzagtzo As others have pointed out, the problem comes from using display_rotate to get a normal landscape layout. Which *could* have been avoided by having the controller board set to landscape, but this is a quick, cheap mod of a mobile phone screen unit, and while the specs do describe it as portrait (1080x1920), the only images of it in actual use on their site show it in landscape mode, which is misleading if it only functions correctly in portrait mode.
I’m at a loss. When the screen is connected to a computer, it behaves as expected. When connected to a pi, there is screen tearing. How is this a problem with the screen? We know the screen works, we proved it by connecting it to something that works, and we don’t have the problem. What isn’t pushing the screen is the pi. Either the hardware is failing (including the adapters), the configuration is failing, or the driver is failing... on the pi.
Are there any options to use a Wayland backend? It could help screen tearing. It could well be a hassle setting up, Gnome might be too heavy for the Pi. Which probably makes Sway the best option, or maybe Enlightenment. Not sure how easy that would be to install over Raspbian, maybe go with something like Arch (hence the possible hassle).
Genuinely interested to know whether this would be a viable OLED upgrade for the zswitch Lite? Dames size and resolution, it’s whether the pins match up or what mods would be needed to get it to work…
It can depend on how you turned the screen 90 degrees? It isn't shown, not as a link or in the video how you did it, so it is hard to suggest what is the problem. It looks to me like it still is rendering in standing mode, even if the output is turned 90 degrees. Try to connect to a PC, and render the test video 90 degree turned like the RPi. I guess that could be the problem, but need to test to see if that is the case.
Have you tried tearing test in portrait mode? if it only happens in landscape mode, you could try run it in portrait mode then use rotate in retroarch.
If the comments below by other viewers fixed the problem I hope you make an update video. It seems to me since HDMI has several data pairs these displays could be designed to use the HDMI instead of a USB connection for touch screen capabilities.
You are rotating the screen in software. The raspi is not fast enough to decode videos or play games while rotating the screen. Those phone screens should come with a rotator chip on the pcb, so that the device sending the image doesn't need to do the work.
the fact that the display works perfectly with devices other than the pis strongly suggests to me that it's a software issue, which is either fixable by tweaking driver settings, messing around with compositors or via a driver update. the hardware to me clearly isn't at fault here.
In the past, I've had screen tearing caused by cheap HDMI cables. Have you tried using an actual HDMI cable instead of that little adapter? I think it's worth a try, since it was fine with your PC when you used an actual HDMI cable and because that little screen actually does look really good. Nice video!!
The fact it worked fine over a regular HDMI cable would imply that
At 7 mins during the retro gameplay he has it connected with a regular hdmi cable
@@aubinmoraes3887 no thats just a black usb power supply. So its possible ditching the adaptors and using a good hdmi would fix the tearing issues.
This definitely seems to be case here. I've had a couple super cheap 6 inch HDMI cables through various products and they all either didn't work entirely or had horrible connection issues.
yeah i dont get the troubleshooting he did with this.
if it worked fine on pc its either the pc or the cable. so i would blame the pi or the cable in this scenario
So...screen works perfectly on everything but an r-pi, and it's the screen's fault? doubt.
i guest it's mostly because compositor problem.
I agree.
The display isn't at fault here as demonstrated by hooking it up a PC, This is a good demonstration of how sucky the Raspberry Pi is at playing video in a webbrowser (Vsync is like "Am I a joke to you?"). I guess if he used omxplayer he wouldn't have any screen tearing (because it actually uses the GPU). Maybe broadcom needs to release proper drivers for their videocore GPU that enables VDPAU and VAAPI support. Couple that with a custom chromium build that has VDPAU and VAAPI support and then video in chromium would be a better experience instead of this teary mess.
I have used a similar chromium build from the arch user repository (I used Manjaro) on a 2012 low power PC with an AMD APU, It worked fine until windows update nuked my dualboot setup and had to reinstall everything. The PC is running only Windows 10 Home right now.
He didn't say it was the screen's fault... he said the problem lies within the rpi itself and he's open to suggestions on how to fix it.
i have it and it works perfectly fine, i made a little gamecube handheld out of it
Alex / good info. Can you let us know if you did anything to the OS.
I’m impressed with this screen and was almost ready to buy it.
I've already seen someone else suggest this, but I think this may have something to do with those adapters. The only thing that changes when the screen is not hooked up to the pi is the host device and the cable attaching it, so I would assume it's the cable. The only other thing I could think of is the possibility that whatever compositor RPD has may not have vsync enabled/working. I know that(for me at least) xfce's compositor is always broken on any of my Linux installs, and usually requires installing the compton compositor to fix tearing. That said, it wouldn't really explain why it still tears in retro pie, so I'm leaning more on it being a connector issue. I wish you luck and hope I was helpful in some way.
This is most likely due to the way the screen refreshes. This is a more common issue on cell phone displays, where Portrait mode works fine but Landscape mode has the same issue that you're having, and it's due to the way that the screen refreshes its pixels. I'd be willing to bet money that they use a panel originally designed for a cell phone (hence the portrait-mode by default), and it's the reason you're having the issue.
I'd try running the display in portrait and running your tests again. If everything looks normal in portrait mode, it was originally a cell phone display and designed for portrait viewing.
Worse comes to worst you could build an NDS wedge-like handheld and run it vertically. One could also use it as a secondary display on a PC during NDS emulation. I'm curious if the tearing is present on PC.
@@SimmanGodz Right, and his PC also has enough horsepower to drive a full 60FPS so there's no perceived tearing, however the Pi doesn't have that same level of power, and anything UNDER the refresh rate of the screen can show tearing. When you combine that with wrong direction refreshing, you get the type of tearing he has.
Are you using display_rotate because I believe it cause's screen tearing or used to at least.
you cant expect that HE knows stuff like this, he makes videos only for the money ;-)
@@paparansen what? He's pretty clued up mate and if you watch the beginning of video the screen is in portrait mode and he says he can fix it, so I assume he used display_rotate.
I think
Would like to see some footage of the screen running at its native vertical aspect ratio to see if it happens without the rotation.
@@randymarshole blablabla...
@@paparansen if you'd like to do a better video for free I'll be glad to watch it
6H means its as hard as glass or harder, Glass is typically 5.5H
Also if I decide to do this, I don’t like the whole not having a case thing. Do they make cases for these?
It looked like a phone with that screen. The first ever Piphone
Too thick for a PiPhone though. ☹️
Where do you think the screen came from? They didn't manufacture the units specifically for the Pi, they just stuck an HDMI controller board on the back of a standard phone screen unit.
@@nialltracey2599 that makes sense
wow this screen is tearable
Yeah I'll hOLED off from buying one.
Get out
You go to timeout and @jmsalzman You get out! Lol
clap clap ... CLAP CLAP CLAP CLAP CLAP CLAP CLAP
Tearing up over here! 😂
I have this and I love it. I saw the "tearing" when I ran it on pi zero but on pi 4 8 gig ram I haven't seen it at all. I am not using it for games or video though... I don't think it's an issue with the screen just a limitation of the pi. Recommending avoiding is a bit much. This is the best ever screen for rpi. Thé color is so beautiful and I love that I can see it in full sunlight
I'm thinking one of 3 things are happening here, 1- it has to do with the "works out of the box", it might need a firmware update or something like that. 2- the orientation change, in which case if you get no tearing in the original orientation, it might be solved with a firmware update for landscape, 3- the adapter might not be the greatest, try using a quality HDMi cable. other than that I'm out of ideas.
No. Videocore GPU is rotating the framebuffer by copying one buffer diagonally to another one which actually gets out of to an LCD. That's why it needs more memory allocated to the GPU, for this to work. Apparently a hack to get around some use cases and portrait monitors. I've used display_rotate=1 once when I rotated my LCD and got the same screen tearing. Maybe double buffering would get around it, but it'd have to be implemented in hardware. Synchronized to VSYNC. You can do memory copies on offscreen buffers, but the Videocore GPU evidently doesn't double buffer this video buffer transposition en.wikipedia.org/wiki/Transpose
I've had similar issues when using my GPD Win 2 on some Linux distros. The problem is not the screen itself, but rather the display drivers (is that what you call it?). I'm 100% certain that if you flip the resolution back to portrait mode and test the screen tearing again it would completely disappear.
I'm theorizing that this may be caused due to the developers not intending people to flip their resolution like that all too often, so they probably haven't focused on that feature too much. Though, I'm pretty sure knowing Linux that this issue would get fixed eventually.
TLDR:
The screen isn't the problem! It's just the display drivers that flipping the resolution that's causing all of this.
If the screen only had tearing on the pi, it's not the screens fault for tearing...
For real. I don't understand how one can reach that conclusion, you JUST showed that the issue it's not screen dependent.
Wait, it's only bad on the Pi? THEN I'LL BUY IT
I really hope ETA revisits the screen and explains what he did to get it working. Sounds like a really awesome screen, and the flaw seems like it has a solution (according to WaveShare).
This is an amazing screen, for linux folks, just remember to enable vsync, windows has it enable by deafault :D
Raspberry pi 5 has the best compatibility and resolutions/refresh I’ve seen in pi’s so far. Seriously crazy. Running a 13” AMOLED on a pi5 with recalbox and tons of N64, PSX, PS2, PSP, SNES, etc games.
It's probably been suggested already but I recommend using different power supplies for your display and raspberry pi. There could be some noise injected into the micro USB port on the raspberry pi. I figure it's worth a try considering you don't have to buy anything it takes like 5 seconds to plug it into a new power adapter. if this ends up fixing your issue than you might be able to get away with using a powered USB hub since most isolate their power and data lines.
You have a very pleasant voice and your English annunciation is very good. You speak very clearly. In all, it makes your content more enjoyable.
oh nice... now load up whatever OS/app for use in a car! :) I want to see ODBC2 diag and gauges and and some mp3 play
I know its a bit late to suggest but you should use wayland ond that display cause x11 has issues with vsync, double buffer everything...
I'll go with the video drivers causing the choppiness & screen tearing issues while using my Pi4 and this happens despite using an official power supply and a mini HDMI cable.
Run this:
sudo gedit /etc/environment
And add this to the file and save:
CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True
This is really the kind of content I come here for. You win some you lose some. Hopefully the company comes up with a solution for you and you can let us know.
"But don't buy it!" Aw man, there goes my dreams of a dual 5.5" touch screen Nintendo DS emulator
It might be that little cheap ribbon cable that goes between the raspberry pi and the screen maybe it can't hold enough bandwidth.
The ribbon cable is from another screen. The AMOLED one is connected via the small HDMI-adapter ..
Please make a follow up on this with some TS done in the video. I feel like this should be something that can be resolved with some more TS. If the 4 can push 4K there's no logical reason it can't push this, probably a config/driver issue or maybe a faulty HDMI bridge since it clearly works from PC. I think I may buy one of these next week just to test this theory out myself if we don't hear back from you. This seems like it's an easy enough fix though if we can run through some tests
The Raspberry Pis as of late have strange VSync issues just in general, it just doesn't show up as badly on lower end displays. jamesh, one of the engineers on the Raspberry forums even said as much. Just personally, I think it's a cooling issue, the core is thermally throttling under any real load.
These are GREAT for modding a display into the front of PC cases for temp/ performance software display. Look great on a SFF case!!
"This screen is $130."
Ha ha, no.
"And it has awful screen tearing."
Heeeeeell no.
Jess Ragan $130 for a display that will last for 2-3 years also. I'm not a big fan of OLEDs because of burn-in problem and fullscreen flicker which makes your eyes bleed.
@@shadowflash705 OLEDs can easily last much longer than that lol, I'm still playing my early release edition Vita with an OLED screen and that thing is like 8 years old with no burn in. These are much newer more advanced OLEDs so you should easily get that much out of these, these are literally phone screens and those do static images like crazy. Sounds more like you problems than screen problems
@@shadowflash705 completely depends what you do on it
@@shadowflash705 bullshit - says my nexus6 from 2014
Ameoled is great especially if shatterproof but dims over time especially with high brightness and white background objects.. and prone to screen burn or pixel lines
maybe this is someghing that they can fix with a firmware upgrade of the screen controller .... o the way to hook the Pi .... what do you think ? At the end is an 1080p AMOLED maybe used often into the smarphone market .... and of course no one is facing problems like the ones shown.
That is actually the raspberry pie's fault, not the display.
I mean seriously, problems only occour when used with the raspy
It cannot be more obvios
But yet here we are, with everyone thinking the display is bsd somehow
Trust me and lower the res
Then your problems will be gone
@@icebread9335 Peace, mate, I didn't want to hurt anyone's feelings. Accordig to the video I understood that this behaviour culd be blamed on the display. Frankly speaking I don't care wich is the side to fix, when the systems works properly at 1080p. Is it on the Pi ? Good to know, let's hope that they can provide a solution soon.
Apart from the issue that you're experiencing its a very cool screen. I didn't even think companies were doing stuff like this. I can think of some awesome applications for this.
Please,what applications?gr
Thanks for the useful info! That's why you have 389k subscribers. Because of your honest reviews
Try adding "extra_transpose_buffer=2" or "extra_transpose_buffer=1" to the config.txt
this code line is fixed the problem !!
Id say its unfair to blame it on the screen, as you said it works fine in windows... That means the Pi isnt pumping out the frames correctly.. Thats a software fault in the Pi not the screen.
Thats exactly what I reckon also, the pi dont have the power captain...
You clearly messed something up in the config file...this is clearly a software bug
no its clearly a limitation of crappy raspberry pi units
@@Synthematix except its only on the pi 3 & 4
Works fine with movies up to 2k....world of Warcraft played fine..super clear...no issues
Little late watching this, but had you recommended this, I most likely would have bought one. Thanks for your honest assesment. Love my Odroid Advance Go, by the way. It looks great in yellow with the paint you recommended.
Its not a display problem, but a Pi one, I have the same problem different screen. There are even cases of this on TVs, with no fix, stay away from a Pi.
in the browser you should enable hardware acceleration
and in the games you should enable vsync
*Scren tearing only occours when your device falls out of sync with the display*
this happens when your device cant keep up, or is faster than the current refresh rate.
In this case you arw using a way to weak pc-the raspberry pie.
You can work arround this with using a lower Resolutionen
Or stronger Hardware... I only know theese two
Frankly, there's no need to get a whole new display. You can get adapters to make old Pi 3 screens (ones that plug into the GPIO for power and touch interface, at least) work with a Pi4 on eBay for very cheap. I was experimenting with a Pi 4 handheld a while back(abandoned it for the Odroid Go Advance) and it was rather easy once I had the adapter - the drivers would not auto-install, but plugging it into a TV and following the instructions to install them via terminal it worked fine.
I STRONGLY recommend you get such an adapter and test with the displays you already have.
Try changing the refresh rate and resolutions of this display. Different resolutions with refresh rates might produce different results with raspberry pi.
Damn and that screen was looking really good too. Maybe not for that price, but for the size and quality. Hopefully the screen tearing can be solved with a screen-firmware or raspberry pi update.
Thanks for the warning. According to the comments, it might be a configuration issue causing the tearing. A follow-up response video would be worth my time watching.
I've just subscribed, and am hoping we're both still here to care this much about frivolities in the near future.
@ETAPRIME Perhaps separating the Pi from the screen (interference due to proximity?) and swapping their adapters (the Full-HDMI to uHDMI and the USB connector) for quality cables (plugging the USB-to-uUSB into one of the 2.0 ports) you've tested with on the pi with other devices. My only other idea is to make sure your drivers are up to date and that Vsync is enabled.
Like many people have recommended, make sure you try a good HDMI to HDMI cable from the pi4 to screen before writing it off. Those home made adapters they come with can be total crap sometimes.
so did you ever get it to work, that display would be perfect for the Pi, I took note of a few suggestions so many made about the screen tearing
There are on mac custom resolution program that you can try the screen in many resolutions and sync mods. I also think that Rasp pi drive that screen at 24 Hz instead of 60Hz is something there in mapping Hz in the video.
Could you try to make a handheld with this screen and maybe a small compute stick Windows based machine? That would be different and amazing to see. Almost like the Alienware handheld? That would be sexy AF to see
Did it happen before you rotated the display? If not, it's a raspberry pi issue, not an issue with the screen.
Screen tearing not an issue for me, great video.
If this works fine with a PC and not the Pi, the problem is either a bad cable or Pi's video drivers.
There are timings specified in Waveshare Wiki, have you tried those ?
In the description, you misspelled definitely, but the video is still great.
Lol
Damn basically an older flagship cellphone screen, for not much more, you could get the whole phone lol
😂
I'm still using my Coolpad legacy setup with a Lynx 9 controller, and couldn't be happier as far as portable retro emulation. I wouldn't have looked twice at the Coolpad, but ETAs review convinced me. Thanks!
I know I'm very late to the party but try running it again with a hdmi cable instead of the included adapters. I've been doing a bit of self research into pcb adapters and realistically speaking the included HDMI adapter is not large enough or designed well enough to be able to carry the signal.
Hey @ETA Prime, can you please try this: Switch the screen back to vertical mode then seeing if you can run MAME games (vertically) at normal speed. I found in the past that when you flip the screen into vertical mode, it causes Retropie games to slow down. If the makers intended on the screen to only display vertically, then this screen would be a great option for a Coleco tabletop arcade build i'm doing.
Open the NViidia Control Panel on a windows system, go i to the builtin Custom Resolution Utility, and copy the values in that to get your display settings. That should solve any configuration issues.
ya because that's Windows running on an Nvidia GPU
@@blaziken1564 Display resolution and timing works the same on linux or windows, ARM or x86. the tearing is either caused by horrid timing or a bad cable, so being able to copy timing values from a system where they work and mirror them to a system where what it's using doesn't work, would cross off one of the two possibilities. If the tearing is still bad then something to replace the daughterboard-style cable that came with the kit is in order.
The tearing is more noticeable might due to its an 1080 x 1920 resolution, not a 1920 x 1080 resolution.
The refresh direction is sideways might make the tearing more noticeable.
Screen tearing using an adapter? Color me SHOCKED! ;)
Nice Jon!!!
Saludps from San Jose del Cabo
Hi, ETA Prime,
I got the TV HAT and I'm using it on a RPi 4. Got some recommendations what display I should choose? The official one is too expensive plus a protective case costs extra so it's a even bigger turn off..
Would prefer a display with touch so that I can easily use my RPi 4 as a mobile mini TV.
Could I suggest that you try to use a shielded cable instead of the included adaptor? It may help
It sucks that such a nice looking screen would run so badly. Thanks for letting us know about that.
ETA, can you recommend a TH-camr or other modder who is modding these boards into full devices? I'm really curious to see that kind of work.
Future video suggestion. Peloton old monitor/tablet. See if u can get anything running on them. They are selling on eBay for 50-100$. People got android 4.1
6H hardness just means tempered glass, it basically means (like JerryRigEverything always says when using Moh's hardness test) scratches at level 6 with some deeper grooves at a level 7.
Whatever is causing tearing is software related. Something is not v-syncing. Most probably the rotate of xrandr. Check there.
(I'd say, blaming this to the screen is a little too much, the screen has nothing to do with it, it's a diplay driver issue)
in the screen tearing test you should put the speed at 2x due to the test is at 30fps in a 60fps capsule
It doesnt really matter because 60 is a multiple of 30. The screen will just refresh twice before actually updating the image
Not having variable refresh or the ability to run the screen at slower speeds than its refresh is not the issue. The issue with this device is with the touchscreen the image processor cant actually handle the task of keeping things synced properly and not have screen tearing. This is a real issue its why a flawless screen with touch tends to be expensive. the image processor needs to be 3 times as powerful being more like a coprocessor than a simple chip for putting the image on the screen from the digital signal being sent to it. This is why gsynk freesynk and variable refresh tech is still something that billions in r&d is spent on it.
@@theoneyoudontsee8315 thanks for the helpful information !
@@theoneyoudontsee8315 Would this mean, that if one just leaves out the touchscreen capability, it might perform better?
@@Kumimono if you just disconnect the touch screen part it just wont work thats how this screen gets its power via usb so no because its not engineered to be optional on this screen witch also means disabling it in software wont work. This is why i dont like always on display because the touch is always on scanning for touch using power and running on the cpu/soc on my galaxy S9 for saving power on long trips. Most touchscreens are made in such a way to be thin and not take up much space so the screen and touch layers are just too much a part of each other and share the one processing chip and as far as i know that cant be changed because its also one of the things they do to eliminate internal latency to combat screen tearing to have one chip for the screen and touch. All this means is you just cant go too cheep or buy just a screen and hope there even made in the resolution youre looking for with the screen panel technology you want.
#Nice to see an honest review. Honestly I've had several - and even if it did work - when looking at the command line on a screen that size - one is asking for eyestrain... if they were a tenner yes but 19" monitors are dirt cheap..
Sounds more like a Raspbian/DesktopEnvironment issue to me. Did you test the same configuration on other HDMI displays (e.g. a tv)?
VSync in linux isn't always that easy to do depending on the used software.
Excellent video as always.
Question: Have tried other OS to see if it will work better?
Yeah I wanted to re-emphasize for people that this is *not* a display issue. It is a 100% rPI issue. So while the "takeaway" might be correct, it should be amended to more like "For use as a horizontal display"...because the panel is natively vertical, likely made for a phone.
Maybe it's the connectors they included, have you tried connectivity with a normal HDMI cable to the pi?
Do the screen issues exist when not rotated via the pi?
Rotation to 90 or 270 through the pi directly causes performance issues. If the screen is better without rotation you can grab the dev branch of EmulationStation and have it rotate on start.
Hii ETA
Plesae a video guide for final burn alpha using on retro handhelds. Adding correct rom ect.
I like how he skips hearting the comments saying its probably the hdmi cable or driver issues
Have you tried any other os? Is it only issue for raspberry pi os?
Knowing Waveshare they'll prolly release a patch for that soon(ish) if it isn't a hardware / cable problem.
I take you have looked at their wiki and the "3.2 Working with Raspberry Pi" section for this display?
They seem to set /list some specific timings in there.
Sounds more like a Pi issue rather than a screen issue if it works fine with other devices. But i see your point.
That's why he said specifically if you are buying it for a pi build he doesn't recommend it.
@@Geion yeah, that's why I said I see his point. It is a nice screen, though.
It hardly matters when the guys selling it are selling it specifically to Raspberry Pi users. If you sell it as compatible, you can't blame the incompatibility on the other party.
@@nialltracey2599 It IS compatible, though. I'm just saying the screen does in fact work with the Pi even with the screen tear. And if it does not have tearing with other devices, then maybe the Pi is the culprit. maybe a fixable issue through a gpu update or something.
@@ramzagtzo As others have pointed out, the problem comes from using display_rotate to get a normal landscape layout. Which *could* have been avoided by having the controller board set to landscape, but this is a quick, cheap mod of a mobile phone screen unit, and while the specs do describe it as portrait (1080x1920), the only images of it in actual use on their site show it in landscape mode, which is misleading if it only functions correctly in portrait mode.
I’m at a loss. When the screen is connected to a computer, it behaves as expected. When connected to a pi, there is screen tearing. How is this a problem with the screen? We know the screen works, we proved it by connecting it to something that works, and we don’t have the problem. What isn’t pushing the screen is the pi. Either the hardware is failing (including the adapters), the configuration is failing, or the driver is failing... on the pi.
Are there any options to use a Wayland backend? It could help screen tearing. It could well be a hassle setting up, Gnome might be too heavy for the Pi. Which probably makes Sway the best option, or maybe Enlightenment. Not sure how easy that would be to install over Raspbian, maybe go with something like Arch (hence the possible hassle).
I feel like you can get it working. Good luck!
Genuinely interested to know whether this would be a viable OLED upgrade for the zswitch Lite? Dames size and resolution, it’s whether the pins match up or what mods would be needed to get it to work…
What a bummer! This would have been perfect for a replacement display for my OpenAuto Pro setup
I was thinking the same. An oled screen in a car pc would be fantastic.
@@meestahwah Just buy a used smartphone or tablet with OLED display and you will get display and the whole rest for a lower price.
It can depend on how you turned the screen 90 degrees?
It isn't shown, not as a link or in the video how you did it, so it is hard to suggest what is the problem. It looks to me like it still is rendering in standing mode, even if the output is turned 90 degrees.
Try to connect to a PC, and render the test video 90 degree turned like the RPi.
I guess that could be the problem, but need to test to see if that is the case.
check the refreshrate - i had one (i used for windows), it had ugly tearing @60Hz - but was fine @59Hz (which was automatically set when connected)
Thanks for the conclusion at the title :)
Have you tried shielding the back of the display from the raspberry pi's? Might be an interference issue.
Do you have a MiSTer? I'd be interested to see if it works well with that device since it focuses so much on low latency and cycle accuracy.
ETA Prime you should try that with a Mister
Do the screen tearing test in portrait mode, if you don't see the issue you can narrow it down from there.
Have you tried tearing test in portrait mode? if it only happens in landscape mode, you could try run it in portrait mode then use rotate in retroarch.
He did and its the same.
I would love to know if you are still having problems with this screen three years later or if they have corrected these issues in software
Did you assign more memory to the VRAM?
@ETA Prime, have you checked if you have HW accel in Chromium? I'm 100% sure it's not hardware, but rather a software issue on your end.
If the comments below by other viewers fixed the problem I hope you make an update video. It seems to me since HDMI has several data pairs these displays could be designed to use the HDMI instead of a USB connection for touch screen capabilities.
You are rotating the screen in software. The raspi is not fast enough to decode videos or play games while rotating the screen.
Those phone screens should come with a rotator chip on the pcb, so that the device sending the image doesn't need to do the work.
Thanks for sharing !
How do you test it out with any other different raspberry pies