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.)
Related
Don't remember changing anything at all, and suddenly when I opened Android Studio today (running it through the AVD Manager), it did this. How do I fix it? As you can see, workspace is much much smaller than emu.
Edit: Just in case it is somehow related, the emulator always gives me a "adb not found" error. Never seemed to mess with anything I did, so ignored it.
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.
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.
Sometimes I notice the Android emulator starts with a very small font size. This seems to happen randomly. Other times it has a normal font size.
I use ADT 10.0.1.
Do you know what is the problem?
This happens very often, and although I'm not sure about the exact reason behind this, it seems that somehow the wrong density was detected for this and resources for a lower dpi is loaded inside a higher dpi emulator. That's why everything is smaller, but the layout works properly and aligns things at their own places. And you're right: when this happens, network doesn't work in emulator! These two things seem unrelated, but my guess is that emulator fails at loading config for the current virtual machine successfully, and that includes density and network capabilities.
Anyways, there doesn't seem to be any official info on this, and similar reports in android-developers mailing list didn't get any response for developers of Android, although this is a very popular bug.
And the solution right now is only restarting the emulator. Sometimes you have to do this more than once, but finally it works.
Make sure your computer's display resolution can satisfy your emulator's exact resolution. If you are using Mac with Retina Display, this problem may occur. Try changing display resolution via Display settings.