Related
I mean, I understand why the background auto-rotate when we tilt the phone. When accelerometer detect the phone tilt, the screen tilt and the background tilt w/ it. And that's kinda make sense. But, the problem is when you have a tight crop person as a background, and set the background to be non-scrolling. Then I think it's obvious that the background want to be set static in a certain way. Currently I have not found a way to lock the background wallpaper. I mean as I rotate the screen I want everything else to rotate and get landscape/portrait UI as necessary, but the background remain the same whether portrait or landscape. Well, I have yet to found a way. The only thing I came across is to disable accelerometer, but that's not very a solution. Anyone know how to do this?
Thank you,
The only thing I can think of is to find an app on the market that will manage your wallpapers for you. I know they have apps that will set a seperate wallpaper for each homescreen, so maybe there's one that allows seperate wallpapers for both portrait and landscape.
As far as finding a checkbox in Android to do this, there isn't one.
Sent from my SPH-D700 using XDA App
So it has been mentioned throughout a lot of threads but I figured I would give a step by step and overview for the people who do not know about this or are unsure what it means and does. You must be rooted to use this.
When you compare our phones to a phone that has a qHD display you will see that the qHD display will have smaller text and will allow you to view more on the screen at one time then our WVGA screen allows. Well this is how you can even the playing field and view your phone like it was a qHD or even a 720p screen.
No more super large text like your phone was built for the blind. Also, a great feature if you use an alternate launcher you can set the screen to 5x5 or even 6x6 depending on the resolution you pick.
You will need the 2 apps from below.
First you need to install busybox. Download the app and then open it. From there it will ask you to install. Just choose okay for all the defaults and don't change anything.
https://market.android.com/details?...t=W251bGwsMSwxLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
Next app is lcd resolution. This is where you change the resolution.
https://market.android.com/details?...NvbS53ZW1vYnMuYW5kcm9pZC5sY2RyZXNvbHV0aW9uIl0.
There are 2 settings I use, 200 which is almost identical to qhd. qHD is 960x540 and the app allows you to set it at 960x576. You can also set it at 160 which is 720p. You can use all the settings in-between as well but I stick to these 2. You can do your own testing and see what works best for you. Make sure when testing that you do not click save on boot in case your Rom does not play nice with that resolution. I have found that 200 works almost everything but 160 can be a little more tricky, especially with certain themes. You top bar will be all blurry. A reset will put you back to stock if your Rom does not like the resolution as long as you did not click set on boot.
By doing this hack, TW launcher will not play nice so you must use an alternative. All other launchers will work. The stock dialer will also not work. You can use Go contacts, dialer one or Ex Dialer. They all look and function great. You will also need an alternate calendar and calculator app. Their are a ton to choose from.
When setting your system to 200, you might encounter an error message saying certain apps are not compatible with your phone in the market. This is because this setting while close to qhd is not exactly the same resolution so the market app does not think is is compatible as it is not a standard resolution. There are 2 ways around this. You can install the app through Amazon market as it does not know the resolution you are running on your phone or you can switch back to stock (240) then clear market data and you can download the app. Then switch back to 200. This won't happen with every app as a lot will still download when st to 200.
When running at 160 (720p) you will not have this issue in the market as this is a native resolution of Android and is recognized by every app.
I think that covers it all for now and I cannot imagine going back to a WVGA resolution as it looks sooooooo much better running at a near qhd res.
Below are 2 picks showing the difference. One is stock, one is set to 200 (qhd) and the other to 160 (720p).
Stock (240)
qHD (200)
720p (160)
I like 720p. Also, you can edit your build.prop manually and modify:
ro.sf.lcd_density=240
Does anyone know how to modify a theme to make it work with this?
bertm13 said:
I like 720p. Also, you can edit your build.prop manually and modify:
ro.sf.lcd_density=240
Does anyone know how to modify a theme to make it work with this?
Click to expand...
Click to collapse
Yeah TW theme built for 720p setting would be a keeper.
bertm13 said:
I like 720p. Also, you can edit your build.prop manually and modify:
ro.sf.lcd_density=240
Does anyone know how to modify a theme to make it work with this?
Click to expand...
Click to collapse
That works as well but the app makes it much quicker to jump between resolutions then having to edit the file.
When i changed it with LCD density the resolution changed but there was lots of space under the home screen # indicator, can you do a shot of your home screen and wallpaper to see what it looks like?
xlGmanlx said:
When i changed it with LCD density the resolution changed but there was lots of space under the home screen # indicator, can you do a shot of your home screen and wallpaper to see what it looks like?
Click to expand...
Click to collapse
you can't use Touchwiz. Need another launcher, and dialer. On some roms the camera and music apps break too if you go too low (like 720p), likely others.
I am confused, if the resolution can be improved via software, then how come the manufacturers are not doing it, what is the catch?
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I am confused, if the resolution can be improved via software, then how come the manufacturers are not doing it, what is the catch?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was going to take issue with OP's terminology but decided to not be 'that guy'...
...but here we are.
This doesn't actually change the resolution of the panel at all. You always have the same amount of pixels. Period. All this does is scale the UI. at a screen density of 160 our screen will display things at the size that a 720p screen of identical size would display them. However we lose detail on fonts whereas a 720p screen would have the same amount of detail at 160 as we would at 240....roughly. If you can live with smaller and slightly blocky fonts, go for it.
I can. It's awesome.
another confusing but interesting tidbit: LCD Pixels are made up of red green and blue subpixels. Our panel and the 720p Galaxy Nexus panel have an identical amount of subpixels. But the 720p panel achieves a higher resolution by using less subpixels for each pixel. That is why it is said to have a "pentile" display, as each pixel is composed an arrangement of 5 sub-pixels whereas we have 12 sub-pixels for each pixel. This also explains why 800x480 (WVGA) "pentile" panels look like crap...err...ahem...receive so much criticism. (See: motorola displays)
EDIT: Also, more sub-pixels per pixel means better 'sub-pixel hinting'...which is an effect used to enhance text on LCD panels. The fact that we have so many sub-pixels is probably the only reason why we can pull this off. Of course I'm assuming that android takes advantage of subpixels.
Just a reminder to everyone to nandroid before doing anything like this;
My phone won't boot after doing this. I can get into CWM, but anytime I try to reboot it gets stuck in a loop at the Sprint / 4g animation. I suspect it has something to do with busybox installation but who knows.
I did NOT have the "Set on Boot" selected in the LCD density app. I think I already had busybox support... maybe trying to install the market busybox app borked something.
Anyhoo... always do a nandroid, kids!
As Dan mentioned, it does not actually change the resolution in the true sense but for the purpose of this thread I didn't get into that detail.
I think our screens look 10x better then the Evo 3d and the photon screens when our screens are set to WVGA compared to their qhd display. This only makes it better. With a screen this large it only makes sense to shrink things down to get more on the screen.
Now the Galaxy Nexus screen, I am expecting that to be a killer screen.
Ok thanks, it was leaving like choke real estate under the page number on the screens, I actually like Touchwiz but thanks for the heads up
daneurysm said:
you can't use Touchwiz. Need another launcher, and dialer. On some roms the camera and music apps break too if you go too low (like 720p), likely others.
Click to expand...
Click to collapse
xlGmanlx said:
Ok thanks, it was leaving like choke real estate under the page number on the screens, I actually like Touchwiz but thanks for the heads up
Click to expand...
Click to collapse
I think if we could yank touchwiz off of a Galaxy Note it would do 720p (160) and if not whatever the density setting is on the Galaxy Note would make it fit perfectly.
As far as I've seen, touchwiz isn't ingrained in Android at all. I could be wrong, but, it seems like just a launcher. It's nothing like Sense which has it's big fat tentacles way up Android's ass.
...though I'm not a fan of Touchwiz, so, it really doesn't bother me at all. It's not that I hate touchwiz--I was actually astonished to find how nice it was after all of the Sense-o-philes bashed the crap out of it--I just love me some Launcher Pro and/or ADWex, depending on the time of day....though every now and then I throw on Launcher7 for giggles.
I think you are right on all accounts. I actually like its styling (well with ICS + ICS Twist) but the fact that the launcher is hardware accelerated is too much to give up
daneurysm said:
I think if we could yank touchwiz off of a Galaxy Note it would do 720p (160) and if not whatever the density setting is on the Galaxy Note would make it fit perfectly.
As far as I've seen, touchwiz isn't ingrained in Android at all. I could be wrong, but, it seems like just a launcher. It's nothing like Sense which has it's big fat tentacles way up Android's ass.
...though I'm not a fan of Touchwiz, so, it really doesn't bother me at all. It's not that I hate touchwiz--I was actually astonished to find how nice it was after all of the Sense-o-philes bashed the crap out of it--I just love me some Launcher Pro and/or ADWex, depending on the time of day....though every now and then I throw on Launcher7 for giggles.
Click to expand...
Click to collapse
xlGmanlx said:
I think you are right on all accounts. I actually like its styling (well with ICS + ICS Twist) but the fact that the launcher is hardware accelerated is too much to give up
Click to expand...
Click to collapse
Has this been verified? I stopped caring about it once I got LP/ADW up and running and it seems supernaturally smooth. Though I have to admit that the transition to the app drawer in TW is phenomenally smooth...aside from that, though, I don't really see it.
...and if only TW is hardware accelerated that must be via an API. Samsung proprietary? Considering the popularity of the SGS2 worldwide I'd imagine there would have to be another launcher that would take advantage of these hooks.
Honestly if we do, in fact, have hardware acceleration (and I believe we do) why wouldn't that be system wide? Once you go into settings you are out of the launcher and if anyone remembers Cupcake or Donut holy crap was that a painful experience for what was at the time super fast 528-800mhz phones (g1/hero and moment).
this is a great find I think, I really like the tight resolution, not too keen on having to change the type of launcher either
Has anyone noticed the jacked up notification on the notification bar?
And too bad there's not a way to make the dialer and home screens fit the screen now!
Thanks for the hint
Tried this at 160 using go launcher on starburst 1.9.8r with the beta ICS theme and it looked great except the status bar was screwed up. Do you think it might be the theme or rom?
psych2l said:
Tried this at 160 using go launcher on starburst 1.9.8r with the beta ICS theme and it looked great except the status bar was screwed up. Do you think it might be the theme or rom?
Click to expand...
Click to collapse
Was it a theme you added on to the Rom? If so, you can try it without the theme.
I am running Calk's 1.5a Rom and it works at 160 by itself, with the honey theme and the ICS mixup theme as well...
Tried it at 200 but didn't like how it screwed the dialer up and went back to 240.
tenaciousj said:
Tried it at 200 but didn't like how it screwed the dialer up and went back to 240.
Click to expand...
Click to collapse
Download GoContacts, it comes with GoDialer. Both better than stock apps and free and work at any density.
Sent from my SPH-D710 using XDA App
Anyone figure out a way to replicate a true qHD resolution? Being that it is a little off you get the apps not compatible message in the market. If you were able to replicate the exact res like 720p does you would not get that message.
Hey!
I received my tabpro and i notice so much lag in games like simpsons tapped out. My girlfriend has Tab 3 and it runns perfectly. Is it about the resolutions, since i have 2560x1600. Is there any way to lower my resolution or do I have to install custom ROM.
And why my homescreen resolution is not that 2560x1600. My image is 2560x1600 and it looks nice in gallery but after i use it as my wallpaper on homescreen it gets blurry.
I thought this tablet is powerfull in games and so on. But i am very disappointed. All help is needed so help me to to get clean rom or just help to lower my resolutions.
Any suggestions?
I'd like to know this aswell.
Sent from my XT897 with Tapatalk 4
It should be possible to change the resolution of an app with "app settings", an XPosed Framework module. (root required)
When you set an image as your wallpaper it gets zoomed in (as it has to fit screen and scroll horizontal), therfore, the pixels of the image won't match pixels on the screen anymore and get re-calculated, making the picture blurry.
Hejkompas said:
It should be possible to change the resolution of an app with "app settings", an XPosed Framework module. (root required)
When you set an image as your wallpaper it gets zoomed in (as it has to fit screen and scroll horizontal), therfore, the pixels of the image won't match pixels on the screen anymore and get re-calculated, making the picture blurry.
Click to expand...
Click to collapse
Thanks for reply. I got images working now and installed custom rom. I also found a application to change resolution but then my touch wiz is not responding. I can still use browser etc at lower resolution but games Se till run at high resolution. Any help?
telot said:
Thanks for reply. I got images working now and installed custom rom. I also found a application to change resolution but then my touch wiz is not responding. I can still use browser etc at lower resolution but games Se till run at high resolution. Any help?
Click to expand...
Click to collapse
You found an application to change the resolution? Give us some more information to work with mate.
GLTools: http://www.google.nl/url?sa=t&rct=...5mzqqgTVIaRYGZCQgTLXGQ&bvm=bv.71667212,d.d2k
Hello all, so I'm having a little problem that's keeping me away from TW Roms. I use a DPI changer from the play store and all goes well, my only problem is my phone app becomes smaller and shifts upward toward the left side. Its a minor problem, but its pretty annoying. I'd post a pic of it if anyone needs more clarification for what I mean but I'm currently on a spirit ROM. If anyone knows how to fix the in app DPI settings I'd appreciate it.
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.