I have my Raspberry Pi 2 setup with Rasplex. Works a champ, it was very easy to do with the installer and I can’t believe this tiny little device can be a PHT client. Kudos to all involved in making it happen.
I do have a small issue.
I am running the Rasp Pi 2, overclocked with the following settings:
I have a 2.5A power supply and a SanDisk Class 10 8GB MicrosSD.
I am hardwired to my network, connected with HDMi to a Vizio P-Series (P602ui-B3).
I have the CEC Adapter in Preferences>>System>>Input Devices>>Peripherals disabled.
If I leave the TV input selection on the Pi when I turn off the TV then turn it back on, I get artifacts on the screen. The best way to describe is that they look like little aqua pixels. They are usually as ghosts on the screen, for instance a number 1 might have them ghosted to the left of the 1.
If I change input to regular TV and then back it usually clears up. If I go into one of the apps (Netflix, etc) while on the RasPlex input then exit out they show up.
Eventually the Pi locks up and I have to unplug and replug. Not sure if it is the overclocking or something else.
Anyone seen this or have any ideas for what it might be?
Thanks for any help.
This may be due to the make of TV, I haven’t seen this mentioned before as far as I can remember, I use only Sony TV’s and don’t get the problem. Not sure why the RPi is locking up, can you enable debug, restart the RPi then try to reproduce the locking up and then post the log file.
In the next release there have been some improvements made to rendering, but not sure whether this is your problem. Try enabling CEC, even if not using it it may prompt the TV to behave correctly, just uncheck most of the options, I don’t use CEC either but leave it turned on.
If you mean the rainbow pixels on the top right, your PSU or cable is not supplying enough current, despite the rating. Second the removing of the overclocking on the RPi2, that won’t help the power issues which usually are responsible for random crashes.
No, it looks nothing like that. I will post a picture of what I see in the next couple of days.
Removing the overclocking seems to have solved the lockups, but the ghost pixels remain.
I’ve seen this similar behaviour once when I was messing around with config.txt values. This was however on Kodi, though of course the config.txt is not specific to RasPlex or any other OS. Aside from the overclock have you made any changes to /flash/config.txt recently?
@jamesmacwhite - None whatsoever. The only changes I made were for over clocking then to go back in and comment them out.
It was doing it before commenting it out and still doing it after.
I will get a better HDM<I cab le and try that.
@rsava said: @jamesmacwhite - None whatsoever. The only changes I made were for over clocking then to go back in and comment them out.
It was doing it before commenting it out and still doing it after.
I will get a better HDM<I cab le and try that.
Fair enough. As NedtheNerd has said, I’d focus on the hardware at this point.
Try swapping the HDMI cable
Try a different HDMI port (if your TV has more than one)
Try using another TV with a HDMI port (if possible)
Try a different Raspberry Pi board (if you have a spare)
It seems very likely its hardware related at this point.
Just realized I never came back here to follow-up.
Looks like it was a bad HDMI port on the TV. Not sure what could have caused it, but it eventually stopped working and when I switched the Pi to another port it appears to be working properly now.
@rsava:
Please change the ‘Accepted answer’ marking of this thread so that it shows an ‘answer’ post that mentions the issue being solved. Currently the text of the post shown as ‘answer’ gives no indication of this.
@dlanor - I would love to but I cannot choose my own answer as being an answer and @NedtheNerd’s answers are the only ones that give me that optio (posts 2, 3, and 12 only).
The one I chose was the closest that was allowed to be marked as such.
(Yours show up as being able to be marked as an answer also.)
