I 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..
View 2 Replies
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
We can set the pixel values in custom views by multiplying them with
this.getResources().getDisplayMetrics().density;
This is ok when the screen aspect ratio is normal means not long
But how can we set the pixels along Y-axis when the aspect ration is long.
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?!
I'd like to have some fancy effects on my Activities when entering or exiting. So I tried to use theming. But it seems that it's completely ignored?
themes.xml (activated in Manifest) <itemname="android:windowAnimationStyle">
@style/Animation.Activity</ item> styles.xml
<style name="Animation" parent="android:Animation"/>
<style name="Animation.Activity" parent="android:Animation.Activity">
<item name="android:activityOpenEnterAnimation">@anim/fade_in</ item>
<item name="android:activityOpenExitAnimation">@anim/fade_in</ item>
<item name="android:activityCloseEnterAnimation">@anim/fade_in</ item>
<item name="android:activityCloseExitAnimation">@anim/fade_in</ item>
</style> fade_in.xml <alpha xmlns:
android="http://schemas.android.com/apk/res/android"
android:fromAlpha="0.0" android:toAlpha="1.0"
android:duration="1000" />
Can someone please explain Adobe AIR and how it affects android.. All i see is that it is like a flash or something, but not popular.
View 7 Replies View Relatedi have list views with image views and text views etc in them, and i'm trying to fix up a situation where the background image of a list element changes in the "pressed" state. if there's a straightforward way of doing that, please let me know! right now, i override onTouchEvent() in the topmost view, and also in those child views who don't just delegate to their parents which would be image views. i have to check for long clicks myself, but basically this scheme works. the list views are potentially different sizes depending on how much text is in the views etc, so i thought i would use a 9-patch as the background. however, when the background changes from flat white to the 9-patch, this seems to indent the view a bit - ie give it margins. eh? if i change the image to a non-9-patch, the margins remain as they are. i've tried different sizes of 9-patch, from 320x150 or so down to 100x30 etc, no change. what's going on?
View 3 Replies View RelatedI realize how much faster the hero can be when its wimpy processor is overclocked. I would imagine that ocerclocking would be bad for it though, to push the CPU faster than its made to be, but most people don't mind it. I'm wondering, realistically, if it is hard on the CPU to be overclocked and also how it affects battery life. Keep in mind, I'm talking about overclocking the ROMs made to be like zen, aloysius, purehero, busted, etc.
View 4 Replies View RelatedDoes moving apps to system/app folder affects battery life? I've moved Dolphin & removed the default browser. It opens a bit faster now. But I'm just curious about whether it takes up battery in the same manner to give performance.
ST25i
I had a little time with the captivate today and noticed it has 4(i think) horizontal scrolling screens for apps. What happens when you fill those? Does it automatically add another one or what?
View 2 Replies View RelatedThe following what written on the Android 1.6 Platform Highlights: Android 1.6 includes the updated OpenCore 2 media engine, which has: * Support for OpenMAX encoders * Support for additional audio codecs in AuthorEngine * Improved buffering model supports shared buffers allocated in the decoder Could someone explain to me how this affects us the developers? Does this mean now we can play other media types? What in reality is new to us on Android 1.6 in regards to OpenCore?
View 2 Replies View RelatedIs copying the reference to the object and not the value of the object. Meaning, when I modify pos.top or pos.bottom, the original object gets modified. I'm guessing I am missing a concept of pass object by reference vs value here which I thought I understood. What is the fix here? Is it a problem with how I defined my custom class?
View 2 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 RelatedHow 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 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 View RelatedI'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.
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 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.
in xml file we can define measuring units along with the values. If I want to set some property through code it only takes "int" value. What is the default unit for this int? px(pixels) or dp(density independent pixels) ?
View 7 Replies View RelatedI have created the launcher icon(48x48 px) for 320x480 screen resolution and it's working fine. but while using same icon in WVGA854(480x854 px) it's displaying small compare to other default launcher icon. i want to know, what is the size of High Density WVGA854 launcher icon?
View 1 Replies View RelatedLCD Density Changer for Android, LCD Density Changer Application v3.0 Released | xda-developers Dev Thread [APP] LCD Density Changer 3.0 - create HighRes screen effect - xda-developers I set my EVO to 200. made things way way better! Some text on the MENU in LauncherPro are cut off, but nothing i cant deal with.
View 49 Replies View RelatedI'm running cm6 and the Galaxy S Theme. I would like to run my density at 160 because I really love how tiny the icons look on my screen. However, when I run the density to that setting my notification menu bar no longer stretches across the top of the screen, it appears as a small square in the left hand corner. I also have the same problem in the market place, where the grey background should stretch across behind where it says "market". My friend runs his at 160 and has no problems like this, however he is not running cm6 or the theme I am. So, while it doesn't really narrow it down any, I'm sure the problem is in one of the two, more likely the theme in my mind. Any idea's how I can fix or repair this problem?
View 9 Replies View RelatedI 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 RelatedHas everyone seen that you can change the LCD density on the Desire? (Well, on all Android handsets really). It simulates a higher resolution, fits more text on screen etc. There's an app on the market which does it, although it won't work on the Desire unless you're S-OFF. All you need to do is extract the build.prop file from /system to your PC (in recovery, use ADB PULL), and using a text editor change the value of LCD Density from original 240 to 200, then ADB push it back and reboot. I'm *really* pleased with the result. Combined with Launcher Pro I've a whole new feel to my phone...
View 8 Replies View RelatedI have a problem with my sgy s5360 (rooted). i recently changed my lcd density in error and instead of the 120 default setting, I changed it to 288. that was really frustrating. I haven't been able to fix it myself. I have already done the factory reset but that didn't work. I used the ROM toolbox. Now my sgy is like in a zoomed state. Large fonts, cannot unlock and change to default setting. I cannot click the android icon that can be seen when you reboot your phone and did the factory reset. assistance is badly needed. i have browsed through the theads, but this issue has not been addressed.
View 1 Replies View RelatedI have problem with displaying bitmap image on imageview on high density screen (480x800). When the bitmap image loaded from file on sdcard, the image does not scale to fit hdpi screen. On medium density screen it works normal (320x480).code...
View 1 Replies View RelatedRunning Incredible with Froyo. I rooted using Unrevoked3, but I forgot to make the nandroid backup, I guess. the LCD Changer app has my reboot looping. After the very first HTC Incredible screen it goes totally white and I just hear the "Droid" voice(plays when the red droid eye comes up on screen normally" nothing but white and the voice just repeats after the screen flashes every minute or so. Tried applying the update.zip that was linked to on the developers blog, but no luck. Any ideas? I even tried resetting to factory defaults, formatted everything, basically. Lost a great of data, I'm afraid, but I just want my phone back.
View 14 Replies View RelatedPeople seem to be having problems using the LCD Density changer app, so I am making this write up to help you out If you would like to make your Droid X look like this.
View 35 Replies View Related