Wednesday, 17 July 2013

RenderServer::create failed to listen.it seems too many emulator instances are running on this machine. Aborting

If you have Windows Firewall (or another software firewall) active, try temporarily turning it off and then running the emulator. If that clears up the problem, then you need to teach the firewall how to open up the ports the emulator needs.

Sunday, 14 July 2013

What is an Pending intent ???

A PendingIntent is a token that you give to a foreign application (e.g. NotificationManager, AlarmManager, Home Screen AppWidgetManager, or other 3rd party applications), which allows the foreign application to use your application's permissions to execute a predefined piece of code.
If you give the foreign application an Intent, and that application sends/broadcasts the Intent you gave, they will execute the Intent with their own permissions. But if you instead give the foreign application a PendingIntent you created using your own permission, that application will execute the contained Intent using your application's permission.

Tuesday, 9 July 2013

Failed to rename directory tools to temp\ToolPackage.old01 in C:\android-sdk-windows



There are two solutions.Please it .it may help you.
1.Make a copy of the \tools folder, name it something like \copy. So you should have c:\android-sdk-windows\copy. Now run android.bat from the \copy folder with Admin privileges. This should prevent the issue with items currently being open in the \tools folder.


2.This is due to a zip folder named *tools_r21-windows* is created inside temp folder during update of your Android SDK. To remove error like that simply unzip this folder and paste inside your main Android installer folder(commonly named as android-sdk-windows).

Friday, 5 July 2013

unable to execute .dex file Multiple dex file are defined:

To resolve the problem like:-
unabletoexecute .dexfileMultipledexfilearedefined:

I pinpointed the cause of the error to /bin/classes. If I deleted the /classes dir before running the app, the app would compile and run. Of course, when I tried to actually export the app, the /classes dir would come back and along with it the error.
The solution to my problem was to install the latest version of Eclipse. When I export or run the app through the latest installation of Eclipse, the /classes folder does not appear now.