" message whenever I wake the Switch from sleep mode?
Yes, you have to enable Bluetooth connectivity. This can be configured via System Settings under the Airplane Mode tab.Somehow while thinking about all this, I forgot that I can just dump them and just restore my NAND to a state before running the CFW.
Thanks anyway.
Is there a way to get rid of that extremely annoying "Pls turn airplane mode off and connect joycons
Well I myself have never used SX OS as a CFW before, I did use it to make my emuMMC partition before Hekate had the ability to do so. After that, all I did was use the 'migrate emuMMC' option in Hekate. You will also need a way to launch emuMMC which I already had with my hekate_ipl.ini. If you do not have one, you can grab it and maybe some other useful tools as SDSetup.com
Daybreak is a homebrew application that installs firmware files. If you downloaded Atmosphere from its official GitHub page and didn't delete the /switch folder that came with, it should already be included in your setup. As for your second question, it is extremely vague yet impossible to answer. Atmosphere like SX OS is just a CFW meaning all it does is it provides the user an environment to use hacks. The real usage comes from the homebrew applications and potentially other RCM payloads that actually alter the console to do whatever it is you want to do.
Not sure what you mean, if you use primary instead of secondary (hekate) including a change of patches, everything will be working without a need of reinstall any game. The thing is I really prefer using secondary and hekate and I hate whenever this things happens and make me switch temporary to it.
In order to hack Mariko units, you need an SX OS modchip which not only is hard to track down but requires soldering. Unpatched units can be hacked with simply a USB cable and paperclip. Unless you can track down the modchip and have a way to solder it inside, unpatched units are the way to go.
Well usually the point of emuMMC is to have it be on a firmware higher than your sysMMC but it can be used in the opposite way. Just be aware that if you update sysMMC to firmware to 12.X, you will have to choose between playing cartridges on your 12.X sysMMC or your 11.X emuMMC. The reason is because there is an irreversible update for the cartridge slot on firmware 12.X that once applied will prevent cartridges from working on any firmware version below 12.X. The only way to prevent this update is by breaking the cartridge slot which can only be achieved with nogc. The only reason one may not wish to update their cartridge slot is in case an exploit is released in the future that requires a not updated cartridge slot. So in essence, you have to pick between being able to play cartridges on a higher or lower firmware version.
It is pretty self-explanatory. When a CFW does not support that firmware anymore, that means you cannot boot that CFW on that firmware anymore. But just because the CFW does not work anymore doesn't meant OFW will not work anymore. When it comes to emuMMC however, there is no way to boot OFW so if emuMMC is on a firmware that is no longer supported by CFW, then you cannot boot emuMMC period. On the bright side though, emuMMC can always be uninstalled and recreated which cannot always be said of sysMMC. Anyway, just remember that booting a CFW requires a firmware compatible with that CFW and that emuMMC does not affect sysMMC (and vice-versa).
Yes, you should just make all of the partitions at the same time. From what I've seen on Google, there doesn't seem to be a size that is recommended for all users but they can be as big or small as you want.
What firmware version is the one you are trying to convert with ChoiDujour?
