Related
Can someone please help me with this? i'm trying for the life of me to get these android builds to stop looking so blurry. i've searched the threads about lcd density and i've seen "128", "120", "113" and so on.
you know when android linux is booting up (black background and penguin) and all those words are scrolling? what would be the lcd density of that? how do i get the vogue to look like that? thanks.
what resolution kernal are you using?
try using the next one down
Since the Vogue screen was never meant to "officially" run android 120 is probably about as good a compromise as your going to get. That's what most users are set to.
On Kaiser I find the best combination to be 320x428 resolution, and a density of 144, this should also be a good combination for Vogue
anything under 155 or above 163 @ 320x428 doesnt look right. for vogue, if running 240x320 then use lcd 110-120 and see which one you like best. and for 320x428 & 320x480 use lcd 160, anything else just doesnt look right.
Has anyone had success with the LDC Density app? My friend used it on his galaxy s it was pretty cool
I tried it and my phone just froze. Had to do a battery pull to fix it.
Yes, im rooted.
this has been answered multiple times in a few thread.
maybe if you tried searching you'd have an answer.
Froze on my rooted TB with Adrynalyne's Rom. Curious to see if anyone has this working.
Didn't work for me either. Just manually edited /system/build.prop to change it around. Messes with the look of the Sense Clock Widget, and certain skins for the SenseUI.
Chris Hansen said:
Didn't work for me either. Just manually edited /system/build.prop to change it around. Messes with the look of the Sense Clock Widget, and certain skins for the SenseUI.
Click to expand...
Click to collapse
where in the build.prop do you edit the file?
nm found the line. it was obvious enough
FWIW 190 has been a good number for me. I was at 200 for awhile, set it at 190 today and it runs pretty well.
So I take it you aren't running Sense then? Because anything lower than 240 messed up the flip clock and some of the themes bar at the bottom.
I am sure I am not alone when I say this but does anybody know why the fonts on the screen are so massive? Was this phone originally intended for people with failing vision?
Why, with such a lot of real estate, doesn't htc squeeze in more info into the screen so that we lessen scrolling? Beats the hell out of me.... Its irritating to say the least. The net effect is that I have a bigger phone than the inc but I have exactly the same amount of info on the screen. I really do not see the point...
Rant over - now how do we lower font size and line spacing without messing everything up. Any easy fixes? In the uber z rom for the inc, gmichaelow made a zip that changed font sizes and line spacing to much lower levels without messing anything up. So its possible. LCD density is definitely not the answer.
khanam said:
I am sure I am not alone when I say this but does anybody know why the fonts on the screen are so massive? Was this phone originally intended for people with failing vision?
Why, with such a lot of real estate, doesn't htc squeeze in more info into the screen so that we lessen scrolling? Beats the hell out of me.... Its irritating to say the least. The net effect is that I have a bigger phone than the inc but I have exactly the same amount of info on the screen. I really do not see the point...
Rant over - now how do we lower font size and line spacing without messing everything up. Any easy fixes? In the uber z rom for the inc, gmichaelow made a zip that changed font sizes and line spacing to much lower levels without messing anything up. So its possible. LCD density is definitely not the answer.
Click to expand...
Click to collapse
I thought the exact same thing, my Droid has a higher resolution than the Thunderbolt (480x854 for OG Droid vs. 480x800 for Thunderbolt). Everything was blown up like crazy. I don't understand why they wouldn't have gone higher for a crisper look to rival the sleek look of the iPhone. There should be font packs out there, but I'm not sure where yet. Lowering my density to 190 definitely looks a lot better for everything but the notification bar icons. I'm going to look into smaller fonts as well, but for now, I'm happy with the lowered density, as it also makes things on screen look more crisp.
I've heard people talk about this in the past, but never fully understood what it did? Any explanation of what this actually does is appreciated. Thanks in advance
Just look at my picture compared to the stock setup. Mine is much crisper and smaller. It's like upping the resolution basically.
Chris Hansen said:
I thought the exact same thing, my Droid has a higher resolution than the Thunderbolt (480x854 for OG Droid vs. 480x800 for Thunderbolt). Everything was blown up like crazy. I don't understand why they wouldn't have gone higher for a crisper look to rival the sleek look of the iPhone. There should be font packs out there, but I'm not sure where yet. Lowering my density to 190 definitely looks a lot better for everything but the notification bar icons. I'm going to look into smaller fonts as well, but for now, I'm happy with the lowered density, as it also makes things on screen look more crisp.
Click to expand...
Click to collapse
Thanks. Will try this. Hopefully it does not mess any widgets.
Sent from my thunderbolt
Lcd density just hangs on my phone. I'm running storm. Anybody else manage to get it working on that rom?
Sent from my thunderbolt
Does anyone have themes out for specific lowered densities? I have found that when I lower the density, the bottom dock (Where the phone, app tray and personalize button are) looks disconnected and not very nice. Only thing holding me back.
Is there a way to keep with the stock launcher and theme it so it fits or would I be forced to switch to another launcher to alleviate that problem?
going to give this a try and see how it goees
i tried 225, 220, 210 and would rather just leave it at stock 240 than have blurry status bar icons...that drives me nuts and makes the phone look like ****..the rest of the screen looked perfect at 225 for me tho..
I run at 190. I used to run at 140 on my dinc. I hate big resolutions. I don't use the sense launcher so I don't have aproblem with it getting messed up
Sent from my ADR6400L using XDA Premium App
Even manually editing the build prop (CHMOD 777) I'm unable to get the changes to take effect. Any advice?
Gimpeh said:
Even manually editing the build prop (CHMOD 777) I'm unable to get the changes to take effect. Any advice?
Click to expand...
Click to collapse
Use root explorer, find build.prop, open it in a text editor, change the line that says LCD density. Save and exit, reboot. Done.
FatTony666 said:
Use root explorer, find build.prop, open it in a text editor, change the line that says LCD density. Save and exit, reboot. Done.
Click to expand...
Click to collapse
Yeah thats what I meant by manually changing the build prop.
Just curious now that we have had a good amount of time to mess with our NC tablets... What density did you settle on and why?
I am running the RC4 of CM7 and have tried 160, 161, 181, and 204 and still don't know which I like the best.
Did anyone find one they think worked the best for apps and also the looks of it and now have decided that you are going to keep it at a certain density from now on?
Just wondering what the masses are finding on it.
Where does one go to change the density on a cm7 build? I've heard this fixes some apps not fullscreening when downloaded from the market.
I prefer stock.. We have a high res screen (for its size), and we should use it that way. The icons look horrible at fisher price size... bleh. 160 for me.
I've learned to deal with the stock LCD density because I'm lazy, and don't want to change it every time I update. That being said, I've found that 210 not only looks good, but I could not replicate the market and app issues everyone was talking about. I personally like the larger objects, and being forced to have a limited amount of widgets and such makes the interface, honestly, minimalistic. If you do try that resolution out, please let me know if everything works as it should. I'm curious if it works for others.
I am on customized Nookie Froyo and using 200. The touch screen is smoother and responds better with 200. The larger icon is easier on my eyes. I switched back and forth between 160 and 200 for about three weeks. Finally settled on the 200.
Stock 161 for me.
for all the people having issues with densities, did they try disabling Compatibility mode?
i never had issues with Market, Maps, etc with changing LCD Density on any of my devices.
I use 160 on my Nook and 190 on my G2.
Faralon said:
Where does one go to change the density on a cm7 build? I've heard this fixes some apps not fullscreening when downloaded from the market.
Click to expand...
Click to collapse
I use LCD Density from the Market to change density on the fly. I go between 190 and 200 as a good compromise since I still use the stock ereader stuff but haven't made it permanent yet.
CM7 RC4 with density 204 here.
I've used 140 on every custom ROM I've installed... I still keep it minimalistic though with 2 or 3 widgets on a single home screen.
Faralon said:
Where does one go to change the density on a cm7 build? I've heard this fixes some apps not fullscreening when downloaded from the market.
Click to expand...
Click to collapse
I don't use an LCD Density app, I just edit /system/build.prop using RootExplorer's built-in text editor.
I hope someone knows the answer to this...
The DPI of the nook color is rated for 169dpi, yet the build.prop has it set to 161.
Changing it to the hardware correct value even solves some little graphics bugs. Like the "line on notification bar"
So why does it not match HW
Sent from my NookColor using Tapatalk
As explained by dal:
dalingrin said:
Note that lcd_density is an integer value only. Additionally, when using mdpi, 160 is the default lcd density. Any other lcd density with mdpi involves interpolation. If you compare 160 and 169.x you can see that the images used for icons are significantly more blurry at 169.
The reason I chose 161 instead of 160 was to workaround a Market bug that caused the my apps list to fail to load. In my limited testing it seems Market 2.3.4 may have fixed the issue. If so, I plan to switch back to 160 which has the best image quality and best app compatiblity with the exception of Google Maps. However, 160 will need more testing with the latest Market to make sure the "my apps" list is completely fixed.
Click to expand...
Click to collapse
dalingrin said:
The problem with densities greater than 160 is the interpolation that must happen. I just checked for good measure and the icons are definitely not as sharp. Additionally, you will see artifacts from the interpolation such as gradients on the Gingerbread keyboard and the notification drop down.
In my testing I saw no difference in font rendering.
Keep in mind that another motivation for moving to 160 is that afaik, all apps scale properly to full screen. Any deviation from the mdpi standard 160 causes some apps not to scale to full screen. An example is Google Reader. If you click on an article to read, it will give you a libwebcoreview but it does not scale to full screen at >160.
Click to expand...
Click to collapse
fmkaiba said:
I hope someone knows the answer to this...
The DPI of the nook color is rated for 169dpi, yet the build.prop has it set to 161.
Changing it to the hardware correct value even solves some little graphics bugs. Like the "line on notification bar"
So why does it not match HW
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
You can use 169. Despite what people think, 160 is the best value to use for the Nook. Anything other than 160 means extrapolation or interpolation must take place. This is why nearly every HDPI phone uses 240, not 231 or 248, despite their real world DPI. However, there is a bug in the Android Market @ 160 on tablet size screens. For now I have it set to 161 to get around that bug. I don't use 169 because icons and such are more blurry due to the extra extrapolation needed. Until Google fixes the market there isn't a good DPI for us to use. Each has its own problems, 161 has a line in the notification bar but sharp icons, 169 doesn't have a line in the notification bar but has blurry icons....etc
Dalingrin, are you aware of any ill effects from running lower DPIs, such as 140?
That's where I've had mine for months, and I love it. Then again, I'm also running at 1920x1080 on my 15" laptop.
I love this forum!
Thankyou for a clear and logical answer I couldn't get anywhere else!
Sent from my DROIDX using Tapatalk
Sorry for necrothreading, just wanted to point out that Market 2.3.6 (from gapps 0613) still has a problem with My Apps @160dpi. :/
Rodney
Has anyone else had a problem with Chaos Rings where it runs fine but the game does not run full screen and the text boxes for speech text are not aligned with the text and the characters and interactive items on the screen are out of place from the background when played on a Honeycomb tablet with a 7" screen with an LCD density of 120? If I change the density to 160 it displays fine, but that changes Honeycomb to look like Gingerbread and screws up the menus and everything else and I don't want to have to reboot the tablet every time I want to play the game. I know the game uses pre-rendered backgrounds and that's probably what's causing it, but I've scoured the Web for days and found no one else with this problem or a way to fix it. My Thunderbolt with Gingerbread runs it fine as well. Someone please help!
Sent from my Streak 7 using witchcraft
zenisnotchosen said:
Has anyone else had a problem with Chaos Rings where it runs fine but the game does not run full screen and the text boxes for speech text are not aligned with the text and the characters and interactive items on the screen are out of place from the background when played on a Honeycomb tablet with a 7" screen with an LCD density of 120? If I change the density to 160 it displays fine, but that changes Honeycomb to look like Gingerbread and screws up the menus and everything else and I don't want to have to reboot the tablet every time I want to play the game. I know the game uses pre-rendered backgrounds and that's probably what's causing it, but I've scoured the Web for days and found no one else with this problem or a way to fix it. My Thunderbolt with Gingerbread runs it fine as well. Someone please help!
Sent from my Streak 7 using witchcraft
Click to expand...
Click to collapse
How did you fix the alignment issue?
I didn't. I gave up after a while and I was only able to play it on my Thunderbolt.
The only way to fix it is to change the DPI of your tablet to 160dpi. It doesn't run on 120dpi tablet/smartphone.
btw: If you are going to change the dpi of your device, make sure that you change the resolution as well to match up the icon, 1020x600 is best for 160 dpi on wide screen devices.