• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Flickering screen on Pi Zero W

Scheduled Pinned Locked Moved Help and Support
hdmi problemflickerzeronewbie question
8 Posts 3 Posters 6.1k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C
    chubsta
    last edited by 2 Mar 2017, 02:09

    I am very new to this, having bought my first Pi last week so may be missing something obvious...

    anyway, got one of the new Pi Zero W today and did my first proper 'install' - i tried using a readymade image but that didn't work so installed a Raspbian Jesse Lite and installed RP over the top - bit of a faff as i didn't know how to setup the wifi etc, but got there in the end!

    Trouble is, right from the start i have suffered from the screen constantly blanking out or flickering, seemingly whenever the pi is trying to do something. After much research i have changed the config file to boost the hdmi (up to 11!) and it seems to have made a slight difference but it is still unusable. The problem still occurs even when nothing is plugged into the usb socket, and plugging either a joypad or keyboard in does not change the frequency of the dropouts.

    I am using the same power supply i was using with my Pi3 and had no problems with that at all so don't think that is the issue - unfortunately my multi-meter is broken so cant check voltages on the pi itself.

    Given that i thought the zero had lower power-supply demands than the 3 i would be very surprised if that is the issue so any and all advice would be appreciated!

    Raspberry Pi 400 - overclocked to 2.3GHz
    Theme - Comic book
    Emulators: All of them...
    Roms: Pretty much all of them...
    Favourite games: Circus Charlie, Gorf, Gauntlet Legends
    Controllers: Mayflash F101

    1 Reply Last reply Reply Quote 0
    • O
      obsidianspider
      last edited by 2 Mar 2017, 03:30

      What kind of HDMI cable connection are you using? An adapter with a cable plugged into it? What resolution is the TV? You shouldn't have to do anything funky with at Zero to get it to work with HDMI, but I don't have a Zero W. (yet)

      📷 @obsidianspider

      1 Reply Last reply Reply Quote 0
      • C
        chubsta
        last edited by 2 Mar 2017, 09:45

        it is the same hdmi that i use with the Pi3, but this time plugged in via an adapter (I have ordered a hdmi-minihdmi cable which should hopefully be here in a couple of days.

        The tv resolution is 1920x1080p (it upscales to 4k i think as it is a new 65" job) - i will try on my old 1920x1080p tv later today hopefully.

        Raspberry Pi 400 - overclocked to 2.3GHz
        Theme - Comic book
        Emulators: All of them...
        Roms: Pretty much all of them...
        Favourite games: Circus Charlie, Gorf, Gauntlet Legends
        Controllers: Mayflash F101

        O 1 Reply Last reply 2 Mar 2017, 12:16 Reply Quote 1
        • O
          obsidianspider @chubsta
          last edited by 2 Mar 2017, 12:16

          @chubsta If I recall correctly the Zero will try to output 640x480 (even over HDMI) by default. I had that issue with mine, now that I'm thinking back. I'm looking through my notes to see how I addressed that and will post back.

          📷 @obsidianspider

          1 Reply Last reply Reply Quote 1
          • C
            chubsta
            last edited by 3 Mar 2017, 00:56

            Small update - by enabling hdmi_safe=1 in config.txt I get a stable image on the TV, but of course the resolution is very poor.

            i guess from this it means the power supply can be ruled out as a problem, and i would also guess the hdmi cable is ok too as it is one i have removed from my PS4 which displays 1080p no problem...

            Raspberry Pi 400 - overclocked to 2.3GHz
            Theme - Comic book
            Emulators: All of them...
            Roms: Pretty much all of them...
            Favourite games: Circus Charlie, Gorf, Gauntlet Legends
            Controllers: Mayflash F101

            1 Reply Last reply Reply Quote 0
            • O
              obsidianspider
              last edited by obsidianspider 3 Mar 2017, 12:03 3 Mar 2017, 12:02

              I found a link that talks about manually setting 1080p.

              hdmi_force_hotplug=1
              hdmi_drive=1
              hdmi_mode=16
              disable_overscan=1
              

              hdmi_mode=16 is 1080p. What I'm not sure of is how it would handle being plugged into a 720p screen, but if that's not a concern, then you should be ok.

              Here's a link with all sorts of settings that can be put in config.txt and their meanings.

              📷 @obsidianspider

              1 Reply Last reply Reply Quote 1
              • C
                chubsta
                last edited by 5 Mar 2017, 10:05

                Well, I wont say this is solved but it is not a problem anymore - I connected the Pi0 to a different tv (51" 1080p) and it works fine, there is no flickering at all, fortunately for me this is the tv that the Pi will be connected to permanently, i was only using the other TV as it was more convenient when setting stuff up!

                I guess there is the possibility that the original TV, being 4k, may have been trying to upscale the Pi signal, causing the flickering? Anyone any experience or knowledge of this?

                Raspberry Pi 400 - overclocked to 2.3GHz
                Theme - Comic book
                Emulators: All of them...
                Roms: Pretty much all of them...
                Favourite games: Circus Charlie, Gorf, Gauntlet Legends
                Controllers: Mayflash F101

                1 Reply Last reply Reply Quote 0
                • T
                  Tina
                  last edited by 9 Jun 2019, 13:47

                  Hi, I had a similar problem. It appears I have solved it by forcing the monitor to use HDMI input in the settings as opposed to autodetect. Hope this helps people encountering this issue in the future ;D
                  Cheers,
                  Tina^^

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post

                  Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                  Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                    This community forum collects and processes your personal information.
                    consent.not_received