Real machine debugging, ios real machine debugging
After the environment is ready, we can finally start. I think the new person must be clear about debugging the real machine.
After all, because the computer does not have that much space, and I found that some avd is really slow to start, the installation of Intel atom x86 CPU is indeed much faster, but it is not very useful for beginners.
Therefore, I think it is necessary to use a real machine for debugging as long as there is an Android phone.
The debugging settings for the real machine are as follows:
Create an android program -- click run as -- on this project, and then see run configuration --. Then select always prompt to pick device on the target. (here, different eclipse versions may be different. the selection method is also different)
When the mobile phone is connected to the computer and the driver is successfully installed, you can run the cmd command to enter adb devices to check whether the mobile phone is successfully connected. If the driver is not successfully installed, new users are advised to directly use mobile assistants (such as the 360 mobile assistant computer version or other mobile assistants to install the driver) to install the driver, which is convenient and fast.
After the installation is successful, the device is displayed.
Run as select android application and then you will see the real machine window,
Select the mobile phone to see that the program is running on the mobile phone.