Ok I have been looking everywhere and can't seem to find a app that will set the wallpaper as is without cropping or cutting the edges off. I know the best resolution is 960x800 but it still cuts off parts of the picture. I've tried wallpaper set and save and a host of other apps from market and various android freeware sites. None of them seem to set them right, any help would be highly appreciated. I have an HTC evo running cyanogen 6.1 stable and everything is so far so good and I want to thank this website because without it I was lost. This is my number 1 forum so I know ill get the answer, its out their please help me find it. Thanks in advance!!
flikie wallpapers hd is about the best ive seen at this. it still crops but i keeps most of the image quality
Only thing I can think of is to take the photo you want, make the actual photo whatever the screen resolution is (480x800 from what I've read) with black bars on the side to make the entire picture file 960x800. Then use launcher pro to freeze the background so it doesnt move when you swipe. Your picture should be centered.
When you select the image for a wallpaper, you see that little box in the center? Drag outwards on one of its edges.
dkelle4 said:
Only thing I can think of is to take the photo you want, make the actual photo whatever the screen resolution is (480x800 from what I've read) with black bars on the side to make the entire picture file 960x800. Then use launcher pro to freeze the background so it doesnt move when you swipe. Your picture should be centered.
Click to expand...
Click to collapse
Thank you all for the speedy replies, I see what your saying. I have my desktop set to have only one screen already, but I went and got launcherpro cause of its features. But yea I downloaded a few pictures before that were 480x800 and it had the black bars on the sides but when I set it, it cuts off the head and feet, 960x800 however does not, it only cuts just a little off the sides. I'm guessing now that the picture is to wide and I wanted to know if I could make a picture keep its height and change its width. I don't know maybe keep the height from the 960x800 setup and the width from the 480x800 setup if that's possible.
My friends, friend has his set up so that when he sets a wallpaper it gives him the option to set as is, to crop, and i think the other one was to cut it. I don't know if its a application or if its the firmware (like cyanogen i mean) he uses, I would ask but he lives very far a few cities over. I have been combing the internet for this app or whatever, and I'm fairly new to android phones, but I got a pretty good history with computers so that definitely helps. But this one seems to be a common problem with a somewhat easy fix. Any ideas?
Are you sure you didn't mix up the 2 sizes lol. 960x800, and not 800x960. Not trying to be a jerk or anything, but I've done that before using Photoshop.
I'm trying to use desktop visualizer to place some images on my home screen, but for the life of me can't get them to come out crisp.
I'm using Apex on 10 x 10, and I'm using a high-res picture with some transparency/scanlines, so its very obvious when it isn't displayed correctly.
I've tried all the DVR addons, and put the quality settings as high as I could. I suspect the problem to be a size limitation in DVR, I think I need something that can create larger than a 4 x 4 widget. Does anyone have any ideas? I'd prefer not to lower my grid size... Thanks.
Hi all, please see the below thread. Only sharing the info as this was posted on the Verizon N4 forum.
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Hope this helps...
As indicated below some touchwiz native apps are affected.
List of known affected applications by changing DPI settings:
S-View (for S-View covers -- slightly misaligned but functional)
Touchwiz Stock Dialer (slightly misaligned but functional -- other non-stock options exist such as Hangouts or ExDialer)
Fingerprint lockscreen (arrow pointing to finger print scanner off center)
Exchange email (stock Samsung Email)
Stock Camera App
Just FYI to get some easy download links:
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Enable USB debugging on yer phone
-> http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
Samsung USB drivers you'll need installed
-> http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
ADB / Fastboot installer
navigate to C:\adb\ and then run the command they give in the thread
adb shell wm density 540
(not confirmation will be sent but your phone should prompt you to 'allow' your computer to send adb commands to it.).
Restart phone
DPI settings are now at 540. original DPI settings are 640 BTW
imnoob55 said:
Hi all, please see the below thread. Only sharing the info as this was posted on the Verizon N4 forum.
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Hope this helps...
Click to expand...
Click to collapse
I came across that thread a few hours ago. It's pretty neat to be able to drop the density and make more use of display space (could even drop it down to 384 and make it look more like a tablet), but it has its problems. Samsung apps (Dialer, camera, S Note, S-View, etc) will lose their screen alignment and/or only cover a portion of the screen when altering the density. Finding an alternate dialer was easy enough, but I'm having trouble finding a camera app similar to stock in quality, and was unsuccessful at replacing the S-View...
redphazon said:
I came across that thread a few hours ago. It's pretty neat to be able to drop the density and make more use of display space (could even drop it down to 384 and make it look more like a tablet), but it has its problems. Samsung apps (Dialer, camera, S Note, S-View, etc) will lose their screen alignment and/or only cover a portion of the screen when altering the density. Finding an alternate dialer was easy enough, but I'm having trouble finding a camera app similar to stock in quality, and was unsuccessful at replacing the S-View...
Click to expand...
Click to collapse
Yup unfortunately that is a side-effect of doing this. Only way to do it that I am aware of conventionally would be via xposed or loading in custom TW apps, both not possible. Hangout dialer works well, for this. TW stock browser is not affected. My S-Note is not affected either, too. Dialer and S-View are (not unusable, they just are not center-aligned any longer as their height/width are set on static widths rather than proportional % when Samsung set up the layout.) Maybe they'll change that in L.
BTW I use Nova for launcher and Hangouts as my dialer. I do use an s-view case, though, which is of course impacted.
imnoob55 said:
Yup unfortunately that is a side-effect of doing this. Only way to do it that I am aware of conventionally would be via xposed or loading in custom TW apps, both not possible. Hangout dialer works well, for this. TW stock browser is not affected. My S-Note is not affected either, too. Dialer and S-View are (not unusable, they just are not center-aligned any longer as their height/width are set on static widths rather than proportional % when Samsung set up the layout.) Maybe they'll change that in L.
BTW I use Nova for launcher and Hangouts as my dialer. I do use an s-view case, though, which is of course impacted.
Click to expand...
Click to collapse
I'm also using Nova Launcher. I did download ExDialer at first, but I went to Hangouts Dialer instead since ExDialer has a trial period and costs money.
S Note is largely unaffected yes, but when you open the camera for copying documents, the square used for aligning the camera with the document is off-center. It doesn't seem to hurt functionality in any way, though. Oddly enough, the camera when used in S Note is fullscreen...
As far as S-View goes, I'm thinking about removing the flip cover. S-View is nice, but I'm always trying to not get smudges on the cover screen on top of the phone display, so the cover is a little bit cumbersome to me when holding it. Seeing how much better the phone looks at a lower density makes me lean even closer to just getting rid of it. That leaves me with just the camera replacement...
Exchange email is also broken... when you reply to an email, the screen font is set to eleventybillion.
-----
Sent with my Galaxy Note 4
Can anyone confirm if this impacts the play store? Typically changing the dpi on the whole device would prevent the play store from downloading some apps.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jfenton78 said:
Can anyone confirm if this impacts the play store? Typically changing the dpi on the whole device would prevent the play store from downloading some apps.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
I haven't seen any problems with the Play Store yet, though I haven't been installing much of anything, either. The few apps I've installed so far gave me no trouble.
Also, just found out that the stock camera has no problems with accurate button detection when the phone is turned sideways for landscape rotation, though it's still not fullscreen. You have to guess where the buttons are on the screen in portrait when the density is changed.
Couple of tips:
if you get an error about the device being offline make sure you've got the current ADB installed. The link provided for the adb and fastboot didn't work for me because the file didn't install. The program is just an auto run zip file. you can open with 7-zip and just extract the adb files.
also if you get an error about the device being unauthorized you must select no action on the windows pop up and always perform this action. the phone should then get a pop up with the RSA key number and ask you to authorize. hope this helps.
540 DPI is pretty nice.
I was okay with the dialer and lockscreen, but the camera made me go back to 640. In vertical shooting mode, the touch points for all the icons, including the shutter button, is misaligned and is very annoying. What a shame as 540 looked AWESOME.
cj00ta said:
Exchange email is also broken... when you reply to an email, the screen font is set to eleventybillion.
-----
Sent with my Galaxy Note 4
Click to expand...
Click to collapse
Thanks! Just added to the top thread under impacted apps
Does this effectively change the resolution? I'm curious if lowering the DPI would give positive improvement to high-end game performance. Can anyone shed some light here?
Conkrete said:
Does this effectively change the resolution? I'm curious if lowering the DPI would give positive improvement to high-end game performance. Can anyone shed some light here?
Click to expand...
Click to collapse
It doesn't change the resolution. What it changes is the drawing size of on-screen content which is directly from the 'dpi setting' of the phone.
It's a little complicated to explain but this is how it works;
The phone's default screen density (DPI) setting 640, this is done because that's how many dots per inch of the physical screen there is (a phone of similar screen size would have a similar dpi). This value is stored in your phone's build.prop and is read by numerous applications, it might not match exactly the 'real' dpi of the screen but its normally very close to it.
By changing it lower in dpi you're instructing to applications you actually have a smaller screen size, thus to fit content (i.e words not being HUGE on a small screen) content is drawn to that dpi setting you're providing in build.prop.
Now to go into why we have certain issues when changing the dpi.
This is basically due to how the app did its layout sizing (do I base content on "actual size" of the screen-size or do I base it on "actual density" of the screen density in build.prop? Most apps, since they're targeting to be used with dozens of devices of all sorts of different sizes, will be designed where the layout of content is dependent upon dpi. A layout would be I want a rectangular box on the bottom that has height 10px and width 100%, so that effectively means the width is based on the proportion of the screen size (the OS controls this, its just a matter of scaling). This is why you once had 5 items to show now has 8 items to show in a listbox. The size of the listbox in this case would be based on actual density while the content (text etc.) inside would be based on actual size (scaling I would think is limited to a min/max actual size for text).
Samsung can get away with this on their stock apps because in their mind when they build their roms they are only going to be used on that specific device. They're starting to go away from this, however, and are starting to make their layouts more typical that of a normal application. You have somewhat less control of the layout going from actual size to actual density.
*keep in mind you can actually set parameters for both. Such as if I wanted something to be 10% in width but only up to 2.5 inches in actual size this effectively means that it will scale until it reaches 2.5" and then scale no longer.
I hope that makes sense. Resolution really doesn't have a role at all in this, you're always at the same resolution (4K) and this is handled by the lower-level kernel and GPU firmware. I don't think there's a way to change this at the app layer but than again I have really no background in android development.
*please if anything comes off as inaccurate please point out, I am from a XAML/.NET development background and linux/unix embedded systems and really I focused on back-end/databases/services and not really front-endy stuff. This is how it is handled in XAML though and I have seen android uses the same principals.
imnoob55 said:
It doesn't change the resolution. What it changes is the drawing size of on-screen content which is directly from the 'dpi setting' of the phone.
It's a little complicated to explain but this is how it works;
The phone's default screen density (DPI) setting 640, this is done because that's how many dots per inch of the physical screen there is (a phone of similar screen size would have a similar dpi). This value is stored in your phone's build.prop and is read by numerous applications, it might not match exactly the 'real' dpi of the screen but its normally very close to it.
By changing it lower in dpi you're instructing to applications you actually have a smaller screen size, thus to fit content (i.e words not being HUGE on a small screen) content is drawn to that dpi setting you're providing in build.prop.
Now to go into why we have certain issues when changing the dpi.
This is basically due to how the app did its layout sizing (do I base content on "actual size" of the screen-size or do I base it on "actual density" of the screen density in build.prop? Most apps, since they're targeting to be used with dozens of devices of all sorts of different sizes, will be designed where the layout of content is dependent upon dpi. A layout would be I want a rectangular box on the bottom that has height 10px and width 100%, so that effectively means the width is based on the proportion of the screen size (the OS controls this, its just a matter of scaling). This is why you once had 5 items to show now has 8 items to show in a listbox. The size of the listbox in this case would be based on actual density while the content (text etc.) inside would be based on actual size (scaling I would think is limited to a min/max actual size for text).
Samsung can get away with this on their stock apps because in their mind when they build their roms they are only going to be used on that specific device. They're starting to go away from this, however, and are starting to make their layouts more typical that of a normal application. You have somewhat less control of the layout going from actual size to actual density.
*keep in mind you can actually set parameters for both. Such as if I wanted something to be 10% in width but only up to 2.5 inches in actual size this effectively means that it will scale until it reaches 2.5" and then scale no longer.
I hope that makes sense. Resolution really doesn't have a role at all in this, you're always at the same resolution (4K) and this is handled by the lower-level kernel and GPU firmware. I don't think there's a way to change this at the app layer but than again I have really no background in android development.
*please if anything comes off as inaccurate please point out, I am from a XAML/.NET development background and linux/unix embedded systems and really I focused on back-end/databases/services and not really front-endy stuff. This is how it is handled in XAML though and I have seen android uses the same principals.
Click to expand...
Click to collapse
Extremely helpful and great info. Possibly the best response I've received from XDA. Thank you for the info. I have found a couple root apps that claim to change resolution but I've been hoping to find a non-root alternative.
One of the first things I have noticed with the Tab Pro 8.4 is a severe imbalance between the font sizes of Samsung UI elements and non-Samsung. For example in Play Store when I enter text in the search box it's crisp but quite small. Yet the text in the Settings menus is a very comfortable size compared to the Google font size. If I increase the font size system-wide then the Google font size becomes comfortable and the Samsung font size becomes cartoonishly big.
Has anyone else noticed this and/or come up with a reasonable solution?
Perhaps one culprit is the fact that the true DPI of this device is 359 and Samsung has programmed 320 into the build.prop. That means it's lying to the OS that the screen is 9.4" not 8.4". So apps are drawing text and graphics a bit too small, but Samsung decided to jack up their own font sizes to a comfortable range. If I were to edit the DPI to 320 that still wouldn't be likely to help as then Samsung would just remain cartoonishly big.
I agree 100% with this problem and have tried changing the DPI in the build.prop. Big mistake as it causes crashes everywhere in Sammy apps.
The only work-around I have found was to use the Xposed framework with the App Settings app. This way you can adjust each app individually.
Its not a perfect solution, but its the best I have found in the 5 days I've owned this tab.
cmstlist said:
One of the first things I have noticed with the Tab Pro 8.4 is a severe imbalance between the font sizes of Samsung UI elements and non-Samsung. For example in Play Store when I enter text in the search box it's crisp but quite small. Yet the text in the Settings menus is a very comfortable size compared to the Google font size. If I increase the font size system-wide then the Google font size becomes comfortable and the Samsung font size becomes cartoonishly big.
Has anyone else noticed this and/or come up with a reasonable solution?
Perhaps one culprit is the fact that the true DPI of this device is 359 and Samsung has programmed 320 into the build.prop. That means it's lying to the OS that the screen is 9.4" not 8.4". So apps are drawing text and graphics a bit too small, but Samsung decided to jack up their own font sizes to a comfortable range. If I were to edit the DPI to 320 that still wouldn't be likely to help as then Samsung would just remain cartoonishly big.
Click to expand...
Click to collapse
tpowell.ca said:
I agree 100% with this problem and have tried changing the DPI in the build.prop. Big mistake as it causes crashes everywhere in Sammy apps.
The only work-around I have found was to use the Xposed framework with the App Settings app. This way you can adjust each app individually.
Its not a perfect solution, but its the best I have found in the 5 days I've owned this tab.
Click to expand...
Click to collapse
Yep, I've used it before on other devices. I used the newly released FlashFire to take a backup of my system to external SD before installing Xposed. I currently have a dpi of 360 assigned to all of: Chrome, Dropbox, Gmail, gReader, Google Maps, Netflix, News & Weather, Nova Launcher, Plume, Root Explorer, Tapatalk, Titanium Backup, PressReader, and the App Settings app itself (as everything was a bit too small). That puts these apps in the same range of screen element size as on Nexus devices. Feel free to pick a bit higher for a bit bigger as we do tend to hold tablets further from our faces than phones.
In fact the Nexus 5 itself (which is my daily phone) has a build.prop that is too large for the real screen size, 480 instead of 445 (factor of 7.8%). But it does make the UI a bit more comfortable without sacrificing too much screen space. So theory if you want any apps on the Tab Pro to display their UI elements at least as large as they physically appear on a Nexus 5, you'd assign a DPI in the 380-385 range to those apps.
tpowell.ca said:
I agree 100% with this problem and have tried changing the DPI in the build.prop. Big mistake as it causes crashes everywhere in Sammy apps.
The only work-around I have found was to use the Xposed framework with the App Settings app. This way you can adjust each app individually.
Its not a perfect solution, but its the best I have found in the 5 days I've owned this tab.
Click to expand...
Click to collapse
Old thread but thanks! My GF has the 8.4" model and in the latest Facebook app the font is like 1/32" and she cannot read it
I read here and there the forum, rooted the tablet, installed xposed, installed AppSettings and changed the DPI, it worked! :good::good::good:
Curious if there's a way to have different screen zoom and text sizes per screen. On the front.. obviously like it a little bigger. Opened, I like the screen zoom to small with a slightly smaller text size. Also the screen zoom changes some apps to tablet mode, not ideal for the small screen. Any ideas?
Wondering about this as well. I've yet to find anyway of doing this. At the moment, 'Medium' Zoom looks better for the outside screen but too big for the Inner. I've just set it to 'Small' as the best you can get for now. Any change in developer setting (to make even smaller) makes the outside screen practically unusable due to its tiny size.
yeah from what i understand, the text size setting is completely global which is unfortunate.
with their expensive team of "experts", you would wonder why this was such an oversight.
Iv noticed on small screen you can pinch to zoom which iv used a lot
Someone suggested on Reddit that you can use Tasker to create two different profile for open and closed state with separate dp… The downside is, it will have maybe half a sec delay when you open or close due to switching res...