-
Notifications
You must be signed in to change notification settings - Fork 14
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
Default interface not entirely functional on Android tablet #19
Comments
Any more info on this? |
I have the same problem. I tried on various Android devices and different Android browsers like Dolphin and Firefox. The drag and drop does not work. It does work from my computer. |
Sounds like I'll need to get myself an android device to test on :-( |
@jakkalsj which devices and software versions were you using? |
Samsung note 10.1 2014 edition, using dolphin, firefox and default On Mon, Mar 23, 2015 at 2:04 PM, Ben Pirt [email protected] wrote:
|
Same with Chrome 47.0.2526.83 in a Nexus 5 cell phone with Android 6.0.1 |
@vespito could you give me some more details? In what way is it not working? Also, are you using a v1 or a v2? |
Same on Chrome on an iPod Touch 6 with a V2 Mirobot. You can't drag the blocks over to the playground |
Thanks @bonalybob - I'll take a look |
Same here on Firefox 53.0.2 on Android 6.0. Press+drag on the buttons on the left in the local.mirobot.io page produces no reaction at all, the objects can't be dragged. I also tried with Chrome 46.0.2490. it was similar, the objects gain some shadow when pressed on, one can't move them though. In both interfaces I can select the "collision detect" and "line follow" modes. |
Should have said, firmware version is 2.0.8, UI & wifi 2.0.10. |
On my niece's 2 year-old 7" Asus tablet (presumably not a current Android version), drag-and-drop doesn't work in the self-hosted Mirobot interface – you can't drag commands into the work pane.
I've currently no means of testing this on other Android devices, but will try to at least find the version of the Asus tablet involved. If anyone has successes or failures with other Android devices, perhaps annotate this issue with the OS version? Maybe we can track down a minimum Android or Chrome version required for compatibility.
The text was updated successfully, but these errors were encountered: