@mitu ok sorry

Can you please add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ? How are you trying to wake up the system - keyboard, controller, etc ? If you're running a screensaver, consider disabling the power saving option in ES. For the audio part, try adding audio_pwm_mode=2 to your /boot/config.txt and see if it improves the sound cutting part.

@goobatroopa gles2n64 saves the day. Thank you very much for your assistance @quicksilver

@retromikey6 we don't support 3rd party images, especially the ones with Roms included. Please remove the link to the image.

@herb_fargus That's what I was thinking.. an overclock that won't run on his pi, since every pi is different. Or using different controllers with a driver enabled that is interfering with the controller he is using. @TommyEllas What controllers are you and your friend using ?

I have similar problem. I thought its my adapter to the monitor. I use a dongle for keyboard too. What was the interval when you got this screen freeze? I get it maybe once in a hour. Maybe its a different story on my side.

@mitu I have it disabled, but it freezes too seconds after a game is launched, all I need is a way to auto update runcommand core on any startup.

@jacek We don't support 3rd party images - https://retropie.org.uk/forum/topic/3/read-this-first. You're free to try the RetroPie image from https://retropie.org.uk/download and report back if you can reproduce the problem.

@rthorntn Switch the RetroArch video driver to sdl2 or try logging in with a Wayland enabled session. See https://retropie.org.uk/forum/topic/17679/black-screen-only-audio-on-launching-roms https://retropie.org.uk/forum/topic/17579/libretro-not-yet-ready-for-ubuntu-18-04

@wihaedud I have this exact same issue. However the fix doesn't work for me. The bluetooth disconnects after 5 seconds as it should but then never connects back to the pie and wont until the pie is rebooted. Any ideas or anything I can check using ssh to ensure the bluetooth service has restarted?? I am a bit of Linux noob but can find my way around a putty window :)

@pjft sorry I didnt know i really wanted some help thank you

Try the official image from the RetroPie website. Custom images are not supported here. If you have an issue with the official image we'll be glad to help. If you're using one from another source, contact who created that image for assistance.

Forgot to mention, both partitions are formatted in ext4 format. Not sure if that info was need lol but noticed i had not added it. Cheers

@lostless was simply just bad rips. Thanks

Hi @cineraphael I would suggest you start a support request by completing the information requested in https://retropie.org.uk/forum/topic/3/read-this-first as you will be requested for this information anyway. If you are overclocking your Pi, you need to let us know what you are doing. Maybe start by uploading your /boot/config.txt to pastebin. Also, how are you cooling your Pi?

kodi-peripheral-joystick kodi-inputstream-adaptive kodi-inputstream-rtmp already in unstable ppa for zesty 17.04 https://launchpad.net/~team-xbmc/+archive/ubuntu/unstable/+index?batch=75&memo=75&start=7599

Thanks for the info, I did a search but no solutions to my problem.

@dankcushions said in Zero: Exit a game, system freezes, screen is dim, can't SSH in...: the reason for adding over_voltage is to INCREASE stability; higher clocks demand more power. however it also raises temps... for shader performance i would have thought only GPU and maybe memory performance overclocks are relevant. I tried some new settings last night, and ran it for a good solid 20 minutes switching from game to game like I was doing before (where I could ALWAYS get it to freeze at some point) – and it seemed to be good. Think I dropped each "recommended overclock" number by 25 (475, 475, 475), AND changed the two voltages to 3. Think temp was still around 60º which is normal while you're using it I believe. I will test it even more tonight (including writing down the FPS numbers to see how they compare to the full 500 overclock - I think SNES was still down to like 54-57 instead of 60 FPS...which would be fine as long as it doesn't crash). CRT-Pi Shader performance I gave up on for SNES and Genesis to be honest. It's just too much on the pi Zero even with the full overclock to get to that magic 60 FPS. I'm trying to keep CRT-Pi for NES (as it helps 8-bit look better to a much greater degree than 16-bit IMO), but will have to see if I get any of the weird pausing which plagued the non-overclocked Pi Zero with lr-quicknes + CRT-Pi.