oh god i hate SO MUCH this sdk thing.
I just want to build a game made with Unity, i need androids sdk.
sdk manager alone is in console so not really for standard human. i tried but it didn't worked. the sdkmanager console open and close at speed of light.
I downloaded Android Studio to use the UI and the sdk manager embeded.
I deleted anything related to Android to make a clean install.
At startup, Android Studio ask for wish component i would like to download.
It show me all what i want but i CAN NOT CLICK on these damn things.
Then after installation it says there is no SDK (really?) and it show me what is missing but refuse to install it. still can't click.
I deleted all config files and reinstalled and retried 5 or 6 times.
just want to smash the screen. at least 5 hours lost and it goes on.
Everytime i do SDK it always goes wrong. its a nightmare.
If you want install it for Unity - you just need to install Android Studio. Then just go to Unity, click to "SDK: download" and it will automaticly download it.
So for me the answer was to delete and recreate Android/sdk folder. make sur it is empty.
Related
I have downloaded the latest android studio bundle from android site. Installation was successful, but when I run it for the first time, it shows a window in the screenshot with message "Downloading Android SDK Tools, revision 24.1.2" and then it hangs on infinitely.
When I click on cancel and then show details, the message in attached screenshot appears. This dialog never disappears even on clicking the close button. I have to end it from process manager.
I was wondering if anyone has been able to make it work.
To disable "Downloading Components" at startup,
Go to the installation directory of Android Studio.
There you will find a folder named "bin".
Inside this folder there is a file named "idea.properties".
Open this file and add the following line to the end of the file:
disable.android.first.run=true
What this will do is disable the check that Android Studio performs on first run and decides to download all that stuff.
If it asks to save the file at some different place instead of overwriting the original one, please check the access permissions to the file.
To me it has worked perfectly. You have to download all data for the sdk and can be several GB and can take a long time depending on connection and repositories
If you got stuck earlier and left in middle of download, this may happen
Just go to
C:\Users\Username\AppData\Local\Android
and delete the SDK folder and now try again.
It's actually a bug with the Setup Wizard. See more here
You could try to download the previous stable release: 1.0.2 or 1.0.1.
EDIT
After further testing, apparently if you force close adb the wizard continues normally.
its not stuck. its actually downloading some tools.
if we download like this or through SDK manager.exe the speed is limited.
so it will take much time.
so i tried to open it without internet connection and it showed me some missing tools.
(andoid sdk tool 21.1.1 )
i had 21.1.2 installed but it still showed this. so i manually downloaded it from
internet ( here you will get your max download speed). and placed it with 21.1.2 installation file.
and now it all works.
ps:it was the only file i missed. it won't be the same with everyone
it is a reported bug and I am facing it too in version 1.2.0 see this
Components of the SDK are continuously released and Android Studio's updates aren't very frequent.
You can update the components manually with SDK Manager.
Go to C:\Users\Username\AppData\Local\Android\sdk
Open SDK Manager.exe
Update the packages.
Start Android Studio.
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
I am a beginner to android development,I have downloaded adt-bundle-windows-x86_64 with android 4.2 and started the eclipse version(Android developer tools) provided with it.But when I click finish after filling all the details in new android application dialog box,the finish button doesn't seem to respond at all.At the first click on finish button an application is created but no java files in it and the dialog box stays still.At least the android 4.2 library is not in the application.src is also empty.
I'm working with Windows 7 64bit and JDK 1.6 64bit.
Any idea on solving this?
http://developer.android.com/training/basics/firstapp/creating-project.html
http://developer.android.com/tools/help/adt.html
http://www.chhitizbuchasia.com/articles/chhitiz/2011/02/Setup%20Android%20SDK%20With%20Eclipse.html
http://developer.android.com/sdk/installing/installing-adt.html
Cannot create a new Android Project using Eclipse
install android sdk manager
step1
step2
step3
install the following sdk to perform the application
Download ADT plugin
http://developer.android.com/sdk/installing/installing-adt.html#Download
BASIC STEPS
http://blog.teamtreehouse.com/the-one-stop-android-sdk-installer-you-always-wanted
Best Jvm setting
Eclipse is not that much robust IDE.If nothing can solve your issue.try to restart Eclipse and your Computer.
and yes,before restarting just update the packages.
Go to SDK Manager, and install available updates for following packages.
Android SDK Tools
Android SDK Platform-tools
After updating,it will be look like this,
I just got mine past this bug; hopefully yours will fix too?
On the screens with menus to select from, where one item is greyed (selected?) as default:
Deliberately click the item, to ACTUALLY select it (it turns dark blue or something).
Mine apparently got caught up on the "Make activity" (or whatever) page, and until I went back and assumed that the default had failed to select it, I was unable to choose finish (even though it clicked, looked as though it was going to do something, and then didn't go).
Initially I was working on Android in Eclipse and everything went fine. But two weeks before i installed Texlipse plugin and was working with it. Now, when i wanted to switch back to Android i'm unable to.
In new project there's no option for creating a new Android project nor even a Java project.
Even i tried to change the Preference window to Java or Java Browsing but anything didn't work. Now i'm unable to run or compile even a single java file even after changing the perspective. I don't know whether this could be due to Texlipse, i tried searching google for ways to uninstall Texlipse but nothing worked.
So, pls anyone help me to sort this out...
Unninstall eclipse and install ADT again
If you want to play something before eclipse uninstall, what you can do is, go to your eclipse--->plugin folder (C:\eclipse\plugins something like this). There you will see all androind plugins which starts with com.android.....You may delete them and repeat the steps defined in this link.Android eclipse setup
This is one try but can't guarantee (Remember this may messup your eclipse if it don't work, so get ready for eclipse unstall if it doesn't work).
You could try launching Eclipse with the -clean parameter. This saved me when Eclipse was hanging on startup. Certainly worth a try before a re-install. More info here:
http://www.eclipsezone.com/eclipse/forums/t61566.html
go to windows/android sdk manager. If it works and androids vesions you've choosed are there, AND you don't see android in eclipse, I am afraid you will need to reinstall everything.
If sdk manager won't work, than install start sdk kit (http://developer.android.com/sdk/index.html). After that run sdk manager and set up the packages you need. If it won't work,
go to help/install new software and uninstall items that were installed in the backward sequence. After every remove check the prev step
I HAVE met the situations where only cleaning off all eclipse info and reinstalling it helped.
So, good luck!
Here is how my story goes. At first, I installed the Android SDK in the default directory it selected, which was Program File (x86) (which I thought the default was supposed to be app data?!) After SUCCESSFULLY pulling the APIs I quickly realized the mistake I had made, due to spaces being in the name, so I then uninstalled it and re-installed it in my D drive under a folder called development.
That all went fine, but when I tried to pull the SDK, I received the "A folder failed to be renamed or moved" message. I then tried disabling my anti-virus (more on that later), closing all other windows, and even ending windows explorer, but nothing changed.
To disable my antivirus, I used it's control panel (Avast BTW) to turn off the shields. What I really wanted to do was end the process, but, and here is the big but, Access Denied! I even ran taskmgr.exe as admin, but no success. Can anyone explain why that is? Anyways, after getting fed up with it all, I just booted into safemode with networking, and all is well for now, but I really would hate doing this every time I need to update the SDK, so any suggestions on how to fix this would be a great help, especially how to end my antivirus process so I can see if that's the problem.
EDIT: And I also did all that while running the Android SDK manager as administrator from the folder it is installed in.
I assume that the problem happens because the upgrade program wants to upgrade itself directly while it is running. My solution is that every time before you want to install something new, make a copy of \<sdk dir>\tools dir in the \<sdk dir>\ path, and then, upgrade or install something by excecuting android.bat in the copied tools folder. This works for me.
try rename "platform-tools" folder as "_platform-tools" and create a new folder as name "platform-tools".
that's work for me!
Having eclipse open sometimes causes this.
Open the Android SDK Manager then close eclipse before you press the "install packages" button and it should be fine.