NiyaShy / XB1ControllerBatteryIndicator

A tray application that shows a battery indicator for an Xbox-ish controller and gives a notification when the battery level drops to (almost) empty.
GNU General Public License v2.0
730 stars 52 forks source link

"Controller One - Found but still waiting for battery data..." #97

Open Elaws opened 2 months ago

Elaws commented 2 months ago

Your operating system

Windows 11.

Your controller model (see label in the battery compartment)

Controller 1 and 2 : Model 1914.

How is the controller connected to your device? (if you use Bluetooth, please read issue #49 first)

Through wireless adapter.

Details about the issue, what you already tried and if it happens consistently or just occasionally

Firmware 5.22.16.0.

When connecting one or two controllers, one or both may lead to the following error message :

Controller One - Found but still waiting for battery data.

NiyaShy commented 2 months ago

Hey, asking just in case, what kind of "wireless adapter" are you using? An official Microsoft dongle, a 3rd party one? Sadly can't replicate your issue, I have the same controller model and just updated its firmware (was on 5.21 before), and it got recognized almost instantly.

Does it happen every time you connect a controller or just sometimes?

The "waiting for data" status has been a recurring thing that pops up every once in a while, and I never found a cause or fix for it. All the program is doing is asking the controller about its status through Microsofts official API, and getting no reply most likely means that either the controller or the API are not doing what they're supposed to do, so it's all factors I have no influence on...

Elaws commented 2 months ago

Thanks for your reply : it's the official Microsoft dongle (and official Microsoft batteries)

There is at least one of the controllers (it can be either or both) that gets this error message. It is quite consistent for the last ~4 hours.

I haven't yet rebooted the computer, will update if necessary.

NiyaShy commented 2 months ago

K, so we seem to have a similar setup since I also have an official dongle (the first large version, not the smaller refresh), though I'm still on Win10. But if it were an issue with Win11 there would be quite a lot of reports by now.

Are you using the "main" release (1.3) or the "preview/beta" from #55? The core detection logic hasn't changed much, but the overall code got many changes and additions, so it should be worth a try.

Elaws commented 2 months ago

Thanks for your prompt reply : I got the 1.3.1.2.

As for the dongle, I got the smaller version (on the bottom on following picture) :

image

I will use the preview/beta version you linked and update !

Elaws commented 2 months ago

Mmm unfortunately it's even worse, now none of the controller is detected :

image

image

NiyaShy commented 2 months ago

That's really weird... Just in case I dug up my other working controller (an older model 1697) and connected both at the same time, and it worked as usual. grafik So I really can't replicate your issue. Can't even say if it could be something with Win11 or your specific system.

Elaws commented 2 months ago

Just connected 2 controllers (still v1.4.0), one of them is properly detected this time. So, same as v.1.3.1.2.

image

(Unrelated : By the way, can your program show battery %, or only "Low / Medium / Full" ?)