I apologize for the delay. We have obtained the same device and were able to confirm this issue. We will proceed with the correction now.
This issue has been fixed in version 0.03.
