Home › Forums › Hardware › Arduino Due › Connecting DUE to Android
This topic contains 31 replies, has 0 voices, and was last updated by Eric 3 years, 1 month ago.
-
AuthorPosts
-
January 21, 2015 at 2:16 am #183
not having luck..
Got my DUE.. flashed the master.cpp.bin as stated in your post..
connected it to my android device and it sees nothing.
I have a USB OTG cable
It does not detect the accessory
January 21, 2015 at 2:51 am #479Which side is the OTG cable hooked up? It needs to be OTG cable in the “Native USB” port, the one farthest from the power connector. Then the micro USB cable plugs into the OTG cable, and then into your Android device. It’s opposite of what t
January 21, 2015 at 3:17 am #504got it working.. I think my OTG cable has a issue.. but it works
I have another consistent issue though
-Connect DUE
-Set pin
-pin toggles
-Connect ALDL Cable
-Pin no longer toggles-Disconnect DUE from Android
-Connect to Android
-Pin Toggles-Discon
January 21, 2015 at 3:28 am #505I’m not sure what to suggest right now… maybe after I see the video I’ll have a better idea.
January 21, 2015 at 3:29 am #506More oddly acting items
above was using SIDE Menus
works fine if the buttons are the Home Buttons..
-Check Toggle (Side) working
-Check Toggle (Home) working
-Launched ALDL
-Pressed home
-Selected Autosense
-Press SIDE Toggle – Not working
-Press HOMEJanuary 21, 2015 at 3:34 am #507Hmmm, ok, well that’s good info. I will see if I can reproduce the issue.
With the firmware changes the color changing has been temporarily removed. It will be back. I’m trying desperately to get an Arduino IDE setup that doesn’t suck. I’m really hopiJanuary 21, 2015 at 3:38 am #508ok.. Glad the Color change is on purpose
here is the 2 buttons ( both control same LED)
Home works Side does not.. maybe your code is different between the 2?<a class="postlink" href="https://drive.google.com/open?id=0B5WZBOc_LAb4QjVzLVo2TVJy
January 21, 2015 at 3:48 am #509MORE:
if I unplug and plug in the ALDL Cable both buttons quit. in the car they will always be connected (Planned) I will power down and check again
Just realized.. I cannot test power off.. no memory for DUE
January 21, 2015 at 4:01 am #510That second video is helpful. I will see if I can pin down the error. At least since it works on the home screen means it should work everywhere. Just gotta find what’s wrong.
January 21, 2015 at 4:03 am #511One I test and make sure the new EEPROM code works I’m going to order up some boards. You can either buy one once they arrive, or you can wire up an EEPROM directly.
Also if you want, the old EEPROM I was using will work with your current setup, but buJanuary 21, 2015 at 4:27 am #513Well.. I am planning on getting this in the car next month.. the Arduino may or may not be installed then.. I have manual switches for what I am going to use the arduino for so it can wait
January 21, 2015 at 5:57 am #515Does the button error happen only with your ALDL program, or does it happen when you launch other apps and return? I’ve yet been able to reproduce, it’s working properly so far.
January 21, 2015 at 5:28 pm #517@eric wrote:
Does the button error happen only with your ALDL program, or does it happen when you launch other apps and return? I’ve yet been able to reproduce, it’s working properly so far.
Never tried other apps..
January 21, 2015 at 9:53 pm #519Can you try it without the ALDL connected? And also other apps. If you reproduce the problem with as little connected and running as possible that would help me a great deal.
January 22, 2015 at 3:53 am #520I can.. Give me a couple days. But it seemed fine as long as I did not manipulate the usb cables. I think it is something with android getting confused on which device is connected.
-
AuthorPosts
-
AuthorPosts
-
not having luck..
Got my DUE.. flashed the master.cpp.bin as stated in your post..
connected it to my android device and it sees nothing.
I have a USB OTG cable
It does not detect the accessory
Which side is the OTG cable hooked up? It needs to be OTG cable in the “Native USB” port, the one farthest from the power connector. Then the micro USB cable plugs into the OTG cable, and then into your Android device. It’s opposite of what t
got it working.. I think my OTG cable has a issue.. but it works
I have another consistent issue though
-Connect DUE
-Set pin
-pin toggles
-Connect ALDL Cable
-Pin no longer toggles-Disconnect DUE from Android
-Connect to Android
-Pin Toggles-Discon
I’m not sure what to suggest right now… maybe after I see the video I’ll have a better idea.
More oddly acting items
above was using SIDE Menus
works fine if the buttons are the Home Buttons..
-Check Toggle (Side) working
-Check Toggle (Home) working
-Launched ALDL
-Pressed home
-Selected Autosense
-Press SIDE Toggle – Not working
-Press HOMEHmmm, ok, well that’s good info. I will see if I can reproduce the issue.
With the firmware changes the color changing has been temporarily removed. It will be back. I’m trying desperately to get an Arduino IDE setup that doesn’t suck. I’m really hopiok.. Glad the Color change is on purpose
here is the 2 buttons ( both control same LED)
Home works Side does not.. maybe your code is different between the 2?<a class="postlink" href="https://drive.google.com/open?id=0B5WZBOc_LAb4QjVzLVo2TVJy
MORE:
if I unplug and plug in the ALDL Cable both buttons quit. in the car they will always be connected (Planned) I will power down and check again
Just realized.. I cannot test power off.. no memory for DUE
That second video is helpful. I will see if I can pin down the error. At least since it works on the home screen means it should work everywhere. Just gotta find what’s wrong.
One I test and make sure the new EEPROM code works I’m going to order up some boards. You can either buy one once they arrive, or you can wire up an EEPROM directly.
Also if you want, the old EEPROM I was using will work with your current setup, but buWell.. I am planning on getting this in the car next month.. the Arduino may or may not be installed then.. I have manual switches for what I am going to use the arduino for so it can wait
Does the button error happen only with your ALDL program, or does it happen when you launch other apps and return? I’ve yet been able to reproduce, it’s working properly so far.
Can you try it without the ALDL connected? And also other apps. If you reproduce the problem with as little connected and running as possible that would help me a great deal.
-
AuthorPosts
You must be logged in to reply to this topic.