Posts: 5
Threads: 1
Joined: Feb 2018
Reputation:
0
02-23-2018, 11:50 AM
(This post was last modified: 02-23-2018, 11:51 AM by ncv.
Edit Reason: Added game details
)
Hello! I just built a Freeplay Zero. When I play any game for 20-30 minutes, the screen inevitably turns white, even though I still hear sound and buttons still work. Exiting the game does not fix the screen, only powering off does (the screen will still be white during the shutoff script, but not after the system reboots).
Things I've tried:
- Resoldering the LCD-related GPIO pins
- Reconnecting the LCD display
- Adding a heatsink
- Disabling onboard wifi & bluetooth
Has anybody else had this problem? Is there something else I can try? Thanks!
EDIT: This happens with multiple games for multiple systems, including both 8 and 16 bit systems
Posts: 1,610
Threads: 19
Joined: Feb 2012
Reputation:
29
This is a weird one that I haven't heard before, so let me get it straight (please correct me if I'm wrong)...
1) You play for 20-30min.
2) The screen goes pure white (like when you're first turning on the Freeplay Zero).
3) You turn the Freeplay Zero off.
4) You instantly turn the Freeplay Zero back on, and then it works just fine for another 20min or so???
If so, I really don't think it's a software problem. You are right to resolder, as that could cause this problem. The fact that it works for a while does seem to suggest heat, but I don't know if I believe that it would be.
Are you 100% sure that your LCD ribbon cable is fully locked into place?
This could be an issue with the LCD itself.
Have you tried to boot the machine up and just leave it for an hour or so (untouched)? Does it go white then?
Posts: 5
Threads: 1
Joined: Feb 2018
Reputation:
0
Yup, that's correct.
I tried a new Pi Zero this afternoon, and reconnected the ribbon cable again. Then, I booted it up into a GBA game and left it untouched for a while. It white-screened on it's own, still heard the sound and everything as usual
Posts: 5
Threads: 1
Joined: Feb 2018
Reputation:
0
Hmm, it definitely seems heat related. It happened once, I rebooted immediately, and it happened again in roughly ~10 minutes (much faster than usual).
Posts: 5
Threads: 1
Joined: Feb 2018
Reputation:
0
Amazing, thank you! I'll open a ticket tomorrow, have a good weekend
Posts: 5
Threads: 1
Joined: Feb 2018
Reputation:
0
Nope, no overclocking. The only boot/config.txt modification I've made is disabling wifi and bluetooth.