[Q] Why do information apps report the DPI as 160dpi? - TouchPad General

I changed my DPI to 132 dpi in the build.prop file and rebooted. If I run an information app like SystemPanel or Android System Info, they report the DPI as 160dpi. Which one is the real DPI of the tablet? Why do they report this density? If 132dpi is the true density, then why do the fonts look odd in menus and a lot of apps?
Sent from my Touchpad using Tapatalk

mjsztainbok said:
I changed my DPI to 132 dpi in the build.prop file and rebooted. If I run an information app like SystemPanel or Android System Info, they report the DPI as 160dpi. Which one is the real DPI of the tablet? Why do they report this density? If 132dpi is the true density, then why do the fonts look odd in menus and a lot of apps?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
afaik, android only recognizes like 4 dpi's: LDPI, MDPI (160), HDPI, something elsedpi. So, as far as the app knows, your running MDPI, but changing you value will still result in visual changes. I'm not 100% sure if this is accurate, but i think it is, lol
it works this way because there is so many densities and so many screen sizes in android.

Related

LCD Density?

With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador

DPI changing in JB

Heyo,
I was wondering if there are other people here that can't change the dpi after they moved to JB.
I've tried altring the build.prop file which gave me a soft brick after I rebooted the phone and got the same result with "DPI Changer" and "LCD Density Modder" apps with other people leaving bad reviews on the play store for these apps because apparently they got the same results as I had.
So what's going on with JB and DPI changing?
tal123 said:
Heyo,
I was wondering if there are other people here that can't change the dpi after they moved to JB.
I've tried altring the build.prop file which gave me a soft brick after I rebooted the phone and got the same result with "DPI Changer" and "LCD Density Modder" apps with other people leaving bad reviews on the play store for these apps because apparently they got the same results as I had.
So what's going on with JB and DPI changing?
Click to expand...
Click to collapse
I just edited the build.prop and restart, all OK then.
Which value dpi are you trying to set?
Sent from my GT-I9100 using xda app-developers app
i changed mine in build.prop to 220 and had no problems except market incompatibility, but a modded vending apk fixed that

LG G2 is more awesome with 320dpi

LG G2 is More Awesome with ̶3̶2̶0̶d̶p̶i̶ 380dpi
I came from galaxy note 2 before had G2
On that forum, people love 240dpi
Because the original 320dpi is too big and bulky
Not as crisp as 240dpi
After I got my G2
I realize, the current dpi is too big
And I edit build.prop and change to 320dpi
And modified home to works with 320dpi
You got to try it
It's really awesome G2 with 320dpi/380dpi/400dpi
I wish some skillfull dev will port original apps from 480 to 380dpi
In the mean time.... i just had to learn trial and error changing dimens
To make it looks good on 380
===========380dpi===========
@sosimple point me, he use 380 dpi, after I tried it, It's my favorite DPI now..
===========================
- - - How To Change DPI Manually - - -
===========================
1. You must be rooted (need root explorer/build.prop editor) + Xposed Module (App Settings)
2. search ro.sf.lcd_density=480
3. change it into ro.sf.lcd_density=380
4. reboot
drc13 said:
People might find experimenting with different DPI's easier with an app like texdroider rather than manually editing the build prop.
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
Click to expand...
Click to collapse
of course, many apps on playstore can change density
just search playstore
*some LG apps doesn't works properly with new DPI
*even playstore is acting weird
--------- the fix ---------
1. For LG Camera App and LG Message App
http://forum.xda-developers.com/showthread.php?p=48743938#post48743938
Install Xposed Frameworks - Open the apps - go to download menu
1. Install App Settings Module (for LG apps)
2. Install All apps in Play Store (for Playstore Fix)
3. reboot
4. open App Settings, Search Camera - click - On - DPI = 480
5. open All Apps in Play Store Module - change fake dpi to 480
I use between 390-400 I also use tiny text in the display settings so everything fits much nicer. I haven't tried 320 but I imagine that would be a bit too small for me.
320 r u serious? im using 400 and already feel thats little bit too small
Im using my tablet port for G2 and it hurts my hand using it. Woudnt advise to use at 300 or lower
480
Build prop set to 480, xposed app settings changes everything else that's compatible to 320.
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
spiderio said:
I came from galaxy note 2 before had G2
On that forum, people love 240dpi
Because the original 320dpi is too big and bulky
Not as crisp as 240dpi
After I got my G2
I realize, the current dpi is too big
And I edit build.prop and change to 320dpi
And modified home to works with 320dpi
You got to try it
It's really awesome G2 with 320dpi
I wish some skillfull dev will port original apps from 480 to 320dpi
In the mean time.... i just had to learn trial and error changing dimens
To make it looks good on 320
Click to expand...
Click to collapse
Unless you're running a ASOP ROM, stock LG apps dont scale right under a different density. It sucks. I agree though everything looks better at 320.
phatmanxxl said:
Build prop set to 480, xposed app settings changes everything else that's compatible to 320.
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Unless you're running a ASOP ROM, stock LG apps dont scale right under a different density. It sucks. I agree though everything looks better at 320.
Click to expand...
Click to collapse
I am using 380 dpi. If you use xposed app settings , you can define stock lg apps to run in default dpi (480) so you have no problem at all..
sosimple said:
I am using 380 dpi. If you use xposed app settings , you can define stock lg apps to run in default dpi (480) so you have no problem at all..
Click to expand...
Click to collapse
Yea, I felt it was just easier to adjust the apps that looked better at 320 instead of the whole phone.
sosimple said:
I am using 380 dpi. If you use xposed app settings , you can define stock lg apps to run in default dpi (480) so you have no problem at all..
Click to expand...
Click to collapse
After I tried 380 and it's indeed better than 320..
It's not too small and still crisp great looking now..
anyone know how to edit lghome.apk dimens for 380..
I use app settings for LG camera.. set it 480
For home.apk is better hardcodded than using appsetting.
I am still searching how to make the quickwindow apps in 480 dpi, I haven't found for now.
Yup 320 DPI looks just like my note was on 240 DPI :laugh:
How come this all seems backwards to me...comparing to a PC LCD monitor? I thought that more dot per inch was better...made things smaller...and yet I keep reading that fewer DPI's are the way to go?? What am I missing here?
Dedided to try 320 (from 380 which i had).. A bit small but i think i can use it..
Sent from my LG-D802 using XDA Premium 4 mobile app
jaseman said:
How come this all seems backwards to me...comparing to a PC LCD monitor? I thought that more dot per inch was better...made things smaller...and yet I keep reading that fewer DPI's are the way to go?? What am I missing here?
Click to expand...
Click to collapse
Maybe you should read this
http://stefan222devel.blogspot.com/2012/10/android-screen-densities-sizes.html?m=1
i have mine set at 380 dpi. looks great! thanks!
Im still on the stock rom but rooted and using xposed framework w g2 xposed and greenify. I changed dpi under android system but once rebooted i kept getting a bootloop and had to boot into recovery and flash the xposed disabler. Was the android system the correct tab to change or which ones are you guys using?
I also have build prop tweaker from the PS. Under ro.sf.lcd_density_secondary it states 480. If u change that will that take effect?
Sent from my LG-D800 using Tapatalk 2
jeff5347 said:
Im still on the stock rom but rooted and using xposed framework w g2 xposed and greenify. I changed dpi under android system but once rebooted i kept getting a bootloop and had to boot into recovery and flash the xposed disabler. Was the android system the correct tab to change or which ones are you guys using?
I also have build prop tweaker from the PS. Under ro.sf.lcd_density_secondary it states 480. If u change that will that take effect?
Sent from my LG-D800 using Tapatalk 2
Click to expand...
Click to collapse
idk, i just changed ro.sf.lcd_density from 480 to 380 and rebooted (using buildprop editor)
ethanhunt123 said:
idk, i just changed ro.sf.lcd_density from 480 to 380 and rebooted (using buildprop editor)
Click to expand...
Click to collapse
That did it
Sent from my LG-D800 using Tapatalk 2
400 seems about right to me. But I don't like to worry about having really precise selections.
updated thread with how to change dpi for noobs :good:

Tablet UI DPI ?

I would like to try tablet ui in all the apps and system,so please suggest suitable DPI.
about 280 to 290
If you are rooted I would use xposed an app settings and just do pre app changes as some apps dont play well with the changes
blueether said:
about 280 to 290
If you are rooted I would use xposed an app settings and just do pre app changes as some apps dont play well with the changes
Click to expand...
Click to collapse
Thanks. Ya am using xposed. I have installed Phab7 module which makes status bar at bottom like tablet. Also using app setting modules for chrome, youtube etc.
Wanted to try changing DPI and see how it goes , well will give 280 dpi a try and if I feel comfortable then its good otherwise will stick to current Phab 7 and app settings modules.
One question.
If I change DPi of system UI to 280 in app settings modules will it give tablet like bottom status bar as in Phab7 module?
- DPI 290 and lower = Tablet statusbar (split)
- DPI 320 (and lower) and 800x1200 DP (in App Settings) tablet mode for apps
There is 4 dpi densities. 160, 240, 320 and 400. 160 and 240 are full tabled UI. 320 and 400 are phone UI. On 280 you got some kind of Phablet UI where some apps look like a phone UI (Play store) and some app like tablet UI (Chrome).
I have set dpi density to 240 on my ZU and it is just about to be to small but to me it is still okay. If you like you can enlarge font a bit. (Settings/display/font size) I just like tablet UI so much.
UI, UI, UI how many times I sad that? UI, UI....
simunovic said:
There is 4 dpi densities. 160, 240, 320 and 400. 160 and 240 are full tabled UI. 320 and 400 are phone UI. On 280 you got some kind of Phablet UI where some apps look like a phone UI (Play store) and some app like tablet UI (Chrome).
I have set dpi density to 240 on my ZU and it is just about to be to small but to me it is still okay. If you like you can enlarge font a bit. (Settings/display/font size) I just like tablet UI so much.
UI, UI, UI how many times I sad that? UI, UI....
Click to expand...
Click to collapse
That depends on how you're doing it. There are, like you say, only four official DPIs (160, 240, 320 and 400) but you can kick it into tablet mode way before 240 if you also adjust the DP. You can't do that by editing the build.prop, so we have to use a module like App Settings to set the DP to 800x1200, and then you'll get tablet mode at a higher DPI (without the split statusbar of course, since that required the DPI to be under 290). Yes, i've tried tablet mode at 400 DPI. A million cries could be heard across the universe when i hit "Apply". It's that bad.
320 DPI and 800x1200 DP looks right since the stock DPI for the Ultra (except for the GPe version) is 320, so all UI elements are properly fit. Anything under 320 is too small for me (personally) since i want to actually hit stuff with my finger when i'm standing on my legs, but that's just me though and people can set it to 20 DPI if they want too.
LordManhattan said:
That depends on how you're doing it. There are, like you say, only four official DPIs (160, 240, 320 and 400) but you can kick it into tablet mode way before 240 if you also adjust the DP. You can't do that by editing the build.prop, so we have to use a module like App Settings to set the DP to 800x1200, and then you'll get tablet mode at a higher DPI (without the split statusbar of course, since that required the DPI to be under 290). Yes, i've tried tablet mode at 400 DPI. A million cries could be heard across the universe when i hit "Apply". It's that bad.
320 DPI and 800x1200 DP looks right since the stock DPI for the Ultra (except for the GPe version) is 320, so all UI elements are properly fit. Anything under 320 is too small for me (personally) since i want to actually hit stuff with my finger when i'm standing on my legs, but that's just me though and people can set it to 20 DPI if they want too.
Click to expand...
Click to collapse
Yes i know about DP. I use to have Xposed with module for that. But then you have to set apps manually. That is way to much work for me and then I can not use ART cache and whole phone is a bit slower and battery is affected too. That is the reason I just simply put in DPI density to 240 in build.prop and forget about it. 6.44" screen is big enough for that. Anyway to me it is but like you sad it is just personal opinion.
simunovic said:
Yes i know about DP. I use to have Xposed with module for that. But then you have to set apps manually. That is way to much work for me and then I can not use ART cache and whole phone is a bit slower and battery is affected too. That is the reason I just simply put in DPI density to 240 in build.prop and forget about it. 6.44" screen is big enough for that. Anyway to me it is but like you sad it is just personal opinion.
Click to expand...
Click to collapse
True, it's a lot more work with App Settings, but if you don't want a "One size fits all" it's the only thing to do. There are also a lot of apps that i don't want in tablet mode, so the build.prop way of doing it isn't my style anymore. But like we've both mentioned already, it's all about personal preferences.
Thanks guys for all the responses.
Will give changing DPI to 240 in build.prop a try as I am already using app settings module.
@simunovic
So at 240 dpi status bar will be at bottom too? as I am more comfortable with bottom status bar.
@LordManhattan
Also if I change system UI using app settings module to 290 will it give tablet statusbar (split) as you mentioned.Or do I need to change something else too in app settings?
techpal said:
Thanks guys for all the responses.
Will give changing DPI to 240 in build.prop a try as I am already using app settings module.
@simunovic
So at 240 dpi status bar will be at bottom too? as I am more comfortable with bottom status bar.
@LordManhattan
Also if I change system UI using app settings module to 290 will it give tablet statusbar (split) as you mentioned.Or do I need to change something else too in app settings?
Click to expand...
Click to collapse
I don't think you can move status bar to the bottom anymore. Tablet UI dues not have that in 4.4.2 KitKat anymore. I am not sure about App setting module but regular way (build.prop editing) I don't believe is possible. You can try Paranoid Android ROM if you like. There is all of that and more. Personally I like that "old way" Tablet UI. To bad they changed that.
simunovic said:
I don't think you can move status bar to the bottom anymore. Tablet UI dues not have that in 4.4.2 KitKat anymore. I am not sure about App setting module but regular way (build.prop editing) I don't believe is possible. You can try Paranoid Android ROM if you like. There is all of that and more. Personally I like that "old way" Tablet UI. To bad they changed that.
Click to expand...
Click to collapse
I am using stock 4.3 rooted so its possible on having status bar at bottom. Currently I am using Phab 7 xposed module and I have status bar at bottom.
Ya for kitkat it wont be possible.
Tried 240 DPI via build.prop and really love it. Really makes best use of big ultra screen. Has two status bar notifications one in phablet mode and other phone mode. Overall pretty impressed with it,going to stick with it. Also changed status bar to bottom by Phab7 so in end got what i aimed for
simunovic said:
I don't think you can move status bar to the bottom anymore. Tablet UI dues not have that in 4.4.2 KitKat anymore. I am not sure about App setting module but regular way (build.prop editing) I don't believe is possible. You can try Paranoid Android ROM if you like. There is all of that and more. Personally I like that "old way" Tablet UI. To bad they changed that.
Click to expand...
Click to collapse
Paranoid Android is only in Beta for Android OS 4.4.x at the moment, they don't include hybrid settings until it leaves Beta. Even so, they are saying that the combined bar as we knew it is gone.
ETA: The only thing that I don't like about the combined bar is that it is hidden on the lockscreen, meaning no quick access to notifications.

build.prop DPI change?

Just curious has anyone with root successfully changed the DPI? Or maybe even with the text_droider app? Without a custom recovery I'm leary to try.
bamfsig45 said:
Just curious has anyone with root successfully changed the DPI? Or maybe even with the text_droider app? Without a custom recovery I'm leary to try.
Click to expand...
Click to collapse
Hello,
i chanced the DPI /Density with the Build.prop bzw there is one little problem. The camera and dailer app does not support a other DPI the laylout is a littlebit strange.
i changed from 640 to 480 and it looks good.
i found 2 entrys in the build.prop and chanced booth.
Dr4g0n said:
Hello,
i chanced the DPI /Density with the Build.prop bzw there is one little problem. The camera and dailer app does not support a other DPI the laylout is a littlebit strange.
i changed from 640 to 480 and it looks good.
i found 2 entrys in the build.prop and chanced booth.
Click to expand...
Click to collapse
Thanks for the information. I'll give it a shot.
external apps
Have you tried google camera and external dialers instead?
I'm using 384 and switched to Open Camera. Dialer is wonky but still usable.
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
Please don't use double post. My peace of advice : write your post in this thread : Good bye DPI changing?
You'll find some important informations

Categories

Resources