Ive started with android development today.
Im having difficulty creating a virtual divice
Ive done everything to the word that the android tutorial said.
But on creating a new device, the target only has one option. Android4.4W - API Level 20
This in turn renders the CPU/ABI to be greyed out. No System images installed for this target.
I went to the Android SDK Manager and had to manually add urls to download form.
Here they are:
My assumption would be that I need a ARM emulator (if you call it that), but I dont know the url to that and also, Im not 100% sure that that is the problem.
Got the answer. Why would this be the case. Installation problems?
https://stackoverflow.com/a/23243432/2240163
Related
Sorry for posting here, I can't find any support for android studio. Tried posting on reddit but no one is there. If this is the wrong place then please point me to support.
The AVD manager is missing. It's not in the hotbar and it's not in the Tools menu. Just completely gone.
It's a fresh install on the pixelbook go. I've tried uninstalling / reinstalling. I've installed on other chromebooks and it's showing there so have no idea what's going on.
And.. i need to rant a bit before i explode. To the android studio devs if your product is not working then please SAY SO. The amount of time, money, and effort I've wasted trying to get android studio working on a chromebook is insane. This has been the worst software experience of my life.. seriously, you guys need an award for how bad this is. In the three days and three chromebooks I've purchased trying to get this working I've ran into at LEAST 10 different issues and interestingly enough they are different for each chromebook / install.
Try using Linux, It will be more faster then windows.
Ideally it is advisable to use MAC.
And Yes,
Android Studio is heavy. It needs more processing and memory requirements than other development environments. But when you list out the features available it's nothing.
Use proper hardware for good experience.
For AVD find the screenshot.
check the highlighted part for device manager
Easiest way to press shift two time and search for device manager. I have submitted some more way to find device manager or AVD manager via toolbar et.
When clicking the Create New Hardware Profile button or the Clone Device button in Android Studio AVD (Windows platform) neither button does anything. In looking for any log files which may indicate what is going on, I located the following folder and do see that upon launch, two thread-dumps are generated, but no logs are written when attempting to perform either function.
C:\Users\Bob.AndroidStudio2.1\system\log\threadDumps-20160718-072320-AI-143.2915827\freeze-20160718-072340-10
I have read through many posts on this and similar issues with AVD, including a defect from Google that was posted almost 2 years ago. I have yet to find any solutions or work-arounds that will address this issue.
Has anyone found a way to fix this?
I was never able to resolve my issue while working with Android Studio in a Windows environment, so my resolution to this was to build/use a system which is running Ubuntu and now everything is working perfectly.
So i'm having awful trouble trying to get the Emulators in the Android SDK to start up. I can create the AVDs just fine, and then when hitting the 'start' button from the SDK Manager, bring up the small loading console window, indicating that the emulator is launching. However, after that, nothing happens!!
I have read many threads and posts with people having the same problem, maybe to do with the settings requiring too much memory, with some people waiting 30 minutes for the emulator to load!!
When trying to run the AVD emulator through terminal, I simply get a 'Bus Error' with no further indication of what could be going wrong...could it be a memory issue?
What I did to get where I am now:
Download the Android SDK package for Mac. I'm extracting the sdk only, not eclipse. I'm on Mac 10.6.8.
Install the SDK, and download the latest version of Android in the SDK Manager, along with default tools.
create a AVD and hit start.
window pops up to boot the emulator, that process is complete and window closes.
Nothing happens.
My knowledge of the sdk tools are very limited, all I want is to be able to do some testing...
Any help greatly appreciated!
Thanks
Actually, the simplest way to get emulators running right now is probably GenyMotion. They provide an interface, and pre-configured emulator images to make it pretty simple to get running.
This is not an endorsement (I use the standard ADT myself) but a lot of people find their tools useful.
Here is my suggestion: instead of using AVD, start using espresso and virtual remote android hardware emulator from Google servers - also known as android-test-kit. You will have the possibility to run and test you App on several different devices, without the need to spend money on actually all different devices for developing and testing purposes before releasing your Apps. You find further details here:
android-test-kit
Why Espresso
The 2 videos are somewhat long, but worth watching.
Taking this approach will solve your problem, save you money, and improve your productivity.
I run into the same issue on my mac 10.6 and it only works if i do
emulator64-x86 -avd my_android
Besides, my virtual device has to configured using x86 but not ARM
maybe this link can help you.
I have have been using the Android emulator both and the command-line and in Intellij for some weeks running ApiDemos and my own apps with no problems.
Now, without any exceptions or messages to indicate the reason why the emulator will only run the emergency call app and nothing more.
Is this a bug? If so, how do I create an issue for the Android SDK dev?
I'm cautious to load any .apk now into my handset to see if the condition is the same.
Particulars follow:
OS: Ubuntu 12.04
Android SDK: 4.1 (ICS).
JDK: 1.7.x
Maybe a stupid answer, but are you sure you didn't set a PIN code on the lock screen? This will load the PIN entry screen whenever you load the emulator but still allow you to make emergency calls.
You have to set a PIN on Android ICS when you save new security certificates, which caught me out.
You need to use 2 GB of RAM o avoid that problem in your android emulator.
I am trying to view a sample app on a real device (a ViewSonic G-tablet), but the device won't display in the "Choose a running Android device" area. The virtual devices show, but no real devices show (there is only one plugged in, the G-tablet). Some other information...
I am using a Mac with Eclipse SDK 3.7.1 w/Android
App is noted as debuggable in manifest file (android:debuggable="true")
G-Tablet is set to allow debugging
Device selection is set to manual in SDK
I CAN view files on G-Tablet using Finder
I have reviewed Android developer docs
I have searched a lot online for a fix, without success
Please also note...
There is NO option on G-tablet to allow "unknown sources". However, I have downloaded apps outside the customary channels (e.g. Firefox from the Firefox site) and it works fine.
I do NOT want to do anything to the G-tablet to void the warranty.
I have already checked for/installed updates using the Android SDK Manager.
The fixes I was able to find on StackOverflow related to this problem did not work for me. I am thinking the problem may be device specific. One fix discussed getting a driver for the device, but I couldn't find one.
Can anyone please help me figure out how to get the SDK to recognize my device? I'd appreciate any insight on this.
Can you export the app as an .apk and run that on your G-tablet?
also is the android:minSdkVersion set to a value lower than your G-tablet's version?
Found the answer after trying a zillion things. All that needed to be done to fix the problem was turn to OFF 'USB debugging' and then turn it right back on. I found the idea on this page... http://www.mobileread.mobi/forums/showthread.php?t=156247 . Hope that might save someone else hours of time.