Cause: the locking mechanism of AVD is used. . Lock is a lock. If the program crashes or is not normally exited, the lock cannot be cleared. this problem occurs in the folder at the end of lock, that is, the AVD lock is not released, causing AVD manager to think that the AVD is in use. By default, the simulator is locked and the resource is occupied.
Solution:
1. WINXP:
C/Documents and Settings/user /. android/AVD/* Device */(for example, my directory is c: \ Documents ents and Settings \ Administrator \. android \ AVD \ android2.0.avd)
Then delete. the folder at the end of lock (I will explain why to delete these files, in fact. lock is a lock. If the program crashes or other causes, it cannot be cleared. this problem occurs in the folder at the end of lock, that is, the AVD lock is not released, causing AVD manager to think that the AVD is in use .)
2 /. Win7:
C/user/. Android/AVD/find the AVD corresponding to the simulator in the directory, and then delete the. Lock file.