MissionControl VS Nintendo_Switch_Reverse_Engineering

> Pirates will always find a way

Except it's usually not pirates who find these exploits, rather curious tinkerers that want to unlock the full capabilities of the hardware that they own. The pirates / script kiddies usually come in after the groundwork has already been laid by these true hackers. E.g. the people who hacked the Switch in fact condemn piracy and any discussion of it on within their communities will lead to an immediate ban.

I'm proud to say that I've hacked my Switch, but have never pirated anything on it. An impressive homebrew scene has formed around the console, which has produced gems such as Mission Control, allowing you to seamlessly pair third party controllers. I use it with my PS4 controllers.

https://github.com/ndeadly/MissionControl

Now try installing Tinfoil to manage your games, themes and mission control so you can use any bluetooth controller! https://github.com/ndeadly/MissionControl

Here ya go

[https://github.com/ndeadly/missionControl/releases/tag/v0.1.0.

MissionControl

I think this is the page for it: https://github.com/ndeadly/MissionControl/issues/568

This implementation uses GDExtension and libhid to get the controller's information. This was very helpful when making it. I think it'd be possible to get the IR camera's info in Godot, too. I also got it to work on Web using the WebHID API and the JavascriptBridge singleton.

So recently i dropped my right joycon and it stopped working. When I opened it i found that right shoulder button had broke of the motherboard and metallic piece was shaking around inside. This is not the main problem (cause i know the testing points on motherboard that i could solder to in order to fix the button). After i removed broken button and assembled it back i discovered that my joycon now only works in handheld mode. Also the console is reporting that the battery is low. So i disassembled it back and checked the battery and the pins on the connector itself, everything was ok. I then tried to supply power externaly (5V to JC pins 1 and 4, as stated in this github repo: https://github.com/dekuNukem/Nintendo_Switch_Reverse_Engineering) and it connected fine wirelessly. So now i thinking that maybe there is some fuse that had blown up cause of that metallic piece. The problem is i could not find any information about fuses that may cause this and also i could not find any information on testing points (like VBAT). I will appreciate any help in finding some kind of schematic diagram or just info about fuses or testing points!

I know there is some work (on the protocol) done over there: https://github.com/dekuNukem/Nintendo_Switch_Reverse_Engineering

https://github.com/dekuNukem/Nintendo_Switch_Reverse_Engineering is the most comprehensive source of documentation on the controller and protocols involved. Most of the communications are described in the bluetooth notes, but the protocol for wired is the same, just wrapped up with some additional headers (see https://switchbrew.org/wiki/Joy-Con)

Given they credited this project (when looking at SDL_hidapi_switch.c), unlikely.

People have reverse-engineered the entirety of joycon hardware for no reason other than curiousity.

https://yuzu-emu.org/

https://ryujinx.org/

https://github.com/dekuNukem/Nintendo_Switch_Reverse_Enginee...