I am new to android. For getting more number of downloads. I will make application in Android 1.5 version. How can I support multiple screen resolution from android 1.5 version. Is there any problem develop application in Android 1.5 and release in market. Is it visible to higher version mobile market for downloading apk file.
View 5 Replies
In my android application, I would like to support multiple screens. So I have my layout xml files in res/layout (the layout are the same across different screen resolution). And I place my high-resolution asserts in res/drawable-hdpi
In my layout xml, I have
CODE:...........
And I have put bkg.png in res/drawable-hdpi
And I have started my emulator with WVGA-800 as avd. But my application crashes:
CODE:................
I have a program that should work on Android 1.5, but when it's run on newer devices with higher resolution screens, it should support the full resolution and not emulate a lower resolution screen. As far as I can tell from the documentation, this should be simple.
I just specify
code:.........
The problem is that if I tell Eclipse to compile for 1.5, it refuses to accept this. It reports an error (targetSdkVersion is an unknown tag) and refuses to compile or run. If I tell it to compile for 1.6 it works fine, of course. But if I then try to install on a 1.5 AVD, the program immediately crashes with a java.lang.VerifyError. I'm clearly missing something simple. How do I get it to compile an apk that works under 1.5, but still includes the targetSdkVersion tag?
I want to develop UI of the application which looks similar on all screen sizes. I have gone through the Android developer article regarding this. I am using supports-screen tag but then also the screen is displayed not displayed properly in the larger screens. The screen is displayed properly in HVGA and not in WVGA.
I have developed the application using Android 1.6 and set the minimum SDK version as 4. The application is running properly on HVGA avd but not on WVGA avd. Can I know the reason for it? Is there any solution for this? I want that the user interface of the application should look uniform in all the handsets.
I am having an issue understanding how to get Bitmaps from resources in density specific directories to scale properly when drawing them to a Surface View.If I have a resource in folder "drawable" I expect it to be scaled up when run on hdpi screens and scaled down on ldpi screens and left as is on mdpi or 1.5 screens.Likewise I expect anything found in hdpi when run on an hdpi screen to remain unscaled. However, there is some combination of settings that I am not getting right to do this seemingly simple thing.I am not running compatibility mode so my manifest supports all screen sizes with anydensity=true.I do not understand the BitmapFactory.Options fields of inScaled, inTargetDensity, and inDensity that I am thinking have to be set appropriately and slightly different for each resource decoded depending on which directory they were found in and what screen they are currently run on.
All I have been able to find is that if either inTargetDensity and inDensity are 0, no scaling occurs, but if not, scaling occurs such that inDensity matches inTargetDensity. Is this correct?I have no idea what valid settings are for these fields from the documentation other than ints.What are the integer values for LDPI, MDPI, and HDPI? And how do I determine the density of a resource in order to set this before I decode it? Am I way off base in my approach for drawing bitmaps from various resource directories on various screen sizes?
If I run my android application with htc magic with locale English. I find my application running properly and if I find to run it on Motorola droid with locale Korean, I find even my application(apk) cannot be installed on the device. Do android support different language? Is it because of different language OS version?
View 3 Replies View RelatedI am looking for a weather app that supports multiple cities like an iphone weather app. I have tried many apps, but could not find the one that I want.
View 9 Replies View RelatedSo I'm trying to make sure my apps are compatible with the 1.6 SDK emulator skins WVGA800 and WVGA854. The Android Developers Blog post regarding this seems strange to me. The post talks about upgrading your app using the 1.6 SDK, then says this:
"Note that not all devices will be upgraded to Android 1.6 at the same time. There will be significant number of users still with Android 1.5 devices. To use the same apk to target Android 1.5 devices and Android 1.6 devices, build your apps using Android 1.5 SDK and test your apps on both Android 1.5 and 1.6 system images to make sure they continue to work well on both types of devices."
Now resource directory qualifiers (e.g. "res/drawable-mdpi/" or "res/ layout-large") don't work with the 1.5 SDK. So right now as a dev I have the choice to either:
1) Update my apps with the 1.6 SDK so that they are compatible with the various 1.6 emulator skins and the various hardware configurations coming out. If I do this, the updates will not be available to those users that still have 1.5, which is a "significant number of users."
2) Continue using the 1.5 SDK, without the available tools in 1.6, but try to somehow get my app to render properly in the various 1.6 emulator skins.
Some of my application's users are on android 1.5, some on 1.6, and some 2.0. So how do I release my app for all customers? If I release a 1.5 version, then the 1.5 phone can use it - but not the newer phones with smaller screens (aka Tatoo), they require 1.6 or higher? correct?
View 4 Replies View RelatedI have a project compiled with and targeting 1.5. I now want to support different screen sizes instead of letting android handle the scaling.That's all I need to do, right? All my layouts are using dip, so it should scale, and I don't want to mess with different size bitmaps just yet.
View 1 Replies View RelatedI am trying to develop an app 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 necessary that I provide layouts for all combinations of dimensions and density i.e. in layout-small, layout-large, layout- medium, layout-long,layout-notlong?
Is it just me or are 99% of applications are very low resolution and all the pictures look very dull and fuzzy.
The new facebook update looks crisper, so the phone cleary has the capabilities but why aren't developers making apps to the highest resolution?
Here is the problem, I am building an application and have multiple images that need to switch when the user touches the screen, doesn't matter where the users touches. The press the screen and the images switch randomly. I purchased the ebook "Professional Android Application Development" and have torn though it. I am stumped. I'm thoroughly confused at this point. Any ideas on where I can go or how I can accomplish this?
View 11 Replies View RelatedI 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 have an existing android app in version 1.5 . I have to make it to support Multi Screen.
View 1 Replies View RelatedMy application will have two layouts, one for large screens and one for normal. For testing I'm working with one phone (800x480 240dpi) and one tablet (1024x600 240dpi) but both are detected as large screen hdpi and long aspect ratio, so I'm not able to assign different layouts.
The only approach I think that can work is to create layout-large and layout-normal, get the resolution and programmatically set the layout folder. Is that possible?
I've read the article "Supporting Multiple Screen" on Android developers site. But that doesn't apply to game logic.Let me get straight to the point. My situation is as follows:
- I'm creating a game using LunarLander code as a base.
- In my game, there'll be an object flying up from the bottom of the screen. The object will fly in projectile motion.
- I set the starting velocity, gravity and angle so that the highest point(of projectile motion) is almost at the top of the screen.
- The screen tested is Motorola Milestone. (480x854 resolution) Meaning the object travels around 854 pixels vertically.
I'm thinking of adjusting starting velocity based on screensizes. But that sounds unreliable when we've so many devices/resolutions out there. How do you combat these kind of problem when making games?
I have a number of apps, and so far I have supported all versions from level 3, android 1.5.
For my latest app, I'm considering supporting only from 1.6, or possibly 2.1, upwards.
What's the trend thesedays? Is it becoming usual, or acceptable, to adopt this strategy?
I developed application in android 1.5 and i make it for support screens in large and medium and small through coding if i release android 1.5 on market it will appear in all android version phone market (android 1.5 +) .am i get application in droid,small device market and it is work fine or not.
View 1 Replies View RelatedAs we know, bluetooth-related APIs was not included until version 2.0. And the current condition is Droid is the only 2.0-supported choice. I've known there are many kinds of unofficial 2.0 build, but are they stable enought to program? Does anybody has the experiences of programming bluetooth on a non-Droid handset? What is it, and what is the version of your OS? Did you hear of whether G1/magic/hero/tattoo is going to support eclair officially or not?
View 6 Replies View RelatedI wanted to know if Android 2.2 (Froyo) supports Bluetooth V3 .
View 1 Replies View RelatedIs any SDK version which support Windows 2000? r05 doesn't - I found that android-sdk-windows oolsemulator.exe imports from WS2_32.dll functions freeaddrinfo, getaddrinfo and getnameinfo which missed from this library.
View 1 Replies View RelatedI want to know when will Android support Multiple PDP.
View 15 Replies View RelatedAccroding to GregS's "Announcing OpenCORE 2.0 release" mention, video telephony (a.k.a. 2way) engine is supported by OpenCORE 2.0. but he(?) was not sure that is included at Cupcake version.
So, can I get information about any progress for supporting video telephony service? like, whether video telehpony service is supported at Cupcake or any other version.
And where can I get any document about OpenCORE 2.XXX release?
Every time I try to add a contact icon (from a saved image on my phone), my Magic saves a low-resolution version of the crop I make.
When I dial the contact, the picture looks HORRIBLE (it seems like the resolution is about 50x50px or something). I tried making contact icons from photos made with the phone or from high-res images that I transferred from my PC, but the outcome is always the same: the resolution of the icon is too small.
Is there a way to solve this problem? There's no point having a low-res image in a high-resolution image placeholder.
If an android device wants to support multiple cameras, then how does the API support this? Right now the framework API is a simple static method to create an instance of camera Camera.open(). I see couple of options:
1. Using camera.setParameters() to set a name/value pair that instructs which camera to choose?
2. It would be nice and cleaner perhaps if this was done right on the open() method perhaps with additional enum.
Obviously option # 1 would not result in any addition to the API. Does this use sound right to you to support multiple cameras?
I've just switched to launcherpro from sense, and the one thing I miss is the news widget. On sense in had three full page widgets devoted to it, and I need a replacement! Requirements are:
Full page widget
Multiple homescreen support
Simple aesthetics
Customisable news feeds
I'm an application developer, trying to develop a graphics application. I have been trying to get multiple windows each rendering their view up for quite sometime with no headway. I have gone through the documentation but have not come across any technique to enable multiple window support. Does Android have multiple window support as of now?
View 4 Replies View RelatedI'd like to have two GMail (Google Apps mail, if that makes a difference) accounts active at once, both getting new mail notifications, and having the ability to send and reply through both accounts. My current solution is to simply forward all of Account #2's mail to Account #1 -- but then I can't send. Am I missing an option here? Surely this must be possible on Google's OS.
View 3 Replies View RelatedI want to know if it is possible to support multiple profiles within Android? To explain my question better, can we have two or more applications, which uses a Data Call, operating simultaneously in Android? For e.g. is it possible to have one IM, one e-mail application and one SNS(like Facebook) operating simultaneously in Android phones? If yes, I want to know how this is being handled within the Android Stack code. Since the platform code is open source, any suitable reference to any portion of the code handling this behavior would be perfect.
View 1 Replies View Related