Basically, you get a controller, a dongle, and a really, really hard to understand manual that seems to confuse most people trying to figure out how to use the darned thing the first time. But once you sync the gamepad and thte dongle, it'll work with whatever NES Compatible system you're playing on as long as it uses the US 7-pin ports.

So I suggest charging the Hyperkin at least for 30-min to an hour before using it, using a Micro USB charger. I use one for my cellular phones that has all three jacks on it and it works great for this.

Plug the dongle into the Nintendo/NES Compatible unit, put in a game, power it on. The charged controller and dongle SHOULD find each other - indicated by a solid blue LED on the dongle, and a solid blue LED on the controller. If not, hold the tiny "sync" button on the dongle and then on the controller, and see if they link up. You might have to try a few times, some people say doing both at the same time works best.

That said, I did find a few differences, CONS in some cases, pros in others, regarding how this controller reacts vs. a standard NES wired gamepad. I believe both of these to be introduced by the fact this is basically an NES gamepad passing it's signals over Bluetooth to a Dongle. First and foremost, I was playing a round of Star Wars and found that I could not, for the life of me, get Luke Skywalker to run to save my life. This is done in Star Wars by double-tapping in the direction you want to run. I tried this multiple times and just could not get it to work at all. Likely this is caused because the interpretation of the button presses in Bluetooth are not fast enough to register as a double-tap - because think of this, this is how a NES controller works....+ bluetooth.

A shift register chip inside scans all the ports on the chip, that takes fractions of a section to do, but those fractions of a second do count in playing video games, this is basically, for all intents and purposes to science, a computer after all. The shift register reads a hit to the button, it might read it twice in the spaan of time.

On a regular NES with a wire, it'd just send the double-tap to the controller port and be done with it, but Bluetooth adds an extra layer of complexity to the picture. now that button hit has to be converted to a standard "language" the bluetooth module can understand, then converted BACK into a NES button press - almost like a modem would do over an analog phone line - and then send that button press back to the NES. So having to do that add a very minor - to the player unnoticeable - delay between the controller and when the NES reacts. When the programmers at JVC/LucasFilm Games were making Star Wars in 1990, I don't think they were thinking people would be playing their cash-grab game on a then 13 year old movie franchise in 30 years time with some kind of new wireless technology wired into their 30-35 year old NES via the controller port. They would probably speculate we'd all be playing it in 3D photorealistic graphics with a VR headset and no controller at all, in sometime that basically just put you inside the movie itself - like the Star Trek Holodeck.

Another thing I noticed is with Dragon Warrior, and this is actually a total BLESSING in diguise, especially if you can be as fumble-fingered as me. On an NES, in at least some of the Dragon Warrior releases, you can often rip through the command menu by just pressing the A button and holding it. This does not work with the Hyperkin Cadet. Again, Bluetooth translation lag-time - not noticeable to human hands - but noticeable to the NES on it's microscopic level. I think it also may be intentional so as to prevent a button "hang" where the button stays pressed and either does not address or carries out multiple functions at the same time. It's actually quite a blessing because you're not likely to accidentally sell quest items or essential weapons and armor not for sale in any shop this way.