requesting to show me martin dpi changer
download it from play storeTexdroider DPI
try this
Dude, Best and easy way to change DPI is adding 'ro.sf.lcd_density=<Value>' to the end of build.prop file in /system.
Where, <Value> is your DPI! (I use 188)
If there is a # symbol at the end of build.prop, remove it.
Related
Is there a way to change/increase resolution of tablet running the vegan 5.1?
I love the high resolution which comes with the gingerbread build?
Sent from my PC36100 using XDA App
Try LCD densitychanger from the market. Its free and doesnt survive a reboot, There is a paid version that will make it permanent. You can do a search of this forum and the instructions for changing it permanently manually are around.
rob_z11 said:
Is there a way to change/increase resolution of tablet running the vegan 5.1?
I love the high resolution which comes with the gingerbread build?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
bittrix said:
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
Click to expand...
Click to collapse
Thank you both for your help, and I think 120 is too small, and 140 did the trick for me which is the nice combination of the workspace and not too much strain on eyes.
I am sorry to report you Bittrix, but down in Florida temperature is gong to hit 60 and may be 68 tomorrow, so enjoy the cold weather in Canadian rockies
I use 120 for my tablet on all roms. I used 140 for awhile when starting to use lcd density, but eventually went to 120 because of app issues. 120 and 160 seem to nativly supported in android, and numbers in between its hit or miss as to whether they would work or not, even with compatibility turned on. (Some would only take up 3/4 of the screen instead of full or not open at all)
My build.prop does not have a line ro.sf.lcd_density=xxx and am running the latest Vegan build...
Any ideas?
EDIT: Added the line and no issues - just dont like it that small.. reverted back. Thanks
bittrix said:
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
Click to expand...
Click to collapse
Moved to general
Thought I'd share a 'fix' for your TouchPads if you don't want to be tied to 120 or 160 dpi (which btw look good but still..).
Now we all now the edit build.prop or dpi change apps but this one is pretty neat.
It allows you to manually set your desired DPI (f.e. 132 as the TP should be) but also comes with a solution for 'breaking' your market. The app will Fix your Market compatibility issues by modding your Market.apk into thinking you are using the market at f.e. 120 DPI. You can do this for any DPI change
Guide:
1) Install LCD Density Modder Pro here (official Android Market link)
2) Open app (only for root users but if you are running Android on your TP...)
3) set your DPI
4) Save as System DPI (perma + reboot) or
4a) Temp Apply (fast reboot and is merely there to see if your chosen DPI looks good)
5) after reboot hit "Fix Market compatibility issues"
6) Download modded Market.apk for the PDI you want the market to think you have (either 120 or 160 DPI, depends which file you installed from CM9)
7) Install Mod
8) Asks you to reboot so that the 'new' Market.apk works
9) voilá!
(note: instructions will also appear when opening app)
I hope this isn't considered something 'not done' on this forum as I am merely linking to an official apk on the market and points TP users in the right direction.
Good luck!
ps: credits go to anthonyjcasagrande aka theb1rdm4n for developing
halo
i don't see so well and the Resolution in the one s is to high to me
i raise the DPI Through rom toolbox to 260
but i get some error of the system ui "Unfortunately system UI has stopped"
for example when i enter to "recent up" i got this erorr and i can't enter there....
there is a way to fix it ??
thanks
If I'm not totally wrong raising the resolution will result in smaller letters. You should lower it instead. So please try it.
And you can change letter size within settings -> display & gestures -> font size. By default it is medium, so you can change to large or extra large.
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!
rootrider said:
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!
Click to expand...
Click to collapse
I just checked that out.
What's with the notification about it "collecting" info? Collecting it where? And what? I didn't go any futher.....
Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.
Haven't tried it on this phone, but at least on every sense Rom I've used for the hero changing LCD density has always messed up everything. One of the reasons I allways used aosp
Sent from my HTC One S using XDA
usrbrv8 said:
Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.
Click to expand...
Click to collapse
as i said i did it with romtoolbox. it is the same , i raise the dpi to 260....
it makes some problems with system ui and i got some errors
i now replace the rom to miui and the dpi change doesn't Affects the system ui
dpi change can be on a rom without htc sense ui and i think even regular ice !
but..... now there is some problem with the market because Resolution Compatibility i think... there is some app i can't download .....
for now i need to come back to 240 dpi for download some apps and its Annoying
maybe if could change the Resolution to Exactly 800\480 i wouldn't get the market-app-Compatibility issue but i dont know how... maybe someone know how to do it?
my vision isn't so bad and i know the regular options aka font enlarger Etc ...
dpi change is the best choice for me .
I'm confusing myself I think. I have my DPI set at 133 and now I'm having incompatibility issues with the market. I know this isn't a new problem and I know its been discussed before. But info is scattered and nothing I set DPI at fixes the issue. I've tried 160 and a million others but no success. The thing is my DPI was always set at 133 and I have downloaded apps that now say are incompatible. Can anyone help me straighten this out?
Change the dpi back to 160 with :
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en
Open up Rom tool box lite , select :
Performance >build.prop.tweaks>LCD density> set to 160.
APPLY and reboot.
Yeah see. This is why I'm confused. I have that app and that's how I've been changing the DPI. It will change the DPI but won't fix market incompatibility.
Edit: This is going to get annoying really quick lol. I got the apps I needed to download by changing DPI to 320. Now set back to 133 and all is good. Sort of.
Are there any TW roms that work well with LCD density set at 240? Specially the dialer. Thanks
You can try Galaxy Mod, http://forum.xda-developers.com/showthread.php?t=1953008
--------------------------------------
Multi-DPI support
--------------------------------------
This ROM has been modified to support different DPI settings, however don't expect it to be at the level of Paranoid Android. I still have yet to figure out per-app DPI, but as of right now you should not get any force closes or unexpected behavior when changing the DPI. There may be graphical glitches. Be careful, in my testing the phone would NOT boot with a DPI lower than 165. To be safe, I would suggest using a DPI of 180-220 if you plan on changing it. Make sure you do not set the DPI above the max which is 320. Doing so would result in a non-booting device.
To change the DPI open the build.prop using an app like Build.prop Editor and edit the following:
Code:
ro.sf.lcd_density=320
Change "320" to whatever value you want, but be careful. Reboot the device when you have made the changes.
Do not post a bug report if you changed the DPI. Some apps may not work with well with a DPI lower than 320.
Click to expand...
Click to collapse