Skip to content
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 process is erratic in Android 9 #24

Open
microbit-mark opened this issue Feb 17, 2021 · 0 comments
Open

Pairing process is erratic in Android 9 #24

microbit-mark opened this issue Feb 17, 2021 · 0 comments

Comments

@microbit-mark
Copy link

microbit-mark commented Feb 17, 2021

https://support.microbit.org/a/tickets/43035
https://support.microbit.org/a/tickets/45003

Describe the bug
Using Android Bluetooth pairing and the serial Bouetooth app works as expect.
Using the micro:bit Android app pairing. The app asks to enter a pattern, then that you will be promped to enter a PIN, then reports success, then on reset reports failure

To Reproduce
Steps to reproduce the behaviour. e.g.:

On completion of Step 1 and releasing the micro:bit reset button:
Micro:bit screen fills;
then displays the bluetooth logo;
then the unique pattern

After entering pattern and pressing “Pair”
Says: “When asked for a PIN, press button A to enter code
(you only have 30 seconds).”
There is no place to enter a PIN!!

Says “You have successfully paired
Please press reset button and you’re done.”

Upon pressing the reset button
Says “Pairing unsuccessful Cannot pair with micro:bit. Retry?”

After completing the task the micro:bit displays the character that I have programmed it to display on successful connection, but that’s all.
Following on from this the micro:bit is programmed to repeat a message that should be displayed by the Terminal app.

If I pair using the Android device pairing facility in Settings everything works as expected.

I have tried two different micro:bits with the same results.

The events listed above are the best I can do bearing in mind the speed at which things happen. It would be helpful if there were user controlled breakpoints.

Expected behavior

Screenshots/Recordings

micro:bit version

  • V1.3, V1.5, V2.0, not hardware related [Edit as applicable]

Device

  • Make: [e.g. Motorola]
  • Model: [e.g. G8]
  • OS: Android 9
  • App Version [e.g. 2.8.8]

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant