I don't have a tablet but I wanted to take screenshots from the emulator for display in Google Play. I did that using Eclipse (using the method given in the top answer here How to take emulator screenshots using Eclipse?) but the screenshots are not good quality: the image is broken (some areas are kind of shifted) in at least one spot each time I take a screenshot.
Is there any better way to do it?
According to this answer that is an emulator issue. To solve this, you need to enable the 'use host GPU' setting when creating an emulator, according to another answer.
I would use the DDMS shipped with ADT (also listed as Debug monitor) and choose the device and app, then click that camera icon. It creates very good looking screenshots.
I also got some rendering errors with the emulator... It's best with actual devices. You can also try if other images/emulators perform better.
Related
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 am developing an application for android 4.0. that app in emulator is looking in good size but when we check that application in real device, all images in apps are being very small in size. what should i do? please help me.
If I am following you correctly you are under the illusion that the emulator will mimic a device exactly? And that because your design looks good on the emulator it will translate exactly over to the device?
If that assumption is correct then you need to be aware that the emulator is never going to give you that kind of accuracy. From my own experience the emulator will help as a guide but it cannot and should not really be used as a like for like match against a set or specific device. This all comes down to the fact that different phone manufacturers use different chipsets and render their screens differently to each other. The best thing you can do is to effectively follow the guidelines here http://developer.android.com/guide/practices/screens_support.html to provide a layout that closely resembles what you want.
I have built android ICS(4.0.3) for virtualBox. And it runs well with default resolution 800x600.
However, when I change the virtualbox resolution to non-default ones, say 1280x800.
Then I get error "Unfornately, System UI has stopped". And the system hangs there. In addition, I cannot even connect to this device to see the logs when resolution changes.
Would you please give me some help? Thanks.
BTW,
The way I change resolution is suggested by Buildroid ----
First add a “custom video mode” to .vbox configuration file : Add the line
< ExtraDataItem name=”CustomVideoMode1″ value=”1280x800x16″/>
just after the already present “ExtraDataItem” entries.
Modify the linux kernel options to replace the existing vga=xxx by a vga=ask
Then, choose the expected resolution.
Maybe you find solution in this wiki article: Android Emulation.
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.
I need to make a screencast of an app to present to a client, but need it to look better than the ugly red phone or the various other incarnations of the emulator. Is there a way to swap out that image?
Also would be great to get rid of the keyboard that displays next to it and make the window borders go way (since I have to capture it full screen on a mac, unfortunately, I can't crop it tight).
When you create an AVD, you can specify a different skin to use. Besides the ones available by default, there are also a bunch on the web for various devices. You can search for "[phone name] emulator skin" to find a variety, but here are a couple of examples:
Nexus One
Nexus S
The Motorola MOTODEV site (http://developer.motorola.com/docstools/tools/) has addons for nearly every one of our released phones. Registration is required. Most of the addons are full system images, which should work or you could extract out the skin for your own uses. There is a "skin only" addon for the upcoming XOOM tablet that uses Gingerbread for the runtime.
Good luck