i have an Ardunio mega ADK R3 and Samsung Galaxy S3 , i'am trying to control the LED at pin 13 using an application on galaxy using this tutorial:
http://allaboutee.com/2011/12/31/arduino-adk-board-blink-an-led-with-your-phone-code-and-explanation/
I've uploaded the Ardunio sketch , installed the application on galaxy , but when i connecting the galaxy to the Ardunio nothing happens and i'm not promoted to open the application on the galaxy , it's not even charging the phone ?
my question , if the phone not charging by Ardunio does it mean that there is a problem on the Ardunio board or this is an ordinary since the application on the phone not started?
i other words , if i connected the ardunio to the computer and then connected the galaxy to the ardunio without uploading or installing any sketch or application to android or ardunio and the galaxy not started to charge does this mean that there is a problem on the ardunio board?
I've tested the Ardunio ADK with Google Nexuses and the Ardunio works fine without any problem ,so there is no problem in the Ardunio board ,but after referring to "Beginning Arduino Programming" page 51>>
http://www.amazon.com/Beginning-Arduino-Programming-Apress/dp/1430237775
""
If you are experiencing that
nothing happens after you connected your device, check if your filter matches the values you defined in
the Arduino sketch. Another error source is that your board can’t deliver enough power to power the
Android device properly. As this is a requirement for the Open Accessory standard, make sure to power
the board with an external power source, if necessary.
"""
so it's seems that the Galaxy S3 consume a lot of power and Ardunio can't deliver enough power to it.
Related
I have compiled and signed the sample and it scans and connects flawlessly to the Microchip RN4871 on the Samsung Galaxy 3 & Alcatel Fierce XL. However, the scan does not find the RN4871 on either of my HTC's.
The HTC's can see the RN4871 in the settings -> Bluetooth menu, and will pair.
Even after this, the app still fails to find the device when it scans.
I plan on trying to get the mac address from the list of paired devices and trying to connect that way.
What kind of device specific issue could I be running into?
ANSWER: wow that was fast, but I had to turn on location services under setting->apps->"app name" then turn on location services
I have been using the Arduino board successfully, uploading sketches without any problem. I've got most of my project running - Stepper Motor shield and motor, IR LED, everything. I just can't get my Galaxy S3 to recognize that it is connected to the board so that I can complete my project.
I am using a 9Volt battery as logic power for the board and to provide power to the G S3. I have uploaded the proper drivers to the board using the demokit sketch distributed by Google.
I have the ADK 2012 App installed from the Play Store on my G S3.
When I plug in the usb cable from my Arduino ADK to the phone the phone acts like nothing is plugged in. When I execute the ADK 2012 app on my phone I get a message stating "Your ADK is not connected".
This is both with the stock Samsung microUSB cord and with a USB OTG cord.
This is a Model SCH-I535 Verizon Phone. Not Rooted. Running Android 4.1.2
I understand that there are potentially 2 problems with my combination of board and phone:
adequate power to supply both board and phone.
using the proper cord.
I think I've addressed both issues. I have searched for months for an answer to this problem. I'd hate to break down and get a tablet as I really want to get this to work with my phone.
Has anyone found a solution to this problem?
I have a Samsung Galaxy Gio and want to connect it to an Arduino Leonardo. I use the Stackable Bluetooth Shield 2.1 from ITead Studio.
It works with a Windows PC (I can send and receive strings with PuTTY), but my phone doesn't even recognize it - the Bluetooth device list is empty.
The strange thing is that a Galaxy S recognizes the Arduino immediately. And my phone can see all other Bluetooth devices - except the Arduino.
Why can't my Gio recognize the board, when all other devices work?
Well, I finally found the problem!
Apparently the Galaxy Gio with Android v2.3.6 has some problems with "special" Bluetooth devices - like Arduino boards.
I installed CyanogenMod (I think it's Version 7.1 or 7.2) on the phone and after that it had no problems recognizing the board. That's because CyanogenMod contains many fixes for Bluetooth and other problems.
Now I'm using ITEAD BT Debugging Assistant to send and receive strings from/to my board.
I tried to connect an Arduino Mega ADK using Demokit sources to several phones in vain.
I compiled and upload the Arduino sketch "Demokit.pde" with arduino 0022. It looks ok as the board sends "start" on its usb client port.
I compiled Demokit app under Eclipse using Google API 10 (for phones running Gingerbread) and Android API 15 (for ICS ones). Everything fine.
On the phone side, I tried these setups :
samsung i9000 running CM 7.1 and after pushing android.hardware.usb.accessory.xml and com.android.future.usb.accessory.jar
samsung i9000 running ICS
nexus S running ICS
And nothing happened. There's only a warning in the eclipse logcat :
W/PowerUI(654): unknown intent: Intent { act=android.intent.action.ACTION_POWER_CONNECTED flg=0x10000010 }
Nothing else. I wonder if the board can have a problem on its usb host...
If anybody has an idea?
Thanks
There are couple of places where things go wrong.
First to check the board, try running a simple blink program, to make sure that the board itself is working.
Next when you connect your to the board, does your phone starts to charge? This will show whether there are any issues with the phone-board connectivity.
Out of the 3 phones, I would suggest you to try with nexus S, with stock ROM, since CM (even after pushing the jars) has issues enabling ADK.
The problem came from the setup procedure in the Demokit.pde sketch. I used a bread board to run it but I didn't connect all components and the i2c joystick initialization needs the component to be connected otherwise the procedure goes into an infinite loop. So if you try to run Demokit.pde without the demokit board be sure to connect the right joystick, or comment its init procedure call.
The demokit example is actually rather complex for an initial test. I would suggest after running the blink program to make sure your Arduino Mega ADK is working to try a simpler first test.
There are a couple of good examples that are much simpler than demokit.
http://allaboutee.com/2011/12/31/arduino-adk-board-blink-an-led-with-your-phone-code-and-explanation/
http://digitalhacksblog.blogspot.com/2012/05/arduino-to-android-turning-led-on-and_29.html
Neither of these target an Arduino Mega ADK so some changes will be necessary but they should be a good place to start.
Unfortunately, the Samsung Galaxy Tab 10.1 I received at Google IO does not support accessory mode (http://stackoverflow.com/questions/6355031/how-can-i-get-the-adk-demokit-example-working-on-a-google-i-o-galaxy-tab-10-1). Which Android tablet currently does? I spoke with one of the Google engineer's at the conference who was running the DemoKit app on a tablet, but I didn't catch which one he was using, and whether that device was rooted or not. Is there a tablet out there running Honeycomb 3.1 that installs/runs the DemoKit app right out of the box without having to be rooted?
The adk stuff runs great on the Xoom, now on Android 3.2. I've been using both ADK accessory mode and USB host mode, and I haven't rooted it. The demoKit works great, although the Arduino-side can be a little tricky (usb host shield libraries) without an official ADK board.
Samsung Galaxy 10.1 Tab with updated Android 3.2 works fine with Google ADK board. I could see all sensors working fine. My issue is to get the tab work with Arduino Mega ADK.
I got the simple demo's working on the asus eee TF101, android version 3.2.1
I do have a bit of weir behavior that the android app wants to force quit a few times and the connection to the adk is not made immediately (can't choose to have the accessory connect to the app from a list the tablet pops up), but after a few times back and forth between the app and the home screen (through several 'force quit' dialog boxes), I do get the option to connect the accessory (ADK board) to be connected to the example app and then it all works as wanted.
I do have the same behavior on a Nexus One phone, so I'm guessing there may be something not quite right in my SDK setup.