My Pixel 2 Android Emulator won't play sound, not from my app, not even from YouTube. I've restarted my computer, cold-booted the app, yet nothing works. I can use a physical device, but I'd like to have my emulator on the side while coding. Any Ideas?
Most of the other similar questions seem to be from 5-10 years ago, probably out of date? I've been working on this all day, so any advice is hugely appreciated.
Try restarting the virtual device from scratch without using a snapshot. Here are two ways to do that:
Change the power button on the virtual device so that it actually does what it is supposed to do.
Go to Settings->System->Gestures->Press & hold power button. Select the Power menu option. Then press and hold the power button on the virtual device and select Restart.
Start your virtual device with the Cold Boot Now option.
Fortunately, I found the problem, although it wasn't directly related with the Android Emulator. The problem was with my missing/outdated usb sound drivers. Here's basically how I fixed it.
Press on the Window Key
Type "Device Manager" and hit Enter
Open "Sound, video and game controllers"
Note the name of any of the driver with a yellow warning sign on it.
Head to Google, search for that driver name, and download it
Open the Android Emulator, Test, and Enjoy success :)
Related
The first day my V60 thinQ smart phone worked fine with android studio. The next day after working on my project for about a hour my smart phone no longer showed up in the run/debug configurations drop-down. I was not able to run the app on my device.
I went to trouble shoot device connection
When I clicked on Re-scan device my smart phone showed up. Also in windows Explore my smart phone shows up,
Right before my device stop showing up a dialog came up asking me what i wanted to do after plugging in my smart phone. I forgot exactly what it said and what I clicked on.
Does any one know what is going on?????
I believe, the popup that you saw right after plugging your device is asking if you trust your PC to connect over adb usb-debugging mode.
Sometimes, this happens to me. The way it works for me is: going to Developer Options > USB Debugging Mode. Then, i disable usb debugging then, re-enable it again and after that usually Android Studio detects it or, it shows the popup again. If you don't see the popup just unplug and re-plug your device once.
The popup should look sth like this with an RSA fingerprint of your computer:
Now, you have to click: "Allow". And, android studio should detect your device.
I'm following along with the tutorial provided by the Android Developers official site and using the help files in Android Studio, but I'm finding out of date screenshots and feeling very confused and a little frustrated.
I have a Pixel 2 connected via usb.
I've enabled developer mode on the device.
I've got it not sleeping when connected via USB.
I've enabled USB debugging in the Developer Options on the phone.
...I just need to figure out how to get my Mac to see it via Android Studio.
The tutorial alludes to a configuration screen that I don't see in studio. I see something similar but the device drop down is disabled.
Hit the sync button,
Wait for downloads(don't stop the hidden downloads)
Restart if necessary, wait for the first invocation to complete work.
Then enjoy your first app.
Happy coding :)
answer: hit the sync button (elephant/mouse looking icon with a diagonal arrow), wait for downloads, don't stop the hidden downloads, then restart if necessary, wait for first invocation to complete, ...then it will (hopefully) work.
I opened AVD,clicked on create a virtual device then I choose nexus 5 ,clicked next and selected KitKat and pressed next,and then clicked finished. But then it just takes me to the home window of AVD which was there when I opened AVD. I cant know for sure if the device was created or not even. Can any one help me out please.If its generaring any error message where could I see it?
avd takes lot of time to open, so you will have to wait sometime
i will suggest you to use your android mobile for running your project that way you dont have to wait.
follow this tutorial
https://www.youtube.com/watch?v=Qb2olFyoMV4
What i did was opened android studio from my terminal,then did the whole process again.the error was dumped to my terminal and it was the problem of so many files in my /home/kirubel/android/sdk/tools/ directory didn't have the read-write permission.so when i changed that it worked.
As alternative you can use Genymotion or droi4x or Nox app player for me it's better than AVD ( you can debug your app directly to droid4x or Nox app player like you are using your android phone via usb )
I'm using Eclipse+ADT on Mac OS. I have a Nexus 5 connected via USB, but it does not show up in the Android Device Chooser when I run my app from Eclipse. Actually, it did show up once, and I could deploy my app to the phone, but then it just disappeared from the Android Device Chooser.
The really weird thing is that the device is listed when I run
adb devices
on the terminal. I even get the debug messages from the phone in Eclipse's LogCat, so it clearly is connected and recognized – but it still doesn't show up in the Device Chooser. I have tried all the solutions proposed here (rebooting the phone, turning debug mode on and off, restarting adb, restarting Eclipse, etc.) – to no effect.
Any ideas?
I had the same problem. I couldn't see my Nexus 4 in the Device Chooser list even though I could see it in the DDMS. I found out it is just hidden from view. Click the device chooser list and scroll up with your mouse wheel. The device should now be visible in the list.
Eerily similar to what I just spent the last hour figuring out. OS X, Nexus 5, shows up in adb devices, tried everything under the sun.
In my case, it turned out that even though the device wasn't listed, I was able to press the OK button and it launched just fine. (seen below)
I'm not sure if it also helped, but before I stumbled upon that solution, I edited my Launch config options to change from "Always prompt to pick device" to "Launch on all compatible devices/AVS'S" and selected the "Active Devices" options. I ran that and it worked! I expected the device to start showing up in the above menu afterwards, but it didn't. Then I realized it didn't matter and I could hit OK and it would build. Go figure.
The solution of blazeline worked for me but it was a little bit tricky to scroll up to make appear the device.
Another way to do it and to make appear the device more clearly is to disconnect your device when the Device Chooser List is opened and to reconnect it. It will clearly appear now in the device chooser list.
Eclipse is really sometimes strange...
My case was same as mentioned here and obviously i did all tricks with no success but solution was very logic:
device i was missing in pickup list had lower API then allow by AndroidManifest.xml
My Device shows up on the Android Device Chooser as:
Serial Number -- Ige-vm670-A0000028F1773B
AVD NAME -- N/A
Target -- 2.2.1 (with a green check mark next to it!)
State -- Online
Everything seems fine..So, I press the "OK" button on the bottom right hand corner of the Device Chooser screen. When I do this the Device Chooser closes and the Launching bar in eclipse eventually finishes, but then the application never starts on my phone!! :(. Am I missing something? I tried using different USB cables, switching from USB 3.0, and checking if there is enough memory on my phone but nothing seems to work :(. PLease help this newbie!! I'd much appriciate it!! ALso, i'm running eclipse in windows 8.
following steps may help you
1)Restart your Device
2)Go to application settings and enable the USB debugging.
3)also enable other application to run on your device.
4)make sure that device status is online on android device chooser.
5)make sure that your device appear in device list in android Eclipse.
If above steps wont help you then try to run your project on emualator.And if emulator fails to launch your project then you need to see the android console
Enabling SD-Card access may result failure of connecting to the device.
Please try to switch MTP on instead of either PTP or SD-Card