I installed a fresh api 19 emulator (x86 variant) and it doesn't get past the splash screen. someone told me that sometimes it gets finicky that way and I should delete the device and create a new one, so I tried doing that but it goes back to the same problem, infinite "android" splash screen.
how do you diagnose stuff like this? I have several other, newer emulators and they all work.
I have the device frame off just to make sure it is not that.
It is using the 5x as the basis for the device.
I increase the heap size to 256mb, and the ram to 2gb, but otherwise don't change much.
Try changing the graphics mode from Hardware/Auto to Software:
Go into the AVD Manager, select the Virtual device, and click "Edit"
Find "Emulated Performance" -> Graphics, and switch that from auto (or hardware) to Software.
It will not perform well compared to in Hardware mode, but it may give you insight into what is causing the problem if it runs this way. Hopefully Google/Jetbrains will get that figured out in a future update.
I ended up posting a bug report. The bug has been confirmed, given medium priority, and a work-around solution has been outlined which I can confirm works.
Related
I recently had to reinstall Android Studio as a last ditch attempt to fix the "java_find.exe not found" bug. Unfortunately, this new build seems to have a radically different AVD interface that makes me unable to configure a lot of aspects of my virtual devices that I would have been able to with the original format and worse seems to only create emulated devices that never progress past the boot-up screen. After an extensive amount of google-ing I seem to be the only one on the planet who has this interface, so any explanation or advice would be massively appreciated.
(EDIT) Here's an image of an emulated device I just made. For the API I have no other option other than different versions of 21. In this case I chose the first option.
However, the same problem still persists where the emulator never progresses past the android screen. (It's been running for 10 minutes now when before my emulators would start in less than two.)
I've also just noticed this error hidden way in the bottom left corner of android studio.
"Could not find a matching system image for ABI x86, API 19/null: Could not find a matching system image for ABI x86, API 19/null"
Could this be related at all?
After an extensive amount of google-ing I seem to be the only one on the planet who has this interface
Fear not! I have the same screen. I installed android studio last week and I'm on the Beta version 0.8.14
Unfortunately, this new build seems to have a radically different AVD interface that makes me unable to configure a lot of aspects of my virtual devices that I would have been able to with the original format and worse seems to only create emulated devices that never progress past the boot-up screen.
I just created an AVD for the sole purpose of trying to recreate the issue. I created an AVD with a Nexus 4 and api 19 (kitkat 4.4.2), then booted it by pressing the play button in the Actions area.
It did take a couple mins (~4) but eventually it booted and now works fine.
any explanation or advice would be massively appreciated.
Explanation: sadly don't have one
Advice: reinstall and see what happens. Or show me your actual virtual devices screen so I can try and reproduce your errors.
Edit
I created a new AVD with the same specs as yours, and it booted fine.
Do you have these system images installed? (in SDK manager) or at least the one(s) you are trying to use for your AVD
I have used Eclipse to write apps for android multiple times without issue but I am now trying the new Android Studio which I like but here is my problem.
When I run the app I pick my AVD and then tell it to start. The emulator starts loading and then says paired. Then it starts telling me to swipe up and left and right to display and remove cards. Then it says to put hand on screen to dim the screen, ok well I'm on a MacBook Pro so that don't work I swipe to get past that part sometime I can others I can't. Next it says to touch the clock and say some words which also can't do on my Mac, and that is where the emulator stay it never goes to a home screen and it does this no matter what AVD I choose. How can I get the Emulator to just plain open to the home screen like it should.
Thanks for any help.
In your AVD Manager, edit your AVD and make sure your Target is "Android L" and not "Android X.XW". The "W" stands for "wear" and that is causing your issue.
Alright I figured it out. I remember having a similar problem recently when I was taking an android development class for college using eclipse and sure enough that was it.
So here was the solution eclipse gave same problem. for some reason if you have caught exemptions such as hard coding a string etc. the emulator will not run till you ignore these exemptions or fix every last ! mark in your code. Once you do this the emulator will load and run properly.
I also had the same problem with my AVD. The Android Emulator window just used to pop us and the green bars flowed infinitely. After lots of trial and error I arrived at a solution for my problem. the problem was with the Heap size and the RAM size.
Initially the default heap size was 128 MB and RAM was 1563 , I just changed the heap size to 512 MB and reduced the RAM size( high RAM was making my PC run slow) also I enabled hardware acceleration. And Yipeee, it worked.
I am developing an app in Android that I hope to release. I've got most of my GUI done, but it does not look even close to correct on the device when installed and opened. I have a screenshot of how it looks, and a screengrab of how it should look (taken from the Emulator in Eclipse) at the links at the bottom of this post. It's best to take a look at the two images rather than me try to describe how screwed up the app becomes on my device.
I had a friend with the exact same device, including hardware and Android version, and his loads up just fine. Does anyone have any idea what's going on here? Both devices are Galaxy Nexuses, running Android 4.0.2, GSM on AT&T (unlocked).
Installed on my device: http://i.stack.imgur.com/x66Jo.png
In the emulator: http://i.stack.imgur.com/qE0J6.png
I've seen this occur in some Galaxy Nexus' and I put it down to a bug/glitch in the OS on that Galaxy Nexus. Try a Factory Reset of your Galaxy Nexus, if that fails, try reinstalling the current OS version you have (if you can get your hands on it), if that fails, get it fixed under warranty.
Does your app use multiple activities?
Can you compare on your two devices if this setting is the same?
Settings > Developer Options > Don't keep activities checkbox.
I realise this is an old question now but I was having the same problem as you and stumbled across a solution. I didn't particularly want to factory reset my phone as per straya's instructions, so I started playing around options in the Settings > Developer Options menu.
As it turns out, this problem occurs for some applications if you have the Force GPU rendering option checked. Disable this (I'm not sure why it was enabled anyway) and everything displays as it should.
Well? I've tried increasing the RAM size of the emulator to 1024 MB and there was little improvement on the speed, however, it's still unusable. It has the speed of a turtle.
Anyone got better ideas to make it faster? Is there something I'm not doing correctly?
Check out the android developer documentation regarding 3.0 emulator performance. Scroll down to About Emulator Performance.
Copied tip for convenience:
Tip: To improve the startup time for the emulator, enable snapshots for the AVD when you create it with the SDK and AVD Manager (there's a checkbox in the AVD creator to Enable snapshots). Then, start the AVD from the AVD manager and check Launch from snapshot and Save to snapshot. This way, when you close the emulator, a snapshot of the AVD state is saved and used to quickly relaunch the AVD next time. However, when you choose to save a snapshot, the emulator will be slow to close, so you might want to disable Save to snapshot after you've acquired an initial snapshot (after you close the AVD for the first time).
Seems like everything 3.0 and beyond is slow for me. Everything before that runs very fast in emulator for me. However, I have an Intel integrated graphics card in my laptop. When I turn 3D setting to "Application Settings," I get relatively decent performance from the emulator, at least when it starts up, but then when I try to start any app from the default main app menu (contacts, for example) I get launcher errors. That happens for me on 3.0, 3.1 and 3.2. The one thing I'm suspicious of is that I'm running 64-bit Java SDK. Seem to be a number of posts out there related to 64-bit, but mostly they seem to be point to using 64-bit SDK with 32-bit Eclipse or vice versa, but in my tests, I am not even running Eclipse, haven't even reinstalled the ADT yet, just the Android SDK and created a few emulator instances. Again, prior to 3.0 everything is fast. 3.0 and beyond not good, but A LOT better with graphics settings as I mentioned above. If I could get past the launcher issues, I think I might be all set. Oh, btw also, for 3.0 and beyond, I bumped the memory up to 1024. I've tried increasing the heap for apps to double the default (from 48 to 96) but that doesn't seem to have alleviated my launcher problems.
It is slow. You can try creating a new Emulator with a smaller resolution.
I remember someone at google I/O saying that the HoneyComb emulator will run really really slow due to hardware acceleration turned on.
The PC may use software rendering for OpenGL hence the bad performance. The almost everything you see on the HoneyComb screen is rendered using OpenGL ES.
감사합니다,
Reno
The problem I am having is that when I run a FWVGA or WVGA sized emulator it sometimes runs at a MDPI size instead of HDPI. Here is an example with pictures
http://wonton-games.blogspot.com/2010/06/emulator-problems.html
I create the AVD with the proper hw.lcd.density setting and screen size and it randomly does this. There doesn't seem to be a pattern. I used to be able to just delete the AVD and create it over again and it would fix itself for a while but now it's getting worse.
Does anyone have any ideas cause I posted on the Android Developer forum but all I got was other people saying they get the same problem.
I get the same problem and find that it is often only solved by a reboot - of my PC rather than of the emulator. I've not needed to edit or recreate the AVD to solve the problem.
I think it might be related to unplugging my laptop from an external monitor and so changes the Windows display resolution but I haven't been able to regularly recreate the problem.
Since the same AVD image can work one day and not the next and the start working again after a reboot means that this must be a bug in the emulator rather than a problem with the configuration of the AVD.
Unfortunately, I don't know of any workarounds for the problem and as far as I can tell this hasn't been logged as a bug. (I haven't logged it myself since, as you say, it occurs randomly which makes it hard to fill in a decent bug report.)