A young friend of mine would like to push a game created using www.buildbox.com to his Samsung Android Tablet. He is using Windows 10 and Android Studio 3.6.1.
But the Device Drop Down is greyed out and for some reason the AVD Manager, the SDK Manager and the Connection Assistant are missing from this tools menu.
On my Android Studio 3.4 I can still see the Connection Assistant
I checked the Release notes but could not find anything.
https://developer.android.com/studio/releases
I checked that Windows can see the tablet as a USB device and the friend told me that developer mode is enabled.
Any ideas what is going on ?
So I got a chance to look further into the problem.
It turned out, that the problem seems to be with Buildbox not generating a proper Android project. In particular the generated project is missing a proper module and a proper app configuration. Once I added those the missing connection tool reappeared.
However I still got an error.
A few hours ago, my Android studio was working very fine. I could write, build and run on my test device (TECNO K7).
I decided to update my Android Studio to 3.5. The whole process went well except that I cannot find my device among the list of devices any longer. I have also tried with multiple devices, I got the same outcome. When I click on the run-button, the app runs on the Pixel 2 emulator. However, I want it to run on my device.
Here's a screenshot of what my menu looks like. Note that the device (TECNO K7) is currently connected:
Is there something I am doing wrong?
UPDATE:
I tried restarting my ADB server and I go the following error:
Unable to locate ADB.
I have also tried re-installing the following tools multiple times, still the same outcome:
Android SDK tools
Android SDK Build-Tools
Android SDK Platform-Tools
PS: For reference, I use Mac OS and it is also important to remember that my Android studio was working perfectly fine before the update.
Solution:
Drivers not installed: If the Android Physical device is not a Google/Nexus product than you have to download the OEM drivers of the particular model.
HAXM not installed properly : Hardware Accelerated Execution Manager must have not installed properly on your computer. Try reinstalling it directly from the options available in your SDK.
No proper Path : Sometimes though the files are available in the local system, The Android Studio is not guided with the accurate path name to reach the file.
Hope this will be useful to you.
After spending hours on this I found that the Studio update had un-assigned an SDK for my project.
Selecting File -> Project Structure, then selecting an SDK under 'Project SDK' immediately displayed the 'allow debug on this device' dialog on my phone, then within a few seconds after accepting it, the device showed up in the device list.
Go to:
File > Invalidate caches/Restart > Invalidate and Restart
That should work.
Before going to bellow steps make sure
Your "Google USB Driver" package is installed ("Tools" -> "SDK Manager" -> Check "Google USB Driver" -> "Apply" -> "Ok").
If you are trying to access with emulator then check "Intel x86 Emulator Accelarator(HAXM installer)" is instaled. ("Tools" -> "SDK Manager" -> Check "Intel x86 Emulator Accelarator(HAXM installer)"" -> "Apply" -> "Ok")
Go to Tools.
Then go to SDK Manager.
Open SDK tools.
Uncheck "Android SDK Platform-Tools" (On my case it was checked).
press apply then ok.
Again goto Tools.
Then goto SDK Manager.
Open SDK tools.
check "Android SDK Platform-Tools"
Restart Android Studio :)
Hope this will help somebody like me.
This option is definitely not the most optimal. I eventually deduced that the problem was with my HAXM and simply re-installing this would have solved the problem. If you face, this exact problem, simple re-install the HAXM in your SDK.
I hope this helps someone out there.
I am trying to run my app on canary build of the android emulator from android studio on AMD processor but I am getting the following error
1:47 PM Emulator: [2440]:INFO:android/android-emu/android/verified-
boot/load_config.cpp:236:Verified boot params were not found.
1:47 PM Emulator: **
1:47 PM Emulator: ERROR:/usr/local/google/buildbot/src/android/emu-master-
dev/external/qemu/fpu/softfloat.c:486:round_canonical: code should not be
reached
1:47 PM Emulator: Process finished with exit code 3
I got to know about the canary build of the android emulator for AMD processor from here. My virtual device' CPU/ABI is armeabi-v7a. I searched for what the 'exit code 3' for the emulator mean but I didn't get any solution.
Can someone help me please!
I got the android emulator working today.
I have done the instalation process for canary build of android studio from the beginning:
1. Enabled "Hyper-V" and "Windows Hypervisor Platform" in "Turn Windows features on or off" settings of Windows. This has been explained in here.
2. Downloaded the latest Canary build of Android studio from here.
3. After downloading the zip file I followed the guidelines in here under "Install alongside your stable version" heading. The guide lines are:
a. Unpack the ZIP file.
b. Rename the resulting folder to something unique like "Android Studio Preview."
c. Move it to a permanent location, such as next to your existing Android Studio install in C:\Program Files\Android.
d. Inside C:\Program Files\Android\Android Studio Preview\bin\, launch studio64.exe (or if you're on a 32-bit machine, launch studio.exe).
4. After launching studio64.exe I got a pop-up message to update Android emulator. After the update I created a new virtual device with an image of x86 with android 9.0. I started the android emulator to test my app. Though I got the
Verified boot params were not found
popup error message initially, the emulator started functioning well.
I am a very new Android developer and was until today having the same issue as yourself. Here is how I got it to work (Please note I am also on an AMD system).
Make sure you have enabled Hyper-V and Windows Hypervisor Platform. If you type "turn windows features on" in your run bar you should be able to locate it. Also enable virtualisation in the Bios. Mine comes under "SVD".
(Please note after this step I was still experiencing the problem but this is a pre-requisite).
Delete all devices from the AVD manager.
Install a new x86 device from the AVD manager. What I did here was select a version down from the one I was previously getting issues on so Oreo from Pie. When it asks to confirm if you want to wipe the user data please confirm positive.
Once setup, run the device from the AVD manager. It may ask you if you wish to enable Instant Run. I elected to disable this. (I had enabled it when I first was trying to run a device).
You will still receive the 1st error regarding no boot parameters but the emulated environment should load. You can now run the APP and it should install the APK. Previously due to the device not coming online properly, the APK would not install. I can also now setup a device on Pie without experiencing the issue so I think it may have been the wiping of the previous data that helped.
I wish I could tell you WHY this worked for certain and previously it would not work, sadly I cannot but hopefully this will get you working.
I am using Windows 10 and when I launch the Virtual Device Emulator in Android Studio I keep getting the message which reads:
"The ADB binary at C:\Users\siviw\AppData\Local\Android\Sdk\platform-tools\adb.exe is obsolete and has serious performance problems with the Android Emulator. Please update to a newer version to get significantly faster app / file transfer".
I am a new developer with little experience. What do I need to update to a newer version so that message is no longer shown?
I am new to android as well. dkalev's answer is correct but not very descriptive for a new user. I have outlined the steps below.
Double Shift to open the search box
Type SDK Manager
In the results shown click "SDK Manager"
In the window that opens click the second tab "SDK Tools". You should see that there is an update available for SDK Build-Tools on the first line
Check "Show Package Details" in the lower right hand corner
Scroll to the last (latest version) item under "SDK Build-Tools" and check the box. (Mine was 28.0.1)
Click "Apply"
In the dialogue box that pops up, click "OK"
When the installer finishes, click "Finish"
Uncheck "Show Package Details" and look at "Android SDK Build-Tools" (first line). There should be no update available and it should say "Installed"
Click "OK" to close the SDK Manager
For me, update SDK doesn't help. I solve this problem by unchecking the emulator option "Use detected ADB location". Give it a try.
I had the same problem and solved it by updating the Android SDK Build-Tools. Open the SDK manager in Android studio (double shift and type SDK manager). Then on the second tab (SDK Tools) update the Android SDK Build-Tools and the error message should go away.
This is an years old bug.
Check your adb version like this : (the adb path is given with the error itself)
C:\Users\<your_user_name_>\AppData\Local\Android\Sdk\platform-tools\adb.exe --version
output :
Android Debug Bridge version 1.0.41
Version 29.0.4-5871666
Installed as C:\Users\sunil\AppData\Local\Android\Sdk\platform-tools\adb.exe
It means this adb comes from the latest sdk platform tools 29.0.4.
Check the latest version from official site here.
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
17-01-2019
This works for me.
Just opened Android SDK Manager Then it showed 4 Updates Available. So I just Updated it and No more above warning.
Had the same issue but in my case the fix was slightly different, as no updates were showing for the Android SDK Tools. I opened the Virtual Device Manager and realised my emulator was running API 27. Checked back in the SDK Manager and I didn't have API 27 SDK Tools installed at all. Installing v 27 resolved the issue for me.
In my case what removed this message was (After updating everything) deleting the emulator and creating a new one.
Manually updating the adb didn't solved this for. Nor updating via the Android studio Gui.
In my case it seems that since the emulator was created with "old" components it keep showing the message. I had three emulators, just deleted them all and created a new one. For my surprise when it started the message was no more.
Cannot tell if performance is better or not. The message just didn't came up. Also I have everything updated to the latest (emulators and sdk).
This happened to me. And, in my case I need Android SDK Platform 29 because I am using react native 0.63 and Android 10 (Q). I had to uninstall Android SDK Platform 28 because it was the one that caused the warning.
I found this video See Here explaining the process.
Open Android Studio then click on configure
Go to SDK Manager
Go to SDK Tools and click show package details
Uncheck Android SDK Platform 28 (OBS: for me) and Apply
Click OK and Finish.
With this I was able eliminate the warning.
I had the same problem and solved it by updating the Android SDK Build-Tools in Android Studio.
step 1 - Double shift and type SDK manager, this will open the SDK manager
step 2 - Then on the second tab (SDK Tools), update the Android SDK Build-Tools and the error message should go away.
if this does not resolve check the option in Setting tab,use detected Adb tool in Setting tab
(You mentioned you are new to Android Studio) so I recommend pressing the Android Studio > Help > Check for updates... button that will update your environment.
I solved this error by uninstalling two older SDK build tools versions, leaving only the most recent one.
The solution that worked for me -
I closed my Android Studio.
I visited this site - https://androidstudio.io/downloads/tools/download-the-latest-version-of-adb.exe.html
From there I downloaded the latest adb.zip file
I unzipped the folder and copied the 3 files -
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
I went to the folder - C:\Users\PayelSenapati\AppData\Local\Android\Sdk\platform-tools
There I replaced the old files by the new files. (Paste followed by replace the existing files)
Then I reopened my Android Studio, opened my virtual android device. Everything went fine. The error was no more.
In the SDK Manager, in the SDK Tools tab, check if you have any updates, if not, deselect "Hide Obsolete Packages" and check if you have something marked as (obsolete) if so, deselect the item and apply. In my case, it was the Android SDK Tools.
First you need to check which SDK your Emulator is using and as #kuya suggested you need to follow those steps and install the latest version of that SDK Build Tool. Suppose your Emulator uses SDK 27 then you need to install latest in that series. For me it was 27.0.3. After that the error was gone.
Try factory reset to virtual device from Android Device Manager
None of the top-voted answers worked for me, except when I unchecked "Use detected ADB location" as mentioned above by #褚阳光. Fortunately, in my case though, the message didn't show up, even when I turned it back on. In other words, the problem might be resolved by restarting "Use detected ADB location" :)
Try update your SDK Tools items, and then delete all currently created emulator and recreate again. it works for me
This might sound normal but I was getting the same error but just updated it and it worked now without any error. I suggests anyone to try for updates first.
If you are stuck after following each of the steps outlined in above, I will suggest you combine more than one answers. The answers of #Kuya and #褚阳光 worked for me. Try them out. I can explain more if the steps are yielding results for you.
This can also be an issue with hyper-v settings on Windows 10 pro. Because with this error I was facing BSOD - https://www.techclassy.com/fix-hypervisor-error-bsod/
I faced the same issue, and I tried following things, which didn't work:
Deleting the existing AVD and creating a new one.
Uninstall latest-existing and older versions (if you have) of SDK-Tools and SDK-Build-Tools and installing new ones.
What worked for me was uninstalling and re-installing latest PLATFORM-TOOLS, where adb actually resides.
I got this error and I tried all the possible solutions that I found on every site, nothing worked.
I was working with flutter, and the command flutter doctor showed me that I need to accept a few agreements
I did that and ADB started to work
So conclusion:
If nothing works, install flutter, run flutter doctor, execute the commands that flutter doctor suggests to you. This should solve your problem
the command was: flutter doctor --android-licenses
I followed the answer, but the magic final step was deleting the existing virtual environment and creating a new one.
I've searched all over the web for the past 3 days and can't seem to find a solution. I've done everything mentioned in this post:
Android emulator not showing in Visual Studio
It seems all the 'working' solutions to this problem has been stated in what this guy says he did in his original post, including restarting ADB server (kill and start), restarting my computer, reinstalling emulator and HAMX, installing and running as an admin, changing the timeout delay, reinstalling almost everything, making sure my emulator is installed, etc.
It keeps saying Gradle build finished in 475ms, etc and then waiting for target device to come online for like 5-10 minutes and nothing happens. No emulator shows up. I can't seem to find the solution to this and I am on the verge of giving up, I really need Android Studio to work so I can start on my app.
Can I please get some guidance with this?
If it's relevant, I'm using a Mac.
Have you tried this. Go to the emulator settings and set the Graphics Emulation mode to Software GLES. The default mode will be automatic. I am not sure how it works, but that worked for me on two Linux machines. Being software emulation, the performance of the emulator will not be as good as when using hardware graphics. It seems to be a bug with the SDK.
For me the only thing that worked in macos was to disable docker before starting Studio.
Wipe the data of your Android virtual Device and then start the emulator.
I was using Android studio 4.2 and faced this issue.
No Solutions worked for me so I just erased android studio files. Updated to Android Studio Arctic Fox.
Link to remove android studio files from mac : How to completely uninstall Android Studio on Mac?
For Windows : How to completely uninstall Android Studio from windows(v10)?