Overview

This page lists identified bugs, describes any impacts and workarounds, and indicates the date at which they were identified and/or fixed. Bug fixes are wrapped up in MDK releases—to establish whether your robot has a bug, establish whether the software installed on your platform has a release tag that comes after the fix date for that bug.

Release R190211

190211a (Stuck in calibration mode)

Module
MiRoapp.
Symptom
Enter the calibration screen, and leave by an unusual route (e.g. if the application quits). MiRo will remain in calibration mode, despite not being in the calibration screen.
Workaround
Either re-enter the calibration screen and leave by pressing close, or reboot (power cycle) MiRo.
Fix
Not yet addressed.

190211b (BLE scan stops working)

Module
MiRoapp.
Symptom
Under some conditions, the scan screen will stop working so that nearby MiRos do not appear.
Workaround
Turn the Bluetooth module on the handset off then on again; you may also restart MiRoapp (or your handset).
Fix
Not yet addressed.

190211c (BLE connection fails repeatedly)

Module
MiRoapp.
Symptom
Under some conditions, the scan screen will be working, but every attempt to connect to a robot will result in the message "...disconnected".
Workaround
It will usually be enough to "swipe right" the app in the open apps list of the handset, then re-open the app; if this fails, restart the handset.
Fix
Not yet addressed.

190211d (MiRoapp has stopped working)

Module
MiRoapp.
Symptom
Coming back to the app after it has backgrounded (e.g. following a display timeout) may cause the app to crash when it is used again ("MiRoapp has stopped working").
Workaround
Restart the app.
Fix
Eliminated at R190518.