Pairng rejected by REVOBUMP

[lmcwilli]

Though I have successfully connected by Bluetooth to the BUMP controller using my Samsung Galaxy S7 Edge (Android v6.0.1), I frequently get the message "Pairing rejected by REVOBUMP" and can't connect. This usually occurs when I attempt to connect when a charge is in progress.

I see no "accept connection" message on the BUMP. Pop-ups appear on the BUMP, first stating "BlueTooth connecting..." then "BlueTooth disconnected".

After I went into the Android application manager and selected "Force Stop" for the Bump Controller app, I could subsequently make a BlueTooth connection to the BUMP.

Suggestions for avoiding this behavior?

[RevoKelly]

Originally Posted by lmcwilli

Though I have successfully connected by Bluetooth to the BUMP controller using my Samsung Galaxy S7 Edge (Android v6.0.1), I frequently get the message "Pairing rejected by REVOBUMP" and can't connect. This usually occurs when I attempt to connect when a charge is in progress.

I see no "accept connection" message on the BUMP. Pop-ups appear on the BUMP, first stating "BlueTooth connecting..." then "BlueTooth disconnected".

After I went into the Android application manager and selected "Force Stop" for the Bump Controller app, I could subsequently make a BlueTooth connection to the BUMP.

Suggestions for avoiding this behavior?

"Pairing rejected by revobump" is not something shown by our app ... are you attempting to pair to it like a legacy BT device ? .... if so, that will fail every time because this is a BT/LE device that does app-level pairing. No manual pairing step is required/supported - you just Scan for devices and connect.

There is a bug which causes random disconnects if the app is left running and attempting to connect while out of range of the Bump. What happens if you kill the app, power up the Bump, then start the app - does it connect cleanly ?

The disconnect bug will get fixed with the new "universal" app coming in Feb - it has much better handling for BT error conditions.