i have created a AVD,it starts normally asking for "Connect to charger" and then it stops working.Unable to understand the problem.please help
You need to set a sufficient memory for your emulator in the AVD settings, try to update if you didn't and as suggested use genymotion which is a good alternative, if your using eclipse try out Android studio
Related
I cannot get sound working in the emulator in Android Studio. It's not my code as it's a very simple example program to demonstrate the MediaPlayer that works fine on an actual device.
On the emulator in Android Studio there is absolutely no sound, not even system sounds. Is this an Android/Android Studio bug? Or could it be the configuration of my particular system? Windows 10 issue?
Anyone else having this problem? Any solution other than using a real device or Genymotion (which I've never used) ?? Thanks.
EDIT: The only way I can get the emulator in Android Studio to start with audio is to launch it from the terminal with both the "-no-snapshot" and "-no-snapshot-load" options. And this only works about 80% of the time. It has something to do with snapshots. There are a couple of old questions on this but no solutions.
it seems that the problem has something to do with the emulator api so changing the emulator api solved it for me and I guess it will do for you.
Try to open your Oracle VM Virtualbox. Go to Settings -> Audio -> Host Audio Driver and change it to PulseAudio.
Let me know if it helps.
In Android Studio, click the Volume Up button (doc).
The android device monitor in Android Studio is not running no matter how many times I click on it, there are no errors showing up or warnings.It's just not running, I don't know why this is happening because I used to open it with no problems whatsoever. what could the problem be?? THe android sdk path is correct and the emulator is running and there are no errors in the code. Please help
Try using ALT + 6 to open the device monitor window, or are you saying that Android Studio is not finding your device?
It takes an awfully lot of time for the ADM to finally appear. Just wait, do something else while it is opening.
i'm using titanium appcelerator for developping an opp on android but i think this question can be answered by any android developper and anyone else using the android emulator.
It's already too long to wait for the emilator to be ready and for me always the first execution which makes the emulator for the first time stops on the "waiting for the emulator to be ready" step and i have to restart the app again and if the new launched app will start a new emulator instance it will be worst.. So is there a way to force always using the already created emulator instance ?
you mean emulator?
If there is an emulator, it will not start new one .
Do not close it .
I would suggest that you install Genymotion to use for emulation. Titanium Studio will see this as a device, rather than an emulator. On the flip-side, I'm not sure if debugging works with it yet. You may need to look for mods to make to get this working.
After installing Genymotion you select some emulators from their available list. You'll start the Genymotion emulator yourself, rather than Titanium Studio starting it for you. Titanium Studio's list of devices will need to be refreshed or restart Titanium Studio. Run your project. Titanium Studio sees the device more like a physical device, so it won't keep opening a new one on you and speed up the process a bit.
https://www.genymotion.com/
There my be a more official way to fix the Android interaction, rather than my idea of side stepping it.
Simple :
Goto Terminal/command prompt
Type in adb connect 127.0.0.1:5555
Now the emulator will be seen as device to Titanium studio, enjoy!
I've setup Netbeans using nbandroid (http://kenai.com/projects/nbandroid) which has been working just fine for the last few days. I've already made a small app which runs in the emulator and even on my phone.
The thing I can't get to work is the debugger console in netbeans.
If I add these lines of code to my app nothing appears in any of the output screens in netbeans.
System.out.println("blaat");
Log.d("info", "blaat")
Even though I'm 100% sure the code should run. Any suggestions on what I might have missed?
Try opening a new cmd prompt and type "adb logcat".
Ok, just found a better solution in another question:
Android Debugging with Logcat and Emulator. Is it possible?
started using ddms, which is exactly what I wanted.
I'm developing a application that works on linux. I want to port this to the Android SDK Emulator. But everytime I start the application the emulator crashed with a segmentation fault.
Somebody has any clue why a selfmade program that's running on the Android Emulator could crash the entire emulator?
Can you post up some code examples / logs of what is happening? You don't provide enough information for us to suggest why it would fail.
Best thing I can advise is to create a new emulator (only takes a few clicks) and try deploying your app on that, possibly try a different version.
If you can post up some logs/code examples of what might cause this, we can provide better answers
Another debugging point to try would be launching a demo application/Hello Android on the emulator, to see if it is your application specifically.
Apparently there was a bug in the version of the emulator that I used. When I updated the emulator to the latest version, it was solved.