Glorious isn't it? OK, not really. But it's cheap, simple & does work (and glory be, physical volume buttons!). You've prob seen these around & like most air mouse remotes, it takes some fiddling to make right. Here's how I did it.

First, be rooted. Its a must. Get the remote, plug in the USB dongle to the Shield & pair it as the instructions. Download ES File Explorer, enable root file browsing & give the /System RW access in the popup.

Go into Device (Root), System, usr, keylayout. In there you'll find a bunch of .kl files. These are what Android & Nvidia include to make certain controllers & remotes work correctly w specific keymaps & such. Creating a new one requires certain permissions & formatting I didn't wanna get into, so I elected to just modify an existing one I knew I'd never use. If you click on them & open as text, you can see what remote its for in the notes. So find one you don't care to lose. Do NOT alter the Generic.kl file & instead, choose one of the Vender ones (mine was one about a Wii controller). Edit it to make it look exactly like this. Also note the file name I have given it. That is specific to this remote model & it won't work without remaining it. Make your edits, save it & rename the file. Restart the Shield & you should be good to go.

All buttons will now function as they should & the air mouse still works too if you activate it. Note that the "back" button on this remote (and most air mouse types) isn't a back button at all, but a right mouse click (dumb). You can't remap that, so I made Back the Menu button right next to it. Also I could never get the keycode to the Home button because any app I'd try it with, pressing the key would exit the app before registering the code. If anyone knows a way please let me know. Regardless, you can get around this by side loading a simple app called Buttons Remapper. It sees the remaining Home button as a generic "0" key, but it will map it to the home function so it'll work perfectly after this.

Here is the exact one I bought, but there's a bunch of different versions floating around that may or may not have the same Vendor & Product numbers for the .kl file so be aware. Look up the ADB way of finding out these numbers via Terminal (its easy).

That's it. Enjoy your shitmote!