Android SDK installation doesn't find JDK

  11:02 AM            No comments

Problem:
Trying to install the Android SDK on my Windows 7 x64 System. jdk-6u23-windows-x64.exe is installed, but the Android SDK setup refuses to proceed, because it doesn't find the JDK installation.
Is this a known issue? And is there a solution?
SDK Error

Solution:

Press Back when you get the notification and then Next. This time it will find the JDK

May be sometimes this do also


Install the x64 JDK, and try the back-next option first, and then try setting JAVA_HOME like the error message says, but if that doesn't work for you either, then try this:
Do as it says, set JAVA_HOME in your environment variables, but in the path use forward slashes instead of backslashes.
Seriously.
For me it failed when JAVA_HOME was C:\Program Files\Java\jdk1.6.0_31 but worked fine when it was C:/Program Files/Java/jdk1.6.0_31 - drove me nuts!

and Dont Forget to do this too.


Found the solution and it's beautifully stupid. I found Android SDK cannot detect JDK.
Press the Back button on the SDK error screen that tells you that the EXE couldn't detect the JDK. Then press Next.
Who would have thought that would happen?

From Stack OverFlow: http://stackoverflow.com/questions/4382178/android-sdk-installation-doesnt-find-jdk


Android Debugging Tips

  10:56 AM            No comments


I can't see anything in the LogCat or otherwise useful information elsewhere to find out what's gone wrong.
Look harder. Every crash generates something in LogCat.
The only thing I see is some kind of exception.
That would be "what's gone wrong". The stack trace will show you the line of code where your bug resides, and the exception will give you information about what has gone wrong.
This is unacceptable and makes Android programming nearly impossible
Tens of thousands of other developers do not have a problem with this. And, since the same thing occurs in Java applications (exceptions and stack traces), millions of developers worldwide have not had a problem with this. Logged exceptions with stack traces are also used in many other languages and are considered a rather commonplace technique in software development.

Aanswers gives by http://stackoverflow.com/users/115145/commonsware

Solution: Android INSTALL_FAILED_INSUFFICIENT_STORAGE error.

  2:48 AM            No comments
 Eclipse will sometimes say this:
[2010-11-20 11:41:57 - My Cool Ass Application] Installation error: INSTALL_FAILED_INSUFFICIENT_STORAGE
[2010-11-20 11:41:57 - My Cool Ass Application] Please check logcat output for more details.
[2010-11-20 11:41:57 - My Cool Ass Application] Launch canceled!

This is cute and utterly annoying. In fact, this has caused me to completely give up on coding boated Android/Java for the day on a few occasions. waiting for the AVD to reboot – sucks. This Google Groups post says to restart the emulator. Yeah, thanks Google. At first I gave the emulator the benefit of the doubt and thought, “hey, my app has an mp3 compiled into it making it rather big (12MB), maybe I should move the mp3 to the SD Card upon installation or put the mp3 somewhere online and stream it to the system. Then I clicked on

Settings->Applications->Manage Applications and the Android AVD said this:

You do not have any third party applications installed.
After hours of research, I figured out that this error means nothing at all. If you reattempt to upload your project (CTRL+F11) it will not solve the non-existent error. This means that you need to either restart the AVD (Android virtual machine you are testing the project on), or sometimes it gets so bad you need to restart the emulator too. If you still get it, you need to delete the AVD and create a new instance:

Window->Android SDK AVD Manager->Delete->New...

Sometimes the Error console will say that it just brought the old version to the front screen! This is AFTER you tell the IDE to upload and install a new version. How disrespectful!

Speed is another thing to consider. I use CTRL+F11 to hurry up and upload the app to the device and run it. If you edit your XML file to say wrap the contents of the LinearLayout tag in ScrollView tags, this causes Eclipse to slow down to a crawl. Not only that, the project will be loaded into the emulator AVD and you will see a nasty red X next time you go back to the XML to view it and not know why it’s there. – Take your time with this gigantic Cthulhuian slow IDE.
Or 



>

You need to increase the Android emulator's memory capacity, there are 2 ways for that:

1- Right click the root of your Android Project, go to "Run As" then go to "Run Configurations..." locate the "Android Application" node in the tree at the left, then select your project and go to the "Target" tab on the right side of the window look down for the "Additional Emulator Command Line Options" field (sometimes you'll need to make the window larger) and finally paste "-partition-size 1024" there. Click Apply and then Run to use your emulator.

2- Go to Eclipse's Preferences, then Select “Launch” Add “-partition-size 1024” on the “Default emulator option” field, then click “Apply” and use your emulator as usual.

Want to see more details about this problem click these links 

1.   http://stackoverflow.com/questions/6788996/installation-error-install-failed-insufficient-storage-during-runing-emulator
 2.    http://stackoverflow.com/questions/4709137/solution-android-install-failed-insufficient-storage-error
3.      http://stackoverflow.com/questions/5359766/i-have-enough-memory-but-am-getting-the-install-failed-insufficient-storage-erro 
4. http://stackoverflow.com/questions/2239330/how-to-increase-storage-for-android-emulator-install-failed-insufficient-stora
5. http://groups.google.com/group/android-developers/browse_thread/thread/920db96745cff96f?pli=1

Sources: http://google-androidlovers.blogspot.com/2011/07/solution-android-installfailedinsuffici.html

The DDMS Perspective

  12:18 PM            No comments

The DDMS Perspective in Eclipse lets you access all of the features of DDMS from within the Eclipse IDE. The following sections of DDMS are available to you:
  • Devices - Shows the list of devices and AVDs that are connected to ADB.
  • Emulator Control - Lets you carry out device functions.
  • LogCat - Lets you view system log messages in real time.
  • Threads - Shows currently running threads within a VM.
  • Heap - Shows heap usage for a VM.
  • Allocation Tracker - Shows the memory allocation of objects.
  • File Explorer - Lets you explore the device's file system.
To access the DDMS perspective, go to Window > Open Perspective > DDMS. If DDMS does not appear, go to Window > Open Perspective > Other ... and select DDMS from the Open Perspective window that appears. For more information on using DDMS, see Using the Dalvik Debug Monitor Server.

  

“Debug certificate expired” error in Android plugins in Eclispe

  12:05 PM            No comments
Problem: 
Error on Console

[2013-01-03 10:31:14 - androidTest]Error generating final archive:
 Debug certificate expired on 1/03/13 12:35 AM!

Solution:- 

Solution 1:

Delete your debug certificate under ~/.android/debug.keystore on Linux and Mac OS X; the directory is something like %USERPROFILE%/.androidon Windows.
The Eclipse plugin should then generate a new certificate when you next try to build a debug package. You may need to clean and then build to generate the certificate.


Sometimes, it works for this solution, sometimes it doesn't. 

  •  Project-> Clean the project.->Close Eclipse-> Re-open Eclipse.
  •  Start the Emulator. Remove the Application from the emulator.

    Sources: Stackoverflow.com
    • Subscribe to: Posts (Atom)