I am using Adobe Flash CS5.5 to develop flash air applications on Android. However, I just can't seem to get my phone visible to Flash.
I have a Samsung Galaxy GT-N7000 (Galaxy Note). I have rooted the phone with cyanogenmod 10.1.3-n7000. I have enabled "usb debugging" in the phone settings.
I'm running this on Windows 7 Professional 32-bit.
When I connect my phone to the PC, I am able to see it as GT-N7000 under Device Manager -> Portable Devices heading. I am also able to copy files to/from this device without any issues.
The adb version installed on my system in the flash installation folder is 1.0.26. When I try to run the flash animation on my phone, it can't seem to detect it. I get the error message
"Could not find an android device to connect to. Please ensure that you have the phone connected, the correct drivers installed, and the phone has USB device debugging enabled".
I'm at a loss for how to install the usb driver, as mine is a galaxy note, but is using cyanogenmod. I couldn't find the SDK manager in the flash installation folder, but ran the SDK manager from the android-sdk folder which I have parallel installed for developing android applications using Android Studio. I installed the Google USB drivers from that location. I'm not sure if this will help Flash detect the phone.
I have also tried using the usb connection mode as MTP, PTP, as well as mass storage. But no difference.
What else could be the issue? Any pointers? Please excuse me if any details are missing. I'll add them as they are pointed out.
UPDATE: Found a similar query at Android Device Connectivity in Adobe Flash Pro CS6 Win7 x64.. However, doesn't work for me! :(
Workaround (well, sort of!):I am able to copy the .apk file to the phone memory, and then install it. I had to enable "Unknown Sources- Allow installation of apps from unknown sources". However, I am still not able to publish directly to the phone, nor am I able to debug it from Flash.
Solved it! Since Flash connectivity didn't seem to be working, I thought it better to see if I can at least make Android Studio work with my phone. Tried all the stuff possible, including using the SDK Manager to install the Google USB Driver. Nothing worked.
Since my phone IS a GT-N7000, but with CyanogenMod, I thought that the Samsung USB driver wouldn't work for it.
Finally, after trying a lot with all the other methods, I did the simplest thing possible. Found the Samsung GT-N7000 usb driver (downloaded from the mirror link in this XDA forum post http://forum.xda-developers.com/showthread.php?t=1755001), installed it, and EVERYTHING started working! Flash, Android Studio, etc!
For those who don't want to download just the drivers, or are hesitant to download from unverified links, you can download and Install Samsung Kies, and it'll do the required installation of correct driver!
Duh! Sometimes, the simplest things are the only steps required!
NOTE: Please see my first answer for a simple way to solve this. If this doesn't work for you, you can try the steps documented here.
I'm posting follow up problems and how I resolved them. Since this update was rather long and might not occur for others, I have posted it as a separate answer. It is still pertinent to this question, so I have kept it as an alternate answer.
**
Moderators: please let me know if there is a more elegant way of doing this, and I will do the needful.
**
UPDATE: I had uninstalled Flash for some reason, and re-installed it again after two months or so. However, I found that I was unable to publish to the phone after this. Resolved it finally as below.
Sometimes, even after the device drivers get installed, and show up in device manager as an adb interface, you might not be able to publish to the phone. Ensure that you have enabled "developer options" in the phone, and that "USB debugging" option is enabled. This might solve your problem.
However, in my case, this didn't work. Flash was just stuck at the "Publishing" phase, and didn't proceed to launch my project on the phone.
In such a case, open up a command prompt (in windows) and query the devices using the command "adb devices".
If the device shows up as "offline" status, try connecting the phone to another port. Again, this too didn't work out for me.
Finally, I updated the Platform SDK on my machine using the "SDK Manager". Once updated, I re-ran the command "adb devices" on the command prompt, and voila! The phone is now listed properly without any "offline" status.
Now the problem! The problem is that Flash CS5.5 uses an old version of the Air runtime (which comes with it's own version of adb.exe). In order to update this, I downloaded the latest version of AIR SDK from http://www.adobe.com/devnet/air/air-sdk-download.html. However as Flash 5.5 doesn't have a straight-forward way to use the latest version of the SDKthere were some steps that I had to follow to do so. The original document is at http://code.tutsplus.com/tutorials/enable-the-latest-air-sdk-in-flash-professional-cs55--active-11488, but I am inlining it here based upon my own changes to the steps mentioned in the web page, as well as to ensure that these steps don't become dead links later on.
Step 1: Download the Latest SDK
Download the latest AIR SDK from the following link: http://www.adobe.com/products/air/sdk/
Extract the downloaded file into a separate folder on your desktop
Step 2: Backup Your Current SDK Folder
Go to the Adobe Flash CS5.5 installation folder (
should be "C:\Program Files\Adobe\Adobe Flash CS5.5" on 32 bit Windows,
"C:\Program Files (x86)\Adobe\Adobe Flash CS5.5" on 64 bit Windows, and
"Applications/Adobe Flash CS5.5" on OS X).
Rename the AIR2.6 folder to AIR2.6_OLD.
Create a new folder and name it AIR2.6.
Step 3: Create the New SDK Folder
Copy the contents of the latest AIR SDK folder (that you’ve created on your desktop) to the AIR2.6 folder.
Browse to the AIR2.6/frameworks/libs/air/ folder in the Adobe Flash CS5.5 folder and copy the airglobal.swc file.
Paste the SWC file into Adobe Flash CS5.5/Common/Configuration/ActionScript 3.0/AIR2.6/, overwriting the existing airglobal.swc file.
Step 4: Final Configuration Settings
Go to Adobe Flash CS5.5/Common/Configuration/Players/ and open the following files using a text editor
(you may need administrative privileges to edit these files in the application folder in Windows):
AdobeAIR2_6.xml
AiriPhone.xml
Android.xml
NOTE: Player element and how to point it to the right version. Go to https://helpx.adobe.com/air/air-releasenotes.html and start counting from
2.6 version as 11, to the version updated by you, incrementing every time you see a "user release notes" for each version. For easier reference,
version 19 should be considered as version 30.
Change the version attribute of the player element from 11 to this calculated version (30 in my case) in each file.
Don’t forget to save them after you’re done editing.
Restart Flash, and try publishing to the phone. It worked for me! :)
Related
I have recently bought a HTC Nexus 9 tablet for the purpose of USB debugging in Android Studio. This process works on other computers at university but I cannot get it to work properly from my home system,which is what I require. I have tried every single suggestion I have came across online but none have actually worked.
Steps Tried:
Downloading the latest google USB Driver
Installing it through Android Studio and Manually in device manager
Tried ADB Interface Driver and ADB Composite Interface Driver
Configuring driver inf file by adding hardware ID's
Ensuring usb debugging is enabled on the device
Using different USB ports,3 different cables
Tried connecting in PTP mode,MTP mode,charging only mode
Rebooted device and computer
Re installed android studio
No matter what I do,the device wont be shown in android studio or ADB.exe(under list all devices in terminal,also tried start and kill server). I am officially out of ideas,if anyone could figure this out I would be forever grateful!
I have attached some images of some of the things I have tried without success. Once driver has been installed it is listed as "Android Composite ADB Interface" or "Android ADB Interface". Operating system is Windows 7 64-bit
Device on first plug in
Picking a driver
Download HTC PC suite from following link ,install and give a try
http://pc2.software112.com/getfreesw/231109-1805719/htc-pc-suite-07.html
I personally have had many issues with setting things up for Android. Things you should ensure you do include;
Ensure you obtain the appropriate packages in the SDK manager - for example, I wasn't able to make logcat work when debugging with my phone until I downloaded the files for my specific version of Android (so the API files for a Nexus 9).
I believe you may also have to download drivers for your actual phone to allow connection - you should be able to download this from the HTC website. This might be what you need, although I haven't checked it out, and I cant find where I downloaded my drivers from;
http://forum.xda-developers.com/showthread.php?t=2217396
In general, you want to download lots of things from the SDK manager as you'll need them anyway, so don't hold back on just downloading them.
For those (like me) who is still concerned with this issue. You need to go to win+pause break ->Device Manager->Find "AdbInterface" with exclamation sign->Update driver->Search manually->Specify USB driver downloaded from SDK and enjoy: C:\Users\username\AppData\Local\Android\Sdk\extras\google\usb_driver
Just yesterday I updated Android Studio. Before I updated it everything was working fine, meaning I was able to use my Samsung Galaxy S4 to debug my apps with no problem. After the update, Android Studio no longer sees my device when I try to debug.
Furthermore when I type in adb devices on my terminal (I am using Ubuntu), my device doesn't show in the list of devices attached. Please help! I'm been trying to find a solution but most only talk about reinstalling drivers for Windows users.
Also, not sure if this may help but when I updated Android Studio, I was prompted to move the SDK folder to another location.
Thanks ahead of time!
Google's usb driver is located within the Android SDK folders, so perhaps in moving that, your computer can not find the driver anymore.
Try going to Device Manager (the windows one from the Control Panel), look for your mobile device and choose to re-install the driver, choosing one from your own disk.
It should be located at ~\android-sdk\extras\google\usb_driver
I got a new Gingerbread phone to try to develop on, but Eclipse won't recognize it.
I put it into debug mode already.
The Win7 Device Manager shows a problem with 4 Qualcomm HSUSB devices, this is certainly related to the phone.
Windows update is unable to find any updates for it.
I couldn't find any drivers support downloads from BLU either.
About the phone:
Andriod version: 2.3.5
Kernel version: 2.6.38.6-perf
Hardware version: A5.V1.2
Build number: BLU_D170_v03_GENERIC
Did you try using the Google USB driver?
For me, in device manager, I had an unknown device listed as "Android device" with a yellow exclamation point over it. Right click it, then choose update driver software. Then choose browse my computer, then choose let me pick from a list of devices...
Then click the Have disk button, and point it to the google usb driver (this should be downloaded via the SDK manager). It will be in the folder where your SDK stuff gets downloaded in the /extras/google/usb_driver folder. When browsing, select the inf file in this folder.
You should get three options that pop up, choose Android ADB Interface. It will then install the generic usb driver so you can connect your phone to ADB.
Note: I have the BLU Dash 4.0, but the driver should work on just about any android device.
First of all, are you able to transfer data to the phone normally? If you can, don't bother with the second part below.
If you can't transfer data, look at this second part. When you bought the phone, did it come with a driver disc? If it did, install the drivers from there. If it did not, try checking the official manufacturer site to see if there's a driver online.
I managed to make contact with BLU service, and they e-Mailed me a driver that only works on 32-bit Win7, not 64-bit :-(
I figured out that I can still test my apps on my DASH 3.5 by uploading the .apk file to a webserver & using the phone to browse to that link. Android will recognize that .apk is an app file it can install. So you could also distribute your own apps to anyone this way, without using any of the Android stores|markets at all.
I've done a bit of research since my previous question was not considered question. I have nexus 7 to use it with Flash Builder 4.6.
I initially downloaded Android SDK and installed the Google USB driver. I turned on the debugging option for my nexus, and I also made USB computer connection to PTP connection.
Finally, I run an app from Flash Builder I get the following screen:
I try to uninstall adobe air and re-install but it didn't work. Please, I need your help. My laptop is windows 7 OS. I also run command line and checked my platform-tools and run adb devices.
It recognizes my nexus is attached with its serial number and ‘device’ word. One more thing, the nexus connection also show the device is charging.
I was having the same issue. As user user1986244 said, I had to do some moving around of executables.
I placed all the .EXEs (adb.exe and others) as mentioned into the
<FlashBuilderDir>\sdks\4.6.0\lib\android\bin folder, but, I also had to place them here:
<FlashBuilderDir>\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\android\bin
It then asked me to install the AIRSDK and my application began working.
I'm assuming there is a more elegant solution here, but, I've yet to find it.
For two days, I try to find solution. Finally worked. I want to go through the steps. After installing android sdk that comes with ADT bundle. Running sdk manager. Check Tools and google usb driver from options list. My device is nexus seven. Then I installed Flash builder 4.6. I created simple Hello program, and run. But gave me screen 'adobe air not installed' and state 'offline', as I mentioned in my initial question above.
Next, I read a post from adobe forum help, that says copy adb.exe from android ADT folde and paste it to flash builder. My actual path goes like this in the ADT folder sdk/platform-tools/adb. So I copy adb and went to Adobe flash builder 4.6 folder/sdks/4.6.0/lib/android/bin. In this folder i pasted what I copied, pop up message says you cant paste it is open. Instead of making it skip. I ctrl + alt + delete and close adb.exe from applications. Now, I went back and clicked try again. It pasted it
Next run my android test, it asked me 'would you like to install adobe air?' on your device. I clicked yes, then it worked.
You may have to install drivers manually
http://fr.asus.com/Tablet/Nexus/Nexus_7/#download
Then allow usb debugg on your device
Like LordJalek said, I had to copy adb to these two folders. If those folders does not exists locate them from Flash Builder preferences. Then I was neccessary to restart adb:
adb stop-server
adb start-server
Then when I clicked on refresh on the "Choose Device" screen it worked and now I see my device online.
If I write an application using the Android SDK or NDK, can I simply copy the APK produced onto any Android phone (with the right version of the OS running) and run it? Or do I need to root the phone before apps not bought through a marketplace can run?
The context is that I have the choice of a Galaxy S2 as an upgrade to my iPhone4 and I'd like to start writing my own stuff. I can find plenty of instructions and examples of compiling and running apps in the emulator, but nowhere explicitly states I can run the apps I compile on the S2. I'm worried that apps may need to be signed or authenticated before they can run on it (and other phones) and I'd rather not mess about with the phone too much.
You can download it and run it without root.
You can debug directly on a device even from your development environment.
Android development tools environment (ADT) in eclipse (as well as others) and the correct ADB USB drivers for your phone gives you that nice option. Much faster than using the android emulator too.
In settings you have to allow debug (a simple checkbox), that is all.
No you don't need to root. Just install drivers and SDK. Using eclipse you can directly run on device and debug too
it's also faster than working on emulator
If you get Galaxy S2, then you can install Samsung's own free app, "Kies Air". This allows you to transfer files over wifi from your PC to anywhere that you can see in the phone's file explorer. If you transfer an apk this way, then when you click on it in the phone's file explorer, it will install the app. The app can be signed with a debug key, or a release key.
You don't need root. In order to instal on android phones you simply install the app on the phone through eclipse ADT tool or just through the ADT terminal. Just remember to set the phone to development mode by going into settings -> programs, then allow installing from unknown sources.
Alternatively if you want to install the *.apk on you device download an app from market. Follow this link for guides on both this approach and the SDK/debug approach: http://www.talkandroid.com/guides/beginner/install-apk-files-on-android/