-
Notifications
You must be signed in to change notification settings - Fork 151
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
Pairing mode after restart #523
Comments
If you have paired once, you should be able to connect after battery replace. The pairing keys are stored and not dependent on the battery. |
The pairing keys are the same, it's true. The problem is, that the ble manager does not find during scanning after battery replace. I need to switch on again the "Device connection" on the GoPro to be able to discover the camera. |
I have same problem and I don't know how to fix it. But my connection just crash sometimes and I have to open Connection - Quik App every time to fix it. Program just says that it can't connect to my camera. |
Can someone provide a list of steps to replicate the issue here following the Bug Report Template? What I can gather from the conversation above is that the GoPro can not be re-paired to via BLE after pulling and reinserting the battery without some type of UI interaction? This is certainly not true so I must be missing a step somewhere. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
This issue was closed because it has been stalled for 10 days with no activity. |
I have a mobile app that set a livestream on gopro via BLE.
Case: when the battery goes low, i need to replace it. After replacement the stream should continue automatically without any interaction.
Problem: the connection could not be established automatically because the pairing mode is off after battery changing and a ble manager cannot find it during the scanning.
Question: is it possible to set gopro camera that way, so the pairing mode will be on all the time? or is there any other solution? or technically now it is not possible?
The text was updated successfully, but these errors were encountered: