Related
The Instructions:
Short, sweet, and straight to the point: So, here's what you do... you will want to download the app called Screen Filter with the market link provided below. After you do that, within the Screen Filter app you will want to drag that brightness bar to say 85.1% and then hit enable. This won't lower your current screen brightness very much so no worries there. You should hopefully notice a difference for the better all around, especially viewing from an odd angle. It helps to reduce that white backlight look you get from a side view. I will typically set the in app brightness to either 85.1%, 75.5%, or 72.5%, and my actual system brightness to 50%. It works quite well without being too bright or too dark. And it goes without draining much, if any battery life. Feel free to try other brightness settings to fit your personal needs.
Try it on other Android devices as well, it works great! The best way to test it out is to use the widget. You can turn it off and on while changing your viewing angle to compare and see the difference for yourself on your homescreens. Forget about a complicated method and get yourself a better screen today with Screen Filter!
Screen Filter Can Be Found Here:
https://market.android.com/details?id=com.haxor&feature=search_result
Showing Off Side Angle View:
You will be able to notice that in the after screenshot the green bar across the top of the market app is quite a bit more vibrant and has more of a green color than the before screenshot. And you will also notice that the white back light color will be enhanced as well, giving a better appearance from the side viewing angles. A nifty little quick fix, if you will.
Before:
After:
Screen Filter Known Issues Reported By Users:
*Being completely stock and using the stock system apps seems to be causing some major lag issues (Xoom)
*Cannot seem to click install when you are manually installing an apk without disabling (Xoom)
*Cannot compose emails without disabling (Nexus S)
You can add to this list. If you find anymore issues please post them here and I will add them to my list above. After we gather most/all issues that we are having I will let the dev know what we have found and we can make some positive results for all! Maybe we can even have some new features added in a new release. Once the Honeycomb source gets released and we start getting custom ROMs, expect user interface tweaks such as what you find in Cyanogenmod. Until then, use this. It's the easiest and best tool we have for now.
Note For Screen Filter:
This method may only be effective on the 3G version of the Xoom. It appears that it may not be noticeable as much, if at all on the Wifi model.
Make That High Def Screen Even Higher:
For this you will need to be a root user, and always be sure to have a current Nandroid backup handy just in case.
You will want to download the free app called LCD Resolution (Root). You can find it on the market here. Open the app, and then you will see your current density setting as well a list of density options for you to choose from. The default density value for the Xoom is 160. I do not recommend that you go below 140, as certain screen elements may become misaligned. Just dropping the value down by 10 to 150 makes a nice noticeable difference.
Basically: The default density value for the Xoom is 160. I recommend using either 150, or 140 as your density value and nothing less. I think 150 seems to be right where most people would want their screen to be if they wanted to go just a bit higher def. It makes the resolution a little nicer without going too overboard. After you choose your density setting, don't forget to check the "Always Set on Boot" box. This makes it so much easier so that you will not have to worry about setting this up with every single time you boot. Then hit apply, reboot your Xoom, and then make sure that the settings stick. Done!
Apply one of the density settings I have listed with one of the Screen Filter settings also listed for a nice effect. It's almost as if you have a whole new tablet when you combine the two!
Currently: I am using the 140 density value on my Xoom, and I couldn't be happier!
Default Density Value 160:
Density Value 150:
Density Value 140:
If these tips have helped you out toss me a thanks. If I get more positive feedback I will be adding some more great helpful tips for us Xoomers. Thanks for stopping by!
Thank you for a great tip. My Xoom screen look better now. This is why I love to visit XDA everyday.
Will check with Acer A500.
im not really seeing a difference.
patass said:
im not really seeing a difference.
Click to expand...
Click to collapse
The difference is there. Try viewing from different angles instead of straight on and compare. I added my own screenshots of my Xoom just now and you should be able to see a nice difference from the before and after. This method really helps the side viewing angles a lot by reducing the white backlight that causes the screen to distort when not looking directly down on it. But it looks really great all around, not just from the side.
so what do i put the system brightness at? and what do I put the screen filter percentage at?
incrediblenotinstock said:
so what do i put the system brightness at? and what do I put the screen filter percentage at?
Click to expand...
Click to collapse
You can customize and set it to whatever you like. Me, for normal usage I like to use 50% for the system brightness and 85.1% for the Screen Filter brightness. I think it works quite well this way without being too dark or too bright. I use this setting on both my Xoom and my OG Droid.
I see what your saying, the viewing angle is alot better now, thanks OP
wow, makes a huge difference for me, thanks
How does it impact battery usage at the 50/85?
Brolloks said:
wow, makes a huge difference for me, thanks
How does it impact battery usage at the 50/85?
Click to expand...
Click to collapse
It really does not impact the battery life very much if at all. In fact it possibly might save a little bit of battery life if anything. I've been using this setup for months and it has been working great.
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
omnia1994 said:
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
Click to expand...
Click to collapse
Yep...real laggy. Uninstalled
omnia1994 said:
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
Click to expand...
Click to collapse
Hmm.. interesting. I use it all the time without any kind of problem. What launcher and browser are you using? And are you stock or rooted?
I'm using both Adw Launcher and Launcher Pro depending on my mood and they both work great with Screen Filter enabled.. no lag of any kind. And my browser of choice is always Dolphin HD and it also works without any lag. I'm on a rooted 3.1 Xoom with the latest tiamat kernel. Maybe I can help solve the problem?
i am curious why one would jack their screen brightness up to 85% in the first place, 33% gets a perfectly view able screen indoors. Not to mention the savings wrt battery life.
Kokanee483 said:
i am curious why one would jack their screen brightness up to 85% in the first place, 33% gets a perfectly view able screen indoors. Not to mention the savings wrt battery life.
Click to expand...
Click to collapse
The 85% is for filter not brightness.
Sent from my PC36100 using XDA App
omnia1994 said:
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
Click to expand...
Click to collapse
Yep, nice for off angles but for sure adds all types of lag. Bonse stock 3.1 no root. Factory launcher... isn't their a color control like what's available for the Nexus S? You would think with the screen wash out complaints someone would have come up with an answer by now.
Just tested another app. Really liked the effect on off angles so I'm searching the market for other stuff. There is another app called back light filter. It alowsyou to adjust the Alpha levels along with individual colors. Have to tinker to find the best fit but no home screen lag.
lstrike said:
Just tested another app. Really liked the effect on off angles so I'm searching the market for other stuff. There is another app called back light filter. It alowsyou to adjust the Alpha levels along with individual colors. Have to tinker to find the best fit but no home screen lag.
Click to expand...
Click to collapse
I've tested this app before and it's so so. Most users will want something easy to use without much tinkering or setup. It works pretty well through, but it could use some more features, it lacks a widget, and there is no notification bar icon for fast access. Good comment though. Maybe the people who are completly stock everything should give this a go since they are reporting lag issues.
I don't see any difference.
Sent from my Xoom using XDA Premium App
diablo2224 said:
I've tested this app before and it's so so. Most users will want something easy to use without much tinkering or setup. It works pretty well through, but it could use some more features, it lacks a widget, and there is no notification bar icon for fast access. Good comment though. Maybe the people who are completly stock everything should give this a go since they are reporting lag issues.
Click to expand...
Click to collapse
I agree with you on the simplicity of the app in the original post. If the developer can dial out the lag it is definately the best tool for screen filtering on the xoom. I just wish the OEMs would provide simple calibration tools for screens.
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Jade Eyed Wolf said:
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Click to expand...
Click to collapse
Thanks for the tip mate
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Great tip, although this really belongs in the "General" section.
Expect more from someone with almost a thousand posts...
sundazetoo said:
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
exactly
If you didn't create it... this belongs in general...
Sent from my GT-N7000 using xda premium
Jade Eyed Wolf said:
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Click to expand...
Click to collapse
So basically you keep the DPI @ 320 & change the above parameter to tablet?
Will this give me the tablet like two panes in settings, gmail & google play?
Screen shot please, and stop crying about this brlongs here ore there. Cry babys
daddymatt said:
If you didn't create it... this belongs in general...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Spot On
Thread Moved To General​
prgopala said:
So basically you keep the DPI @ 320 & change the above parameter to tablet?
Will this give me the tablet like two panes in settings, gmail & google play?
Click to expand...
Click to collapse
So basically ICS has 2 modes, tablet mode and phone mode. To my understanding this is dependent on the dpi, anything lower than 213 dpi will display ICS in tablet mode i.e. 2 panes on most apps. Apparently 160 dpi is the official tablet mode..and i think 320 dpi is the standard phone mode. I currently run mine in 200 dpi and most apps show 2 panes.. I am sure there is a better explanation somewhere
Sent from my GT-N7000 using XDA
sundazetoo said:
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
So far, I haven't had any issues with Imilka's build. Then again, the stock keyboard still looks funky in portrait tablet mode, but that's nothing new. Everything else works perfectly.
More than anything, this fixes things like tablet portrait Google Music recent's.
sundazetoo said:
So basically ICS has 2 modes, tablet mode and phone mode. To my understanding this is dependent on the dpi, anything lower than 213 dpi will display ICS in tablet mode i.e. 2 panes on most apps. Apparently 160 dpi is the official tablet mode..and i think 320 dpi is the standard phone mode. I currently run mine in 200 dpi and most apps show 2 panes.. I am sure there is a better explanation somewhere
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Absolutely... i don't think just changing the build characteristics parameter to 'tablet' will give you true tablet mode...I guess it will help in apps like music etc where the controls are screwed up in tablet mode...did you try it btw, i mean keeping the DPI below 213 & setting the characteristics to tablet and then check the music app for e.g.
Can sum1 tell me plz ...
what shud i edit in build.prop in order to run gameloft games ...
bcz for default setting it sayz
" your device not compatble blah blah and request for refund "
Using ICS STUNNER ROM
Can ne1 help me out wid dis thing or wts the workaround for this ???
So I've been trying out different LCD densities for a while now, but I always end up using the stock 240. Unfortunately this prevents me from using games I've already purchased, Osmos HD for instance. Now this can easily be solved with, lets just say, less than legal means. But that's a whole 'nother story.
So, what's your density?
ares93 said:
So I've been trying out different LCD densities for a while now, but I always end up using the stock 240. Unfortunately this prevents me from using games I've already purchased, Osmos HD for instance. Now this can easily be solved with, lets just say, less than legal means. But that's a whole 'nother story.
So, what's your density?
Click to expand...
Click to collapse
My density is less than legal
Seriously though I have never seen why people have wanted to change from the stock 240? Seems like the perfect density to me to be honest
Nigeldg said:
My density is less than legal
Seriously though I have never seen why people have wanted to change from the stock 240? Seems like the perfect density to me to be honest
Click to expand...
Click to collapse
Seriously? I find 240 to make everything ginormigous. I like and use 160, no problems with market either.
elesbb said:
Seriously? I find 240 to make everything ginormigous. I like and use 160, no problems with market either.
Click to expand...
Click to collapse
I get what you mean and I could happily live with a lower density, but I neither see the need to change the density nor can be bothered to actually do it, so meh
Nigeldg said:
I get what you mean and I could happily live with a lower density, but I neither see the need to change the density nor can be bothered to actually do it, so meh
Click to expand...
Click to collapse
Lazy bum! lol
+1 for 160, also 165 is good, but normal (240) feels gigantic
217 (stock HD2 dpi) looks best to me, but i use 240 because of market compatibility, it's pretty big but i got used to it.
160 is too small and ugly IMHO.
i prefer a dpi 192, the stock 240 is just too big and 160 too small.
but on the other side i have to deal with some market issues sometimes
hi! you can use 192 dpi with the hacked market ofcourse and everything goes smoothly (most of the time). i use 220-240 because i like it and helps me with my drawing-related apps.
i guess it depends on what suites you better. anyway, i would recommend 192 and more unless your eyes can magically magnify things...
normally i use 160 dpi for every gb rom.
but for ics's roms i use the standard 240 dpi.
in my mind it looks best and there are no complications
MungoHigh said:
normally i use 160 dpi for every gb rom.
but for ics's roms i use the standard 240 dpi.
in my mind it looks best and there are no complications
Click to expand...
Click to collapse
I understand you're trying to get 10 posts, and you're going about it in sort of the right way (in that you're actually helping people rather than spamming) but please stop bringing up old threads, especially when they're already solved.
Okay,i m sorry for this:s
Sent from my HTC HD2 using XDA
Hello. I have a net book with Intel atom inside with a small screen resolution. Windows 8 gives limitations to me because we need a certain minimum screen size for its apps to run. However my screen size is small so I can't run any apps. Also, I know that there is a hack to change screen resolution but that doesn't fit nicely on my screen and looks ugly. Is there a way to remove the screen resolution limitations?
Thank you
Install latest video drivers for Win 7 then search your registry for "Display1_DownScalingSupported" and change its value from 0 to 1
It 's listed more than once so make sure you change each listing.
I hope that helps!
-cp
I know. I was taking about that. Doing that makes my resolution a bit weird. Is there a way to remove the ability to let windows detect resolution so that we can use it without changing? Thanks for helping
Sent from my LT18i using xda premium
TheNegotiator012 said:
I know. I was taking about that. Doing that makes my resolution a bit weird. Is there a way to remove the ability to let windows detect resolution so that we can use it without changing? Thanks for helping
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
I had installed Win8 on an Aspire one and yes, those scaling options suck because their ratios do not match the screen. I didn't investigate heavily because I also have a SS7S but Macs have a program that lets you use custom resolutions, does Windows have this? Then you could at least get the ratio correct.
dragon_76 said:
I had installed Win8 on an Aspire one and yes, those scaling options suck because their ratios do not match the screen. I didn't investigate heavily because I also have a SS7S but Macs have a program that lets you use custom resolutions, does Windows have this? Then you could at least get the ratio correct.
Click to expand...
Click to collapse
No they don't
Sent from my Arc S using xda premium
I want to know how to override resolution error too. I have asus 1015PN.
I got tired of messing around with DPI/Resolution combinations by typing the adb commands every time. So I wrote a nice little batch file that should work for any phone running 4.3 or greater. It doesn't require installation of the android SDK or even ADB - all files necessary are contained in the 7z file. Just run the file and follow the prompts - everything is taken care of for you, including finding the default values for your device in case you mess things up. The program also fetches your current DPI and resolution so you don't have to go digging for it in build.prop or dumpsys to see where you are presently.
Download here goo.gl/YTsHQp
I used to run unrooted on my Verizon GN4 N910V. A resolution at 1080x1920 with 360 DPI forces *some* apps to run in tablet mode, and gives a very large increase in screen real estate. I can live with the small dialer problems (can't be fixed without rooting/xposed as far as I know) and change my launcher, in exchange for a cooler running phone (average 7 degrees cooler under benchmark load) that uses slightly less power (average +27 minutes per charge according to Gsam), scores an increase of 16% in AnTuTu (52077 at 1080p and 45085 at 1440p), and has WAY more screen real estate. I don't notice the difference in resolution at all, even if I'm trying to.
Note that turning animation scale to a value greater than zero may be required for running some launchers nicely while screen scaling is turned on.
The included HOWTO file gives instructions and outlines some acceptable whole number 9:16 ratios and DPI settings for stock DPI ratios - and outlines how to calculate the numbers yourself. Open source on the code, modify, redistribute, etc - just give attribution to zediiiii.
I'm not sure i understand how this improves performance when you are scaling down the objects on the screen.
How can I change the DPI/Resolution per application?
locolbd said:
How can I change the DPI/Resolution per application?
Click to expand...
Click to collapse
You can't without root.
This program works well. I have noticed some issues when running at 1080p using the DPI provided in the readme. Certain things (boots screen, movies in games) won't play because, I'm assuming, it is relying on the build.prop but the resolution defined in that file is not accurate. It's a minor inconvenience in light of the fact that running at 1080p and with a heavy deploy it getting me nearly 7 hours sot on lollipop.
Nice job @zediiiii.
I tried it on a Galaxy S4 with KitKat and a Galaxy Note 4 with Lolipop. On both devices I just tried to lower the resolution while keeping the stock DPI to resolution ratio, the goal being to save some battery. On the GS4 it definitely reduced heat while playing games and increased the Antutu score. Unfortunately it also broke the stock keyboard and camera. I didn't see any problems with 3rd party apps. On the Note 4 I didn't test as much, but the stock keyboard was also broken.
Piercing Heavens said:
I'm not sure i understand how this improves performance when you are scaling down the objects on the screen.
Click to expand...
Click to collapse
My understanding is that driving less pixels per square inch (PPI - I incorrectly used DPI in my program...) means less bandwidth through the graphics processor and thus more headroom. So you either slightly increase performance or slightly save on power - depending on how you use your phone.
I use it for the slight power save, because I can't tell the difference between 500 PPI and 300 PPI, and so I can trick apps into thinking I'm using a tablet on my GN4.
spocko said:
Nice job @zediiiii.
I tried it on a Galaxy S4 with KitKat and a Galaxy Note 4 with Lolipop. On both devices I just tried to lower the resolution while keeping the stock DPI to resolution ratio, the goal being to save some battery. On the GS4 it definitely reduced heat while playing games and increased the Antutu score. Unfortunately it also broke the stock keyboard and camera. I didn't see any problems with 3rd party apps. On the Note 4 I didn't test as much, but the stock keyboard was also broken.
Click to expand...
Click to collapse
When you say broke the stock keyboard, you mean that it's scaled incorrectly and far too big on your screen? How did the other stock apps fair? In my experience, if you stick with the correct resolution to PPI (DPI is the wrong acronym; I was kindly corrected by a fellow programmer) ratio, the stock apps continue to work as expected. Stock apps crash for me when the ratio is lower than it was before, and simply get smaller on the screen when the ratio is higher than before. If stock apps are crashing, you could try incrementally raising or lowering your DPI and checking for results. I made the program so that this was easy to do incrementally for this very reason.
zediiiii said:
When you say broke the stock keyboard, you mean that it's scaled incorrectly and far too big on your screen?
Click to expand...
Click to collapse
Yes, exactly, sorry I wasn't more clear. On the GS4 i tried multiple resolution and DPI combos, always keeping the stock ratio. The stock keyboard didn't scale properly with anything other than the default settings. On the Note 4 I only tested with 1080x1920 and 480 dpi, and saw the same scaling issue with the stock keyboard. This is not the fault of the script, so it's not a complaint. It's just a note to warn others that if you want to tweak these settings on a Samsung phone, then you may need to use a 3rd party keyboard.
On the GS4, some of the control buttons were missing in the stock camera app, but the Note 4 didn't have that issue. I didn't see any crashing on either device, perhaps because I was always keeping the stock ratio.
Thanks for the good information. My guess is that anything touched by Samsung, eg, the dialer, the home screen, the camera etc will not scale correctly and may be buggy even with the sam PPI:RES ratio. Oh how I miss Xposed (which I think @locolbd knows is the best way to change ppi per app if you have root, among other things)... Not hopeful for a real root solution for VZW GN4 at this point.
not sure if i'm going blind where where is the script located or was it taken out?
Mikeng714 said:
not sure if i'm going blind where where is the script located or was it taken out?
Click to expand...
Click to collapse
It's at the bottom of the first post, but it's not formatted as a link.
Here:
http://goo.gl/YTsHQp
Mikeng714 said:
not sure if i'm going blind where where is the script located or was it taken out?
Click to expand...
Click to collapse
goo.gl/YTsHQp
Some people have troubles running the first line of the code in the bat file
Code:
adb devices -l | find "device product"
If so, you can change it to
Code:
REM adb devices -l | find "device product"
I haven't really figured out why this is the case yet. Mine worked until recently. If anyone has some insight I would be grateful. Windows powershell change perhaps?
my swiftkey keyboard became huge after doing this.. Any fix for it?
Thank you for this!
Worked great on my Galaxy S7 edge!
whoa..this really worked..note 5..thx to everyone:good:
Mikeng714 said:
not sure if i'm going blind where where is the script located or was it taken out?
Click to expand...
Click to collapse
goo.gl/YTsHQp (in the really long OP)
Because I mentioned my lack of hope for root on the N910V earlier - if anyone hasn't noticed, there is a great guide for permanent root (start here, it links everything for 6.0.1 upgrade) on the N910V Verizon Galaxy Note 4. I'm running 6.0.1 on Jasmine Rom 7 with all the rooted trimmings and no serious issues to date.