Just now i installed LCD density changer and i have set it to 190.
Is the 190 setting safe and the main thing , is this software safe and future proof that it wont effect my hardware in future.
Thanks.
I'm quite sure you have nothing to be worried about.
Sent from my T-Mobile G2 using XDA App
you have to worry about your eyes though
190 is to much for me, but loving 220
LCD Density works on software level, not hardware level. The hardware display frame buffer is still 480x854, but when you change the lcd density, the software frame buffer is resized accordingly.
If you decrease the LCD density properties (dunno why increasing the value make things bigger), the SW frame buffer resolution will be increased in width and height, then after the OS finished with the rendering of SW frame buffer, this frame buffer will be resized to match the HW frame buffer, then the content will be copied.
So its safe, but increasing too much will make the phone slower because of bigger SW frame buffer, but of course you can see more text because the text is smaller.
Anyone care to post screenshots with 220 density?
Everything looks OK?
hi guys..
i have seen a few posts on the SGS side of things about resizing the dialer / camera etc... correctly when the LCD denisty is changed to a lower than standard figure..
is there a way of these apps "ignoring" the LCD density values set in the build.prop files?
just thinking.....
ta
nutmegy said:
hi guys..
i have seen a few posts on the SGS side of things about resizing the dialer / camera etc... correctly when the LCD denisty is changed to a lower than standard figure..
is there a way of these apps "ignoring" the LCD density values set in the build.prop files?
just thinking.....
ta
Click to expand...
Click to collapse
This ROM has a modified camera app for 200 dpi: http://forum.xda-developers.com/showthread.php?t=1149713
Just extract it from SkyROM and replace yours via adb or root explorer...
please help me i changed my s2 density to 200 now its not booting please super please help.
Indirect deserves a salute for rooting the NT
http://forum.xda-developers.com/showthread.php?t=1354487
Still running a Nook Color with a dpi of 240 in build.prop, I would very much
get any reports on the following
1. Can the same be done on the NT without too many side affects?
2. Has anyone installed skype and tested the built in Mic?
How about a response as to a rooted Nook Tablet with a higher (240) dpi setting?
speaking completely out of curiosity, how can you display a higher dpi onscreen (if I'm understanding what you're asking), if the display is only capable of 169 dpi?
maybe I'm oversimplifying the question and am not understanding you.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
after doing some searching, are you referring to actual font size?
Android allows different dp settings independent of the hardware dpi for UI design. Details in below link,
http://developer.android.com/guide/practices/screens_support.html
Density-independent pixel (dp)
A virtual pixel unit that you should use when defining UI layout, to express layout dimensions or position in a density-independent way.
The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, which is the baseline density assumed by the system for a "medium" density screen. At runtime, the system transparently handles any scaling of the dp units, as necessary, based on the actual density of the screen in use. The conversion of dp units to screen pixels is simple: px = dp * (dpi / 160). For example, on a 240 dpi screen, 1 dp equals 1.5 physical pixels. You should always use dp units when defining your application's UI, to ensure proper display of your UI on screens with different densities.
e.mote said:
Android allows different dp settings independent of the hardware dpi for UI design. Details in below link,
The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, which is the baseline density assumed by the system for a "medium" density screen. At runtime, the system transparently handles any scaling of the dp units, as necessary, based on the actual density of the screen in use.
Click to expand...
Click to collapse
I understand the advantage to a developer laying out UI that needs to run on different display resolutions, but I don't see an advantage for an end-user. Why would you set your dpi to 240 if you can only display 169 dpi on the device? Won't the tablet simply downsize bit-mapped images when they're actually displayed?
Honest question--I'm probably not understanding something here--and I'm certainly not trying to rile anyone. Thanks!
Per above equation, setting your device's dpi setting to 240 would allow the app to be 150% in size. This aids in legibility, at cost of more screen space.
If you have an NC, you can see this firsthand by adjusting abovesaid dpi setting in build.prop up or down.
e.mote said:
Per above equation, setting your device's dpi setting to 240 would allow the app to be 150% in size. This aids in legibility, at cost of more screen space.
Click to expand...
Click to collapse
Ah, cool. Thanks for the info!
All I wanted to know was if the build.prop can be edited on a rooted NT as I have done on the NC.
Also, I will try once more. Did anyone use the Microphone with skype or some other chat app?
if I manually set dpi value to less than 289, the phone UI will switch to tablet mode.
is there any way to prevent this and run a lower dpi, say 200-250?
Stock is 480 and smallest is 330 for reference.
Hi all,
I updated dpi via ADB but it generates a side effect.
Screen size and resolution decrease instead of increase.
I reset the default values but adter that the splash screen resolution decreased (big pictures) and initial resolution (in my opinion) is not the same.
Can yiu share orifinal dpi values and original build.prop file? ( or file with resolution and dpi info).
Regards
Francesco