[Q] Change LCD Density?

---

So i searched and found many posts saying to edit system/build.prop at the line
ro.sf.lcd_density=160
the point is, I do not have this line.
also lcd density changer did not appear to do anything when changing the value.

any clues chaps?

i'm on stock froyo build 318

Originally Posted by crashDebug

So i searched and found many posts saying to edit system/build.prop at the line
ro.sf.lcd_density=160
the point is, I do not have this line.
also lcd density changer did not appear to do anything when changing the value.

any clues chaps?

i'm on stock froyo build 318

It's not in the stock build.prop. You must insert that line somewhere using the text editor in root explorer and change 160 to another number. The number must be in intervals of 20. Like 180, 200, 220 etc... Then restart your device and you're golden!

thank you very much mate I sort of imagined it myself but you know n00b to android etc, better safe than sorry

Originally Posted by crashDebug

thank you very much mate I sort of imagined it myself but you know n00b to android etc, better safe than sorry

No problem! I like mine at 200 on the 318 build. Unfortunately on steve's builds 180 is the highest you can go without having the settings turn black when you hit the menu key. But anything is better than 160. Way too small at that setting.

well, i'm not saying that I regret 160, but I find 180 quite disappointing. too many words cut in icons and widgets etc. I reckon 170 would be optimal, that is, if it was a valid value ofc
ah, the perennial struggle for perfection....

looking for the same answer will 170 work ???

Steve's 1.7.0 has fixed the issue with LCD density of 200 and above. The menu works like it should. I can confirm this as I am running density=200.

I've been using a free program called "Incoming Call Plus" and it replaces the stock incoming call screen. This is good for LCD density of 180 and above, since you don't have the caller's name cut off.

Unfortunately, for me it's not fixed
I've tried 200 and 240 and same issue...

With 1.8 issue is now solved for me