Unsure if this belongs in this forum section since it isn't related only to Dolphin, but here we go...
I think I somehow managed to corrupt Wiimote's firmware. Let me explain: I have two genuine Wiimotes, one regular wiimote (without Motion Plus) and one Wii Remote Plus (a non -TR one, from Flingsmash bundle) and about two weeks ago they were working perfectly, without any problem, no random disconnects, all extensions (even some 3rd party) detected, etc. Didn't use them until today, when I noticed that they are working strangely now...
The one without Motion Plus looks like it's completely dead when not connected, pressing any button won't do anything, except for the red sync button on back, that makes it blink and become discoverable, but I remember that when it worked normally, pressing any button would make it blink and try to reconnect to the last paired device. If connected alone, it works in Dolphin and in GlovePIE, but no extensions will work anymore (tested with a genuine Nunchuck and Classic Controller), for Dolphin games it's like nothing is connected, GlovePIE detect that a extension is attached but can't read any data from it. If connected together with the wii Remote Plus, then it'll not respond once connected...
The one with Motion Plus inside doesn't show any strange behavior when not connected, but once connected it doesn't respond, in any app at all. Connecting it alone doesn't change anyhting...
I tried in other computers/laptops, tried in fresh Windows 7/8/8.1 and Ubuntu 12.10/13.10 installs, tried with other BT dongles (even and old one that worked fine), tried Microsoft/Toshiba/Widcomm BT stacks and tried even with some Android apps, in all cases they don't respond once connected anymore...
Using Dolphin builds before wiimote fixes made by Biliard will connect to them just fine and pressing refresh will make them vibrate and Dolphin will assign a LED to them, but once you boot a game the statusbar will say "Wiimote disconnected" and the game will ask to connect a wiimote (pressing Alt+F5/Alt+F6 doesn't reconnect them). Using current Dolphin builds the wiimotes aren't found, and pressing refresh in wiimote settings while they are discoverable will make Dolphin freeze for around 30 secs (but no crash) and then nothing. Continuous scanning option makes Dolphin randomly crash if they're discoverable...
In GlovePIE, when you start a script, the 1st and the 4th LEDs will be lit for around 2 secs and then they'll be defined accordingly to the script (the default is the first LED on and all others off) and both worked like that before this problem, now they'll freeze in the 1st and 4th LED on and nothing more if I connect the two at the same time or if I connect only the Wii Remote Plus. If I connect only the regular wiimote, it'll work but no data can be read from attached extensions...
In Android apps you can set the LEDs, read button presses and make them vibrate, but no accelerometer data/IR tracking/EEPROM reads works...
I would like to know how it would behave in a real Wii in that state but my Wii broke and I can't test anymore...
I also found that if I connect only the wiimote without Motion Plus, they will work fine, but every time that you open Mii Channel, for example, it'll say that the Wiimote memory must be formatted, but it'll always fail. Before this started happening, I could successfully transfer Mii's between my computer/my laptop/real Wii without problems, and now they don't work anymore.
So, a summary: the two wiimotes were working flawlessly but now they'll not respond once connected. The regular Wiimote works if connected alone but it's memory always ask to be formatted in Mii Channel and no extensions are detected anymore. The Wii Remote Plus will not respond once connected in any case...
Googling on WiiBrew I found that Wiimote's EEPROM also contains parts of the firmware, and seen that Mii Channel always complain about it needing to be formatted I suspect that somehow I may have managed to corrupt it. Any clues on what I could do now to get them working again? I'm considering anything, even messing with the Wiimote hardware itself (aka manually editing EEPROM contents) since in the current state they doesn't allow doing anything useful...
I think I somehow managed to corrupt Wiimote's firmware. Let me explain: I have two genuine Wiimotes, one regular wiimote (without Motion Plus) and one Wii Remote Plus (a non -TR one, from Flingsmash bundle) and about two weeks ago they were working perfectly, without any problem, no random disconnects, all extensions (even some 3rd party) detected, etc. Didn't use them until today, when I noticed that they are working strangely now...
The one without Motion Plus looks like it's completely dead when not connected, pressing any button won't do anything, except for the red sync button on back, that makes it blink and become discoverable, but I remember that when it worked normally, pressing any button would make it blink and try to reconnect to the last paired device. If connected alone, it works in Dolphin and in GlovePIE, but no extensions will work anymore (tested with a genuine Nunchuck and Classic Controller), for Dolphin games it's like nothing is connected, GlovePIE detect that a extension is attached but can't read any data from it. If connected together with the wii Remote Plus, then it'll not respond once connected...
The one with Motion Plus inside doesn't show any strange behavior when not connected, but once connected it doesn't respond, in any app at all. Connecting it alone doesn't change anyhting...
I tried in other computers/laptops, tried in fresh Windows 7/8/8.1 and Ubuntu 12.10/13.10 installs, tried with other BT dongles (even and old one that worked fine), tried Microsoft/Toshiba/Widcomm BT stacks and tried even with some Android apps, in all cases they don't respond once connected anymore...
Using Dolphin builds before wiimote fixes made by Biliard will connect to them just fine and pressing refresh will make them vibrate and Dolphin will assign a LED to them, but once you boot a game the statusbar will say "Wiimote disconnected" and the game will ask to connect a wiimote (pressing Alt+F5/Alt+F6 doesn't reconnect them). Using current Dolphin builds the wiimotes aren't found, and pressing refresh in wiimote settings while they are discoverable will make Dolphin freeze for around 30 secs (but no crash) and then nothing. Continuous scanning option makes Dolphin randomly crash if they're discoverable...
In GlovePIE, when you start a script, the 1st and the 4th LEDs will be lit for around 2 secs and then they'll be defined accordingly to the script (the default is the first LED on and all others off) and both worked like that before this problem, now they'll freeze in the 1st and 4th LED on and nothing more if I connect the two at the same time or if I connect only the Wii Remote Plus. If I connect only the regular wiimote, it'll work but no data can be read from attached extensions...
In Android apps you can set the LEDs, read button presses and make them vibrate, but no accelerometer data/IR tracking/EEPROM reads works...
I would like to know how it would behave in a real Wii in that state but my Wii broke and I can't test anymore...
I also found that if I connect only the wiimote without Motion Plus, they will work fine, but every time that you open Mii Channel, for example, it'll say that the Wiimote memory must be formatted, but it'll always fail. Before this started happening, I could successfully transfer Mii's between my computer/my laptop/real Wii without problems, and now they don't work anymore.
So, a summary: the two wiimotes were working flawlessly but now they'll not respond once connected. The regular Wiimote works if connected alone but it's memory always ask to be formatted in Mii Channel and no extensions are detected anymore. The Wii Remote Plus will not respond once connected in any case...
Googling on WiiBrew I found that Wiimote's EEPROM also contains parts of the firmware, and seen that Mii Channel always complain about it needing to be formatted I suspect that somehow I may have managed to corrupt it. Any clues on what I could do now to get them working again? I'm considering anything, even messing with the Wiimote hardware itself (aka manually editing EEPROM contents) since in the current state they doesn't allow doing anything useful...
Avell A70 MOB: Core i7-11800H, GeForce RTX 3060, 32 GB DDR4-3200, Windows 11 (Insider Preview)
ASRock Z97M OC Formula: Pentium G3258, GeForce GT 440, 16 GB DDR3-1600, Windows 10 (22H2)
ASRock Z97M OC Formula: Pentium G3258, GeForce GT 440, 16 GB DDR3-1600, Windows 10 (22H2)