unable to connect to adb.check the event log for a possible issue, verify that localhost entry is pointing to 127.0.0.1 or:: 1 for ipv4 or ipv6
Tried adb kill-server, restart, invalidate restart nothing works.
Same issue reported over here https://issuetracker.google.com/issues/130791561
Note: I have not added any file or anything in studio, it's fresh installed Studio after format a full system still issue is there.
Replace your platform-tools with this one and delete the other one.
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
I was also facing this issue in android Studio 3.4 version, but now I have fixed it , if you are using windows then follow these steps:
Download Platform tools from here
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
Extract downloaded zip file
Go To location "C:\Users\your_computer_user_name\AppData\Local\Android\Sdk" and Delete "Platform tools" folder
Copy and Paste, downloaded platform tool folder to above location
Now Go to your android studio and Rebuild your project Then run.
For Mac Users, follow these simple steps :
Just simply Navigate to Tools > SDK Manager> Android SDK>, then click on the Tab of SDK Tools, then look for Android SDK Platform-tools and update it.
Then the last step, Invalidate cache and restart your IDE, after that, then finally you restart your Mac. (Sometimes it's this step is unnecessary)
It will work out successfully.
Solution for Linux Users.
System info: Linux Mint Cinnamon 19.1 , Android Studio 3.4.1
Issue description: Problem with platform tools.
Solution: Remove the folder manually and update SDK tools through Android Studio.
Step 1: Go to your Android SDK installation folder. By default under your home directory. Choose platform-tools and simply delete. (/home//Android/SDK)
Step 2: Open Android Studio and go to SDK Tools. (File -> Settings -> Appearance & Behaviour -> System Settings -> Android SDK -> SDK Tools) By the moment you should be able to see Android SDK Platform Tools line unchecked.
Step 3: Put a check to install Platform Tools and press OK. Notice it'll relocate the folder to the directory where deleted.
Now that you re-installed the platform tools, restart the Android Studio and your deployment targets should show up.
If you don't install the platform tool back and ever try to build or run a project you'll get this IDE error. Just FYI :)
So that's all. Enjoy.
Happy coding
If you use Windows, you might have a corruption in api-ms-win-crt-runtime-l1-1-0.dll.
Try to update it - you can get the update from Microsoft's website.
You should check it - path/to/sdk/platform-tools and try to run adb.exe
When you update Sdk platform tools(which contains adb.exe) to release 28.0.2 and if you are using windows 8.1 then it needs few updates from windows.
As per SDK Platform tools release notes(https://developer.android.com/studio/releases/platform-tools):
Updated Windows requirements : The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package."
Windows update url: https://support.microsoft.com/en-ca/help/2999226/update-for-universal-c-runtime-in-windows
Prerequisite for Windows update url: https://www.microsoft.com/en-us/download/details.aspx?id=42327
Faced the exact same issue but after updating with prerequisite url first then the other url provided now it is working perfectly fine for me.
It worked for me by selecting -> Use libusb backend
This worked for me on Windows:
Goto cmd write %temp% hit enter -> delete all data from there.
Restart your Computer.
Open Android Studio now, it will work.
Clear all cache memory (related to Android Studio)
Restart ADB manually from Android Studio (first option)
Open Command prompt and got android sdk>platform-tools> adb kill-server
press enter
and again adb start-server
press enter
Restart ADB manually form Android Stidio (second option)
go to your (SDK store path) sdk>platform-tools>adb
press enter
ex. D drive > sdk>platform-tools>adb
Restart your system
Delete the platform-tools folder from the sdk and replacing with the same from your another pc. I am also facing this problem after updating to 3.4. If you face same problem please update to Android Studio 3.5 Canary Channel.
The reason is for ADB server problem. Simply re-run your adb.
(Go to your SDK folder then inside platform-tools folder you can see adb.exe. copy the path location and paste it in your computers system Environment variable. Set a new path there and paste the adb.exe file location there. hope it will solve )
If you are using Genymotion, there is an update that fix the problem.
Genymotion 3.0.2 (April 18th, 2019)
Corrections
We have fixed an
incompatibility with the adb tool bundled in the platform-tools 28.0.2
package of the Android SDK, which caused failures to start virtual
devices.
This new version of adb changed the behavior of the “adb connect
:” command by making the “port” part mandatory. This
broke Genymotion Desktop in a few places where it did not pass the
port. We have adjusted the way we call “adb connect” and also updated
the version we ship with the product to match the one in
platform-tools 28.0.2.
If non of the above answers worked for you (as same happend to me), down grade to the old version of Android Studio by following these steps:
Uninstall current Android Studio
Go to Android Studio Archive and download any older version
After installation, Open the project. You might see an error like this
This version of Android Studio cannot open this project, please retry with Android Studio 3.4 or newer.
Now, open project gradle and update classpath tools.build version. I.e. in my case Android studio version is 3.2 and classpath 3.2.1
Hope it might save someone time.
I faced this issue last night, and I tried these methods to fix:
download older platform-tools and place it in the android sdk folder.(not work for me)
adb kill-server, adb start-server.(not work for me, adb had no response with these cmd)
kill the process that occupies port 5037.(for me, there is no other .exe run at this port)
reinstall platform-tools in Android Studio.(not work)
download ADB Kits and replace them in platform-tools folder.(work!!!)
It seems that my adb file has been modified or replaced by some programs. You can try these methods, and I hope some of them can work for you.
I had this issue only after a Genymotion update, on Mac.
What worked for me: Open Genymotion preferences, Select ADB, choose "Use custom Android SDK tools" and points to your Android SDK folder.
Actually the problem is not with the android studio version 3.4
Problem is with the android platform tools version which is latest one 29.
So install the previous version of the android platform tools version it will solve your problem. as above #Ved mentioned.
Ved link:
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
EndTask adb.exe from Background processes (TaskManager) and Run Application again.
It works for me
I am trying to install the netCDF4 package for Python 3 on my Windows 8 PC. I have already worked through some bugs like adding the visual studio directory to PATH. However, I don't make good headway with the current issue:
when I run
pip install netcdf4
the output indicates that the file io.h could not be found. In fact, a search across the C:/ directory shows that I don't have this file on my PC.
An internet search indicates that the file io.h is somewhat outdated and not used anymore. Is there a way that I can get it from somewhere?
Is there a place where I can
After some more trial and error, I found a solution and I hope that by posting it here it might save somebody else some time.
The only Visual Studio environment that I had installed was Visual Studio Community 2017. What solved my problem was that, additionally, I installed the default (= not changing any of the default modules) version of Visual Studio 2017 Desktop Express. Afterwards,
pip install netcdf4
worked flawlessly.
When trying to install the android sdk for Aldebaran's pepper robot on my computer following this official tutorial:
Step 1: android.aldebaran.com/doc/installation.html
Step 2: android.aldebaran.com/doc/create_project.html#create-project
When trying to launch the Virtual Robot Environment of Pepper's tablet on my computer this message is printed: "Robot SDK'0.9' is not complete. Please download it again or re-create the robot application."
So far I have tried the following on my Ubuntu 16.04 64bit computer:
Uninstalling and re-downloading/installing the Robot sdk over the robot sdk manager provided by the android sdk for Pepper
Uninstalling and re-downloading/installing the android sdk for Pepper
Deleting, recreating and creating the android studio application turning it into a robot application
Removing other non essential android sdks
Moreover I also tried the following on another computer running windows 8.1 64bit:
Repeating the tutorial installation
Downloading and installing older version such as 2.22 and 2.11 of the android studio and repeating the tutorial installation.
Each time after I have completed Steps 1 & 2 when I want to start building or launching the application it fails on step B from this tutorial: android.aldebaran.com/doc/run_debug.html#run-debug and prints the Error mentioned above.
The project structure is identical to the one in the tutorial and I am able to sync the project via maven. But as I cannot actually launch the virtual robot environment or run the application I cannot make use of this sdk.
I have also found a similar question being asked on stackoverflow but there hasn't been a response yet. Also I don't understand the comments.
stackoverflow.com/questions/42824942/robot-sdk-0-9-is-not-complete-please-download-it-again-or-re-create-the-robot-a
I tried using another computer with windows 10 64bit freshly formatted so I installed Java jdk & jre 1.8.0_121 and android studio 2.3.1 as I couldn't find 2.3.3:
Repeated the tutorial installation
But still the same error message.
I got mine to work doing the following:
go to your current android SDK folder
rename the tools folder to tools-old
create a new Folder named tools
download this: https://android.googlesource.com/platform/prebuilts/android-emulator/+archive/android-7.1.1_r1/windows.tar.gz
unpacke it into your new tools folder
Make sure you have your AVD Options set to arm and not x86
and that "Use Host GPU" is enabled
After that the emulator worked.(note that it takes quite long to launche)
The suspected cause is that the Pepper emulator tries to use the emulator-arm.exe wich is not availible in the standart installation of Android Studio
You should try installing Android Studio 2.3.3 on Windows 10, 64-bit. I know that works at least.
I got this working finally thanks to theGary's hint above. No need to wipe out your whole tools directory though -- I was able to get the x86 Pepper emulator running (on Mac in my case) by copying these files and directories from the Android sdk/emulator directory into the sdk/tools directory:
emulator64-x84
qemu
bin64
lib/pc-bios
lib/ca-bundle.pem
Then edit your run/debug configurations and change the “robot app” AVD options from armeabi-v7 to x86.
In the past I could download and install Android SDK separately. I cannot find it any more on Google's Developer site, only Android Studio, which supposedly contains the SDK too (?). When starting the Android Studio it looks for the SDK.
I installed the Ubuntu (I'm using 16.10 Yakkety Yak) repo's Android SDK, that didn't help much because it is in /usr/lib/android-sdk with root privileges and Android Studio disses it. Now I'm scratching my head how I going to scrape all of that off as soon as I find out where can I install an SDK from.
I did check at least 2-3 Stack Overflow Questions on the topic, but all of them seems to be outdated, so please be very careful to mark this as a duplicate.
I have to add that I had both the SDK and the Studio installed before on my system. That turns out to be crucial info.
Are the "command-line tools" at https://developer.android.com/studio/index.html#downloads what you're looking for?
Go to https://developer.android.com/studio/index.html#linux-bundle and download the zip file. Extract it into your home directory(or anywhere inside your home directory).
Move into that extracted files directory, open up bin folder. You'll see a file[script] named studio.sh. Run that and Android will automatically start downloading the SDK.
Alternatively:
Set your ANDROID_HOME environment variable to /usr/lib/android-sdk:
vim /home/user/.profile
Add
export ANDROID_HOME="/usr/lib/android-sdk"
Well, after wiping the .Android-Studio-2.x and .android directories form my home, Android Studio offered the installation of the SDK. So the cause was leftover of previous installs, I haven't mentioned that fully in my question.
I am unable to start emulator. It is giving this error
Cannot launch AVD in emulator.
Output
dyld:symbol not found _AVMediaTypeVideo
I have tried restarting Android Studio, rebooting the system. Can anyone help?
Happens after upgrading Android SDK Tools to 24.1.2 rev 24.3
Upgrading to SDK Tools from 24.3.1 to 24.3.3 fixed this issue for me. You can update the SDK Tools via the SDK Manager in Android Studio.
I had this same problem on my MacBook Pro yesterday with the latest version of Android SDK tools (i.e., 24.3.1). I found that updating my MacOS X to OS X Yosemite resolved the issue. Now, my emulators are starting again.
I am going to assume they are using some symbols that are only available in Yosemite.
Same here. I downloaded the SDK separately and changed the SDK location in Android Studio to use the downloaded one. Now the emulator starts up again.