[Bug Report]: Controller disconnects since last update about missioncontrol HOT 3 CLOSED

Not really sure about that one. This is not a controller I have heard of or officially support. The fact that it works at all means it must share the same vendor/product ID as something else.

At this moment the controller disconnects after one or two minutes of connection, but, after some tries of connecting, it works perfectly. The problem is that it takes like 20 minutes til I can make it works

The only potential problems I know about would cause consistent failure. You wouldn't be able to make it work perfectly no matter how many tries. Maybe you have some intermittent RF interference where you are or something? Could also be worth checking whether you have the atmosphere setting for USB3 enabled. This is known to cause problems with wireless.

Also had problems with the RT trigger that sometimes doesnt works

This sounds like a hardware issue to me. Input mapping is all or nothing. All inputs are all sent together. It's impossible for some to work and others not. Alternately, this could be due to this controller not having exactly the same input layout to the controller that the Switch thinks is connected.

from missioncontrol.

Switched off USB3 in /atmosphere/config/system_settings.ini and still the same. The weird is that it was working fine on 0.8.0. How can I generate a log file or report?
P.S. Dont worry about the trigger, I dont care so much.

from missioncontrol.

How can I generate a log file or report?

You can use this build to make a log. It's not capable of logging much, because a lot of the connection stuff happens inside the layers of the Bluetooth stack, but it may give some clues. Logs are stored in sdmc:/mc-mitm.log

from missioncontrol.