I have some trouble about android studio. if anybody know this program, please read description of my problem.
I created empty activity project android 5.0(lolipop) and just click run by emulator. I already tried different kind of devices, but the error is the same. My friends have no problem like that.
please tell me what to do.screenshot of emulator error message and photo of log error
updated event log after trying reinstall emulator devices
Do you have Bandicam installed like it's suggesting? It's complaining about your Vulkan drivers ( you could update those) and Bandicam messing with them (you could uninstall that).
Alternatively you can open your AVD Manager, edit the AVD you're using, and set Emulated Performance: Graphics to Software (can't do it on every image for some reason - my API 29 Pixel 3 image won't let me change it, my API 30 Pixel 3XL image will). It'll run worse, but it'll run (well it should anyway)
If you use the flatpak of android studio on linux, run "flatpak update" and that should resolve your issues.
If you don't use the flatpak on linux, try restarting your machine and if that doesn't work, do a clean reinstall of your graphics driver.
Don't know why people keep trying to recommend software rendering, it's horrible and not at all practical, it's a barely working workaround not a solution.
Related
I just downloaded Android Studio and the simulator for some reason is zoomed in very far or has enormous text. I've tried everything on the right-hand bar to handle this and there are no menu bar options. How can I resolve this?
I was experiencing the same exact problem at first. After I had opened my project in Android Studio, the IDE installed a bunch of other libraries and tools; in turn priming the environment. To note, this was all after a fresh install of Android Studio. After the supplemental install, I then started the emulator from the AVD Manager from within the IDE. Afterwards, whenever I ran the emulator again I had experienced zero issues like this. I understand some of this sounds anecdotal but it seems that the Android Studio IDE helped sort this out for me at least.
I would also like to note that, if you experienced any warnings or errors when executing the simulator, it may also be an issue originating from the emulator's environment itself. Possibly tweaking some of the settings on the emulator could also help (i.e., memory/storage capacity).
I am trying to start development on an Android app using Android Studio, but whenever I try to run the app I get the error Unable to obtain result of 'adb version' I have tried uninstalling and reinstalling Android Studio multiple times on different computers (both running Windows 10) and every time I get the same error. I have researched the problem and have been unable to find a consistent solution. (or one that actually works) I am very new to Android development and am slightly at a loss as to what to do; any help on solving this problem would be much appreciated.
Found the solution thanks to #user3109468, Android Studio had the directory for the Android SDK wrong. In File>Project Structure make sure the directory for the SDK is correct; mine was C:\Users\[user]\AppData\Local\Android\sdk (Google had given sdk a capital "S" for some reason...)
Uncheck: enable adb integration from Tools>Android and re-enable it.
This worked for me.
This might be because of windows virtual memory problem.
Try running adb from command line. something like
adb version BTW, platform-tools would be located in
c:\Users\<your userid>\AppData\Local\Android\sdk\platform-tools
How much it takes from you firing a command and actually gets an answer ?
if it takes more than 5 seconds, then android studio times out waiting for an answer and throws up an error.
How to fix ?
close all your program ( Process ? )
and go to control panel -> System->advance System settings-> Advanced tab->performance->settings->Advance->Virtual memory change
Try to reduce virtual memory size. Fr e.g. If it's 4096Mb make it 2048Mb ( both initial and maximum) It will ask to restart, so restart and get yourself a cup of coffee, because it will take a while. Then, once your system is up , try running adb version. Does it run quickly ? If yes, problem is fixed. Go back to virtual memory and increase it's size to the one before, and that's it.
BTW, I noticed in my case that simple hello world program was taking 20 sec to execute on my machine before fixing virtual memory problem.
Make sure Android SDK location and Android NDK location is correct.
Go to File -> Project Structure.
Set the Android SDK location and Android NDK location.
When I am trying to run an app using the emulators on the Android Studio, it is stuck on this window.
It should let the user to select an emulator.
What could be the cause for that errors?
sometimes I have seen this when adb isn't able to start. That doesn't seem to be your problem. I can suggest going to your android sdk folder run the avd manager program and see if you can repair / adjust any settings you may need.
I have created a VM Ubuntu 14.04 using Vmware Player, and I've installed the ADT environment for Android Development.
I have created a new Android emulator using the shortcuts present in Eclipse; when I tried to start emulator I got the following known error:
Starting emulator for AVD 'AVD_for_Nexus_5_by_Google'
ERROR: 32-bit Linux Android emulator binaries are DEPRECATED, to use them
you will have to do at least one of the following:
- Use the '-force-32bit' option when invoking 'emulator'.
- Set ANDROID_EMULATOR_FORCE_32BIT to 'true' in your environment.
Either one will allow you to use the 32-bit binaries, but please be
aware that these will disappear in a future Android SDK release.
Consider moving to a 64-bit Linux system before that happens.
I fixed it in both ways: putting a variable in my .bashrc:
export ANDROID_EMULATOR_FORCE_32BIT=true
and also setting the emulator option in the Eclipse preference dialog:
Nevertheless, every time I try to start the emulator I got always the same error.
The wierd thing is that if I try to start the emulator from a bash window, it starts normally.
This could have been a boring workaround, but I would have been happy anyway. The problem is that when I try to deploy an application from Eclipse, the emulator started in this way is shown as "Offline" and I cannot run any application on it. Possibly I can upload the apk into the emulator from the command line, but debugging the app would become a bit harder.
Has anyone got the same problem or does know how to fix it?
I found out a partial solution for connecting eclipse to the running emulator started by command line: the emulator MUST be started with no snapshots.
Indeed, if I start the emulator without snaspshots, it become "online" in DDMS, and I can finally use it.
Although this could be a bit annoying, because starting the emulator from scratch every time it takes a long time, at least I have a way to use it.
On the other hand, I don't know exactly the reason of this behavior, if someone has an answer it will be appreciated.
Moreover, I still do not have idea why I'm not able to start the emulator from Eclipse.
I recently got introduced to Android via a school course. Did some very simple examples earlier, and decided to installed all the required peripherals at my home computer too. I was on my way to develope all kind of cool stuff, until i noticed that something is wrong with my Android SDK or the emulator itself - it won't run any of the programs i try to.
I've got Eclipse & All the required add-ons / plugins installed. I get no error messages at any stage ( in eclipse or in the emulator itself ). Whenever i press run at Eclipse, the emulator takes it's time and starts up, but doesn't start the program, and doesn't actually show even the slightest hint of it. Looks just like if i had tried to start only the emulator. I've tried to create several different AVD's, and tried to use different versions of Android on them. No luck.
Im using windows 7 x64, and after a couple of rounds with Google, i found a few other guys who are having the same problem with the same OS.
Any help is greatly appreciated, as im running out of options here.
You need 32 bit eclipse and 32 bit JVM. There should be an error in the "console" window in eclipse if you hit run.
Click on the Menu button of the emulator to unlock it. You may then need to rerun the app.