I want to launch the React Native application on Android emulator using Ubuntu 16.04. Following the react native docs it should be dove by running
react-native run-android
OR
npm run android
Both these commands are not working without sudo for some reason, but that's not an issue. The issue is when I run them every time I get the same error:
Error running adb: No Android device found. Please connect a device
and follow the instructions here to enable USB debugging:
https://developer.android.com/studio/run/device.html#developer-device-options.
If you are using Genymotion go to Settings -> ADB, select "Use custom
Android SDK tools", and point it at your Android SDK directory.
I don't want to connect device via USB and I don't use Genymotion, I just want an emulator. I tried to run the project via Android Studio, but faced with another issue :
Error: please select Android SDK
I tried syncing the files, removing the project, restart the studio - nothing. (However I can see the Nexus 5X in the devices list and even start it)
Please someone help me, I've tried everything I could find - nothing helps
Both these commands are not working without sudo for some reason, but
that's not an issue.
Probably, this is the root cause.
Because, if you have ever installed your Android SDK / Tools using "sudo" or you installed it into the directories of root user, then those files may not be accessible or executable by a normal account. So, try below steps:
Delete the hidden dirs ~/.gradle ~/.idea ~/.m2 and ~/.android using command
sudo rm -rf ~/.gradle ~/.idea ~/.m2 ~/.android.
This step is to clear up your previously installed files with root previlige. If you don't have those folders, ignore this step.
Re-install your Android Studio into your normal user home directory, e.g. ~/android
Create your AVDs using the newly installed Android Studio.
Don't use any "sudo" for your newly configured environment. Because anything installed with root privilege will go to root directory, i.e. /, but not your normal user home dir, i.e. ~/. If you start your Android Studio with a normal user, usually, it will only be able to refer to your setups under ~/. This is probable the reason for not being able to find your "installed" Android SDK.
While trying to update my Android SDK I am encountering this error when trying to install this particular package:
How do I fix this?
This happens once in a while on my Windows SDK (even when I don't have any antivirus or similar programs running, execute the SDK-Manager as an administrator and so on).
I just update the tools by hand in this case. Which means close the SDK-Manager after the error and open the ANDROID_SDK\temp folder. There should be a zip named tools_R16.zip or similar (don't remember the exact name). Unzip that. You should end up with a tools folder. Copy all the files from this folder into ANDROID_SDK\tools. Overwrite when asked. And take a backup of the SDKs tools folder beforehand, just in case something explodes.
After that, start the SDK-Manager again. The tools version should be updated.
The problem seems to be that Eclipse, or even the SDK Manager itself, locks the folder. Running android.bat from the tools folder should do the trick.
If you launched the SDK Manager from Android Studio then all you need to do is close Android Studio.
I presumed the SDK Manager was a modal dialog that was part of Android Studio - not a separate program.
thanks. this is how I fixed it:
I updated the tools by hand in this case. Which means close the SDK-manager after the error and open the folder android-sdk-windows folder. Using LockHunter, unlock all programs from holding a lock on the android-sdk-windows\tools\ folder. http://lockhunter.com/?ver=&vertype=pro&sm=main_window_64
RENAME the android-sdk-windows\tools folder beforehand to tools_DELETEME
There should be a zip named android-sdk-windows\temp\tools_r19-windows.zip. open that, You should see a tools folder in it. Copy that tools folder to android-sdk-windows\tools
After that, start the SDK-manager again. The tools version should be updated.
When you install tools/softwares use SDK manager. But don't use it when update. Do right click -> Run as administrator on android-sdk-windows\tools\android.bat file for updating tools. Always try to run commands as Administrator specially on Windows Vista/7/8. That'll fix most of permission issues etc...
You probably started the SDK manager from eclipse? I encoutnered the same problem, and fixed it by manually opening the SDK manager from the directy tools.
My solution was to start it from within eclipse - as Administrator.
well i had the same issue on windows 7 ... problem is that during the update it tries to rename the tools folder (inside the SDK folder) and that folder is used by a process "ADB" which is currently running ...
so you cannot do the update smoothly until you stop / kill that process ...
BTW copy pasting the new contents of tools folder from the temp would also work ...
With windows 7, when "failed to install popup" appears kill the process called adb (from task manager ctrl+alt+del) then press "Yes" and stuff is being installed.
I tried running android.bat and got the same error.
What worked for me was using unlocker to unlock the \tools folder.
Ensure you don't have any essential files or folder opened/being used by other applications including explorer.
I've read before, people take a copy of the platform-tools folder and run the update from a different location. This ensures you haven't got open the files it's trying to update.
Could also disable your antivirus for 5 minutes o0o0.
On Windows 7 and probably Vista, run Eclipse as administrator.
My problem was Windows 7 security. I opened up the security on C:\Program Files\Android to EVERYONE with FULL access and it then worked. I then removed EVERYONE after the update was complete.
I had to make a copy of the tools folder itself (keeping it at the same directory tree
level, thus "tools" and "tools-copy" were both in the "android-sdk-windows" folder).
Then ran Android.bat from that copy.
After the update just delete the tools-copy folder.
The error message was Failed to rename directory C:\devtools\android-sdk\system-images\android-21\google_apis\x86 to C:\devtools\android-sdk\temp\SystemImagePackage.old01. I deleted the C:\devtools\android-sdk\temp\SystemImagePackage.old01 directory by hand (it was a leftover? I don't know) and it was able to proceed.
Same error i got while updating sdk. It is because of targeted folder locked (access permission is denied).
You can resolve it as follows in "Ubuntu" :-
Press ALT + F2 and type 'gksudo nautilus' and navigate to the targeted folder like tools or extras and give create and delete permission.
then update, every thing will be working fine :)
First make a copy of tools folder in same directory (android-sdk or android-sdk-windows) then delete the original tools folder and then open the android.bat file by double clicking in tools-copy folder to launch sdk manager and install the tools.
If tools folder is not being deleted then use the unlocker LockHunter to delete the folder and then open android.bat to update the tools.
After successful installation of tools delete the tools-copy folder.
Close Eclipse or Android Studio if open.
It worked for me!!!
On my PC it was caused by monitor.exe running in the background. Terminating that proces solved the problem.
Close the currently launched android studio window from task manager by going to the studioprocess (So when closed there are currently no active studio windows). Then go to Android studio in windows explorer, select the studio64/studio(if 32 bit OS) and right click and select run as administrator.
In one line - you need to run Android Studio as a administrator.
These are the steps followed by me.
Restart the computer.
Open "C:\android\androidStudio\sdk\tools\android.bat" as admin.
Now install packages should run fine.
I know this is an old post but I want to write my personal solution to the problem:
Failed to rename directory C:\android-sdk\tools to C:\android-sdk\temp\ToolPackage.old01.
Obviously I have had the same issue and every time the Android tools needs to be updated it's a nightmare.
None of the solutions I found googling the net worked for me up now, but this is a vital job to maintain Android SDK updated. So I started to find an alternative working way to solve this issue and I found it finally.... at least... it works for me, even if it is a bit tricky.
The basic problem is that the android.bat batch file comes from the ~\tools\ folder and it's still in memory (running) while the same ~\tools\ folder needs to be updated (in our case, renamed).
The problem is that the android.bat runs java to launch swt.jar (the SDK tool), and it remains uselessly waiting for completion of this java program.
You can edit the android.bat and see the call in the latest row of this batch:
call "%java_exe% %REMOTE_DEBUG%" "-Dcom.android.sdkmanager.toolsdir=%tools_dir%" "-Dcom.android.sdkmanager.workdir=%work_dir%" -classpath "%jar_path%;%swt_path%\swt.jar" com.android.sdkmanager.Main %*
The problem is the "call" CMD command. It waits for the called external program completion.
But ther's another way to run external programs from a batch file: the "start" command. It launches an external program and terminates.
So I just replaced the "call" command with "start", so that after the change the latest row of my android.bat was:
start "" "%java_exe% %REMOTE_DEBUG%" "-Dcom.android.sdkmanager.toolsdir=%tools_dir%" "-Dcom.android.sdkmanager.workdir=%work_dir%" -classpath "%jar_path%;%swt_path%\swt.jar" com.android.sdkmanager.Main %*
Note: Keep the "" in between start and the application path. You can add text in those hyphens and this text will be the caption of the java.exe command window you will see after the changes. In my case I left the caption as an empty string but you can write there what you want.
After the changes, you can start the SDK and the android.bat will be no more waiting, leaving the SDK tool free to play (and rename the ~\tools\ folder without headaches).
Obviously, after updating the SDK tools, you have to redo the same changes in the new, updated android.bat batch file. This could be a bit unconfortable, but you'll have just to remember to make the changes before running the SDK tool and you'll have no other headaches while updating Android.
In Ubuntu following solved issue for me
cd [tools/directory/path]
sudo ./android
Solved this on my side by killing the adb.exe in Task Manager.
I just stopped the emulator, and problem was solved.
This question already has answers here:
Closed 11 years ago.
Possible Duplicates:
Not able to launch android emulator
Starting the Android emulator in SDK tools, revision 12
http://developer.android.com/sdk/eclipse-adt.html#installing I followed the instructions here for a windows 7 machine using a 64 bit operating system. It's a clean system install. I first installed the Android SDK and then installed Eclipse and then installed the ADT Plugin.
At first, simply nothing was happening. I'd click window-> android and it'd bring up the list of emulators I had made. I'd select one then click start and nothing. ADB.exe wasn't even in my systems resources. I made sure Kaspersky had added adb.exe to it's trusted list and tried again, still no dice.
I then saw an article saying I should move adb.exe from platform-tools to just tools so I tried that. That made it switch from doing nothing (and reporting nothing in the console or logcat) to where it is now. It says
invalid command-line parameter: Files.
Hint: use '#foo' to launch a virtual device named 'foo'.
please use -help for more information
Any more theories on what I can try would be greatly appreciated.
For further clarification the foo message happened with platform of 2.3.3. or 3.2 selected. When trying platform 3.0 it went back to nothing.
I had the same problem which was quite annoying me until I found a "fix" (well it does not solve the problem at its roots but helps a lot anyway):
Simple create a batch file with the following content:
CD "C:\Program Files\Android\android-sdk\platform-tools"
adb kill-server && adb start-server
Of course you have to adjust the correct android platform-tools path.
So whenever a running emulator is not recognized by Eclipse or DDMS simply run this batch.
I had this trouble when my SDK was installed in 'Program Files'.
The invalid command line parameter was the space in the program files part of the argument. I guess Android coming from a Linux world means that whitespace is it's enemy! Despite this being the default install location.
I moved the whole SDK (emulator included) to the root 'C:\' drive. It then started working a treat.
There is bug on the windows version.
Open a command line prompt in the /tools/ folder (which you can find in the sdk folder) then run the emulator-arm.exe -avd nameOfYourVirtualDeviceHere
(btw this will not fix the real issue but allows you to continue to work)
"Error executing aapt. Please check aapt is present at ... /platform tools/aapt"
I am trying to build Android apps using Eclipse Android SDK in Ubuntu.
I installed Ubuntu 32bit 10.10 in two different computers and I can't fix the problems now.
I installed Eclipse, ADT plugin, Android SDK, all Android APIs, ...and also I have set Preferences to Android SDK folder. I also carefully put all SDK and Eclipse in my username folder to make sure I fully have right permission.
I also try to use google to find similar cases. Most cases use 64 bit Ubuntu.
I also fix the GNU compiler and some instructions here.
But now I am really hopeless. It looks like this problem is really serious.
I really appreciate all of your helps.
Thanks so much
ddienle#gmail.com
ledangdien#yahoo.com
Thanks again
*Also, I try to restart my Computer many times and try to install many different version
of Eclipse. Each time I set Preferences for Android SDK, the following message box occur
"Failed to get the adb version: Cannot run program "/home/sdc/android-sdk-linux_x86/platform-tools/adb": java.io.IOException: error=13, Permission denied"
Now I try everything but they don't work*
Have you tried the adt-eclipse-bundle?
https://developer.android.com/sdk/installing/bundle.html
You have some wrong permissions. Perhaps some files are owned by the root user because of using sudo when it wasn't needed. All files in your home directory should be owned by your user. You can fix that with the following:
sudo chown -Rc $USER:$USER /home/sdc/
I'm completely frustrated with the Android SDK Manager.
I'm running Win 7 Home edition and have the SDK installed in its own top level directory on my D:\ drive.
When I run SDK Setup.exe from the command line (and I've even opened the prompt as an administrator), I get an error when trying to update the packages.
The SDK manager is telling me that I need to install the SDK Tools rev 7. But when I accept the license, I get an error message stating:
"A folder failed to be renamed or removed" yada yada yada. The Installing Archives window says "Failed to rename directory D:\android-sdk-windows\tools to D:\android-sdk-windows\temp\ToolPackage.old01."
I looked here for help:
http://groups.google.com/group/android-developers/browse_thread/thread/4b784f3eb1e096fd/ecadfb28ce5daf5f?lnk=gst&q=cannot+rename+folder#ecadfb28ce5daf5f
but the content there didn't help.
I DO have my antivirus (AVG) disabled.
I DO NOT have any other programs running -- just the command prompt to launch the SDK Manager.
I have even given the everyone group, for the D:\android-sdk-windows\ folder, full control.
I tried to rename the tools directory before starting the SDK Manager but then I get an error that a batch file cannot be found when I try to launch SDK Setup.exe. Grrrr.
None of this works.
Suggestions how to get the package to update without error are greatly appreciated.
Thanks!
A simple thing,
There will be zipped file after this error has been occured. Meaning that Updated tools got store as
tools_r16-windows.zip in C:\Program Files\Android\android-sdk\temp
Just extract it and copy it in our tools folder
C:\Program Files\Android\android-sdk\tools
Enjoy:)
I think ths might help. Please give your comments!!
If you get this error while using Eclipse on a 64-bit Window 7 (might 32-bit as well), exit Eclipse, go to your SDK folder and run "SDK Manager.exe" as Administrator. In my case, Eclipse turned out to be what locked the folder in the first place.
# Stratos - Thank you for your instructions, they worked for me.
Go to Android\
android-sdk\
tools\
Delete "source.properties" (Right click - delete)
Open SDK Manager and update
And everyone lived happily ever after...
You can't use 64 bit java or 64 bit eclipse. That's almost certainly your problem.
Had the same problem. For me it was a bit circular, the SDK manager had a hold at source.properties and closing the process terminated the update. I deleted android-sdk\tools\source.properties before running the SDK manager and it all worked. Oh and I was not updating through Eclipse so it is not an Eclipse problem.
I can't vote yet, or I would have voted for Stratos.
I had already disabled my Norton antivirus (after reading other posts).
Removing the source.properties file helped.
Don't forget to run SDK manager with admin rights if not already.
There is another simple way:
When the SDK asks to install the Java SE JDK press back and then press next. This time it will detect the installed JDK. I solved this problem twice with this method
Use Unlocker to unlock the tools folder.
Right click on tools folder -> Unlocker. This way you don't even have to find out what is locking the folder...
Start task manage and end Adb.exe. Thisnisnthe program that has a hold on the folder. Rename the tools folder to some other name eg. 'toolsold'. Then extract the zip file containing the new tools folder. Rerun the updates and it should be detected as updated and it should proceed with the outstanding tasks.
Run SDK manager as Administrator, this fixed for me