Related
I'm developing an android app on AS 3.3.1 on ubuntu linux for some time and every thing was fine.
Today I opened AS as usual to find out that it updated it self to 3.4 without asking and I don't know when this took place and how and it spitting error messages about android sdk then after fixing that my code is full of errors and my themes and settings are lost.
1-How and why did this happen?
2-How to fix it and roll back?
3-How to prevent it from happening again?
It was something called snap installed in Ubuntu
so I used the following command in terminal emulator:
snap revert android-studio
If you are not root use:
sudo snap revert android-studio
and everything is fine.
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 have been trying to use android studio 2.0 emulator but I can not run my App on the Emulator. When I Run my App it shows the emulator with following details:
Hax is Enabled
Hax ram_size 0x800000000
HAx is working and emulator
runs in fast virt mode.
console on port 5554,
ADB on port 5555
After that it takes to next TAB Launching app and shows
Waiting for the device to Come online
After that it shows error:
Error while waiting for device: Time out after 300seconds waiting for emulator to come online.
What I have tried so far.
Installed fresh android studio 2.0 with all update to date SDK
Tired to increase Emulator Memory.
Installed android studio 2.1 Beta with latest SDK
Discussed this issue on Google.
What's the solution?
I haven't found any solution yet. I opened new issue on 4th may 2016 because it is known bug in previous versions. Please report on the following link if you have same issue.
https://code.google.com/p/android/issues/detail?id=209095
The solution for me was setting the Graphics option on the Android Virtual Device to Software instead of Automatic or Hardware.
I believe this was the solution because I am working on a windows machine that did not have a dedicated graphics card.
You might have forwarding enabled on adb. You can try this: Quit Android studio and launch terminal. Run these commands:
adb kill-server
adb forward --remove-all
adb start-server
Now you can launch Android Studio and try again.
Also something that can go wrong: Make sure you exit Docker for Mac (possibly all other kind of docker installations as well).
My problem went away after I shutdowned VirtualBox on my machine.
One thing I know is that Linux KVM can't get along with VirtualBox well.
I found a workaround even though I am not sure why this is happening.
Go to Menu->Tools->Android and uncheck the option Enable ADB Integration
Run the application. Now the emulator will be launched, but app will not run. Once the emulator is fully launched, check the Enable ADB Integration option and re-run the app. Now the app will be launched in the already running emulator.
Go to Device Manager (Tools -> Device Manager)
Wipe the data of your device and try starting it again.
Go to Android Studio Command Line, and follow these steps:
__> cd /Users/your_root_name/.android/avd
__> ls
__> rm -r Nexus_5X_Edited_API_17.avd There are two avd files.
Rerun the app.
You could try :
run the emulator from the console manually and see whether adb can connect("see") it from android studio. Does it run at all?
delete avd , recreate a new one for testing, always a good idea in 2.0. lot's of stuff is changing ( instant run etc.)
what does adb say from console ? adb kill-server , adb start-server, start an emulator, then adb devices does it list your emulator ?
try to change this solved my issue, you may other graphics options, and change to a lower resolution model
Upgrade to the latest SDK, for the android emulator:
use 512MB RAM
256MB heap
You can leave the default disk space.
I had the same problem. I'm using Android Studio 2.3 and Debian 9.1 Stretch 64 bits.
In my case, the problem was in default settings established in graphics aceleration configuration.
To solve the problem I opened the AVD Manager, then I selected the device and I opened config file (config.ini) selecting "Show on disk" option whitin "Actions" column. Within the file, I changed the value setted in hw.gpu.mode variable from mesa to swiftshader. After saved the changes, the emulator started without any problems.
More options availables could be found on this link.
These are the steps I took (I'm on Linux).
Switched to Software rendering (works but is too slow)
Tried running on commanline and an error displayed.
Forced emulator to use the system graphic drivers.
First, as #jlars62 suggested, I tried using Switching the Graphics to "Software" and this DID work. However, the performance is far to slow so I dug a little deeper.
Then I tried running the device from the console, as #CaptainCrunch suggestion. (My device was created in Android Studio; emulator in the Sdk may be in a different place on your system)
$ ~/Android/Sdk/emulator/emulator -avd Nexus_6_Edited_768Mb_API_23
For me this produced the following error:
libGL error: unable to load driver: i965_dri.so
libGL error: driver
pointer missing libGL error: failed to load driver: i965
...
Which I tracked down (on ArchLinux) to mean it's using the wrong graphic drivers (Android Sdk comes with it's own). You can force the system ones on the commandline with -use-system-libs:
$ ~/Android/Sdk/emulator/emulator -avd Nexus_6_Edited_768Mb_API_23 -use-system-libs
To force Android Studio to do this you can intercept the call to "emulator" like so (See Mike42) :
$ cd ~/Android/Sdk/tools/
$ mv emulator emulator.0
$ touch emulator
$ chmod +x emulator
In the new emulator file add this:
#!/bin/sh
set -ex
$0.0 $# -use-system-libs
I experienced a similar issue with android studio 2.2. Re-installing a new system image didnt resolve for me. Then found this solution on this link.
unchecking the Enable ADB Integration option and checking it back seem to resolve it for me. I hope this helps someone out there.
Android API Version for application and device should match. Check if minSdkVersion and targetSdkVersion in Gradle Scripts - build.gradle (Module: app) correspond device API.
Also low versions (e.g. API 15) result in ide-emulator link failure, inspite of applicatrion and device versions match.
I had the same problem. I removed virtual device and run app on my phone - worked well.
To remove virtual device: Click icon "AVD Manager" in Android Studio, select virtual device and in context menu click "Delete".
Then turn on on the phone "Developer mode". Connect phone via USB to the laptop.
Restarting ADB server works for me, but no need to go for it from command line.
Ctrl + Maj + A -> Troubleshoot Device Connections -> Next -> Next -> Restart ADB Server
Sadly none of the solutions worked for me! I solved my problem by uninstalling existing APK from my phone and it all started working perfectly!
This started happening after I've updated android studio to latest version.
I almost tested all solutions in this topic and other pages. Finally after lots of searching I found the issue!
I had to enable Hyper-V on my system (If your system does not support Hyper-V you need to install HAXM instead).
In this link you can read about enabling Hyper-V and HAXM: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows
If you install HAXM and still doesn't work go to this link below and install Hyper-V.
Next, restart your computer.
If It doesn't work again remove the emulator and reinstall again with a high API.
https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows
I experienced a similar issue, i fixed it by deleting the Android emulator then created a new one with a higher API level.
In my case I've selected API-30
To fix it I went to Tools > SDK Manager > SDK Tools and updated Android SDK Build-Tools 31
Somebody said they needed to do a cold boot afterword
I encountered the same problem, when I tried to run it from the terminal by following command
~/Documents/development/android/SDK/emulator/emulator -avd Resizable_Edited_API_31
I encountered the following error
qemu-system-x86_64: -chardev socket,port=36201,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:36201: Name or service not known
^C^X^Z
And I realized that I had disabled ipv6 in the system, after I activated it, avd ran for me.
Usually, deleting the current emulator that doesn't work anymore and creating it again will solve the issue. I've had it 5 minutes ago and that's how I solved it.
I have faced the same issue you have mentioned and could solve it by just deleting the current avd and creating a new one.It's working perfectly well now.
This error is gone for me by remove the AVD and create a new one.
after some compile and clean, the error was gone away.
I am unable to test my application on Android studio via genymotion.
Genymotion warning: You must specify the path to the Genymotion folder to use this feature.
when trying to location Genymotion.app I get this error: "Cannot find Genymotion in the specified path"
this is the path I entered for genymotion.app:
C:\Users\Rua\AppData\Local\Genymobile\Genymotion
On Mac,this is my solution:
/Applications/Genymotion.app/Contents/MacOS/player.app
Using Windows
First off, you need to install Genymotion. Go to https://www.genymotion.com/#!/pricing and download and install it.
The default path is on Windows
C:\Program Files\Genymobile\Genymotion
And that's what you enter in the Android Studio prompt window.
Using Mac
Following this tutorial, the default path on Mac seems to be
/Applications/Genymotion.app
If you already installed the Genymotion and VirtualBox, you can add
/Applications/Genymotion.app
when you click Genymotion Device Manager in Android Studio.
Verified on MacBook Pro (OS X 10.11.6 EI CAPTAIN).
if you are receiving this error that means that you do not have the genymotion app installed on your Mac
you can to download a .DMG file from here and install it by double clicking on it
you can try and run the installed app but it still won't run as it is missing the underlying virtual machine tool
to run genymotion you need virtualBox Guys at genymotion have mentioned their preferred choice as 4.3.12 which you can download from here
Once downloaded you can double click on the .DMG file and then the .pkg (package file) and then follow the normal installation procedure
once you have the virtual box installed then you can run the genymotion app and you will get there was supposed to be an image here
I was posting an image which would have helped you but SO says i need 10 reputation points to post images. then i decided to help you by posting an imgur url and SO says i need 10 reputations to post more than 2 links
kind request to SO either give me more reputation points or make it easy for me to help others
Now you Gennymotion is finally installed just go ahead and create a new virtual device
and once you have created a new virtual device you can access that device from the Gennymotion Android Studio Plugin
Hope this helps
When I start Android Studio, it shows popup regarding new update of 1.1 release. But when I start updating, After downloading all patch files, while restarting, it shows following error:
I searched almost everywhere on Google and Stackoverflow. There are already two questions on so: this and this. But none of them are have any correct answer. I also tried running as administrator, restarting PC, turning off the firewall, uninstalling antivirus. But none of them worked.
I am using windows 7 32-bit. How to solve this problem? Can anyone help?
I know this is an older question but I encountered the same error while updating SDK components in Android Studio 2.3.3. I was able to fix the problem by starting the SDK manager and un-checking the components that showed the error and clicked "Apply". That un-installed just that component. When it was finished, I re-checked the component and clicked "Apply" again. When it was finished, the problematic component was updated to the newest version. This was much quicker than doing a full un-install/re-install as stated in one of the solutions above.
Hope this helps someone.
This is another option, it is not much easier than reinstalling but at least you don't have to worry about your settings getting lost
Go to help->about and note the version you currently have installed
Download zip file for your current version at https://developer.android.com/studio/archive
Manually overwrite conflicted files with files from zip
Update normally
I had a similar problem on some other files and could not figure it out.
You should download the last Android Studio version and remove the old one.
It appears like the only way to bypass this error and successfully update Android Studio is to uninstall and reinstall it.
Before uninstalling, make a backup of your IDE settings through File | Export Settings.
Download the "No SDK tools included" exe from the Other Downloads section. Avoid using download accelerators as they often mess up the downloads from https://dl.google.com .
In the Install Wizard, you may uncheck to update AVD if you use Genymotion and don't need Google's Android emulator.
Use the JetBrains Toolbox for Android Studio update, problem solved. No need to mess with the file permissions. Especially on company devices.
I had this issue on Ubuntu 18.04 when tried to update Android Studio from 3.4 to 3.5 version. I have changed Android Studio directory's ownership to my user:
sudo chown -R <username> /opt/android-studio
It resolved all but one errors for me, because I still had a jre/bin/java - Access Denied error, which I have resolved by killing its process:
# The second column of this command's output is PID.
ps -aux | grep /opt/android-studio/jre/bin/java
kill <PID>
It might also happen that you need to logout and and re login as admin user in your system.
Update the Android studio [in admin user].
Re login as a previous user.
You should check the JDK Location settings, which appears be changed on every Android Studio update, with commands ctrl + Alt + Shift + S (to reveal the Project Structure menu options, and uncheck the Use embedded JDK and find your current JDK Location, on windows machines, you can see that location on environment variables JAVA_HOME.
There is a workaround, try deleting or moving the files that are causing the conflicts to another folder when the Update starts NOT BEFORE! That worked for me.
I know this is a very old question, but I face this issue almost every time I try to update my studio. Only solution I know which works for sure is clean install of studio....which is time consuming. So the solution is when you get to know the name of the file, search the location of that folder containing specified file. Check if that folder has lock icon on it, if it has then change the sharing settings to everyone and share the folder. If it does not have the lock icon on the folder check if it is in read-only mode. This worked for me hopefully someone finds this useful.
Cheers.
I had a similar problem. What I did was to make sure of the whole folder's ownership. For some reason, some files where owned by root, so I changed it to my ownership. In linux you can use the followoing command on the Android Studio folder:
sudo chown yourusername:yourusername -R android-studio-folder
I just tried again and everything updated successfully. Hope it helps!
The only solution worked for me is I have reinstalled Android Studio the latest version without uninstalling manually it and when starting the installer it asked me to uninstall and said that your settings will not be lost so I checked the uninstall and everything went smooth without any problems and got the latest version installed and all my settings the same.
I had this symptom when updating from Android Studio 3.4.2 to 3.5.
In my case, the affected file was plugins/Kotlin/kotlinc/bin/kotlinc.
The cause turned out to be that while the file's contents had not been modified at all... the Unix permissions bits on it had been.
Specifically, this was a file that comes as non-executable, and I had at some point chmod'd it to executable (because it should be) in order to use it from the command line.
The fix was to set those permissions bits back, with chmod:
$ chmod a-x /PATH/TO/android-studio/plugins/Kotlin/kotlinc/bin/*
This probably isn't a super common cause for this symptom, but hopefully it will be helpful to someone else. :-) I certainly didn't remember making that change, though once I spotted it I know exactly why I made it.
You can found the files in the android-sdk folder, and delete those files, and check your permission of the folder(android-sdk, build-tools, tools), if your can write, and download again.
I solve the issue.
I had the same error when upgrading from 3.1.x to 3.5.x. What worked for me was downloading the new Android Studio image from https://developer.android.com/studio and installing it (when asking me if I want to replace the old version I said yes). Everything seems to work fine now.
I also had the same error when upgrading from 3.5 to 3.6, I managed to solve this without losing any sdk platforms and virtual machines in avd by installing the latest version of android,First Export the settings and then delete the two folders ".AndroidStudio3.x" in home directory and the "android-studio" in /usr/local or /opt directory, then download the zip file of latest version of android studio and move the "android-studio" folder to /usr/local or /opt. Now run the /android-studio/bin/studio.sh and import the settings,Now Latest version will be installed.
I got this error when I was trying to upgrade Android Studio using a different user account to the account that installed Android Studio (the account had admin privileges). When I switched to the account which installed Android Studio I was able to upgrade without this problem happening.
I have had a similar issue and solved it. Some documents were encrypted by the software installed on my PC, so updating to Android Studio 3.6 was not possible (in fact every update I have the same issue).
To solve it, just find those files in the Android Studio installation folder (probably Program Files/Android) and decrypt it. After that, you should be good to go. I hope it helps!