For all the unknown reasons tonight, the system that accompanied me for two years was finally given to me. In the process of defragmenting the hard drive, it was found that the Android development environment was not available. Alas, the C-plate strokes of the child less hurt Ah, hard disk children more hurt AH. Simply on the whim of the Android development environment to build up, run a long-lost helloandroid program. I go, start incredibly full let me wait nearly three minutes ah, online some buddies said he waited n hours, ate a meal back results still in waiting for home .... Well, alas, sad and hurried:
I just started to think it was the first time the Android emulator was running slower, then turned off the simulator again, and the result was still ....Swaiiow instantly petrified, on-line search N multi-solution, and some said upgrade machine configuration, some said to increase the simulator memory, and some said tick choose what snapshot what east, not a reliable. Did I reload the system to bring down the performance of the computer? I broke my toes and thought, it's not a nonsense. At a critical juncture, you have to have your own hands. suddenly a thought flashed through my mind: after the Android SDK and AVD Manager was installed, it was the emulator created in the Android SDK manager, and tonight it was in eclipse after the Android plugin was installed. Will the simulator created by clicking on "Open the Android Virtual Device Manager" be related to this? With a try, I just open the Android SDK Manager and then open the Android AVD manager from the Android SDK manager to remove the emulator Testphone created in Eclipse. and create a new emulator with the same name, identical to the original configuration. Note: My Android SDK has been upgraded to the latest 20.0.3. The steps are as follows: first step: Go to the installation directory of the Androdi SDK and click Run SDK Manager.exe. Step Two: Run AVD manager from the SDK manager. Step Three: Remove the old emulator that was created in Eclipse and create a new emulator with the same name as the same configuration. The fourth step: the direct point of operation, do not have to choose, rumors will be untrue. when the emulator is running, open Eclipse and run the Android test program HelloWorld once. then, close Eclipse and Android SKD manager and AVD Manager, everything, then rerun Eclipse separately and execute HelloWorld, at which time the execution speed is as follows: actually more than 30 seconds to start up, the world is really too beautiful.
Waiting for home solution encountered in Android development debugging
