-
Torque Pro is the OBD2 scanner I have. Android asks which app I want to run. I'll go out there and try again. Hopefully Google won't be too kissed off if I buy and then refund the app again if it still doesn't work. I'll take my laptop out there too, just to make sure the APU1 is sending out correctly.
-
Maybe also try to unplug/plug the USB cable while the app is open and tap connect / disconnect a couple times. See if that makes a difference.
I've just tried it on my side and everything seems fine for me (and I know a bunch of users are using USB) but it might be something specific to your device (Android fragmentation is a pain :D)
-
Tried all kinds of stuff. Reconnecting, restarting, resetting, nothing worked. What's the next step for troubleshooting? Any ideas?
-
has anyone you know of used an APU1 from moates on an OTG cable?
-
Are you using Torque with USB too ? I guess I will have to add more debugging in the USB area to understand what's going on on your phone...
Oh also, did you ever saw the USB permissions prompt and clicked "Yes" ? It should look something like that: http://www.phidgets.com/wiki/images/...ermissions.png
-
Torque uses Bluetooth. And yes, I was asked twice for aldldroid to use the adapter and both times I said yes.
-
Oh, this phone is rooted and such, so if you need me to do something with debugging or something, let me know.
-
Can you try something else that uses USB host like a keyboard, mouse, external drive, digital camera or whatever ? Just to confirm there is nothing wrong with USB host itself on your phone and that you're able to make it work with something else. I will probably end up adding some debugging and have you give that a go and send me the log.
-
Works fine with a mouse, Xbox controller, and flash drive.
-
Good to know, really seems to be some sort of issue with the app triggered by your phone somehow then. I can add debugging but I've seen you've returned the app twice, I don't think you will be able to do it another time. Are you still interested to continue, if not, I will understand, otherwise I will continue adding some debug and hopefully be able to figure it out with you.
-
Since you are willing to debug and move forth, I will get it going again.
-
Let me know what you need me to do, I got it again.
-
Ok cool, I will be adding more debugging to see exactly where things get problematic. Hopefully later this weekend I will have a new build for you to test and we'll go from there. Thanks
-
Looks like I will be pushing the new version to Play tonight. The new logging should be pretty useful. Here what I have come up with. Just need to think about it some more to make sure I haven't forgot anything. Will let you know
[INFO] (ECU) 06/14/14 15:06:42.110 --------------------------------------------------------------------------
[INFO] (ECU) 06/14/14 15:06:42.112 Starting ALDLdroid version 0.44
[INFO] (ECU) 06/14/14 15:06:42.113 Found USB device /dev/bus/usb/001/005, key 0403:6001
[INFO] (ECU) 06/14/14 15:06:42.116 User already has accepted USB permission for device
[INFO] (ECU) 06/14/14 15:06:42.117 Found an attached USB device
[INFO] (ECU) 06/14/14 15:06:43.148 Attempting to open USB device
[INFO] (ECU) 06/14/14 15:06:43.183 Connected to FT232R USB UART A6027U80
[INFO] (ECU) 06/14/14 15:06:43.186 About to set baud rate to 8192
[DEBUG] (ECU) 06/14/14 15:06:43.354 Starting ECU comms thread
[DEBUG] (ECU) 06/14/14 15:06:43.355 ECU connection type is USB_FTDI
[DEBUG] (ECU) 06/14/14 15:06:49.541 Sending command "Mode 1 ALDL Dump Request Send" (F0 56 01 B9) and now listening for packet (71 bytes)
[DEBUG] (ECU) 06/14/14 15:06:49.652 Got response from ECU: F0 56 01 B9 F0 95 01 02 D1 00 08 82 00 46 46 00 3D 8F 01 12 01 6D 00 00 00 65 03 80 80 01 80 6F 00 5A E8 2F D9 00 00 00 79 00 00 44 00 63 47 8D 00 76 FF 00 00 FF 09 A8 20 00 83 F4 E1 04 C3 03 02 6F 4B 0B 40 41 FF
[DEBUG] (ECU) 06/14/14 15:06:49.654 Data is at offset 7 and 63 bytes long
[DEBUG] (ECU) 06/14/14 15:06:49.657 Sending command "Mode 1 ALDL Dump Request Send" (F0 56 01 B9) and now listening for packet (71 bytes)
[DEBUG] (ECU) 06/14/14 15:06:49.765 Got response from ECU: F0 56 01 B9 F0 95 01 02 D1 00 08 82 00 46 46 00 3D 8F 01 12 01 6D 00 00 00 65 03 80 80 01 80 6F 00 5A E8 2F D9 00 00 00 79 00 00 44 00 63 47 8D 00 76 FF 00 00 FF 09 A8 20 00 83 F4 E1 04 83 03 02 6F 4B 0B 40 41 3F
-
If I go to Chip Programming is finds the hardware, Moates AutoProm 2.17.A