Before I ask the question let me state that I have attempted to google for this using several key words but haven't had much luck.
I am after a list of "Device Layout Configs" for the eclipse graphical layout editor. A list of popular phones, such as the Samsung Galaxy range and HTC's various desire phones is the sort of thing that I am after.
If anyone is able to point me in the right direction I would be very grateful.
Thanks,
James
shameless self plug
Looks like I need to improve my SEO a bit!
Here's a list of 'device layout configs' (Emulator Settings) for each density bucket:
http://blog.blundellapps.com/emulator-settings-for-each-android-density/
It's a start. Further reading is my list of popular devices by density bucket:
http://blog.blundellapps.com/list-of-android-devices-with-pixel-density-buckets/
Related
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.
Developed a application of size 40MB. I need to test it for all screen support but the android emulator really a bad choice(I feel... ). It gives Insufficient memory error almost every time). How developer test their application?
One more Question
I have designed app for four different layout(normal,small,large and xlarge). Will every device(In future) satisfy these layout params?
And i faced a real problem that i tested my app in Sony xperia minpro(Small screen 240*320 2.4inch) and in Samsung galaxy 5(smallscreen 240*320, 2.8inch) but the layout is overlapping in samsung device. This can be a serious problem , actually we cant check our app in every device.. that is impossible too.
TIA
40MB is way too big for an Android application. Many users will have problems installing the app on their devices. You should consider moving some resources out of the application and downloading them either on demand or on first app run.
The list of layout types (normal, small, large, xlarge) is definitely not final, for there quite possibly will be even larger screens (xxlarge) or tiny ones (xsmall?).
Developed a application of size 40MB. I need to test it for all screen
support but the android emulator really a bad choice(I feel... ). It
gives Insufficient memory error almost every time). How developer test
their application?
You can configure the emulator with any amount of memory you wish, including an emulated SD card so memory shouldn't be a problem. However, 40MB is quite big so you may be hitting the package size limit.
One more Question I have designed app for four different
layout(normal,small,large and xlarge). Will every device(In future)
satisfy these layout params?
You're asking us to predict the future - there's no way we can know what Google are planning if they haven't already announced it though I would suggest that there will never be a commitment to keep screen sizes or resolutions static - technology constantly evolves and specs that are OK for today, will not be OK for tomorrow.
I have seen dictionaries weighing in at 40Mb, best practise is to download the database as a separate file. Some graphically intensive games approach that size. If you want to emulate many Android devices make sure your PC is up to snuff and you have the latest SDK.
How developer test their application?
You do not have so many choices: you have to use as many (and different) physical devices as you can, from different vendors and technical specifications (screen, etc), to try to detect as many specific bugs as possible.
This is difficult, as you are often limiten to a few physical devices.
To give you examples, I recently struggled with the Camera, for a bug happening with Motorola Defy only. I am currently struggling with the Camera, but only for Samsung Galaxy this time.
When you find a specific bug, try to fix it "the general way": instead of detecting the vendor/version of the device to write specific code for it, try to enhance your code in a way it will work for all tested phones. So far, I never had to write anything specific to a given device. The bugs I encountered were always tied to a permissivities or particular cases that could be handled by making the common code more complete or resiliant. Let's say by "making as less assumptions as possible" knowing that we tend to make assumptions without meaning it.
On top of testing on as many physical devices as possible, create emulators. You can parameter them to have different screen layouts, different embedded hardware, memory, etc. And on top of the default emulator that comes with the Android distribution, you also have emulators provided by the devices vendors and that reproduce the specificity of these devices. For example, Samsung released a Galaxy Tab emulator. Sony Ericsson released a EDK Cellphone emulator. You can get them thru the regular android distribution update workflow.
Will every device(In future) satisfy these layout params (normal,small,large and xlarge)?
Yes, as Android distributions are backward compatible. Any of these layout will still be supported in the future, but may become 'deprecated' (so not recommended, but still working), and new layout types will certainly be created.
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
On the Motorola Bravo, at the left bottom of a MapView, there is an ugly orange square rather than the google logo. I notice this not only on my app, but on say, Yelp -- see screen shot:
Has anyone else seen this, and is there a workaround? I don't know if it happens on other motorola phones, but I'm guessing it does because there is another, similar problem with a missing image on google maps, which is easy enough to solve and documented elsewhere as being on Droid phones as well.
Here is what i found out, hope it helps at least a bit.
I have a Motorola Milestone (it is the EU version of the Droid as you probably know) with vodafone branded rom (so no ported custom rom) and do not have this 'bug' at all.
Here are some screens of Google Maps and Yelp...
so I do not have this problem at all but that does not mean other Milestone users do not have it. Maybe it is because of a missing image in one of the operators firmware files - when they customize their roms, they may delete some google-specific images and then forget to replace them with their own images (or put an ugly orange png at this place).
So I'm afraid I can't help any further, but at least i could show that this is not necessarily a motorola problem but maybe a provider problem?!
you could have written that you already posted this to motorola developers forum so i would have saved the time to look at this resource ;) click
edit: i found a post at modaco forum where a user describes the orange square as a bug in a custom rom --> the post. this is on acer liquid.
I'm looking to create AVDs to test my apps on, and i'm trying to figure out the correct settings for a square screen such as the new Motorola Flip Out. I don't see a wikipedia article for it, or many specs...
On a related note, what about tablets? Actually.. Why aren't there a set of AVD instances with params from popular devices.. or at least a site that lists them for each of the 60+ devices.
Thanks in advance :)
The Motorola Flipout has a 320x240 screen.
For the specs of many other phones there are quite a few sites where you could find all the details. For example phonearena.com is one of them.
At the risk of getting another dubious badge for resurrecting old threads, I'll give the semi-official Motorola response... :)
Nearly every Motorola handset is accompanied by an SDK addon that includes a system image and a skin. In a few cases, the addon contains only the skin. Just download the archive and make sure the top-level directory of the archive is in into /addons. After that, you should be able to create new AVDs based on the addon. I find that it's a lot easier to use the GUI AVD Manager than a command line, but both are usable.
Download the addons at http://developer.motorola.com/docstools/tools/
Good luck.