Summary of issues in the android Development Process

1. About error: please ensure that ADB is correctly located at in Android SDK 2.3 .....
Please ensure that ADB is correctly located at 'd: \ phone \ Android-SDK-Windows \ tools \ adb.exe 'and can be executed.

After the SDK is updated to 2.3, the following error may occur when the simulator is started using myeclipse:

[21:59:57-helloandroid] Android launch!
[21:59:57-helloandroid] the connection to ADB is down, and a severe error has occured.
[21:59:57-helloandroid] You must restart ADB and eclipse.
[21:59:57-helloandroid] Please ensure that ADB is correctly located at 'd:/android_develop/SDK/platform-tools/adb.exe 'and can be executed.

 

The solution is to add both the Tools Folder path and the platform-tools path in the SDK folder to the environment variable (my computer-right-click-advanced-Environment Variable-classpath ).

 

Adb.exe is put in the Tools Folder in version 2.2, but the platform-toolsfolder is added in Version 2.3, and adb.exe is transferred to this

Then restart myeclipse. If so, restart the computer. (Note: restarting a computer is sometimes necessary. I started to suffer from no computer restart)

Down vote I simply did "help"-> "check for uppdates" in eclipse. then I checked every update possible (I had 2) accepted, waited for the updates to complete, restarted eclipse and then everything was fixed!

I had some new build errors after the update, though, saying something like:

 

2. Warning: application does not specify an API level requirement!
Solution: androidmanifest. xml

Join:

<Uses-SDK Android: minsdkversion = "3"> </uses-SDK>

 

 

If your C:/Android-SDK-Windows/toolsdirectory does not contain the executable file "adb.exe.

When you open eclipse, the android plug-in reports an error.

In this case, you should do the following:

First, change your environment variables to C:/Android-SDK-Windows/tools:/Android-SDK-Windows/platform-tools.

(If the environment variable cannot be found, you do not need to set it)

Next, set adb.exe and adbwinapi under the C:/Android-SDK-Windows/platform-toolsdirectory. DLL, adbwinusbapi. DLL files are copied to your C:/Android-SDK-Windows/tools directory,

Copy other files to the C:/Android-SDK-Windows/platforms/Android-9/tools directory,

Now you have doubts. There is no tools folder in the C:/Android-SDK-Windows/platforms/Android-9 directory. In this case, you need to create a new folder, put them in it.

At this point, most of the work has been completed, and now you can restart your eclipse, but it will prompt you to update the android plug-in, then you will be OK as prompted.

3. activitymanager: Warning: activity not started, its current task has been brought to the front

 

This is not a bug of the Android platform, but a processing mechanism of Android itself.
On the Android platform, when we end a process through the return button or exit Operation of the program itself, the android virtual machine may not actually end the process, if the memory permits, this program will be cached in the android virtual machine. Only when the memory is insufficient, the android system cleans up tasks that are not activated for a long time and provides memory for other programs.
Android starts this program more quickly next time.
Therefore, when your program has not changed, and the memory is sufficient, the program will be executed in the previous time, from the cache cached status to the top of the task stack, your program can continue to run.