Hmmm. I am able to update and save this file. Do you have it open somewhere else or maybe have the SDK Manager or Virtual Device Manager running?
Sorry I can't be more helpful,
Senior Content and Community Manager
Have closed everything but still alert. I will try on another device and compare the settings.
B.t.w. - I am also unclear about No.6: Copy and paste a comment and hardware listing - where does each comment start and the listing end?
Is this the complete addition for Nexus 7 for example:
; Nexus 7
%CompositeAdbInterface% = USB_Install, NEW HARDWARE ID
I´d really appeciate your help - (for arts on the web).
Finally an installation package of drivers for androids from the developer site of android solved the problem:
There are instructions for different O.S. and Wndows Versions and the installation is commented.
Everything works fine now with Nexus debugging. Thanks.
I'm using Flash Builder 4.7. I've connected my ASUS Eee Pad Transformer Prime TF201, which is in the list of supported Android Devices. Drivers are installed and windows recognizes the device, and allows me to transfer files to and from the device no problem. However, Flash Builder does not recognize the device when I try to debug. USB debugging is turned on in the tablet. I've tried adjusting all the Developer settings on the tablet, but Flash Builder still will not recognize the device. Suggestions?
Make sure the device is not mounted as an external drive. Flash Builder/Android SDK needs to see your phone as a phone, not a mounted drive.
Let me know how it goes.
Creative Cloud Product Integration Manager
Thanks Randy, but that option doesn't seem to exist on this tablet. My only options are Media Device and Camera.
After some research it seems I'm not the only person having this problem with the TF201. I found this link which seemed to help MAC users having the same issue, but I still can't get it to work for Windows. http://nc-design.net/home/-/blogs/debugging-air-mobile-on-the-asus-tra nsformer-prime-tf201-
Hmm. That's odd. If you have the appropriate USB driver installed and haven't mounted as a Media Device, it should work.
I only have one more idea: Do you have the Android SDK installed? If so, navigate to the platform-tools directory in a command shell and issue an adb devices command. This will tell you whether or not the Android Development Kit recognizes the device. (Because Flash Builder not recognizing the device is really Android not recognizing the device).
My Samsung Galaxy S4 is doing the same thing to me... I cannot get Flash Builder 4.7 to recognize it at all, despite the fact that it does show up correctly in the Windows Device Manager -- it says "Samsung Android ADB Interface in the Device Manager, so Windows is clearly recognizing it correctly...
One thing I have noticed -- when I plug in the phone, it automatically defaults to "Media Device". There is no option to turn that off -- I can leave it either as a Media Device or switch to Camera mode, but there is no option to turn off the connection. It always shows up on Windows Explorer as an external drive, no matter what I do.
Where is this 'platform-tools' directory you're talking about? Where can I find the adb command? I can't find it anywhere in my Flash Builder 4.7 folder...
Thanks for any help you can give.
Mableton, Georgia, USA
The platform-tools directory is part of the Android SDK, which you download separately these days from developer.android.com.
And you might want to check http://stackoverflow.com/questions/16256048/eclipse-android-sdk-cannot -see-new-samsung-galaxy-s4-device-via-a-usb-connection. It sounds like a similar problem to yours.
Oh, yeah -- I've already done that. Developer Options is enabled, and I have selected USB Debugging... If I turn off USB Debugging, the phone doesn't show up as "Samsung ADB Interface" in the Device Manager -- it only shows up as an external USB drive in Windows Explorer...
I guess I'll try downloading the SDK and see if that will work...
Did you enable Developer Mode? It sounds weird to me, but this page describes the "secret handshake":
Let me now how it goes.
Well, typing "adb devices" from a command-prompt gives me no devices attached. So if the Android SDK can't recognize it, I'm assuming Flash Builder 4.7 never will... I'll report back if I figure out how to get the Android SDK to recognize it.