I'm getting ready to release my first application the marketplace. It's being written for devices running Android 1.5 and above, however there aren't any specific folders for the three different screen densities (I think those came around in 1.6). Should I make these folders myself? Where should I put image resources for the different densities and what should I put in my Manifest?
View 2 Replies
I read the official document about supporting multiple screens http://developer.android.com/guide/practices/screens_support.html
According to that document, I should just create different directories for different resolultion.
Now the question. How to support devices with normal screen and high density or low density?
I ask it because, there are two posibilities (WVGA800 (480x800) and WVGA854 (480x854)) and (WQVGA400 (240x400) and WQVGA432 (240x432)) and I don't know where to store some background images for them.
I would take drawable-normal-hdpi or drawable-normal-ldpi, but how to make difference between 480x800 and 480x854 or between 240x400 and 240x432?!
How to get the screen density programmatically in android?
I mean How to find the screen dpi of the current device?
Can you please tell me how can I specify dimension of layout for different density of screen?
i.e. the layout are the same across different densities, but some dimension are different.
how can I do that?
I'm being confused by the 'screen density' concept in Android. I knwe that dpi (dot per inch) came from the printing device. 160 dpi means 160 dots in every inch on the paper. However, when dpi is used for the screen density, for example, what's mentioned '160 dpi screen' in Android document, what's the meaning? 160 pixels on every inch of the display?
As described in http://code.google.com/intl/zh-CN/android/reference/available-resourc..., 1 dip (density-independent pixel) means 1 pixel on a 160 dpi screen. Why does the ratio of dp-to-pixel not necessarily change with the screen density in direct proportion?
When the dpi is changed from 160 to 80, how many pixels will 1dp will take? 0.5?
I can hardly understand why dip/dp is introduced into Android.
I have an image put on an ImageButton, which looks good on a mdpi (medium-dpi) screen. However, when the device has a hdpi (high-dpi) screen, the image is still pixel-by-pixel accurate, which look small on the device screen.How do I make such that the image (and therefore the ImageButton) scaled based on the density-independent pixels (dp or dip) instead of pixels?
View 3 Replies View RelatedA lot of hay is being made over the iPhone4's 326 ppi screen density. I was just curious, for comparison purposes, what's the pixel density of the Evo screen? This would be an easy calculation to do if I knew what the horizontal and vertical dimensions of the screen were, but I can't seem to find that information anywhere.
If anyone knows the pixel density or even just the exact X and Y dimensions of the screen..
Due to my changing of the screen density i can't get it via play store. can't see a working link on google either.
View 9 Replies View Related<supports-screens android:anyDensity="false" android:largeScreens="false" android:normalScreens="true" android:smallScreens="false" android:resizeable="false"></supports- screens>
first of all what is the resizeable attribute? It does not seem to be documented. This is working almost 90% for my game except when testing in WVGA screen resolution, all my images are scaled incorrectly, it is longer vertically than horizontally. I was expecting the screen compatibility to maintain aspect ratios as that of HVGA.
Also in my layout I have a scrollview and it is designed in such a way that in HVGA when it is not scrolled down, the items are hidden away, however now in WVGA those things are shown. If the aspect ratio of HVGA is maintained I won't have this issue. How can I make sure the aspect ratio is maintained? Also in my layout I am positioning some items using pixel positions. Should I convert these to dpi? How do I calculate what dpi they should be?
I want to make my app compatible to different screen sizes. I am right now developing on the Droid and need to know how can I import the screen image on eclipse emulator? I don't have a droid phone but want to make sure my app layout doesn't change on the Droid.
View 2 Replies View RelatedAs per managing resources(images) in > Android 1.6 version, we need to keep different-resolutions image in Drawable-Hdpi, Drawable-Mdpi, Drawable-Lpi folder particularly.
And as per this page: http://developer.android.com/guide/practices/screens_support.html ,
In Low density section - there are three resolutions used: 240*320 , 240x400 , 240x432 for the Small screen, Normal Screen, Large Screen particularly.
same way for Medium density section - there are three resolutions used: 320x480 , 480x800 , 480x854 for the Small screen, Normal Screen, Large Screen particularly. and same way for High density ........
But i am confused here:
(1) How do i come to know that whether small, Normal or Large screen is used, i mean is there any way to know ?
(2) How do i come to know which type of density i am using ?
(3) And in Drawable-Hdpi, Drawable-Mdpi, Drawable-ldpi folder, which resolution's image we should keep particularly?
I'm confused regarding the densities. I see that with medium density, the screen resolution could be either 320x480, 480x800, or 480x854. So if I have an image thats 300px wide in the mdpi folder, how is it going to look the same size on all 3 different screen sizes (mainly 320x480 vs the other 2)? And by look the same size, I mean scale to be bigger or smaller depending upon the screen size.
View 5 Replies View RelatedIs there any Java ME compatibility layer for Android, which makes porting Java ME (aka. J2ME) applications easier? I mean a third party class library which redirects calls to internal Android API.
View 2 Replies View RelatedI would like to know whether the Android provides any sort of compatibility i.e either forward or backward. It means as in Blackberry if develop an Application with JDE 4.2 then that application will work on any handset with OS 4.2 or higher which means it has forward compatibility. Is there anything similar in Android? Suppose I develop application with Android SDK 1.5 then will that application work on any handset having OS 1.5 or higher.
View 1 Replies View RelatedI developed UI for iphone apps and now want to use the same UI in Android apps. I read that Android use dip for image resolution and i also read that 1 dip=1.5 pixel.I simply multiply the image size by 1.5px. Now the problem is that the image is blur and not as clear as in iphone apps.So will some body suggest me how should i make a design so that it could be used in iphone and android.
View 2 Replies View RelatedI have recently updated my app to a build target of SDK version 8 in order to include the App2SD feature for my users. However I have had reports of devices on SDK 3 (1.5) having problems starting the application, with the following stack trace: If i change the build target back to version 4 as it was previously this issue goes away, also if i remove any graphical resources from my XML files this issue goes away.
View 2 Replies View RelatedI'm currently working on a web service-client for Android. I'm using a Java client library which provides an abstraction for interaction with the service. The client library works on normal machines. However, when I use the classes in my Android project, some calls don't return a result on Android, the background-service stops working at the first of those commands. Wireshark shows a tcp exchange, the server gets the requests. There is no exceptions or anything. Something in the serialization/serialization seams not to work. I'm using the newest version of Jackson libraries (1.5.3) and the restlet jar in the android edition. Is there any known problems with Jackson and Android? Which code and libraries are compatible with Android?
View 2 Replies View RelatedI was unable to find much information regarding compatibility of the Samsung Galaxy with MAC computers. On behalf of the small number of MAC users in this forum, I made a call to Samsung tech support re: how to do the Frodo update with a MAC computer. I was told that the Galaxy phone is PC based and, at present, Samsung does not have a plan to port Kies to OS X. In order to install the Frodo update when it is available, if we don't have an application such as Parallels or Virtual PC, we will have to borrow a PC to do the job.
View 2 Replies View RelatedDoes anybody know if and when Samsung will be releasing drivers for their PC software that are compatible with a 64 bit OS (Vista or Win7)? I currently own a Samsung Tocco which I have been unable to connect to my PC since I bought a new computer in December, and the phone has become a virtual white elephant other than for making calls and sending texts etc. I have looked at the Galaxy S which looks like a great phone. However I did a search on Google and discovered that Samsung's Kies software still has no support for any 64 bit OS, and this is now 12 months since Win7 was first released to developers. As far as I'm concerned this is Samsung's loss and HTC's gain, as I will go for the Desire unless Samsung can get their act together.
View 12 Replies View RelatedSimple really, anyone have any experience with their moment and the Sync system that comes with newer model Fords (and their Lincoln and Mercury brethren)? I have an '08 Fusion (great car BTW, and I'm definitely no domestic car fanboy) and want to make sure I'll be good if I decide to get the Moment.
View 10 Replies View RelatedI wonder if Samsung Moment use the same battery as BH2.I was looking at eBay and found Moment Battery and charger around $10, and thought it would be nice to have an extra battery.Does anybody know if they are compatible?
View 1 Replies View RelatedI'm new to the android scene and the samsung galaxy s is my 1st android based phone.I recently got Mystique chapter one... but my character in the game cant move forward due to the lack of a joypad.Is there a way to remedy this or it is absolutely not compatible wd the Samsung Galaxy S?
View 1 Replies View RelatedDoes anyone know if by chance, with the pending upgrade in the near future for the Moment, if it will correct the voice dial compatibility with a BT headset? Coming from a BB Curve, I miss the above and also the speak option when it comes to the search and driving navigation. I am thinking I may have made a mistake.
View 1 Replies View RelatedThis may sound pretty weird and there may be a lot of reasons y this was never attempted, but would it be remotely possible to flash spicas firmwares on galaxy after adding galaxy specific drivers to it? The reason why I ask this iz that both the phones are of similar(not same) configs.
View 6 Replies View RelatedI'm wondering if it is possible to inflate a layout using a different density value than the default system density. I have a high density layout, which looks good on the Galaxy Tab (1024x600px, hdpi) and I like to use the same layout on another tablet with the same pixel resolution but medium density. The mdpi layout which is used works on the device but the screen just looks really empty and I would prefer to scale things up. So is there a xml argument for scaling the layout, maybe something similar to Bitmap.Options.targetDensity. Or could this be done with a new LayoutInflater class?
View 6 Replies View RelatedIs it possible to force Android to use a given LCD density value? For example, if the app is running on a WVGA phone that reports LCD density of 160DPI *and* screen size of 3.7inch, one of those two values must be wrong. Is it possible to tell Android to ignore the 160DPI value and use 240DPI instead (for my Activity only)?
View 2 Replies View RelatedI have used absolute layout in order to display image buttons in my application's main.xml.
how exactly it affects to using my app on different density screens..
My project contains three drawable's folders: drawable-hdpi, drawable-mdpi and drawable. I build it with android:minSdkVersion="3". When it runs on Andriod 1.6 or higher it always uses images from drawable-mdpi on high density screens.
How to fix this?
I am trying to develop an application for which I want multiple screen support. I have read the Android article on Best practices for Multiple Screen Support. As per the article we have to follow 3 important things
1. Mention support for different screen sizes(large, medium and small) and any density in AndroidManifest.xml.
2. Place images of 3 dpi's (120, 160, 240) in 3 folders res/ldpi, res/mdpi and res/hdpi.
3. In layout's the dimension should be mentioned in "dip" units. Then Android will take care of the scaling on its own.
I have implemented all these points in my project. The images are picked up correctly from the appropriate folders. But the arrangements of the controls in not same.
e.g. I ran the app on three emulators
1. Resolution 240*320 dpi 120.
2. Resolution 240*320 dpi 160.
3. Resolution 240*320 dpi 240.
(All the emulator have same resolution but different density.)
The problem is the position of the controls is not same on all the three emulator. As per my understanding if the android:layout_marginLeft and android:layout_marginTop are mentioned in "dip" then this problem should not occur. As the density of the emulator increases the controls get placed more towards the right. Is it absolutely necessary that I provide layouts for all combination's of screen dimension and density even if the layout is same for all the devices?
Images:
https://docs.google.com/leaf?id=0By3GYC3k5AMDNzUwNjkwMWEtOGQzZC00MjQ0LWE2OTgtYjFhYzZmM2ExOGVl&hl=en&authkey=CLOEsZsI
I was working with Eclipse some minutes ago and I simply launched the emulator with a couple of AVDs that I created (QVGA, HVGA and WVGA screens). I've been doing thta for months, in order to check that every time I change something, the app looks fine for each type of phone.
The problem is that suddenly, the emulator in QVGA and WVGA start with huge icons on the desktop. They even overlap and the home of Android is corrupted. And when I run any application to test the emulator, the screen only shows a portion of the main View. It's like everything was zoomed in. I'm blocked because I can't use anymore the emulator. I'm going to remove completely Eclipse and re-install it, but I don't know if it will be enough.