Update: Mi Box Flickering Workaround.

by Roseysdaddy

Here is my origninal post which you guys were kind enough to downvote to zero.

Anyway, what I've found is that if I boot the mi box while another input is selected and active on the receiver, and then go back to the mi box after it's fully booted, the glitching issue resolves itself. If I however boot the mi box and watch it boot on the screen, the shitty glitching returns. Something must be going on in the handshaking while the box is booting to cause this issue. Hope this helps someone out.

realslizzard

Check the cable or the video settings. Sounds like it's trying to push an incompatible signal or the cable is no good

Coldpho

I returned mine for this issue and HBO go incompatibility. Finding a workaround like you did is great - kudos to you. However, it should not be necessary and the product should simply work. Their support team is a joke and told me to reach out to Wal-Mart for technical support. Only online chat tech support; no one to take phone calls. If Xiaomi wants to succeed in the US market, they're going to have to adapt to the US consumer....I was really looking forward to this product and was greatly disappointed

dcdevito

I tried 3 Mi Boxes and all had issues streaming videos via Google Cast. 4K, 1080p, 720p videos all had audio and video sync issues. 4K and 1080p were so bad the video would play in slow motion. I returned it, and tried two other boxes, all had the same issue.

I have a Vizio 55" 4K TV. It's so disappointing, the Mi Box worked well otherwise. I installed the firmware update on each also, but did not fix the issue. Hopefully it gets fixed soon.

go_cam

Hi - So after playing with this infuriating box for a couple of days, here is what I have found.

It seems like the handshaking and the signal the mi box is putting out are just not up to spec. It is not clear to me whether this is fixable with some sort of firmware update, but I experienced the jumpiness, the HBO Go stopping after some time, random jitters etc etc. For me this was occurring with the Mi Box connected directly via HDMI to my Yamaha soundbar (which passes it's HDMI output to my Vizio TV - this works for every single other device I use - Roku, Chromecast, Blu Ray player, Dish DVR etc).

So - as an experiment, I connected the HDMI out directly to my Tv. After the obligatory reboot, guess what, the jitters, the jumpiness, the non standard frame rates and the HBO Go stalling went away completely. Great ! (I thought). Now my problem was just one of getting audio into my receiver so I could hear something. So I take the SPDIF out of the Mi, directly into my Amp, reboot again, and lo and behold out comes the audio to match the now non-jumpy picture. But ! The optical audio out is only stereo regardless of the signal I feed, so there goes that idea of a workaround. Sigh.

This box has so much raw potential but the implementation is just bananas. Shaky handshake - check ! Date & Time that sometimes don't stick - check ! Optical out that can't send surround signal - check ! A terrible 24p implementation that plain doesn't work (for me). Decoding of only a small number of formats (e.g. Vudu does not send surround, but Netflix does) Etc etc.

I am torn between taking it straight back, or waiting to see if any updates are forthcoming - my intention was to rid myself of the Chromecast, Roku and Dish and replace with a single ATV unit. Alas, that is not possible in its current state.

Another piece of info for anyone interested in cutting the cord and going all Android TV (or some other streaming variant) - the cable-like services such as Vue and Sling TV do not output/decode anything other than 2 channel stereo, so forget using them to supply surround to your decoder/amp - stereo it is, and of course your unit can invent the surround, but if you are e.g. watching some surround show on either, you will not be able to receive the broadcast surround you would get from DTV or Dish. Ug.

I don't know if others here have experience of the Shield TV - I suspect the handshake it supplies works fine, that it decodes audio correctly etc so I may give it a try.

hooha23

I returned mine for the same reason. Now I wonder if your work around would have worked with my Pioneer receiver.

Thinking about picking another one up and seeing if 7.1.1 fixed it. Anyone try that yet? Or another receiver?