What's the error you are seeing and which OS is your computer on?
I got it working - needed to shut down flash builder and restart... The
usual kill it and re-open did the trick.
Was no error, FB just reported it couldn't find a device...
I have the same problem, but the restart didn't work.
Anyone have some other advice?
Make sure you have downloaded and installed the 2.x components of the Android SDK:
This was not explicitly mentioned in the Sample Tutorial, but i found out in other blogs/forums. So your computer needs to have this installed separately even though Burrito comes with the android mobile app framework.
Follow the steps that Google provides and install everything you need, takes a while.
Then it will work - i also did a restart, but i think this was the real solution
Let me know how it works!
I installed everything Google wanted to, but it didn't work
Did you check my original post - make sure you have done all the things in the bulleted list.
Some other questions:
1. What phone are you using
2. What type of computer and OS are you using? I was using Dell desktop with Windows XP.
3. Get the IP address from your phone (go into wireless settings, etc..), and be sure your development computer can ping your phone. Even though you are connected via USB, you still need to be visible on the network.
4. Did you install the USB and droid drivers so the phone can communicate with your machine?
Other than that, i am not sure.
I had some problems in debugging mobile android app and the reason was that even the laptop and mobile phone was on the same wi-fi somehow they didn't get thru to each other....
What worked for me was that i turned the wi-fi tethering on( Nexus one ) and hooked my laptop to that....after that debugging started working like a charm.
I think that the wi-fi tethering is available in android 2.2 and later...
I did not have to do tethering on my Motorola Driod - but good to know that
is a potential requirement for other phones.
It's not a requirement but more of like a potential solution for debugging.
wifi tethering -> turns your phone to a wifi router to which a laptop can hook on to and there wouldn't be any strange rules to prevent your debugging.
Sorry I didn't answered earlier.
For some reason my company had all the USB ports blocked and Burrito couldn't write to the device.
I unblocked them and it worked fine
same problem here but I'm using the HTC Desire
I've installed the driver but FB cant connect to the device whether its on debug or run mode.
Windows 7 32 bit.
But does it still add your app to your device ?
and it keeps asking for the debugger location ?
nop, the .apk file doesnt get to the device at all.
I've tried running the app without connecting the device, the builder notified me that no device was connected, so I plugged it again and hit refresh. The device was recognised, I selected it but after running it again, still nothing on the device. :S
is your phone in debug mode ?
yep, the debugging setting is enabled. Flash Pro was communicating with my device perfectly! the problem is with Buritto for some reason.
maybe the usual restart burrito / pc would help...
or check the usb driver installation instructions from adobe site
..cant remember the url now but google...i think i remember that they had instructions how to add the newer android phonesto the usb driver support list...that might be the problem...
My problem, mentioned earlier, was that I did not have all the android SDK
files downloaded from google. This was not explicitly spelled out in the
burrito tutorials. This took a while to download and install, but that
solved it for me.
It just worked!
Looks like the device needed a restart. As soon as I did that it worked.
Good to hear...
It seems like people are talking about two seperate issues here. There are two main issue types that could be preventing someone from debugging:
1.) USB Debugging connection isn't working
2.) Wifi connection to the the actual debugger is failing.
For the first issue as long as your drivers are loaded (most drivers are included with Burrito and can be found in utilities\drivers\android under your burrito install directory) you should be fine. If you can run your application and have it install to the device and launch through burrito then you don't have to worry about issue 1.
For the second issue I still haven't been able to get past the initial unable to connect to the debugger screen that pops up and asks for an IP address, even though I can ping my computers ip from my phone and vice/versa. However I was able to view the debugging (trace) output from my application by installing the Android SDK and running the Dalvik Debug Monitor (ddms.bat in the tools dir of the SDK, useful for trouble shooting usb issues as well) . Unfortunately you still have to deal with closing the initial unable to connect window and burrito displaying connection timeout errors but at least you can see what's happening on your phone.
Not sure why the wifi debugging connection doesn't work the way it should, that's the only real unresolved issue as far as I can tell.
Unfortunately you still have to deal with closing the initial unable to connect window and burrito displaying connection timeout errors but at least you can see what's happening on your phone
Try disabling your firewall temporarily to see if it helps. My understanding is that the AIR runtime (on the phone) does a pure ICMP ping with a low timeout to determine whether to show the connection dialog or not.
On Windows 7, I've found that this ping fails even though adb shell ping succeeds. The AIR team is aware of this issue. (Though if your port 7935 is open, canceling the connection dialog connects you to the debugger eventually)
Just installed the Android SDK (win xp) and still unable to debug from my Nexus One.
The device is properly detected in FB, but shows nothing in the OS Version column.
FB also throws an error "Device's OS is not supported by AIR. Minimum supported OS version is 2.2 (Froyo)".
Seems like a bug in FB because I actually run 2.2 Froyo and AIR is installed on my device.
Anybody encountered that type of behavior?
Double check the OS, as I tried to debug/test on HTC Eris Droid, and it was
dropped from the Android update list - it is stuck forever at 2.1. I
thought it was at 2.2, then I checked and it never got the update.
If yours is really at 2.2 and you installed Adobe Air, check that your phone
is in debug mode and that it is connected to your wireless network.
Thanks pmcalenney1 for your quick response.
- OS is 2.2 under Settings -> "About this phone"
- Phone is in Debug mode
- Both my laptop and my device uses the same wireless network.
Also, please note that Flash Builder is showing the correct AIR version number installed on my device in the configuration menu, but nothing in the OS Version column.
Anything I might have missed?
Thanks in advance
I'm having a similar problem on a Samsung Epic 4G from Sprint, I updated to Froyo manually using an official release from google. For some reason my app (air.com.justinbuser.BuzeyTunes) doesn't show up in the market when I search even though Air itself does and my app runs fine on the device when I install the apk manually. I'm thinking there is some setting in the Android OS somewhere that indicates what the devices capabilities are that for whatever reason doesn't get updated when installing non service provider updates. Ergo I don't believe it's actually an issue with FB so much as an issue with the capabilities reported by the phone.
Interesting. How did you manage to export your Flex app to an apk? Using command line?
My Nexus One is brand new (Videotron), was coming with 2.2, and FB just won't let me export it correctly.
Could this be related to the USB drivers that comes with Flash Builder? Is there some updated version of the file?
Burrito builds the apk automatically every time you choose run/debug on device, it also builds an apk when you export release build. You did create your project using new->mobile application right?
If the fb founds the phone once selecting the target where to export, i doubt that it is the usb drivers.
Have you disabled the firewall ?
Yes it is a mobile application.
Thing is there is no way for me to run/debug on my device as FB detects lower than 2.2 Froyo and just throws an error.
Did you ever ran into this. Is there any other way to generate my apk file using Flex's SDK? (without Flash Builder)
I don't think it's a firewall issue, Lemtz are you able to click debug on device and have it successfully install and run on the device and connect to the debugger without the popup asking for an IP address? I've tried this on several different devices without firewall, with firewall ports opened, with several different wifi configurations etc... and have never seen this work properly.
but did you checked the firewall that the port is open ?
i remember watching a tutorial in adobe tv that showed how to make the apk packet in commandline....
Have you tried exporting a release build, that should generate an apk.
Yep i have debugged it on device and also made an release build and it works on the device.
i managed to go around the debug problem so that i set my n1 into wifi tethering and connect my laptop to it, since my work place has configured the wifi stations so that the debug info isn't going thru.
Have you tried that ?
So you are saying that you are connecting to wifi on your device and then tethering it to the desktop and using that for the desktop internet connection? I don't really see how that could work or would solve the problem simply for the fact that you can't have usb debugging and tethering enabled at the same time...
WellActually i do have....as i have understood that the fb deploys the apk file thru usb cable and the debugger connects to the fb thru wifi.What i am saying is that i connected my laptop thru usb AND thru wifi to the N1 phone.Well to be precise, i have my usb debugging and wifi tethering on in the phone.
Thanks guys for the suggestions. A few questions.
- Which port(s) should remain open for FB to correctly debug on device?
- When exporting a release build, in which folder of my device should I copy the file to test the app?
- How could Tethering be an option if both my devices are connected to the same Wi-Fi? Not sure to get that one.
- i just make a release build on my desktop and push the apk packet to my phone thru bluetooth... i guess that there is much more straight way method also but this is the way i have used to do it...
- Well the wifi tethering is an option in that case that the trafic in the above port is closed in the wifi router. so you basically connect the laptop straight to the phone , not laptop-> wifi router -> phone..
Thanks Lemtz, really appreciate your help.
Is there a specific folder to drop apk files on the device or you just drop them in the root?
I just add the files under downloads and open the apk file thru N1's browser->downloads...i think its quite fast way...there might be much more elegant way but its just something that i have used to.