I am developing an application that contains stock wallpapers of almost all Android smartphones brands.
The problem is that i can't deal with the resolution of images. Let's take an example: i have an image with dimensions 1920x1280
I know that the best image resolution for an Android home screen wallpaper is 2x of screen width (for example width of s2 is 480x2=960px) and exactly same height (for example s2 height is 800px) so the right wallpaper size for galaxy s2 (with screen resolution 480x800px) will be 960x800px. But on the market there are plenty of smartphones as well as different screen resolutions.
I am asking if is there any "universal" resolution (i know that this does not exist but at least approximately) for the wallpaper so that to fit on most of screen resolutions ? If there is not this means that i have to crop every wallpaper and resize to the right resolution for most of smart phones screen ?
Any suggest will help me, please give me something like referent, any other app, or any Java code so i can put into my app.
Thanks
Related
I just got a really good couple of packs of wallpapers i really like, all 480 x 800 (thinking that the screen resolution so that be fine)
I can display them on my phone perfect, but i cant set them nicely as a wallpaper !
always asks me to crop it when i dont want to!
anyone now a work around?
Scroll across different screens and you'll see it pans across the wallpaper, which means the wallpapers are wider than 480px. So if you give it a 480x800 image, it's going to have to crop it to get the aspect ratio right. I'm not sure what width it needs to be though.
Desire's wallpaper resolution is 960x800, i've been making my own recently but this site has a good selection ...
http://nexusone960x800wallpaper.blogspot.com/
If i email myself a jpeg of that size will it let me set it as a wallpaper without having to crop it?
Desire's wallpaper resolution is 960x800, i've been making my own recently but this site has a good selection ...
http://nexusone960x800wallpaper.blogspot.com/
Click to expand...
Click to collapse
that's quite a fantastic page there, thanks for sharing
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
I recently got an Epic 4G Touch. I created some custom wallpapers and sized them to 480x800 to match the screen's resolution. The wallpaper has a single object (the HAL 9000 eye) which is a circle.
When I use the wallpaper as the lock screen, the eye is distorted slightly so that it's no longer a circle.
The gallery displays the image properly and the selection screen for the lock screen also displays it correctly.
I think I can compensate for this by resizing the image slightly, but I don't know how many pixels to remove from the image. I think the status bar might be a good starting point, but I don't know how many vertical pixels it uses.
Thoughts?
Lobo Droid said:
I recently got an Epic 4G Touch. I created some custom wallpapers and sized them to 480x800 to match the screen's resolution. The wallpaper has a single object (the HAL 9000 eye) which is a circle.
When I use the wallpaper as the lock screen, the eye is distorted slightly so that it's no longer a circle.
The gallery displays the image properly and the selection screen for the lock screen also displays it correctly.
I think I can compensate for this by resizing the image slightly, but I don't know how many pixels to remove from the image. I think the status bar might be a good starting point, but I don't know how many vertical pixels it uses.
Thoughts?
Click to expand...
Click to collapse
Because of wallpaper scrolling, you need 800x960 wallpaper. In other words, double the horizontal dimension to allow for scrolling...
My wallpaper doesn't scroll anymore, I'm not sure why.
nabbed said:
Because of wallpaper scrolling, you need 800x960 wallpaper. In other words, double the horizontal dimension to allow for scrolling...
Click to expand...
Click to collapse
I tried creating an 800x960 wallpaper using the same eye image and it didn't work. I used GIMP to create a black background image and then inserted the eye image as a new layer. The 480x800 images I created were done with the same method.
The 800x960 wallpaper is still distorted. So the problem is that the aspect ratio of the lock screen is not quite 480x800 or any multiple of those dimensions.
Through some experimentation, I think that changing the vertical dimension to something less than 800 seems to work. For example, I took my original 480x800 image and cropped 30 pixels off to make an image of 480x770. I then resized the image back to 480x800 while ignoring the aspect ratio. This results in a distorted eye, but the distortion is in the opposite direction. (The 480x800 wallpaper is distorted in the horizontal dimension. The 480x770 resized image is distorted in the vertical dimension.)
The 480x770 image is slightly less distorted so I think this might be the way to go. Short of guessing the right dimensions, I was hoping for a way to determine the best dimensions to use.
To help anyone else reading this thread, I'm attaching the wallpapers I've created. Feel free to download them and try them out.
galaxytabevo said:
My wallpaper doesn't scroll anymore, I'm not sure why.
Click to expand...
Click to collapse
I think I read somewhere here that the latest Samsung stock update disabled the scrolling wallpaper.
home screen or lock screen?
Lock screen does not scroll.
For home screen you need 800x960 image or you may need to adjust your original 800x480 image to 400x480 and double the pixel size.
To scroll the home screen wallpaper, you need to change the option to make it scroll.
kobridge said:
home screen or lock screen?
Lock screen does not scroll.
For home screen you need 800x960 image or you may need to adjust your original 800x480 image to 400x480 and double the pixel size.
To scroll the home screen wallpaper, you need to change the option to make it scroll.
Click to expand...
Click to collapse
I'm working on the lock screen. With most wallpapers, the difference in the aspect ratio is likely not noticeable. I just happen to see it because my lock screen image has only one component and it's very easy to see when it's distorted.
Lobo Droid said:
I think I read somewhere here that the latest Samsung stock update disabled the scrolling wallpaper.
Click to expand...
Click to collapse
This really sucks. I also miss the bounce effect on the browser/when you reach the end of a menu. Was it due to the Apple lawsuit?
I've been searching and searching for the appropriate Nexus Galaxy desktop resolution and found a HUGE variety of answers. Someone has probably figured this out already, but here are the *actual* values for the NG desktop:
NB: All dimensions given in Width x Height - portrait orientation
Entire Single Home Screen:
720x1280
Wallpaperable Area - Single Home Screen:
720x1135
Status Bar Area
720x50Soft Button Area
720x96
Wallpaper Ratio (WxH) - Scrolling Desktop
960x853 (yes, 853!)
It appears that the system crops a bit off of the top and sides of each image before applying it to the desktop.
1440x1280 - That is all.
stereoprologic said:
1440x1280 - That is all.
Click to expand...
Click to collapse
Hmm. It appears that you are right. I'm still a little mystified though. The stock wall papers that the OS ships with are all 960x853. That sizing ratio and 1440x1280 both work even though they don't appear to be multiples of each other. I'm a little baffled as to how those both can fill the same "crop box" exactly.
m developing an Android app but im still inexperient with some sdk stuff. One of the things is about multiple resolutions.
I know that, Android documentations talks about using multiple image folders for the screen resolutions. But i ask myself, how to reduce App size? And thats where i find "rezise Images". Plus, i unpack some App's and saw that they used just one folder, for one image.
My questions is, should i use "resize images" or should i use many images for multiple folders? What is the differences? What people usually do? What advantages and disavantages?
Im really thinking about this.. Get Android device density, and rezise image by density.. But i dont know if this is the best pratices, or something.
Usually the purpose on using different images for different densities is used on buttons or graphics that you want to have a specific "real-life size". For example in order for a button to be touchable by a human finger it needs to be about 48dp (dp = density independent pixels), for example in a device with high density 48px (pixels) makes the button too small, so if it is 48dp it becomes 72px on screen which is about the same size in real-life.
On big images like in a gallery or something this should be discouraged, you can provide an image in big size and android will automatically resize it in smaller densities. This is quite visible on buttons but not that visible on images.
I'm not sure about the "line" that defines when you need to choose one way or the other, just whatever suits your needs.
Edit: I forgot to mention that it is not good practice to resize images by yourself, if you put an image on "drawable-hdpi" folder (for high density) and a device is using medium density then android will resize the image for you.
I prefer to use less image files. For example I store all app images in xxhpi and xhdpi folders. For other destinies android will reduce image sizes automatically.
Also I use services to reduce image size like tinypng
SergeiPekar said:
I prefer to use less image files. For example I store all app images in xxhpi and xhdpi folders. For other destinies android will reduce image sizes automatically.
Also I use services to reduce image size like tinypng
Click to expand...
Click to collapse
I agree we should try to use less image files than possible but as VGDTom said they is no clear line of when we should provide all the different image sizes and when we would provide only some of the largest which can be re-sized. I would say you will have to compromise on which aspect of your app your totally want to provide the best image for it. For instance I think the app icon is needs all its images just to always make sure you look create in every home screen but for other less important item you can compromise.
Instead of always creating 5 images, creating 5 emulators is a trade off to test, based on what you see you can decide if you need to create one image for each spec.
Up until fairly recently I would have said that providing at xhdpi and mdpi - essentially equivalent to iOS regular size and @2x - is all you really need to get decent visuals across most devices. However, high-res screens are now increasingly the norm, so I'd do xxhdpi as well. Also, always provide launcher icons at all recommended sizes. Nothing kills an app's appeal faster than a blurry launcher.
You can you one folder with one image, but when you do that, you significantly slow down your app. On low screen resolution device, its CPU is too weak but have to work the same task as a high screen resolution device with powerful CPU.
The attached image shows MobileSheetsPro running on my old Galaxy Note 10.1 (left) and on the S4 (right).
The note is 1280x800 and the S4 is 2560x1600.
I would expect the applications to look the same, but this is not the case. On the S4, the dialog is about 25% larger, the icons are larger, etc.
If you are familiar with MobileSheetsPro you can see that I needed to lower the font sizes used by the program (to about 80%) to get the same contents on the display. Other applications show similar differences.
DevCheck (see 2nd attachment) shows resolution 1280x800 and screen density 160dpi (mdpi), 1280dp x 800dp for the Note, and for the S4 resolution 2560x1600 and screen density 360dpi (xhdpi), 1138dp x 711dp. I find the red numbers puzzling.
Is this normal behaviour? Is MobileSheetsPro misbehaving? Is there some setting that can (needs) be adjusted?
'm confused about this as well. Just picked up a a new s4 for super cheap...and games are too zoomed. I used recheck and an online tool and they both show 1280 x 800. Tried changing min width in developer settings to no avail
My tablet is at home, and this isn't the behavior I remember, but i don't use Mobile Sheets, and it could be specific to software. Android does some weird treatments that are supposed to be based on resolution. The xhdpi is a clue to this. In your old tablet it was using the native resolution in determining what resources to use/scale. On the new one, it appears to behave as if it believes the dPI is higher than it really is and the resolution lower. Somebody who understands better how this works in Android will have to give a more complete answer.