Possibly dpad config issue. Try this:
1 make sure gamepad battery fully charged
2 turn off gamepad
3 hold down the very top dpad button, the one above the directional buttons. Keep holding.
4 power on the gamepad while continuing to hold that top button. Count slowly to 10.
Tell me if that works.
One theory I have is that if you boot the gamepad with a weak battery then the eeprom doesn't work right even though the rest of the nano still works. If the software doesn't see a valid value from the eeprom it uses a default dpad profile.
The reason I had to add this whole 'boot while holding button' feature is that manufacturers recently started sending me randomly one dpad profile or another. There is no difference in appearance of the modules, no difference in any numbering or anything.
This is just one of hundreds of issues this project deals with in the software. It's actually very difficult to field a product like this due to all the little hardware and software quirks!