-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32/nimble forgets BLE pairing connection to Android client #6
Comments
Nice looking. Although I'm not sure if we're using ESP/Nimble indirectly as we're using h2zero/esp-nimble-cpp. I'll keep an eye on that issue and I'll bump the module once it's completely fixed if needed, as it's an nasty fix right now. |
Tried "nasty fix"(manual patch) and solved Android pairing(So we are using it). Windows still have same Behavior. Sadly issue have no updates from February, i will check a related one, i think they moved the discusion there. |
I have tried esp32-ble-gamepad example, and got same windows connection Behavior, so we can discard a problem on our code. pretty sure is a esp-nombre issue. |
Updated all components to latest versiones and got Android pairing Ok without need for Nasty fix. |
Talked too fast, i can now turn bt off and on get reconnected and works OK, can even reboot windows and still get reconnected and works ok. but if i powercicle esp32 i get paired-connected loop same as b4. #$@!! |
Could you upload the code to a zip or to a repository so I could check what could be wrong? |
Cant create a branch, so forked to do so: You can get my code base from there if u want to test. Sould be good to make a discord Channel or telegram for better comunicación . With Victorkte and Yakara i think we are 4 active on the project, |
I think we are affected by this ESP/nimble issue, it have a fix but is on a branch still not merged. So i don't know hot to set ESP-IDF to use that branch.
Any advice appreciated, i will try patching manually to confirm if resolves out pairing Issues.
The text was updated successfully, but these errors were encountered: