FAQ
Frequently Asked Questions and important information for using JoyCon Droid.
Last updated
Frequently Asked Questions and important information for using JoyCon Droid.
Last updated
Bluetooth HID Profiles were introduced in Android 9 which allow your device to function as a gamepad, mouse, keyboard, etc. You cannot do this on lower Android versions. Use the to check if you have it. Android 13 and higher must also install the Magisk module instead of Bluetooth++ due to significant changes to Bluetooth. If using Android 13+, make sure to download the newest version of the app, at least 1.0.91.
Switch firmware version 12.0.0 and up has changed the functionality behind controller connection and input. It now has a Bluetooth Device Class check for initial pairing requests which checks if your device is a Gamepad or others. If your device is on Android 9 to Android 12, it must be rooted with Magisk to use the and change your device class to 002508 or to change your device’s Bluetooth MAC address to a real controller you have already paired with the Switch. . Root is also needed if you want to try to .
If your device is on Android 13 or higher, you must use the Magisk module instead.
Magisk is not necessarily required, however. You can be rooted with an alternative like SuperSU as well and would just have to manually install or edit your files by accessing them with root privileges. Magisk is recommended and easier since you can simply install or remove the module. KernelSU is another option which can install Magisk modules.
The JoyCon Droid app itself does not need root, but the workarounds needed to get paired with the Switch need root.
Every device is different and may use a different set of instructions with unique files to gain root access. Some phones have a difficult process to unlock the bootloader which is needed to flash a custom recovery and install custom ROMs or root with Magisk. Some phones might also be impossible to unlock or root. The best thing to do is search your device’s exact model on . Please also if you are new to rooting Android.
This process requires a PC, erases everything on your phone, may cause issues with certain apps due to , , etc. Make sure to backup important data before proceeding or use a spare Android device. You can end up with a non-functioning brick if you do not follow the instructions for your specific Android device carefully.
Yes, you can try using the . This still requires Android 9+ and a rooted phone with Magisk to install modules. This module can help for devices that usually have it disabled such as OnePlus, Motorola, Huawei, LG, Sony, and Xiaomi. Restart your device after installing and enabling the module, then try the Tester app again.
There is always some risk to rooting your phone and modifying system settings. Bluetooth++ will save your default Device Class so you can always reselect it after you're done playing with your Switch. It is however encouraged to make backups before doing any of this as a good practice of safety.
It's also possible you have a Samsung Galaxy A50/A51 which is known to give problems with connecting after a Samsung system update.
Certain games may cause JoyCon Droid to disconnect when they are started as it brings up the same screen as the Change Grip/Order screen in-game. This can cause the app to disconnect frequently and make it difficult to get reconnected to enter and play the game. If this happens to you, turning off Bluetooth on your Android device and then trying to connect may help, repeat if necessary.
Another thing that may help in certain games is to enable Airplane Mode on your Switch, then go into the Switch settings, Airplane Mode section, and then you can turn on only Bluetooth to then see if this helps with connecting.
Yes. It does not matter if your phone has NFC or not. amiibos are being sent through Bluetooth.
There are certain amiibos which will not work because they require writing data and JoyCon Droid does not yet support this feature. Some examples of this are Wolf Link in Breath of the Wild, Splatoon 2, Splatoon 3 and many other games that register amiibos.
Yes, you can Select and Edit a Custom UI from the menu options of JoyCon Droid. You will also find other custom UI options created by members of the community such as Macros and TAS UI here. You must have an Internet connection to access these Custom UI options.
You can connect a gamepad to your phone using USB. You may need a USB OTG adapter. You can’t connect it through Bluetooth due to the way JoyCon Droid utilizes the Bluetooth connection to pair with the Switch. To avoid connection issues, you must also disconnect other devices such as wireless speakers, smartwatches, etc. To Remap Buttons/keys, find Map Buttons in the menu options of JoyCon Droid.
JoyCon Droid has had millions of downloads from users. No one has ever gotten banned yet. There's currently no way that your Switch can tell the difference between JoyCon Droid and a real Switch controller. Your Switch does not need any CFW or modifcations for this to work. You should be safe, but there could still be some risk such as if you use Macros or Turbo Controller to cheat in online multiplayer games and someone reports you.
Yes.
JoyCon Droid has been removed from the Google Play Store. Anything using the same name is a fake or has uploaded code without permission and should be avoided unless linked here or on Discord. You can install the APK from
Disconnect any other Bluetooth devices that are connected to your phone such as headphones, speakers, smartwatches, etc. Try the and make sure to . Retry connection by Disconnecting Controller using the status bar notifcation on Android and leaving the Change Grip/Order screen or Restart both your Switch and Android. To yield the best results when trying to connect during disconnecting issues, turn off Bluetooth on your Android device and let the JoyCon Droid controller turn it back on for you. This should usually then ask, "Joy-Con Droid wants to make your phone visible to other Bluetooth devices for 60 seconds". Allow it, then try the . Doing this process with a (connected wirelessly) and Right JoyCon from the app (or even Pro Controller) will make the connection more stable in most cases.
If you're using Android 13, you'll need to make sure you're using the latest JoyCon Droid version and use instead if Bluetooth++ doesn't work.
If your Switch for a controller from JoyCon Droid, DO NOT do it. It will get stuck. Press Later to skip that popup. If you accidentally pressed Update, simply disconnect the controller by using the Status Bar notification on your phone or turn off Bluetooth.
Using a with a Right JoyCon from the app might be a lot more stable on that screen than a Pro Controller by itself from the app. It may also help the Pro Controller from the app as long as a real controller like a Joy-Con is connected.
Bluetooth HID_DEV_MTU_SIZE 512. Most Samsung devices will have this already. LineageOS 16.0 or higher based custom ROMs built after 7th of September 2020 are likely to have this. Make sure to Enable NFC in JoyCon Droid Settings. You can select and change an amiibo .bin file in Settings where it says NFC Binary Path. . [The Patch introduced on 7th of September 2020 is only for the AOSP Bluetooth Stack. If an Android device uses the Qualcomm Bluetooth Stack, HID_DEV_MTU_SIZE is still set to 64.]
Since amiibos are copyrighted content, JoyCon Droid cannot help you obtain amiibo .bin files for legal reasons. It is assumed that you are using personal dumped copies of your own amiibos such as from .
Once again, amiibos only work with Samsung devices or with a custom ROM such as LineageOS 16.0 or higher, and the custom ROM needs to be built after 2020-07-September because they have a Bluetooth HID_DEV_MTU_SIZE of 512 bytes. If you have this, try other amiibos and and also try changing the Packet Rate to other values such as 10, 20, 50, 69, 80, 120 pps in JoyCon Droid settings. Please be aware that the app can be unstable and it can take you multiple tries to get connected properly and "scan" amiibos.
If you have a spare Android phone or a friend with one, you can try the method . If the Device Class check is ever removed in future Switch updates, that will probably help again but it's not likely to happen for future Switch firmware updates after 12.0.0. Not guaranteed to work.
If you've followed this guide carefully, tested different custom ROMs, Android versions, and devices, then you may want to for alternatives.
