Hi everyone.

The remote of my Shield TV Pro 2019 has started acting up recently and I wonder if any of you have experienced this before and maybe have any advice.

About 1 week or so ago the remote was not so responsive; I had to wait for like 10-15 seconds after the system is on and press the buttons a few times before there as any response. I changed the batteries thinking they were dying. Initially it was ok as the remote seemed normal again.

But since a few days ago the remote does not respond after I get into the home menu. I normally just put the Shield to sleep and then turn off the power supply. When I go to the remote menu of Shield (using my TV remote), the Shield remote is shown as "Not Connected". It does not get connected even if I wait for 10 or 15 minutes and by pressing various buttons on it.

Then I discovered by chance that if I remove 1 of the batteries (can be either of them) and put it back, the remote is almost instantly connected to the main unit and will continue to work like normal, but the same problem comes back after I restart the Shield. The connecting springs inside the remote look to be in good condition (no damage or oxidation). I have never dropped the remote.

I have tried the following methods and all did not help :-

(a) clear the cache and data in Bluetooth app;
(b) forget the pairing and re-pair the remote;
© reset the remote; and
(d) unplug the power plug and plug back after 10-15 seconds.

Would appreciate any advice. Thanks in advance!

I bought from a local seller on Shopee. So don't think can claim warranty through Nvidia. Anyway, I submitted the issue to Nvidia and it has asked for my info and proof of purchase. See how it goes. Disappointing that it is already faulty after less than 1 year (never dropped and not heavily used).

To my pleasant surprise, NVidia came back offering to send me a replacement unit BUT (a) it can only send to either the US, UK or Singapore and (b) I have to return my current unit to its warehouse first, the closest of which from Malaysia is in Hong Kong. So all in I guess the costs of transport would probably be enough for me to buy a new one from Shopee (with 12 months warranty to boot). So not taking that option.

Based on other feedback here, I am currently using the USB port in Compatibility mode (I have a USB Hub and a portable HD plugged in) and the remote seems to be working well for the past 3-4 days. So that seems to have resolve the problem. The strange thing I have had the portable HD plugged in since a few months ago and the USB Hub since 1 to 1.5 months ago, but the remote control only started to act up about 2 weeks ago.

Thanks for all the feedback!

Thanks so much, @MU Variant and @juzmafia.

I am currently using the USB port in Compatibility mode (I have a USB Hub and a portable HD plugged in) and the remote seems to be working well for the past 3-4 days. So that seems to have resolved the problem. The strange thing I have had the portable HD plugged in since a few months ago and the USB Hub since 1 to 1.5 months ago, but the remote control only started to act up about 2 weeks ago.

I spoke too soon! Right after my last posts here, my remote control started acting up again with the same problem. So it looks like it is a faulty remote control after all.

Rather disappointed with NVidea that the remote control becomes faulty so fast, without having been dropped. So don't think I want to take the risk of buying another one; for that price I would want it to last a few years and I am worried it may not.

So will continue using this one till I can't stand the work-around method of making the remote control connects to the unit. I mentioned taking out a battery and putting it back works; I discovered by chance that another work-around method is to repair by pressing and holding for a few seconds the Home + Back buttons until the backlight blinks.

You were right after all - it has nothing to do with the USB port. As mentioned in my above post to @jhleo1, right after my last posts here, my remote control started acting up again (2 days in a row now) with the same problem. So it looks like it is a faulty remote control after all.

Hopefully NVidea will come up with better quality remote control for its new version of the Shield.

Hi guys. I know this is a thread on Shield TV (which I have and have no issue with, except for the faulty remote control after less than a year) but I hope u guys can help me out on my MeCool KM3 android box.

It seems that the KM3 doesn't not support Dolby Vision? When I tried playing a DV (4k as well) movie
on Disney+Hotstar thru the KM3 with DV enabled in the Settings of KM3, the file won't play (the rotating sign will go on and on). When I turned off DV, all the DV movies on D+H would play but the colours are messed up. Pls see the attached 2 photos (Jungle Cruise).

When I play a 4K movie without DV on D+H, the colours are normal. Pls see the attached photo (Cruella).

Any idea if this issue is purely because the KM3 doesn't support DV? If do, any way to overcome it?

If that is the case and there is no way around the problem, any suggestions of a good (above entry level) android box which supports DV, HDR10, etc? Worst case I guess will get another Shield, but thinking or trying out something else.

Thanks in advance!


Attached thumbnail(s)

@juzmafia TQVM!

Hi everyone. Hope you all are keeping well.

Just an update on this which I thought I should share so that others who face the same problem with the remote control may want to try this : since the problem with my remote started I also noticed that it drained the batteries very fast [at the rate of almost every week I would get a warning from the system saying that my batteries were low despite having used them (brand new) for about a week only and sometimes not even on a daily basis].

Then recently by chance I read somewhere that apparently the remote had a battery quick-draining problem if you turn on the infrared function and this was supposedly fixed by a firmware update. So that got me thinking whether I had turned on the infrared function; so I started going through my setting and saw that I did turn it on in order to use the remote to control the volume of my AVR while using my Shield. So I decided to turn off that feature to see how it would go.

Lo and behold! Since then (about a week ago) not only my batteries no longer drain like crazy my remote seems to have 'recovered' and has been working like normal! I am still testing it; so far it looks promising.

So it seems that using the remote in conjunction with my AVR via infrared messes up the connection between the remote and the main hub/console. Not sure if the problem lies with Shield, my particular set-up or the AVR (a Denon X2600H).

On another note, does anyone here use the Shield to access Tidal? I have this experience : Shield goes to sleep at the set time (for inactivity) even though while Tidal is running and playing songs. Seems like Shield is unable to detect that Tidal is actually running and hence 'thinks' that there is inactivity?

Thanks in advance!

I didn't check for IR 'leak'. Since turning it on causes problem witj the Bluetooth connection with the hub/console (at least for my set), I am keeping IR off.

On "Stay awake on music", I already have it turned On but it still goes to sleep while Tidal is playing.

I am not using SE 9.0. Withholding the update in view of all the reported issues.

I have opened a ticket with Nvidia but it has not responded. Will update.

Received an e-mail from Nvidia suggesting a list of things to do.

But luckily I don't have to go through them cos the problem I had somehow is gone! Now Shield doesn't go to sleep while Tidal is playing. I really don't know what happened.

On another note, does anyone know whether it is possible to :-

(a) transfer some data from the internal storage to the adopted storage?; and

(b) choose where apps are installed?

I have a USB drive acting as an adopted storage in order to add more space to the meagre internal storage. But I notice that most of the data and possibly new apps which I installed recently are still in the internal storage. This causes problem as sometimes I get a warning from the system saying that the internal storage space is getting very low; the culprit which eats up a lot of internal storage space is the Cache, which I will then clear when I get that warning.

There is a lot more space in the adopted storage which is not utilised by the system.

Thanks!

Thanks so much for this!