Couple things off the bat that I've found:
- Your device may not appear in the Active Profiler dropdown in the Unity Profiler after you launch Unity. Don't worry about that...until after you Build and Run and it still doesn't show. Then worry.
- When you have Development Build checked, and you do Build and Run, and then try to attach the profiler, Unity may freeze up. So, trying to profile or debug your Android app in Unity could freeze Unity 3.4.2f3 until you kill it with task manager. (Find those keywords, Google!)
Here's what I tell myself when I want to debug and profile my apps:
- First, make sure your Android is on your home network via Wi-Fi.
- Ping your Android device from the machine you're using Unity from. If you're not getting a response...then either your wireless setup is incorrect or there's a firewall in the way. I've never had firewall issues here. An improper setup can cause Unity to freeze up if you try to profile while the app is running.
- Go to File => Build Settings
- Check Development Build and Autoconnect Profiler. If necessary, check Script Debugging.
- If you need to see everything going on; like all the Debug.Logs and render statistics, go to Player Settings and check Enable 'logcat' profiler. (Later on I'll open a DOS window and run "adb logcat")
- Click Build and Run.
These steps got me going. I'm open to comments on other peoples' anedcotes or important things I'm probably leaving out.
Check out my homepage and news feeds
And my projects!
