Forum

Full Version: v2.5 not connecting thru USB
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Just upgraded from 2.0.2 to 2.5 set USB connection as default with 9600 baud
Got "unfortunately DRO has stopped" every time connect is clicked.

revert back to 2.0.2 and everything is good, controller remains unchanged.
clear app data from system->Apps->Download and reinstall v2.5 again reboot
start app connect, app dies.

Tried default settings on 2.5, then used metric mode on start up, only x axis enabled
still not able to connect through USB.

Is there some logs that i can post?

Thanks.
(08-16-2016, 04:59 PM)samit_ray Wrote: [ -> ]Just upgraded from 2.0.2 to 2.5 set USB connection as default with 9600 baud
Got "unfortunately DRO has stopped" every time connect is clicked.

revert back to 2.0.2 and everything is good, controller remains unchanged.
clear app data from system->Apps->Download and reinstall v2.5 again reboot
start app connect, app dies.

Tried default settings on 2.5, then used metric mode on start up, only x axis enabled
still not able to connect through USB.

Is there some logs that i can post?

Thanks.

Hi,
I think I nuked my previous post accidentally:
Can you give me the details about your device (make/model/OS version)?
I removed "Crash Reporting" via email from the app for the release, but can easily re-enable it.

Thank you
yuriy
I run touchdro on a Lenovo A3300, 7inch tablet, Android 4.4.2, Kernel 3.4.67
thru the USB port using OTG cable. Been using touch dro close to a year now
I'm also having this problem. I'm running 2.5.10 released 2016-8-12.

I'm trying to get USB working as I'm putting the electronics in a metal enclosure. I'm using an FTDI serial to USB chip, and every time I try to connect the app crashes.
Was this problem ever resolved? I too have a requirement to use the USB facility on an Android tablet but I get different results between my phone and a Amazon Fire tablet. The phone crashes as soon as I attempt to connect to USB and puts up a warning message, the tablet simply reverts back to the home screen with no warning messages.
USB is very dependent on the combination of the UART-to-USB bridge chip and the tablet. Unfortunately, the drivers are very hit-and-miss, and that is out of my control largely. They are implemented at a much lower level, so if things go wrong, they can crash the whole device. At this point I very strongly recommend avoiding USB and use BlueTooth. I'm seriously contemplating removing USB support from the V3 (I will definitely not be listing it in the spec, even it it remains available).
Thank you
Yuriy