George McKinney Adventures in Software Development

December 24, 2010

Getting Debugging Working in Flash Builder Burrito on an HTC Evo

Filed under: Android,Evo,Flash Builder Burrito,Flash Debugger,Flex,Google,HTC,Mobile — georgemck @ 2:15 pm

Getting Debugging Working in Flash Builder Burrito (Flex 4.5) on an HTC Evo requires Android 2.2 froyo or higher

#1) Make sure you have the HTC Sync Software installed on your computer. This contains the drivers necessary for the Flash Builder to recognize the device when it is connected via USB. The software can be downloaded from: http://www.htc.com/www/SupportViewNews.aspx?dl_id=1062&news_id=806

#2) Inside Flash Builder Burrito, Select Run, Debug Configurations and then select On device. You should see “Deploy the application to the device over USB” After you click on Debug, you may see something about the server being misconfigured. That is if you specified a server that the app needs to connect to, just be sure it is reachable by the app while running on the phone. Otherwise remove it because Flash Builder will probably stop you from going further. It may take a moment or two for the app to launch. First you will see the screen go black, then you will see the app launch on the device. Next, you will see the Console in Flash Builder load your swf file. Hooray, debugging is now working.

#3) If you are on Windows and cannot connect, you may have to open port 7935 in your software firewall. Flash Builder uses it to communicate via WiFi to your device. To get to the Windows Firewall, click on the Start Menu button, then go to Control Panel and click on Windows Firewall. You should disable both inbound and outbound protection. Then click on Advanced Settings. Add an inbound and an outbound rule that opens port 7935. There may be a Domain Firewall, Private Network Firewall and Public Network Firewall. Also examine the individual rules in the Firewall to make sure they are not conflicting with Flash Builder.

#4) Don’t forget you may also need to check that your router also allows you to communicate over port 7935, too.

#5) If you try to re-debug the app and nothing happens, it may be because the previous instance is still running on the device. In this case, go to settings and then Applications and go to Manage Applications on the device, and force stop the old app and Clear the Cache and try again. Best practice is to click on the reb box in the Console to stop debugging and kill the running application on your device completely.

If you see a window pop-up asking you for the IP address of the computer running Flash Builder, Force Stop again and Clear the Cache. If it looks like there is nothing to clear, go back out to the Manage Applications section and then go back to your app. Try clearing the cache from that point and re-run your application. Good luck!

Useful Adobe URLs:

Connecting Google Android Devices
http://help.adobe.com/en_US/flex/preview_release/mobileapps/WSa8161994b114d624-33657d5912b7ab2d73b-7fdf.html

Running mobile applications
http://help.adobe.com/en_US/flex/preview_release/mobileapps/WSa8161994b114d624-33657d5912b7ab2d73b-7feb.html

Debugging mobile applications
http://help.adobe.com/en_US/flex/preview_release/mobileapps/WSa8161994b114d624-33657d5912b7ab2d73b-7fe5.html

December 15, 2010

Google Chrome

Filed under: Chrome Browser,Google — georgemck @ 11:52 am

If you use Chrome already, just install it for this week.

Chrome for a Cause

Every tab you open this December 15 through 19 will serve a good cause.

Join the cause
Install the Chrome for a Cause extension to participate. Each tab you open will raise money for charity.
Contribute your tabs
At the end of each day, choose one of five charities to support.

Learn more about Google Chrome »

Powered by WordPress