I have some 9-patch images on my app, and they work great on the medium density. When I load the app on a High density emulator/device, these images look grainy. It happens only to 9-patch images. The others look great after the pre- scaling. Is there a way to make them look good after the scaling, like the non-9-patch images?
View 10 Replies
All these days i used to test my application on my HTC Legend (2.1 OS) only, and i had all my images resources in drawable-hdpi folder.. and everything worked fine
and today i wanted to test my Application on Android 1.5, so i recreated all the images with lower resolution and kept it under drawable-mdpi folder, so now i have High resolution images in drawable-hdpi folder and lower resolution images in drawable-mdpi folder..
Everything looked great on both the HTC Legend and Emulator(with Android 1.5)
Later i found out that the images in drawable-mdpi are shown in my HTC Legend too and not the images in drawable-hdpi in my manifest file i have also included <uses-sdk android:minSdkVersion="3" /> <supports-screens android:anyDensity="true" />
I want to know as to why the images in drawable-hdpi are not used?
I have built android 2.1 on freescale's i.MX platform. But after running Gallery3D, it will crash with the log of failed to load resource. I found that the whole drawable-hdpi/ (it really contains in the Gallery3D source code res/) is not in the apk package, and cause lack of drawable-hdpi/icon_cancel.png. The apk only contains drawable-mdpi/ and drawable/. My question is why the drawable-hdpi/ resource is dropped when building apk? Per my understanding is that, which drawable-* resource loading is determined on runtime, and all the drawable-* should be in the apk package.
View 7 Replies View RelatedI have set up my project with different drawable directories (ldpi, mdpi and hdpi). I have a background png with two different resolutions: 320x480 in drawable-mdpi folder, and 480x800 in drawable-hdpi. Both have the same filename. When I try to load the background as a style in the manifest (using android:windowBackground in the style) if I use the emulator for a 1.6 device, I get the correct one loaded(mdpi). However, if I try this on my Nexus, I see that at first the correct background from the hdpi folder is loaded, but it quickly switches to the mdpi one. I have tried also to set up the background in the layout xml file (android:src=...) but in this case only the mdpi one is loaded. If I delete the mdpi version, everything is loaded ok. Any idea on what is the problem?
View 1 Replies View RelatedI am scaling the canvas of a linear layout on draw, but this throws off all the hit areas of my views inside of this layout. They respond as if there was no scaling taking place. What do I have to do to get themselves to re-register their hit areas?
View 4 Replies View RelatedI made each image a different color so I can tell if it is loading the right image. When I test my program on different density screens it only chooses the mdpi images. It scales them to match the correct dpi but doesn't choose the right folder. It just defaults to mdpi. In the manifest I have, android:normalScreens="true" android:anyDensity="false"
Anyone have a similar problem? I'm sure it is something simple that I am overlooking but I can't figure it out. From what I read on the Android Support Multiple Screens guide is that you should just have to put the different density images in their correct folders and Android will do the rest.
I have some transparent graphics in my game. Up through 2.0.0 they have looked fined. Since Android 2.0.1 though, some parts of the fully transparent regions of the graphics are instead slightly opaque (e.g. a circular gradient that goes to 100% transparency will have a faint halo around it).
I have tried putting my graphics in ../raw/ but that did not help (as described at http://developer.android.com/guide/topics/graphics/2d-graphics.html#d...)
I have also tried exporting the Adobe Illustrator graphics at 16-bit pngs (instead of 8bit), but that did not help either.
I have a texture with 8 equally sized stripes that I am using as a wall with OpenGL. On my Nexus One it scales it properly However, in emulators and on a G1 (and probably on other hardware), it does not scale properly, as the stripes remain the same width, while the height scales as it should. Is there an option that I need to set that is set to default on my nexus one but not on other platforms?
View 3 Replies View RelatedIn a start activity of our android application we're using a linearlayout with an background image for whole space. The image size is 320x480 - the same as device resolution, we're using for testing. The problem is, the image will be scaled und looks not so nice. I tried to use imageview instead, but I've got black borders.
Some ideas, how to avoid scaling or how to get the proper size for background image?!
Most of the time, Android scaling is nice but I have a case where I don't want any scaling and I can't find how to do this.
I made a simple layout to test code...
Say I have a TextView of a particular size (doesn't really matter what... fill_parent, 20dip, whatever). Is it possible to tell the text to shrink/grow in size to fit the available space without doing a lot of math?
View 2 Replies View RelatedWhat is the proper way of sizing the dimensions of an image in a hdpi screen vs a ldpi screen.
For instance, an 89*80 png displays fine, with the text, on my droid 2....but how should I go about resizing the image to be smaller on a smaller screened droid? Do I manually alter the image and place it in the ldpi folder or will it do that automatically?
I can't wait to try out the new 1.6 goodies, but first I'm retargeting my existing applications, and I decided to start with Daisy Garden. Changing to android:targetSdkVersion="4" caused the application to segfault on startup and discovered that the BitmapFactory.decodeResource method now performs scaling based on screen density. In this case the behaviour is unwanted - I'm loading a set of masks that are scaled later during composition. So I've quickly inserted the following method, which seems to perfectly mimic the previous behaviour:
private Bitmap loadBitmap(int resId) { BitmapFactory.Options options = new BitmapFactory.Options(); options.inTargetDensity = 1; options.inDensity = 1; return BitmapFactory.decodeResource(context.getResources(), resId, options);
}
I have a WebView which I'm trying to have scale to a certain percent on loading the page. The iPhone version of this software uses the HTML meta-tag:<meta name="viewport" content="width=320, initial-scale=0.95, maximum-scale=2.0, user-scalable=1">..Since Android's WebView doesn't seem to respect that tag I hard-coded the percent using setInitialScale(). However, the WebView is just flat-out ignoring this method call. No matter what number I put in there it shows at 100%.
View 5 Replies View RelatedI'm loading a URL into a WebView and I'm having difficulty setting the "scale" of the web-page. Specifically, the web-page is too big (800x600) for the screen, so my thought is to use "setInitialScale(50)" to reduce the size. Here is some sample code that doesn't work (i.e. the web-page doesn't scale to 50%)
WebView wv = (WebView)findViewById(R.id.webview);
wv.loadUrl("http://www.example.com/android/symptom");
wv.setInitialScale(50);
I also tried switching the order of the function calls but I get the same resultŠi.e.,
WebView wv = (WebView)findViewById(R.id.webview); wv.setInitialScale(50); wv.loadUrl("http://www.example.com/android/symptom");
As an alternative, I have tried to use the "zoomOut()" function like this:
WebView wv = (WebView)findViewById(R.id.webview);
wv.loadUrl("http://www.example.com/android/symptom"); wv.zoomOut();
This approach works for a split second, and then the image reverts to its original size.
Here is my content view:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/ android"
android:orientation="vertical" android:layout_width="fill_parent"
android:layout_height="fill_parent"> <WebView android:id="@+id/webview"
android:layout_width="fill_parent" android:layout_height="fill_parent" /> </LinearLayout>
Using a VideoView is it possible to set a scale factor for Android? By Default the video view resizes itself to fit the encoded resolution of the Video. Can I force Android to render a video into a smaller or larger rect?
View 3 Replies View RelatedThe problem I am having is that when I run a FWVGA or WVGA sized emulator it sometimes runs at a MDPI size instead of HDPI. Here is an example with pictures. I create the AVD with the proper hw.lcd.density setting and screen size and it randomly does this. There doesn't seem to be a pattern. I used to be able to just delete the AVD and create it over again and it would fix itself for a while but now it's getting worse.
View 1 Replies View RelatedHere's my situation: I have an app that's been compiled using 1.5 SDK and minSdkVersion=3. Now I want to add 2 icons: one for high density screens like Droid and another one for low density screens like G1.
For this, I added the high density icon to new directory drawable-hdpi- v4/. I then compiled using 1.6 sdk and added targetSdkVersion="4" to the manifest. minSdkVersion is still 3.
This is working in limited testing, but I'm not sure if I have done everything correctly.
I have many questions:
1. By specifying v4 in drawable-hdpi-v4, the icon will not be displayed to 1.5 or below OS's. But what about users with 2.0 or higher SDK's? Will they get the non-hdpi icon, since they will have v6 or v7 ?
2. The documentation for targetSdkVersion states, "Specifying this target version allows the platform to disable compatibility settings that are not required for the target version (which may otherwise be turned on in order to maintain forward-compatibility)". Does this mean that my app will not be forward compatible as soon as I specify a targetSdkVersion? What exactly is being turned off?
3. Even if I leave out the targetSdkVersion="4", the app runs ok. So do I really need it?
4. Should I be using the latest SDK (2.1) and setting that as the targetsdkversion and compiling against that? Or some other combination of targetsdkversion and compiling sdk? I'm not using any API's that are not in 1.5..
5. Is any of this related to why some of my HTC Eris users have complained that they can no longer find my app in Market after upgrading to 2.1?
Im trying to do some testing with a QVGA emulator and I find that it looks for an image resource in the mentioned order.
drawable-mdpi 1st
drawable-hdpi 2nd
drawable-ldpi 3rd (it does get found only after i change the name of the image in the other two dirs for testing)
I would expect it to be ldpi first.
When running other emulators (HVGA and WVGA) they use their appropriate drawable dirs... its only QVGA. The only code that I see could affect this is here (based on the docs)
I have tested this with a 2.0 emulator and a 1.6, i get the same result.
I need to scale down images coming from a Network stream without losing quality. I am aware of this solution Android: Strange out of memory issue but it is too coarse - inSampleSize is an integer and does not allow finer control over the resulting dimensions. That is, I need to scale images to specific h/w dimensions (and keeping aspect ratio). I dont mind having a DIY bicubic/lancoz algorithm in my code but I cant find any examples that would work on Android as they all rely on Java2D (JavaSE). EDIT: Ive attached a quick source. The original is 720x402 HD screen capture. Please ignore the top 2 thumbnails. The top large image is resized automatically by android (as part of layout) to about 130x72. It is nice and crisp. The bottom image is resized with API and has severe artifacting. Code...
View 1 Replies View RelatedWe're looking for a method to properly scale our textures and world. The current method we're using is having an arbitrary world unit which calculates the screen resolution and receives the size of a pixel on all resolutions. However is there an easier way of implementing a scaling method for game development? We have looked through dip and other android native elements but these don't work as well for a larger scale on game development.
View 3 Replies View RelatedI developed a game with the g1 in my mind. Now I want to support large screen sizes but I don't want to add in the apk different images for different screen sizes because now the apk is 3mb and when installed thought market it became 6mb (due to protection on). If I have to double the images to support new screens, the apk would be too heavy (about 13mb, I think) so I'm wondering to know if scaling images at runtime by myself (without compatibility mode) maybe the best way for supporting larger screens. Compatibility mode does a great work in scaling images but it slows down drastically the frame rate (I think because the scale operation is made every time an image is used/moved and not only once on the load of the image itself).
View 7 Replies View RelatedI am using android.hardware.Camera to get a preview and display it on a custom SurfaceView that implements SurfaceHolder.Callback.
I am trying to zoom in to the camera preview surface by a specified scale (not using the camera's digital zoom) but I can't seem to find a correct way to do it. I also need to be able to zoom out and scale down the preview.
I was hoping to be able to do this using a ScaleAnimation but it doesn't seem to work on SurfaceView, nor the FrameLayout containing the SurfaceView.
I also tried setting the size of the SurfaceView using setLayoutParams but that doesn't seem to work too well on various hardware and it would be tough to animate smoothly.
How to achieve this effect? Right now I am starting to think I might have to implement this using GLSurfaceView but I'm very unsure.
Any app which can mass resize .png from HDPI resolution to MDPI!
I had seen a similar app for MAC but any such application for windows!
I have a button which I want to occupy 75% of the screen:
On a 480x800 resolution screen this would be 360 pixels wide.
On a 280x320 resolution screen this would be 210 pixels wide.
How do I go about specifying this in my layout XML file?
I understand there is a DIP unit of measurement, but does that also work to scale screen images for resolutions? What DIP measurement would I use for this, and do the images need to be saved at 160dpi.
How does Android handle scaling of a video being played within a VideoView?
So for example if I have a video that is say 480 X 270 (width and height), aspect ratio 16:9. And, say the VideoView is added to a LinearLayout with LayoutParams of (480, 270). What will be width and height of the rendered video in portrait orientation in a device that is 320 X 480? In landscape? In another device that is 320 X 550?
I'm designing an HTML page for display in Android browsers. Consider this simple example page:
<html>
<head><title>Simple!</title>
</head>
<body>
<p><img src="http://sstatic.net/so/img/logo.png"></p>
</body>
</html>
It looks just fine on the standard HVGA phones (320x480), but on HDPI WVGA sizes (480x800 or 480x854) the built-in browser automatically scales the image up; it looks ugly.
I've read that I should be able to use this tag to force the browser to stop scaling my page:
<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0; minimum-scale=1.0; user-scalable=0;" />
... but all that does is disable user scaling (the zoom buttons disappear); it doesn't actually prevent the browser from scaling my image. Adjusting the scale factors (setting them all to 2.0 or 0.5) has no effect at all.
How can I force the WVGA browser to stop scaling my images?
I am making a ROM. And I'm trying to change the stock icons. I've tried every posssible way but i just can't change them. I'm trying to theme Holo Launcher with custom icons. The icons I have are hdpi. So i don't know how to turn them to mdpi. Is there any way i can turn it to mdpi on my PC. And what are the icons supposed to be renamed as well as which directory am i supposed to place them.
View 1 Replies View Relatedis there anyway to trick cm9/aokp theme chooser to think that my device is hdpi, instead of mdpi, without lcd density changer hack most HDPI themes, if not all(with the exception to lucid) work on mdpi devices yet theme chooser doesn't allow me and will give me a compiler error.
if the above does not work. is there anything i could change in the theme apk, whether its an xml, or image or anything I could change to make theme chooser think that i am using an MDPI theme, even if the theme includes hdpi images? THE "APPLY HDPI THEMES TO MDPI PAGE, LCD DENSITY CHOOSER PAGE.
how to port xhdpi roms to hdpi devices? what other steps do we have to take ? im trying to port paranoid android 3.69 to xperia u basing cm 10.1
View 1 Replies View Related