You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
App works perfectly (flashing) on my iPhone X, but not on my Samsung Galaxy S20
It pairs with no problem:
but when I try to flash I get:
the weird thing is that I have got it to work twice out of about fifty tries, I'd really like to be able to flash from my Samsung then it would be truly portable. works from my old iPhone X as I mentioned above and works great from USB just not from my Android phone which is my new primary phone now. I have seen other complaints on the Google Play store of people with this
micro:bit version
V1.3, V1.5, V2.0, not hardware related [Edit as applicable]
Device
Make: Samsung
Model: Glaaxy S20
OS: ?
App Version 2.8.8
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I have the same problem with my newish Pixel 5, and also with an older Android phone the Mi A1. And yet it works perfectly on our old IPad mini! I think that this problem needs addressing since using (cheap) Android tablets in schools to program microbits is a very nice way of teaching coding. But at present this is not possible it would appear.
https://support.microbit.org/a/tickets/42830
Describe the bug
App works perfectly (flashing) on my iPhone X, but not on my Samsung Galaxy S20
It pairs with no problem:
but when I try to flash I get:
the weird thing is that I have got it to work twice out of about fifty tries, I'd really like to be able to flash from my Samsung then it would be truly portable. works from my old iPhone X as I mentioned above and works great from USB just not from my Android phone which is my new primary phone now. I have seen other complaints on the Google Play store of people with this
micro:bit version
Device
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: