Hello, I understand from the documentation that an adb wait-for-device only blocks until the device is online, and it does not wait for a full boot of the application per the docs here:
http://developer.android.com/guide/developing/tools/adb.html#devicestatus I see that when I launch an emulator from Eclipse, there is a line in the console output that reads: Waiting for HOME ('android.process.acore') to be launched... Which seems to wait for that process to start before uploading the .apk file and running the Activity. I'd like to be able to do this programmatically in Ant as we are trying to automate some instrumentation tests. I can do an adb shell ps continually to check for the existence of the android.process.acore process to show up, however this adds a lot of complexity in the Ant build (can't run exec under a waitfor, and running exec multiple times is problematic due to write-once properties). Does anyone have any suggestions for a better way to detect this state in an Ant script? Not sure how ADT in Eclipse does it but it seems to be relatively straightforward. Thanks, Adam -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
